A software engineer was not involved in this if waterfall is painted positively.
I think the last time I heard an engineer unironically advocating for a waterfall IRL was about a decade ago and they were the one of the crab-in-a-bucket, I-refuse-to-learn-anything-new types—with that being the very obvious motivation for their push-back.
I know several who preferred waterfall, but the system I work on is a giant government one and when we were doing waterfall we were in specialist teams working on a small part of the system
At the same time we went agile management also said “everyone can do everything” so we’ve had to work across the entire system
For the rocket analogy: we started building a rocket under waterfall, but when we went agile we also decided that the rocket motor specialists could also work on fuel tanks and heat shields
A software engineer was not involved in this if waterfall is painted positively.
I think the last time I heard an engineer unironically advocating for a waterfall IRL was about a decade ago and they were the one of the crab-in-a-bucket, I-refuse-to-learn-anything-new types—with that being the very obvious motivation for their push-back.
I know several who preferred waterfall, but the system I work on is a giant government one and when we were doing waterfall we were in specialist teams working on a small part of the system
At the same time we went agile management also said “everyone can do everything” so we’ve had to work across the entire system
For the rocket analogy: we started building a rocket under waterfall, but when we went agile we also decided that the rocket motor specialists could also work on fuel tanks and heat shields
Yeah. It’s wild!
Waterfall has been a negative term in software from it’s very first use in software.
Waterfall: Spend 10 years compiling written functional and technical requirements. Cancel the program due to budget overrun.