4 ms·
If you wanted to do some home renovations and somebody told you they had no idea how much it would cost to do until they started working on it, you might be unc
by mindcrime 11y ago
If you wanted to do some home renovations and somebody told you they had no idea how much it would cost to do until they started working on it, you might be uncomfortable.
Right and this why I say that so many people are (intentionally or not) misunderstanding what "agile" means, and selling something else using that label. Look at what the Agile Manifesto actually says about plans / planning and what not:
Through this work we have come to value:
...
Responding to change over following a plan
...
That is, while there is value in the items on
the right, we value the items on the left more
So, all those people out there acting like "being agile" justifies operating with no plan at all, are NOT really in alignment with the core principles of agile. Agile does not prescribe "no planning" and never has. What this was all in reaction to, was the idea of BDUF (Big Design Up Front) and the concept of spending huge amounts of time building models and creating artifacts which, in and of themselves, delivered no value to the customer - and furthermore, were likely to be changed anyway.
If "agile has failed" is really true, then here's the one place where it probably failed: It was never prescriptive enough. Which might seem paradoxical, but the problem is, the AM is subjective enough that people could find justification for whatever bullshit ideas they came up with, in the Manifesto. :-(
- vonmoltke 11y agoHaving dealt with US Federal Government customers and multi-year projects, I think the issue is that it gets really hard to provide an accurate cost and time estimate for the whole project without a BDUF, at least once a project gets beyond a certain size. This is especially true when the project is just a piece of a larger product and needs to coordinate with other subprojects. It may be that agile is just not appropriate for such projects, in which case I wish companies and customers would stop trying to force-fit them.
- TheCoelacanth 11y agoIt's really hard to provide an accurate cost and time estimate even with a BDUF.
- emodendroket 11y agoTrue enough, but I guess the question is whether agile processes help or hurt.
- mindcrime 11y agoThe difference, as I see it, is this: In a "BDUF" / "not agile" environment, the customer expects a rigorous change control process, and that serves to protect the developers when the customer starts changing things around. In an environment marketed as "agile" it became received wisdom that you don't do "change control" because it "isn't agile". So while the agile process (Scrum or what have you) was designed to manage the change in requirements from the developers' point of view, we seemed to get away from the thing that forced the customer to update their view of things, when changing requirements midstream.
- emodendroket 11y agoI guess it depends what people mean by agile, because I've seen some people talking about agile means it's impossible to say roughly how much time work will take without starting out which seems odd.
- emodendroket 11y agoMy favorite variant on this is combining "agile" with no design or requirements up-front with a rigid change request process at the end.
- mindcrime 11y agoMy favorite variant on this is combining "agile" with no design or requirements up-front with a rigid change request process at the end. The thing is, a certain measure of "change control" was always a good idea, even in an "agile" environment. My (admittedly subjective) take is that getting away from change control contributed to everyone's mindset shifting to where "changes are free".
- emodendroket 11y agoWell, in the project I saw this happen on they also stopped the requirements gathering process for an agile process where they promised to implement changes when it didn't match the process well, so it was kind of a bait-and-switch technique.