• You're one step from joining Project Management Forum – Agile, PMP Certification & Leadership.
    Create a free account to post, follow threads, and never miss an update.  Sign up free →

How to push back stakeholder issue professionally

Danny.blair

New member
Joined
Oct 30, 2025
Messages
2
Need some advice on handling a difficult stakeholder situation, I'm asst PM at a mid size company managing a software implementation project. We're using Agile with 2 week sprints, but one of our key stakeholders seems to think agile is room to change anything anytime.
We're in sprint 4 of 8 and every single sprint review, he brings up small tweaks that are actually scope changes. Last week he wanted to completely redesign a workflow we'd already built and tested and when I explained it would impact timeline, he said but it's agile, you should be flexible, I've tried documenting change requests and showing impact analysis and even prioritize against existing backlog
Am I being too rigid here? Is this just the reality of modern PM work?
 
@Danny.blair
No, you're not being too rigid, that stakeholder doesn't understand that agile flexibility doesn't mean unlimited changes with no consequences. Maybe loop in your PM or sponsor to reinforce this with him then start asking him what he wants to deprioritize when he requests new features, make him choose, psychology feels it makes people think twice.
 
Agile doesn’t mean saying yes to every change; it means adapting with structure. The whole point of sprint commitments, timeboxing, and a prioritized backlog is to protect the team from exactly this kind of constant disruption.
It’s good you’re showing impact and documenting changes.
Maybe try saying, “We can plan this for a future sprint so we don’t disrupt what’s in progress.” That helps you stay flexible without losing control of the plan.
 
Agile doesn’t mean saying yes to every change; it means adapting with structure. The whole point of sprint commitments, timeboxing, and a prioritized backlog is to protect the team from exactly this kind of constant disruption.
It’s good you’re showing impact and documenting changes.
Maybe try saying, “We can plan this for a future sprint so we don’t disrupt what’s in progress.” That helps you stay flexible without losing control of the plan.
I must say I admire your knowledge on the emotional side of PM, been seeing you around, keep it up!
 
Am I being too rigid here? Is this just the reality of modern PM work?
nah, not rigid, you're following standard Agile practices by managing scope and protecting the team's sprint commitment. in my opinion, the most effective approach is to help the stakeholder understand the agreed upon rules of engagement for an Agile project. just continue to be firm, consistent, and educational in your approach
 
Back
Top