5 ms·
I don't think this bit is correct: > it was a well-defined methodology with proven effectiveness in areas like construction and manufacturing. If you look at
by wpietri 8y ago
I don't think this bit is correct:
> it was a well-defined methodology with proven effectiveness in areas like construction and manufacturing.
If you look at major construction projects, waterfall approaches don't have a great track record. E.g., the San Francisco Bay Bridge had enormous cost overruns: https://www.citylab.com/equity/2015/10/from-250-million-to-65-billion-the-bay-bridge-cost-overrun/410254/ https://www.citylab.com/equity/2015/10/from-250-million-to-6...
In contrast, the Empire State Building was not built with a waterfall approach. It was delivered on time and 18% under budget. I saw Mary Poppendieck, who has written some excellent books on software development, give a fantastic talk on it. There's a write-up of a related talk of hers here: https://chrisgagne.com/1255/mary-poppendiecks-the-tyranny-of-the-plan/ https://chrisgagne.com/1255/mary-poppendiecks-the-tyranny-of...
My belief is that the waterfall approach is common not because it's effective, but because it conforms to certain naive fantasies people -- especially powerful people -- have about projects. I think it's basically King Canute writ large. (Large, and into a zillion GANTT charts.)
I do agree that it's inappropriate for modern software projects. But I think this is also suspect:
> maybe a controller for a pacemaker
I've talked with a number of medical-device people, including Nancy van Schooenderwoert, who has been involved in the Agile world for at least a decade:
https://sdmdglobal.iqpc.co.uk/speakers/nancy-van-schooenderwoert https://sdmdglobal.iqpc.co.uk/speakers/nancy-van-schooenderw...
They believe that Agile approaches are way better even for life-critical systems. You do need much more rigorous testing, but given the way Agile approaches deliver core functionality early, you end up having way more time for that testing, and many more opportunities to discover ways to improve the testing approach.
- speedplane 8y ago> My belief is that the waterfall approach is common not because it's effective, but because it conforms to certain naive fantasies people -- especially powerful people -- have about projects. That is itself pretty naive. There is a reason why waterfall used to be popular, but it no longer is. Is it because people's ego's have ebbed? Doubtful. It's more likely that something else happened in the interim. The obvious change is the proliferation of instant communications. If communicating is hard and expensive, it often makes more sense to change things as little as possible. If it's easy, then change becomes less expensive. The internet gave us instant communication (e-mail, video conferencing, github, etc). Tools like these made agile more attractive. Humanity didn't just become enlightened.
- ascar 8y agoYou are overgeneralizing one (small) enabling factor of agile as the whole reason. Maybe based on your experience in major corps. Agile doesn't start at the corp level. It starts at the individual and team level (think scrum) and maybe penetrates to the large strategic decisions on a department/corp level. Communication is cheap for teams in the same room or even people in the same building. A far greater effect is the internet itself and software/services that is/are distributed through the internet. This made shipping new versions cheap, gave an abundant access to metrics and fast feedback cycles. Cheap shipping and fast feedback enable frequent iterations. When you had to burn your software to CD and mail it to the customer releasing minor updates multiple times a week or even just every few months was not an option. You also got far less feedback and had basically no usage metrics.
- speedplane 8y agoYou make some good points, but it still boils down to instant communication. Updating software quickly is difficult without internet. Getting feedback quickly and cheaply also isn't. So you're right that agile isn't just enabled by instant communication among developers, but I still think it's enabled by fast communication generally, including to and from the end-user.
- AstralStorm 8y agoNot true at all. It is not about instant communication but about transparency and bug reporting tools. In the past, you got an app and you were lucky if the dev provided a marketing phone number for a drone to talk to. (Here is where IBM and such made bank, they did actual on site support.) Or perhaps an email address that was read manually in a year. Nowadays, a crash is automatically detected and loses some send feedback going is included in many apps for additional reports, preferably landing in a CRM directly accessed by consumers. The one problem left to tackle is marketing selling things that are not ready nor even tried out.
- varjag 8y ago
- timoth3y 8y agoThat's a fascinating article on the construction of the Empire State Building. Thanks for sharing it. However, what the article describes is fundamentally a waterfall methodology. The innovative part was breaking the large project into several overlapping stages of parallel projects, but the project management was still much more waterfall than agile. The waterfall methodology is not a product of "naive fantasies" but of business realities. In many cases changing the plan after you get started is phenomenally expensive. AN agile approach of building three stories and then deciding you want to try a different support structure or to add another sub-basement would be absurd. We all have a natural bias to assume that people in the past were foolish for not doing things the way we do, but for the most part, they were every bit as smart as we are and were making perfectly rational decisions. In terms of the pacemaker example, I've never built one myself, but I suspect that the constraints are not only the need for additional testing but that the functionality and hardware itself would require regulatory approval, and so a waterfall approach to the project might make a lot of sense. The developers could, of course, use an Agile or iterative approach to deliver on those requirements, but I think a waterfall approach might be a better fit for the overall project.
- ealexhudson 8y agoI don't believe the pacemaker example is necessarily a great one. In order to meet the risk-mitigation requirements for device approval, you have to document the design and the various decisions that led you to that point. If you're working in an agile fashion, you end up documenting a bunch of stuff that isn't in the product and doesn't get used, and at best your technical file is going to be much bigger than it needs to be (at worst, you confuse the assessor and don't get approval). That's not to say you can't use agile methods, but I think the sensible way would be to use agile to explore the solution space and learn what to build, but continue using a formal methodology in parallel construction to document the development of the device.
- endymi0n 8y agoWell, at least _some_ aspects of a 50k feet Waterfall are not avoidable in any construction project, as you can‘t redo parts of the foundation when you‘re building the 50th floor. Something that works quite in the same way (not as strongly, but still significantly so) in software by the way is re-modelling of the underlying entity schema. Which by the way is my favorite beef with process-driven agile methods and why I‘m leading my projects with an initial phase of data model and UX sessions until it‘s exactly clear _what_ needs to be built and _how_. Only then does it make sense to build any working code IMHO. Scrum and friends come with a complete disregard for distinguishing the stuff that‘s easy to change later on vs. the parts that are not.
- tomnipotent 8y agoYou should spend 30 minutes talking with a project coordinator for any construction job and you'll change your mind. My company recently opened its first retail store in a new Caruso mall, and it was a considerably eye-opening experience. The pace (and cost) is frustrating, but the end result is generally fantastic and that's more than I can say for most software projects. Even for a simple job, the number of things that need to align to allow for a dump truck to deliver gravel to a construction site is non-trivial. Along with permits and what times the truck can arrive depending on whatever bureaucratic bullshit is at play, you also need to make sure the rest of the crew is in place to receive the delivery and put it to use. Don't forget about the things that need to be done even before the gravel can be delivered, and things dependent on the delivery that begin on that task is complete. This isn't a software project. A simple truck delivery being late can require dozens of people to get involved to reschedule everything else that needed to come after it - this is non-trivial, expensive, and can impact hundreds of people depending on how much the schedule slips since we often dealing with hourly labor. "But it's only changing one delivery" you say? The delivery was probably handled by a contractor, which has other clients and other responsibilities and may not be able to reschedule when it's convenient for you. Multiply this by every contractor or 3rd party you're working with and suddenly Metcalfe's law is punching you in the face. The waterfall approach exists because it works - on average - considerably better than everything else that's been tried before it, regardless of whatever cosmic forces we think are at play.
- gowld 8y agoYou claim that the date and time for the glass delivery for the windows is fixed before the diggers start hauling dirt to make room for the foundation? That a construction isn't constantly scrambling to cover expected-unexpected incidents like a machine breakdown or shortstaff or a contractor screwup?
- tomnipotent 8y agoNot fixed, but date slippage is much more impactful in these classes of projects compared to software. > That a construction isn't constantly scrambling to cover expected-unexpected incidents like a machine breakdown or shortstaff or a contractor screwup They are, but thanks to great tooling and process they've been able to deal with it pretty well all things considered.