PMP · Question #1271
In a project steering committee meeting, a few stakeholders raise concerns that the project manager's report shows that the outcome of the project is already in the market while the project is still i
The correct answer is A. Ensure the content of the project report is clearly understood and request any necessary. To prevent stakeholder confusion in an agile project with incremental releases, the project manager must clarify reporting content and gather feedback.
Question
Options
- AEnsure the content of the project report is clearly understood and request any necessary
- BEnsure that all product features are completed as per the communicated specifications before
- CSend a detailed report to each steering committee member ahead of the meeting.
- DInvite critical stakeholders to the daily project review meetings to ensure their full engagement
How the community answered
(33 responses)- A70% (23)
- B6% (2)
- C6% (2)
- D18% (6)
Why each option
To prevent stakeholder confusion in an agile project with incremental releases, the project manager must clarify reporting content and gather feedback.
The core issue is a misunderstanding by stakeholders regarding the project's reporting and agile delivery model. The project manager must ensure the project report's content clearly distinguishes between features released to market and those still under development, and should proactively seek feedback to adjust communication for better comprehension by the steering committee.
This choice contradicts the agile approach of incremental delivery and releasing value early; waiting for all features to be completed before any release would defeat the purpose of sprints and early market feedback.
While sending detailed reports ahead of time can be helpful, it doesn't guarantee understanding if the content itself is confusing or misinterpretable, and might lead to information overload without proper context.
Inviting critical stakeholders to daily project review meetings (like daily standups) is usually too frequent and detailed for a steering committee; it would disrupt the team's agile flow and likely overwhelm the stakeholders with granular information irrelevant to their strategic oversight.
Concept tested: Agile stakeholder communication
Topics
Community Discussion
5
Mateus R.Jun 8, 2026The answer is A. Think of it like a farmer selling produce at a roadside stand while the rest of the crops are still growing in the back field. The buyers might think the harvest is totally finished, so the farmer just needs to clarify that they pick and sell in batches all season long. In Agile terms, delivering in sprints means completed increments are released to the market early, which is perfectly normal but often confuses folks used to traditional big-bang delivery. The project manager simply needs to walk the steering committee through the reporting structure so they understand the difference between a sprint release and final project
Anjali D.Jun 5, 2026Saw this on my exam last month and the group landed on A. A few of us debated C since sending the report early sounds proactive, but the real issue is that stakeholders misunderstood the content, not that they lacked time to read it. A few folks in our study group also liked D but daily standups for steering committee members is unrealistic. Anyone else see this one recently?
Samuel O.Jul 1, 2026A is the right call here. I've seen this exact confusion in steering meetings when stakeholders don't grasp that agile releases mean partial deliveries hit production while development continues, so the fix is making sure the report itself spells that out clearly rather than just handing them a denser document. C is the trap because a detailed report sent early doesn't help if the content still doesn't clearly explain the sprint and release approach.
Brenda K.Jun 28, 2026A is a 20-second quick win because the root cause here is a communication gap, not a process failure, so fixing how the report is understood resolves it. Saw this on my exam last month and almost overthought it into C, but remembered that sending more pages to people who already misread the first report does not solve the comprehension problem.
Mei-Ling H.Jun 19, 2026Confirmed A on exam. C is the trap because sending the report ahead sounds proactive, but the issue is they misunderstood the sprint and release concept, not that they lacked time to read it.