PMP · Question #42
A business stakeholder for a project is reluctant to accept an agile approach due to a previous bad experience, and is pushing for a predictive approach. What strategy should the project manager use t
The correct answer is D. Propose a phased project approach with multiple small interactions and build trust with the. The project manager needs to persuade a stakeholder reluctant to adopt an agile approach due to past negative experiences.
Question
A business stakeholder for a project is reluctant to accept an agile approach due to a previous bad experience, and is pushing for a predictive approach. What strategy should the project manager use to persuade the stakeholder to use an agile approach?
Options
- AAgree on a predictive approach, but apply agile concepts under the project management
- BEnsure the stakeholder that an agile approach will deliver all of the expected results in a shorter
- CDocument the request and escalate to upper management to consider a modification of the
- DPropose a phased project approach with multiple small interactions and build trust with the
How the community answered
(57 responses)- A11% (6)
- B2% (1)
- C5% (3)
- D82% (47)
Why each option
The project manager needs to persuade a stakeholder reluctant to adopt an agile approach due to past negative experiences.
Agreeing to a predictive approach while secretly applying agile principles is deceptive and could severely damage trust if the stakeholder discovers the actual methodology being used.
Guaranteeing that an agile approach will deliver all expected results in a shorter timeframe is an oversimplification and sets unrealistic expectations, which could backfire if challenges arise.
Immediately escalating to upper management without attempting to address the stakeholder's concerns directly can create an adversarial relationship and undermine the project manager's ability to gain buy-in.
Proposing a phased project approach with small, frequent iterations and demonstrable results allows the stakeholder to gradually witness the benefits of agile firsthand. This incremental delivery builds trust by providing early value and mitigating perceived risks from their prior negative experience with agile.
Concept tested: Stakeholder engagement and agile adoption
Topics
Community Discussion
10
Wesley A.Dec 5, 2025Failed this one my first attempt because I went with A, thinking the hybrid sneak approach was smart. D is correct because when a stakeholder has trust issues from a past bad experience, you build confidence through small phased increments rather than forcing a full agile commitment or promising things you cannot guarantee.
Wei W.Dec 7, 2025Agreed on D, and worth noting that the trust repair mechanism here is empiricism itself: when stakeholders can inspect a real working increment every few weeks instead of reading a status report, the transparency does the heavy lifting for you.
Wei W.Dec 13, 2025D is the right call here. Trust has to be earned back through visible working increments, not promises, so a phased approach lets the stakeholder see real value delivered before committing fully.
Imani T.Dec 14, 2025Agreed on D but make sure those early phases are actually functional, not just smoke-and-mirrors demos, because a skeptical stakeholder will spot that instantly and you lose whatever trust you were trying to rebuild.
Imani T.Nov 19, 2025Confirmed D on exam two months ago. The phased approach lets the stakeholder see incremental wins without committing to full agile upfront, which is exactly how you rebuild trust after a bad past experience.
Viktor S.Nov 21, 2025D is right but the real exam trap is people picking the big-bang agile option because it sounds more modern, when the whole point of the scenario is that the stakeholders got burned before and need proof in small doses before they will buy in.
Samuel O.Dec 6, 2025I first leaned toward A because in my experience you sometimes just have to work around a stubborn stakeholder and quietly run things your own way. But that is a good way to burn trust if they eventually catch on, and it ignores the actual problem of their reluctance. D is the right move because you meet them halfway with a phased approach and let the results speak for themselves. Once they see a couple of successful iterations, that prior bad experience starts to fade and you can build from there.
Viktor S.Dec 6, 2025Good call on D, Samuel, but the real trick is making sure that first phased iteration is something the stakeholder specifically asked for, not just something you think will impress them, or you will be right back where you started.
Viktor S.Dec 4, 2025B is the move. Selling speed and results is how you win a skeptic over.
Imani T.Dec 6, 2025D is the right call here Viktor. B sounds like a sales pitch but the question is asking about trust, and trust comes from transparency and visibility into the process, not just flashing fast results at someone who is already skeptical.