4 ms·
> I think one of the biggest problems with Agile is that everybody thinks it's okay to operate without a specification of what is to be built. On small teams th
by lmm 8y ago
> I think one of the biggest problems with Agile is that everybody thinks it's okay to operate without a specification of what is to be built. On small teams this might be marginally possible but still difficult - on largers ones (> 5 people) leads to madness and failed projects.
I'd say that the biggest failures I've seen have been due to having a specification, and the bigger the project the more important it is not to have one.
As the quote goes: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works and cannot be patched up to make it work. You have to start over, beginning with a working simple system.
You can, and should, have specifications for the next ~two weeks of changes that you want to do. These should be verifiable at a user-facing level. But after that you iterate. Trying to specify further in advance or at more detail than what's user-visible is a recipe for disaster.
- andy_ppp 8y ago> You can, and should, have specifications for the next ~two weeks of changes that you want to do. We completely agree here - are you saying you've never encountered the "we're agile, no need for specs" mindset?
- lmm 8y agoI've encountered it and not found it to be a problem - if you have good access to someone who can answer questions during development then that's better than a spec. Even without that, as long as you're keeping your iterations short and demoing at the end of them then the worst case is you get things wrong for two weeks and then correct them after. I've found the "we're "agile" but going to have a huge up-front spec" mindset far far more damaging.
- shadowtree 8y ago"A complex system designed from scratch never works". And yet we flew to the moon. And have airplanes, and and and. A lot of agile is just an excuse for software "engineering" being in the throw shit at the wall and see what sticks stage of evolution. Construction went through the same, software has freemasons now. But no engineering whatsoever. Example: People still write their own date conversions (and fuck it up).
- lmm 8y ago> And yet we flew to the moon. And have airplanes, and and and. We do, but not by designing from scratch. We achieved those things by incrementally extending existing designs and verifying that the newer, more complex designs had the desired properties. > A lot of agile is just an excuse for software "engineering" being in the throw shit at the wall and see what sticks stage of evolution. Construction went through the same, software has freemasons now. But no engineering whatsoever. The constraints that apply to software are very different from those that apply to construction. What if "throw shit at the wall and see what sticks" really is a better way of making software than "engineering"? > Example: People still write their own date conversions (and fuck it up). Indeed they do. Do you find this is more common in projects that specify and design up front or in projects that don't?
- igouy 8y ago> What if "throw shit at the wall and see what sticks" really is a better way of making software than "engineering"? What if it isn't.
- lmm 8y agoIf it isn't, then maybe agile is a bad idea and we should expect to see agile projects fail more often/expensively than non-agile projects. But that's not what we see (at least not what I've seen).
- andy_ppp 8y agoThe people making the planes made meticulous changes to the design before anything was built so I really don't think your point is supported by aeroplane manufacturers. The builders weren't just told make it faster and more fuel efficient and to get on with building it.
- deleted 8y ago[deleted]
- Jtsummers 8y agoThose weren't designed "from scratch", start-to-finish, with no testing or prototyping along the way. The Wright Brothers developed a wind tunnel and many models on their way to first flight. Same concept for getting to the moon. Those large scale projects were not done in a Waterfall fashion, they were done iteratively with models/simulations/prototypes produced along the way.