Program Manager, PPM&PMO Specialist.| Coppel, Mexico.Culiacán, Sinaloa, Mexico
Nowadays, many organizations claim to work in "Hybrid" environments, trying to combine the financial security of predictive methods with the flexibility of Agile.
However, in practice, we often see projects that start with fixed scopes, rigid budgets, and strict deadlines set by upper management. The execution team simply holds daily meetings and divides the work into "sprints" without any real capacity to adapt or prioritize based on value. Basically, it just becomes "Agile theater" or Waterfall with a different name.
My question for the group is:
What strategies have actually worked for you to manage sponsors who want the flexibility of Agile, but still demand the absolute certainty of a predictive approach from day one?
I would love to read your experiences and solutions!
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Francisco, I believe it really depends on the nature of the project, the phase of the project, and the level of uncertainty involved. Hybrid project management should not mean simply combining Agile ceremonies with a traditional Waterfall framework. It should mean selecting the most appropriate management approach for different aspects of the project.
For example, in our construction projects, we often use a hybrid approach in which the design phase is managed more adaptively, allowing for iterations, collaboration, feedback, and refinement as requirements evolve. However, once we move into construction execution, the approach becomes much more predictive, given the importance of contractual commitments, cost and schedule control, procurement lead times, construction sequencing, and coordination among multiple trades and stakeholders.
At the same time, we incorporate Lean Construction principles and practices, such as lookahead planning, constraint identification and removal, advance procurement planning, and collaborative short-term production planning, to improve workflow reliability and respond to emerging issues before they affect the overall project.
In my view, the key to managing sponsor expectations is not to promise absolute certainty from day one, but to establish clear boundaries around what can and cannot be known at each stage. Sponsors can have visibility into the overall budget, schedule, major milestones, and key risks without requiring every detail to be fixed before sufficient information is available.
For instance, we can establish a baseline for the overall project while allowing design solutions to evolve within agreed cost, schedule, and performance parameters. As uncertainty decreases and design maturity increases, commitments become progressively more detailed and reliable.
Ultimately, I believe a successful hybrid approach is about being predictive where predictability is necessary, adaptive where learning and change add value, and disciplined about managing the interfaces between the two. Otherwise, like you said, we risk creating Agile theater rather than genuinely benefiting from either approach.
...
1 reply by Francisco Herrera
Oct 19, 2026 7:17 PM
Francisco Herrera
...
Rami yes using an adaptive approach for design and a predictive one for execution makes perfect sense. I agree with your strategy of setting clear boundaries around uncertainty rather than promising absolute certainty from day one. This progressive approach keeps sponsors informed without forcing a rigid plan too early, which is exactly how we can avoid "Agile theater". Francisco.
Program Manager| HARPER SRLSanto Domingo / Distrito Nacional, Dominican Republic
Making the trade-offs clear from the beginning. If the sponsor needs a fixed budget or delivery date, then we need to discuss where flexibility will exist, especially around scope and priorities. I also try to establish regular checkpoints where we review what has changed and what decisions need to be made. The challenge is when sponsors expect teams to adapt continuously but still hold them accountable to every original commitment, even when the conditions have changed.
...
1 reply by Francisco Herrera
Oct 28, 2026 2:40 PM
Francisco Herrera
...
Yes the expectation of having 'agile flexibility' but 'waterfall accountability' is a very common trap. Setting clear trade-offs from day one is essential. Your strategy of using regular checkpoints is a great way to manage expectations and remind the sponsor that every new change will impact the original plan. Francisco.
I think the real challenge is helping sponsors distinguish between certainty of outcomes and certainty of the plan. You can set clear budget boundaries, business objectives, and decision points upfront without pretending every requirement will remain unchanged.
What has worked well is agreeing on what is fixed and what can evolve. Keep the budget and strategic goals defined, but allow the team to reprioritize scope as they learn more. Regular reviews should focus on progress, risks, and the value being delivered rather than simply checking whether the team followed the original plan.
The key is making flexibility visible and accountable, so sponsors see it as informed decision-making rather than a loss of control.
...
1 reply by Francisco Herrera
Oct 30, 2026 12:31 PM
Francisco Herrera
...
Yes Sandeep separating the certainty of outcomes from the certainty of the plan is a crucial distinction. When sponsors understand that budgets and strategic goals remain fixed while the scope adapts, they become much more comfortable with change. Framing this flexibility as an accountable, visible process is an excellent way to maintain their trust without sacrificing team agility. Francisco.
I can only speak for my field of experience: information technology projects. "Hybrid" is basically an illusion. That word is rarely well defined but it seems to mean only better planning/phasing/governance. But you can have excellent planning, phasing and governance while being agile - why would doing those things make you "hybrid"?
Nothing wrong with scope, budgets and deadlines of course but if you are failing to validate as you progress, not seeking feedback and not responding to the evidence of testing or to changing needs then you are simply failing. Calling a way of working "hybrid" shouldn't be used as a cover for failing to be agile. Saving Changes...
Program Manager, PPM&PMO Specialist.| Coppel, Mexico.Culiacán, Sinaloa, Mexico
Oct 12, 2026 2:31 PM
Replying to Rami Kaibni
...
Francisco, I believe it really depends on the nature of the project, the phase of the project, and the level of uncertainty involved. Hybrid project management should not mean simply combining Agile ceremonies with a traditional Waterfall framework. It should mean selecting the most appropriate management approach for different aspects of the project.
For example, in our construction projects, we often use a hybrid approach in which the design phase is managed more adaptively, allowing for iterations, collaboration, feedback, and refinement as requirements evolve. However, once we move into construction execution, the approach becomes much more predictive, given the importance of contractual commitments, cost and schedule control, procurement lead times, construction sequencing, and coordination among multiple trades and stakeholders.
At the same time, we incorporate Lean Construction principles and practices, such as lookahead planning, constraint identification and removal, advance procurement planning, and collaborative short-term production planning, to improve workflow reliability and respond to emerging issues before they affect the overall project.
In my view, the key to managing sponsor expectations is not to promise absolute certainty from day one, but to establish clear boundaries around what can and cannot be known at each stage. Sponsors can have visibility into the overall budget, schedule, major milestones, and key risks without requiring every detail to be fixed before sufficient information is available.
For instance, we can establish a baseline for the overall project while allowing design solutions to evolve within agreed cost, schedule, and performance parameters. As uncertainty decreases and design maturity increases, commitments become progressively more detailed and reliable.
Ultimately, I believe a successful hybrid approach is about being predictive where predictability is necessary, adaptive where learning and change add value, and disciplined about managing the interfaces between the two. Otherwise, like you said, we risk creating Agile theater rather than genuinely benefiting from either approach.
Rami yes using an adaptive approach for design and a predictive one for execution makes perfect sense. I agree with your strategy of setting clear boundaries around uncertainty rather than promising absolute certainty from day one. This progressive approach keeps sponsors informed without forcing a rigid plan too early, which is exactly how we can avoid "Agile theater". Francisco. Saving Changes...
Some projects can go through various and diverse phases, and we can establish a different approach for each one. For example, in software development, we can have a cascade approach for frontend design, and an agile approach for backend programming. The nature of the project will reveal the specific needs of its phases, and we can combine the best of the frameworks to obtain the desired final result. Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Francisco, I think the tension you describe is real, but I would distinguish between the certainty sponsors legitimately need and the certainty a project can reasonably provide.
A fixed budget or deadline does not necessarily prevent adaptive delivery. The critical question is which decisions must remain open as new information emerges, who has the authority to make them, and what happens when the original commitments become incompatible with what we have learned.
One approach I would advocate is to establish an explicit decision agreement with sponsors from the outset. This means distinguishing non-negotiable constraints from planning assumptions, defining which trade-offs the team can make autonomously, and agreeing on when evidence should trigger a review of priorities, forecasts or commitments.
The most important part is what happens when a trade-off exceeds the team's authority. At that point, the decision needs to reach whoever has the authority to reconsider the relevant commitments, with the consequences of preserving or changing them made explicit, rather than expecting the team to absorb incompatible demands.
This also means recognizing that predictability is not the same as certainty. We can improve the reliability of forecasts and the transparency of decisions without pretending that uncertainty has disappeared.
For me, the real test of a hybrid approach is not whether predictive and adaptive practices coexist, but whether the governance arrangements allow learning to influence consequential decisions.
Otherwise, we may have iterative execution without meaningful adaptability. Saving Changes...
Program Manager, PPM&PMO Specialist.| Coppel, Mexico.Culiacán, Sinaloa, Mexico
Oct 14, 2026 8:56 PM
Replying to Lissette Indhira Pimentel Sosa
...
Making the trade-offs clear from the beginning. If the sponsor needs a fixed budget or delivery date, then we need to discuss where flexibility will exist, especially around scope and priorities. I also try to establish regular checkpoints where we review what has changed and what decisions need to be made. The challenge is when sponsors expect teams to adapt continuously but still hold them accountable to every original commitment, even when the conditions have changed.
Yes the expectation of having 'agile flexibility' but 'waterfall accountability' is a very common trap. Setting clear trade-offs from day one is essential. Your strategy of using regular checkpoints is a great way to manage expectations and remind the sponsor that every new change will impact the original plan. Francisco. Saving Changes...
Community Champion
