5 ms·
How to Measure Progress in a Software Project – By Adam Ard
- avg_dev 2y agowhile i have only ever worked at places that do some form of agile development, sometimes i think about things that are just foundational elements. to be pedantic, they definitely work. they just, on their own, do not provide any utility. just a means to facilitate things to be constructed later on in development. in particular i think of Black Triangles https://rampantgames.com/blog/?p=7745 https://rampantgames.com/blog/?p=7745 which has been discussed here previously.
- VyseofArcadia 2y agoI would like to hire you to come read this to my PM daily until he gets it.
- wilkystyle 2y agoWhile I loathe the useless abstraction layer that is story points and while I generally agree with all of the points in articles like these, they almost never talk about the other side of the coin, which is the need for predictability. Predictability is the oil that makes nearly every software business run efficiently and smoothly. It affects everything from software development to product roadmap to financial efficiency and profitability. Startups need to know if they have the ability to implement critical functionality before they're out of runway; big companies need to be able to coordinate product development, contracts, delivery dates, product launches across many disparate teams with interconnecting dependencies. Even deciding whether or not something is a roadmap priority requires some concept of how quickly you can implement it. So yes, productivity theater, as it exists in many project management processes today is unnecessary overhead and wasted time/money. But unless you are id software in the late 90s—flush with cash and sitting on a couple of products that only you can bring to market—you can't rely on "it'll be done when it's done" or "you'll know when it's ready when you see it" and expect to remain competitive for long. EDIT: Mobile typos.
- pestaa 2y agoAgile is not "it's done when it's done". Agile is "it makes sense every day of the week, we should talk often".
- intelVISA 2y agoAgile's one of the best things to happen to software in a way: it's good to know your competitors are stuck in ceremonies, arguing over story points.
- loloquwowndueo 2y agoLooks like you’re talking about Scrum. Ceremonies and story points aren’t in any way mandated by the Agile manifesto.
- yihtserns 2y agoThere is no "ceremonies" nor "story points" in the Scrum Guide. Perhaps you are referring to "Fake Scrum".
- loloquwowndueo 2y agoDaily scrum, sprint planning, retrospective and review are ceremonies, and they are totally mentioned in the guide. The guide also mentions the backlog refinement: “ This is an ongoing activity to add details, such as a description, order, and size.” It’s true that scrum doesn’t directly mention story points but tell me whether story points or t-shirt sizing aren’t the two most common ways to size a story.
- yihtserns 2y ago> Daily scrum, sprint planning, retrospective and review are ceremonies, and they are totally mentioned in the guide. Those are "Events", activities to support development work. Unless you mean programming, testing, discussions, code reviews, etc are ceremonies as well? > It’s true that scrum doesn’t directly mention story points but tell me whether story points or t-shirt sizing aren’t the two most common ways to size a story. Borrowing your own words: "...story points aren’t in any way mandated by the..." Scrum Guide.
- joshdavham 2y agoThis was interesting to read as a more "junior" software dev. Aside from Agile, what are other common frameworks that people use, if any?
- cricketlover 2y agothere's kanban
- kylestlb 2y agoAgile isn't a framework, it's just a set of principles. Scrum is a loose framework theoretically based off of those principles with some ground rules that can be broken depending on what works for your team. Same with Kanban.
- smokel 2y agoThe "waterfall" way of working still has some merit. Think first, then make a design, and a planning based on that, and then implement the fucking owl. Unfortunately, a lot of unforeseen problems show up during the implementation phase, and people blame the waterfall model for not being flexible (agile) enough to address these. Now, even more unfortunately, some people interpret agile as not needing to spend time upfront thinking and dive into the implementation straight away, creating an even bigger mess than the waterfall generation could have ever imagined.
- exe34 2y ago> Unfortunately, a lot of unforeseen problems show up during the implementation phase, and people blame the waterfall model for not being flexible (agile) enough to address these. my experience is that people spend half the time bikeshedding the obvious problems that waterfall would have identified in much less time, and then still hit the unforeseeable problems after implementation anyway. if they could have been foreseen, they would have been rolled into waterfall.
- beryilma 2y agoExtreme Programming used to be a thing. Pair programming and all that... Not so much anymore.
- bwghughes-fth 2y agoIt’s not about like or dislike - it should have value in the context for which it’s designed. There are an unlimited amount of ways to do this. Validation in the context of the recipient of the value is the only thing that matters.
- PromptCoding 2y ago[dead]
- groby_b 2y agoThere's no point in measuring progress if you don't have a defined end point. And if you have a defined endpoint, you will get the "is it far? Are we there yet?" question. For good reasons. Maybe your software needs to hit at a certain point, or a lot of money will be losts (ask e-commerce folks about Black Friday). That means you'll need to try to course correct as soon as possible if you take the wrong road - "IDK, but we made progress in the last two weeks" isn't helping. Maybe your software needs a marketing push. The buy for that is months ahead of when it happens. You better know if you can make that date. Maybe other teams depend on you delivering working software at a certain point. "We make progress every sprint" is a nice feeling. It doesn't help you in any of those situations. Especially large-scale efforts need some planning and estimation to work out.
- hinkley 2y agoWe have all collectively forgotten that the main purpose of the burndown chart was to teach upper management about the wages of scope creep and vague requirements. They've taken our paddle and are spanking us with it.
- epalm 2y agoI like this mentality, truly, makes perfect sense. Check in often to make sure you’re building the right thing. Keep going until it’s done. However, the client is going to want to know (A) how much it’s going to cost, and (B) how long it’s going to take. These are extremely reasonable questions in most cases/industries. To answer these questions with a shrug is a nonstarter. The client is working with a time budget and a financial budget, and they need to have some sense of the numbers. If the Waterfall and Agile methods are opposite ends of a spectrum, somewhere in between is where I’ve found an acceptable middle ground for both developers and clients.
- ozim 2y agoProblem is that you can budget time/cost of endeavors that were already done. If you are doing R&D that is not something you can budget because definition of research is you don't really know what you are searching for - well you have to have some reasonable idea of course but if $20k becomes suddenly $50k that should not be a surprise for R&D. People might say "but the CRUD app you are building is not real R&D" if you are really building a CRUD app that is like an existing one - setup Wordpress, SAP, Shopify or pick from dozens of existing ones and be done with it. All else is R&D because there is more unknowns than known stuff, there are always integrations with 3rd parties, some workflows that need implementations etc. . Even building a piece of road - well all tech is there - can end up running over time/budget if for example you find terrain under is not as one expected and it sinks or something and you have to figure out how best to deal with that and there is no expert to deal with that specific type of ground you ran into.
- fvdessen 2y agoDo you rewrite your auth system to modern standards or migrate your infra to k8s ? Some projects take months to complete and don’t deliver value until fully done, so it is valuable to spend some time to do some upfront planning to weigh your options
- dingosity 2y agoHmm... doesn't really offer a suggestion for measuring progress. FWIW, in our dev team, we don't talk about "percent done," but say "percentage of unit tests that pass without mockups" and then "percentage of requirements covered by unit tests." The first measure is pretty easy to quantify, but the second is where ambiguity and guesswork creeps in.
- madrox 2y agoWhen I got my first EM job in 2011, implementing true agile was the dream. I became a zealot to every PM or business leader that came my way. I insisted that not only would we get more done, but we'd get better quality stuff. It was a beautiful dream. I wouldn't say my idealism failed all at once, but through death by a thousand cuts. There are lots of scenarios where trying to bootstrap development into agile is simply more difficult without any clear gain...at least when it comes to principles around measuring progress. In all my time in the industry, I've never met someone who lived true agile for more than a year that wasn't in a very small startup.