5 ms·
Because the premise of this article is totally and utterly wrong. It says: > Whether a methodology works or not depends on the criteria: team productivity, hap
by crazygringo 4y ago
Because the premise of this article is totally and utterly wrong. It says:
> Whether a methodology works or not depends on the criteria: team productivity, happiness, retention, conformity, predictability, accountability, communication, lines per day, man-months, code quality, artifacts produced, etc. Every methodology works if you measure the right thing. But in terms of the only measurement that really matters—satisfying requirements on time and within budget—I haven’t seen any methodology deliver consistent results.
Asking a methodology to always meet requirements on time and within budget is asking for human perfection. You might as well expect it to deliver world peace and end hunger as we know it as well. So of course if you set a ludicrously unattainable goal, development methodologies all fail. In every project, unforeseen obstacles will always come up, which usually means some combination of scope-cutting or delaying or (occasionally) spending more.
But when teams are having major problems in delivering working code at all or at a reasonable pace, that's where different methodologies can absolutely improve the situation, depending on what's going wrong and what the desired product is. So obviously they do work in terms of adding value, when applied appropriately.
Let's not throw the baby out with the bathwater here.
- codingdave 4y agoAlso, even the concepts of "on time" and "within budget" have more or less meaning depending on your methodology and where your company is in its lifecycle. I tend to think of a working methodology as one that produces software that meets the customer's need in a way they are willing to pay for that is sufficient to fund the organization that builds and operates the product. But even that definition can be poked apart because it only accounts for self-sustaining companies, and many software startups do not have an intent to be that.
- commandlinefan 4y ago> Asking a methodology to always meet requirements on time and within budget I'm not quite sure what you're getting at here, because that's absolutely, positively 100% what the people who are recommending methodologies insist they're for and absolutely, positively 100% what the people who adopt them want them for. The ENTIRETY of software developer management is focused - beginning and ending - on meeting requirements on time and within budget. That's the ONLY thing they care about and their ONLY purpose for existing.
- shkkmo 4y agoMethodologies should help projects meet requirements on time and within budget, but expecting 100% success regardless of the project, experience of the team complexity of estimate and what not is completely unrealistic.
- alexgrover 4y agoIn my experience working with a well-known consultancy that uses strict XP, agile, TDD, the whole 9 yards - this isn’t the case at all. They talk about a triangle of (scope, quality, cost) where you can only pick 2. As a business you can choose what trade off you want to make, but no one’s promising that you can have a rocket ship by next week with 2 engineers if you just organize your tickets correctly.
- crazygringo 4y agoI mean I don't know what to tell you, but you're just completely wrong. Sure, that's what management would wish in an ideal world. But obviously that's not what these methodologies are even marketed as -- e.g. the entire purpose of agile/scrum is to break into sprints that have deliverables as goals but not as guarantees, in order to de-risk larger failures by exposing smaller failures earlier, to be able to then adjust requirements/timeline as you go. Heck, it's so important that they insist on estimating tasks in terms of abstract points instead of units of time. Methodologies attempt to give more accurate, less wishful-thinking, estimates of timelines/resources. And they're often quite successful at that with things like planning poker etc. But all they do is improve, they don't give guarantees.
- xiphias2 4y agoYou're totally right, but the main issue is that people don't even learn what the goal of agile / extreme programming is (it's a methology for engineers for giving data to managers to be able to take early decisions / manage the project while it's cheaper). It has taken over by managers to just be used for pressuring software engineers, that's why the name had to change so much.
- jdlshore 4y ago
- GTP 4y agoHes asking for "consistent results", not perfect results.