3 ms·
Waterfall is still quite popular, just under different names. Most of the "agile" projects I come across are really mini-waterfall. And some supposedly agile pr
by wpietri 8y ago
Waterfall is still quite popular, just under different names. Most of the "agile" projects I come across are really mini-waterfall. And some supposedly agile processes, like SAFe, don't even really qualify as "mini". The main difference is that some Agile labels and rituals have adopted. But there are still large deliverables whose plans are completed in advance of production beginning. Delivery is heavily or entirely weighted toward the end, with no expectation of iteration or product improvement based on early release. The major difference with the waterfall of yore is that the chunk size is not 18-36 months, but more 2-4 months.
In contrast, modern Agile shops release early and often, with product choices for an initiative being informed by the real-world data generated by actual use. As an example, last I did a startup, our team of 6 was releasing a few times per day. The product manager would have an idea, find the minimum essence of it, and we would build and release that. User tests and live user data would quickly tell us whether the experiment pointed in the right direction; we'd then either double down on our bet and build a little more or we'd change direction. The average cycle time between having an idea and testing it was under a week for us. In mini-waterfall shops, that number is generally months.
The reason the 18-36-month version of waterfall died out was not modern communication tools. When my dad was a developer in the 70s and 80s, you had nothing like remote work. There was a special room that the computer was in, and everybody had directly connected terminals in an office they went to every day. Some places were pure waterfall. A few were doing what we'd now call Agile, releasing new software every few days and seeing how it helped.
From the way my dad tells it, the difference in the waterfall and non-waterfall shops was the extent to which executives preferred a sense of ultimate control over trusting expert staff. I agree that hasn't changed. What did change to force many companies to a shorter cycle was the change in expectations created by the rise of the internet. 18 months seemed a very long time on the web. (Although as late as 2004, I knew about one prominent brand name that did annual releases for their website.) So you'll see that consumer software now comes in smaller chunk sizes. That's sometimes true in the enterprise context and sometimes isn't. I know of 18-24-month projects at large, traditional organizations with controlling executives, captive user bases, and low-competition business environments.
So waterfall hasn't gone away entirely; it may have gotten a facelift and been forced to retreat to the margins, but it's still definitely there.
- speedplane 8y ago> the difference in the waterfall and non-waterfall shops was the extent to which executives preferred a sense of ultimate control So you're saying that the reason shops have moved to agile is because executives have changed their psychology and are now far more comfortable with relinquishing control than in the past? Hard to accept. What's much easier to accept is that communication tools have reduced the cost of changing specs and building consensus, allowing the same number of people to make far more changes in the same amount of time with the same amount of effort. The incentives of an executive (or generally, of a human) haven't changed for a few thousand years.
- wpietri 8y ago> So you're saying that the reason shops have moved to agile is because executives have changed their psychology and are now far more comfortable with relinquishing control than in the past? I am explicitly not saying that. In fact, the very next sentence from the one you quote is agreeing that the variation in psychology has not changed. If you finish reading that paragraph, you'll see I'm saying what changed is consumer expectation given the rise of the Internet. People were ok with new versions every 18 months when they had to come in the mail and be manually installed. But the web got people used to frequent improvements and fast responsiveness. This caused pressure on executives to shift at least to mini-waterfall. That change in expectations has differing impact based on the industry, and how much executives are isolated from that. Large companies with captive customers can more easily get away with longer waterfall processes, especially when the product is for an internal audience that can't switch tools. Startups and consumer-focused products tend to feel the pressure more, and so stick with much shorter cycles, some of them even doing what I'd consider true Agile. So in sum, I'm saying some shops became Agile and many more just went to mini-waterfall with Scrum labels, the variation being partly due to the existing psychological and cultural variation, but mainly due to the extent to which customers and/or users demanded more responsiveness.