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!
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Francisco, I wonder whether the tension begins one step earlier than reporting. Who participated in tailoring the project approach, and how were the sponsor’s legitimate governance needs incorporated into it?
A sponsor may need a fixed date because of a regulatory or market constraint, a defined funding envelope, and regular information about whether the project is progressing toward its objectives. None of those needs is inherently predictive. A fixed constraint does not prescribe how the work must be performed, and asking for decision-useful information is part of governance, not necessarily interference with team autonomy.
I would therefore distinguish the underlying governance need from the artifact traditionally used to satisfy it. If leadership asks for a detailed Gantt chart, I would first ask what decision or uncertainty they need it to address. A forecast is not a guarantee, but adaptive delivery does not remove the need for credible forecasting and accountability either.
So perhaps the deeper challenge is not translating between two incompatible mindsets. It is designing execution and governance coherently from the outset, with the relevant stakeholders involved, so that adaptability and legitimate organizational commitments can coexist.
...
2 replies by Francisco Herrera and Stelian ROMAN
Sep 21, 2026 2:12 PM
Francisco Herrera
...
Luis Ddstinguishing the underlying governance need from the traditional artifact, like a Gantt chart, is a fantastic approach. You are completely right that a sponsor asking for a forecast is just doing their job, not necessarily attacking the agile framework. This is a great reminder to focus on the 'why' behind their requests. Francisco
Sep 21, 2026 6:25 PM
Stelian ROMAN
...
Constraints at the executive level are something that is hard to explain to people who are not in these shoes. From the trenches, those executives look 'predictive', little understood by the 'developers', they have the responsibility for the bottom line, including retaining talent and paying their salaries. Money doesn't come easy, and to fund the team, they need to comply with regulations. It doesn't mean that they are not Agile.
I agree with you that 'the deeper challenge is not translating between two incompatible mindsets'. I would like to add that, to bridge the mindset, both sides must learn and understand the other side's point of view.
On a separate note, I've had many times the 'opportunity' to see the reverse: Agile executives vs. Predictive teams: How do you survive the "Hybrid" middle? The same way: learn, communicate, trust, respect. In a single word: ethics.
Saving Changes...
Natalie BuchananDirector, PMO & Project Delivery| Cook Media GlobalNorth Carolina, United States
Francisco, I can certainly relate. I have been working through this same challenge over the past year.
We acquired a company partly because of its technology, and its teams operate fully in Agile. Our organization, however, had historically relied primarily on predictive project management, with some hybrid projects and relatively few Agile ones. As we began managing more technology-focused initiatives, our use of Agile increased—but our executive leaders still expected project reporting, timelines, and data to be presented through a predictive lens.
Rather than continually translating Agile into predictive terminology, I have focused on helping our executive leadership team become more familiar and comfortable with Agile principles. We created a dedicated PMO intranet site with dashboards for all predictive, hybrid, and Agile projects, including metrics such as burnup, burndown, and velocity.
I have also provided one-on-one coaching for executives, developed an Agile Stakeholder Guide, posted video tutorials explaining how to interpret the dashboard metrics, and hosted live webinars for our management team to introduce Agile concepts and the resources available to them.
It has taken time to build confidence after many years of working primarily with predictive terminology and expectations. However, we are beginning to see the shift. In my experience, bridging this gap is not simply a reporting exercise—it is a change-management and education effort. The goal is to give leadership the visibility and confidence they need without forcing Agile teams to abandon the practices that enable them to adapt and deliver value effectively.
...
1 reply by Francisco Herrera
Sep 22, 2026 2:40 PM
Francisco Herrera
...
Yes Natalie bridging this gap is a change-management and education effort, not just a reporting exercise. Your approach of providing 1-on-1 coaching and creating an 'Agile Stakeholder Guide' shows that investing time in educating executives is the best way to build real trust in the long run. Francisco
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.
...
1 reply by Francisco Herrera
Sep 28, 2026 2:40 PM
Francisco Herrera
...
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
Program Manager| HARPER SRLSanto Domingo / Distrito Nacional, Dominican Republic
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.
...
1 reply by Francisco Herrera
Sep 29, 2026 12:55 PM
Francisco Herrera
...
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
Program Manager, PPM&PMO Specialist.| Coppel, Mexico.Culiacán, Sinaloa, Mexico
Sep 15, 2026 12:57 PM
Replying to Luis Branco
...
Francisco, I wonder whether the tension begins one step earlier than reporting. Who participated in tailoring the project approach, and how were the sponsor’s legitimate governance needs incorporated into it?
A sponsor may need a fixed date because of a regulatory or market constraint, a defined funding envelope, and regular information about whether the project is progressing toward its objectives. None of those needs is inherently predictive. A fixed constraint does not prescribe how the work must be performed, and asking for decision-useful information is part of governance, not necessarily interference with team autonomy.
I would therefore distinguish the underlying governance need from the artifact traditionally used to satisfy it. If leadership asks for a detailed Gantt chart, I would first ask what decision or uncertainty they need it to address. A forecast is not a guarantee, but adaptive delivery does not remove the need for credible forecasting and accountability either.
So perhaps the deeper challenge is not translating between two incompatible mindsets. It is designing execution and governance coherently from the outset, with the relevant stakeholders involved, so that adaptability and legitimate organizational commitments can coexist.
Luis Ddstinguishing the underlying governance need from the traditional artifact, like a Gantt chart, is a fantastic approach. You are completely right that a sponsor asking for a forecast is just doing their job, not necessarily attacking the agile framework. This is a great reminder to focus on the 'why' behind their requests. Francisco Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Sep 15, 2026 12:57 PM
Replying to Luis Branco
...
Francisco, I wonder whether the tension begins one step earlier than reporting. Who participated in tailoring the project approach, and how were the sponsor’s legitimate governance needs incorporated into it?
A sponsor may need a fixed date because of a regulatory or market constraint, a defined funding envelope, and regular information about whether the project is progressing toward its objectives. None of those needs is inherently predictive. A fixed constraint does not prescribe how the work must be performed, and asking for decision-useful information is part of governance, not necessarily interference with team autonomy.
I would therefore distinguish the underlying governance need from the artifact traditionally used to satisfy it. If leadership asks for a detailed Gantt chart, I would first ask what decision or uncertainty they need it to address. A forecast is not a guarantee, but adaptive delivery does not remove the need for credible forecasting and accountability either.
So perhaps the deeper challenge is not translating between two incompatible mindsets. It is designing execution and governance coherently from the outset, with the relevant stakeholders involved, so that adaptability and legitimate organizational commitments can coexist.
Constraints at the executive level are something that is hard to explain to people who are not in these shoes. From the trenches, those executives look 'predictive', little understood by the 'developers', they have the responsibility for the bottom line, including retaining talent and paying their salaries. Money doesn't come easy, and to fund the team, they need to comply with regulations. It doesn't mean that they are not Agile.
I agree with you that 'the deeper challenge is not translating between two incompatible mindsets'. I would like to add that, to bridge the mindset, both sides must learn and understand the other side's point of view.
On a separate note, I've had many times the 'opportunity' to see the reverse: Agile executives vs. Predictive teams: How do you survive the "Hybrid" middle? The same way: learn, communicate, trust, respect. In a single word: ethics. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
With all my due respect the post has the big mistake which is the first step to fail: think that Agile is a matter of "short iterations, flexibility, adapting to change". My recommendation for people that like to be successful with the use of Agile is going to the basement: USA NSF/DoD Agility Forum at Leighig Uniervsity that was the place where Agile and agility was defined. Time after people that has object oriented method to create software product took it . I was part of both movements.
...
2 replies by Stelian ROMAN
Sep 21, 2026 7:43 PM
Stelian ROMAN
...
Sergio Luis Conte, excellent advice. Agile (Manufacturing) Forum was a group of visionaries who tried to define a way to respond to 21st-century market dynamics. It started as a challenge to the success of Lean Six Sigma in Japan: how can the USA remain competitive? The Agile Forum was the inspiration for my series of webinars, "The Agile Enterprise," on projectmanagement.com. It is sad that nowadays Agile is reduced to a team of software developers' mindset. Iterative and incremental development is how products were developed for millennia. Even software was developed in that way (at least) since the 1960s. A good topic for discussion....
Sep 21, 2026 7:50 PM
Stelian ROMAN
...
Sergio Luis Conte, I will go even earlier than the 1990s, when the Agile Forum was established. In the 1960s, the DoD launched the project "Agile," the first documented reference to Agile as a product development approach. DoD's challenge was that the existing 'products' were not suitable for a certain market. They needed a shorter cycle from requirements to delivery. I assume that was the seed for the Agile Forum. I'm not promoting my view (aka the "Agile Enterprise" History), but I believe that more information is always helpful.
Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Sep 21, 2026 6:37 PM
Replying to Sergio Luis Conte
...
With all my due respect the post has the big mistake which is the first step to fail: think that Agile is a matter of "short iterations, flexibility, adapting to change". My recommendation for people that like to be successful with the use of Agile is going to the basement: USA NSF/DoD Agility Forum at Leighig Uniervsity that was the place where Agile and agility was defined. Time after people that has object oriented method to create software product took it . I was part of both movements.
Sergio Luis Conte, excellent advice. Agile (Manufacturing) Forum was a group of visionaries who tried to define a way to respond to 21st-century market dynamics. It started as a challenge to the success of Lean Six Sigma in Japan: how can the USA remain competitive? The Agile Forum was the inspiration for my series of webinars, "The Agile Enterprise," on projectmanagement.com. It is sad that nowadays Agile is reduced to a team of software developers' mindset. Iterative and incremental development is how products were developed for millennia. Even software was developed in that way (at least) since the 1960s. A good topic for discussion.... Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Sep 21, 2026 6:37 PM
Replying to Sergio Luis Conte
...
With all my due respect the post has the big mistake which is the first step to fail: think that Agile is a matter of "short iterations, flexibility, adapting to change". My recommendation for people that like to be successful with the use of Agile is going to the basement: USA NSF/DoD Agility Forum at Leighig Uniervsity that was the place where Agile and agility was defined. Time after people that has object oriented method to create software product took it . I was part of both movements.
Sergio Luis Conte, I will go even earlier than the 1990s, when the Agile Forum was established. In the 1960s, the DoD launched the project "Agile," the first documented reference to Agile as a product development approach. DoD's challenge was that the existing 'products' were not suitable for a certain market. They needed a shorter cycle from requirements to delivery. I assume that was the seed for the Agile Forum. I'm not promoting my view (aka the "Agile Enterprise" History), but I believe that more information is always helpful. Saving Changes...
Program Manager, PPM&PMO Specialist.| Coppel, Mexico.Culiacán, Sinaloa, Mexico
Sep 18, 2026 10:48 AM
Replying to Natalie Buchanan
...
Francisco, I can certainly relate. I have been working through this same challenge over the past year.
We acquired a company partly because of its technology, and its teams operate fully in Agile. Our organization, however, had historically relied primarily on predictive project management, with some hybrid projects and relatively few Agile ones. As we began managing more technology-focused initiatives, our use of Agile increased—but our executive leaders still expected project reporting, timelines, and data to be presented through a predictive lens.
Rather than continually translating Agile into predictive terminology, I have focused on helping our executive leadership team become more familiar and comfortable with Agile principles. We created a dedicated PMO intranet site with dashboards for all predictive, hybrid, and Agile projects, including metrics such as burnup, burndown, and velocity.
I have also provided one-on-one coaching for executives, developed an Agile Stakeholder Guide, posted video tutorials explaining how to interpret the dashboard metrics, and hosted live webinars for our management team to introduce Agile concepts and the resources available to them.
It has taken time to build confidence after many years of working primarily with predictive terminology and expectations. However, we are beginning to see the shift. In my experience, bridging this gap is not simply a reporting exercise—it is a change-management and education effort. The goal is to give leadership the visibility and confidence they need without forcing Agile teams to abandon the practices that enable them to adapt and deliver value effectively.
Yes Natalie bridging this gap is a change-management and education effort, not just a reporting exercise. Your approach of providing 1-on-1 coaching and creating an 'Agile Stakeholder Guide' shows that investing time in educating executives is the best way to build real trust in the long run. Francisco Saving Changes...
Community Champion
