The "Plot Twist" angle

------------------------------------------------------------------------------------------------------------------------------------

There are few things more ironic than watching Agile turn back into Waterfall.

After managing ~90 projects and programs per year in an IT portfolio, I've seen almost every "Agile transformation" playbook.

Same pattern every time:

And yet… delivery slows down.

Why?

Because somewhere above your beautiful two-week sprints, a CFO is sitting at a spreadsheet doing a very Waterfall thing: approving an annual budget.

Your team ships in quarters. Finance plans in fiscal years. And somewhere in a risk register nobody reads, a contingency budget is quietly held back "just in case", which means the money only flows when the year (or the deadline) is almost over.

But it's not just the money.

It's the deadlines too.

In portfolio planning, every project gets a delivery window, because projects don't exist in a vacuum and resources have to be aligned on a multi year project roadmap. They exist to support something. A product launch. A market entry. A regulatory deadline.

The new product goes live in October? Then the cybersecurity project must be done by September. Not "done enough." Done.

Suddenly your "Agile" cybersecurity team isn't prioritizing based on risk or value anymore. They're prioritizing based on a date that was set in a portfolio spreadsheet eight months ago — before anyone wrote a single user story.

The budget flows down like a waterfall. The deadline flows down like a waterfall. The scope follows quietly behind.

Congrats. Your Agile project just became a Waterfall project in a hoodie.

Real agility isn't a framework. It's what happens when funding, decisions, and delivery all move at the same speed.

Everything else is just stand-ups with extra steps.