Is there a "Modern Waterfall" rising in the new landscape of software development, or am I misunderstanding?

I wrote a post about it:
https://davidvujic.blogspot.com/2026/03/agile-agentic-engineering.html

#agenticengineering #ai #softwaredevelopment #agile

Agile & Agentic Engineering

Don't fall into a waterfall-style of software development. It's a trap.

@davidvujic Interesting. I think that big planning is "coming back", or makes more sense now, since the speed of execution has gone up in recent years. And with agentic coding, planning is a need; the agents do not know what to make without a plan.

At my work, we do scrum, but looking at the bigger picture, the product/UX, marketing, and sales teams have done a month or two of planning before the development team starts working. Then we do two weeks of work, then demo and retro. Adjustment happens during development, and you could argue that's what makes it agile. But we still have a big planning phase. It all looks a bit like a waterfall of smaller waterfalls.

I don't think big planning is an issue. I think the execution matters more. If management throws two months' worth of work into a pile and then lets the developers fight it out, bad things happen. Going agile when executing will make big planning a success.

@hugo I have the opposite experience and hope big planning isn't making its big comeback 😁

@davidvujic Maybe it will be a different kind of big planning coming. I see two kinds of planning:

1) Planning of how to execute - that's the bad kind of planning when done on a big scale. The waterfall kind.

2) Planning what to execute - that's the kind of big planning I see coming.

Maybe some will be doing both or a strange mix of both into some monster plan 👹 that is doomed to fail 🙀

I once heard a Navy Admiral call number 2 for the "In command, but out of control" kind of operation. You leave the execution up to the experts.