Project Management

Please login or join to subscribe to this thread

Agile teams vs. Predictive executives: How do you survive the "Hybrid" middle?

linkedin twitter facebook   Agile   Disciplined Agile   Knowledge Management  
avatar
Francisco Herrera
Community Champion
Program Manager, PPM&PMO Specialist.| Coppel, Mexico. Culiacán, Sinaloa, Mexico

Colleagues, many of us are currently working in "hybrid" environments. In my experience, this often means that the project team is trying to work using an Agile approach (short iterations, flexibility, adapting to change), but the executive sponsors still expect Predictive governance (fixed budgets, exact delivery dates, and detailed Gantt charts).

This puts the Project Manager right in the middle, having to constantly translate between two completely different languages and mindsets.

My questions for the community are:

How do you manage executive expectations when they demand a fixed, guaranteed delivery date from an agile or iterative team?

What kind of reports or metrics do you use to satisfy leadership without forcing your team to abandon their agile practices?

I would love to hear your strategies for bridging this gap!

Francisco

Sort By:
< 1 2 >
avatar
Francisco Herrera
Community Champion
Program Manager, PPM&PMO Specialist.| Coppel, Mexico. Culiacán, Sinaloa, Mexico
Sep 18, 2026 5:50 PM
Replying to David Portas
...
Hi Francisco. In concur with the good answers from Luis and Natalie.

I expect nearly every piece of work requires some element of fixed deadlines and budgets. The best way to meet fixed deadlines and budgets in my experience (software, cloud, data engineering) is to take a highly agile approach: iterative/continuous delivery with value-based prioritisation, ongoing testing and governance, while regularly seeking and acting on user feedback. It's the most reliable way to control delivery risk and get results. I would question why such an approach would ever need to be called "hybrid". That's a bit of a weasel word in my opinion - at least when applied in the field of software and data tech.
David Portas yes a strong Agile approach is actually the best risk management tool for hitting fixed deadlines, simply by flexing the scope instead of the timeline. In software and data, what many organizations label as "hybrid" is often just Agile functioning exactly as it should—delivering the highest priority value within a strict funding envelope.

When you use this continuous delivery approach to meet a fixed deadline, how do you handle the conversation with executives when they realize that not every originally requested feature will make the cut?
Francisco
avatar
Francisco Herrera
Community Champion
Program Manager, PPM&PMO Specialist.| Coppel, Mexico. Culiacán, Sinaloa, Mexico
Sep 20, 2026 12:05 AM
Replying to Lissette Indhira Pimentel Sosa
...
I try to separate the target date from the certainty around the scope. We can work toward a specific date, but if the team is expected to adapt as we learn, then we need some flexibility in what will be delivered by that date.
I also prefer discussing that trade-off early. A fixed date, fixed scope, and changing priorities at the same time usually create expectations the team cannot realistically manage.
Lissette the combination of a fixed date, fixed scope, and changing priorities is the classic recipe for project burnout and failure.

Having that trade-off conversation early is crucial to protect the team and set realistic expectations. As you mentioned, if we want the flexibility to adapt and learn, the scope must remain the variable.

How do you typically frame that initial conversation with a sponsor who insists on locking in both the timeline and the full scope from day one?
Francisco
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Don't compromise yourself. You are all you've got."

- Janis Joplin

ADVERTISEMENT

Sponsors