SANTOSH BADGUJARCHIEF OPERATING OFFICER| Accumax Lab DevicesAhmedabad, Gujarat, India
Late-stage requirement changes can derail timelines and budgets. How do you manage a stakeholder who repeatedly introduces new requirements near the end of a project, while keeping the relationship healthy and the project on track?
Program Manager| HARPER SRLSanto Domingo / Distrito Nacional, Dominican Republic
Start by understanding why the requirements are changing. Sometimes it's a genuine business need, and other times it's something that should be planned for a future phase. I then explain the impact on scope, timeline, and resources so stakeholders can make an informed decision. That keeps expectations aligned while protecting the project. Saving Changes...
Robert SnyderFounder & President| Innovation Elegance, LLCChicago, Il, United States
Santosh, the flip-flopping stakeholder does not feel accountable to the PM, the schedule, or the value proposition. A good first step is to figure out who that stakeholder might be accountable to ... their boss? The project sponsor? Let's proceed here with their boss.
What I do is plainly reflect the changes in status reports and project schedules. I ensure the flip-flopping stakeholder's boss sees the changes. If they or if anyone senior to me cares, they will intervene. If they don't intervene, they don't care, and I recalibrate how much I care to how little they care. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Running the defined project change management process. Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
An important question. I would avoid treating the stakeholder as the problem and treat each late requirement as a business decision that needs to be tested. The key is to understand what changed, make the impact on scope, time, cost, risk, and benefits visible, and present clear options to the appropriate decision-maker. A healthy relationship is not preserved by accepting every change, but by ensuring that trade-offs are explicit, decisions are properly authorized, and the consequences are understood by everyone involved. Saving Changes...
In this situation, you need to negotiate with your stakeholders about the project timeline.
If you want to project timeline intact, you must create a stronger delivery strategy, such as implementing agile practices like Scrum.
By breaking releases into smaller, iterative cycles, any changes that arise mid‑iteration can be deferred to the next cycle rather than disrupting the current one. This approach allows you to deliver planned artifacts smoothly while packaging stakeholder requests into subsequent iterations. In doing so, you maintain the timeline for the requirements already in progress, while preparing the next set of requirements for the upcoming iteration and satisfying your stakeholders need without delays.
Each iteration should ideally span 10–15 business days, ensuring manageable scope, predictable delivery and flexibility to accommodate change without derailing the overall schedule.
When any new requirements that arise near the end of a project can be treated as Change Requests and implemented after the project has been delivered. Alternatively, you can incorporate them by creating an additional iteration for the final delivery, while negotiating extra Cost and Time for the new changes based on your Service Level Agreement.
Look into agile and Scrum, you’ll find effective solutions to manage stakeholder expectations, negotiate timelines more easily, and deliver results faster. Saving Changes...
PMI Team Member
Community Champion
