Managing Stakeholder Expectations for Release Dates
When stakeholders request definitive answers about release dates and features, it is essential for the Product Owner to manage their expectations appropriately. This involves providing information transparently while avoiding promises that the Scrum Team may not be able to keep.
Exam Question
Stakeholders are asking the Product Owner for definitive answers regarding the next release date and what features will be in it. Which of the following should the Product Owner do?
(choose the best answer)
A. Use flow-based metrics to calculate the exact delivery date.
B. Decide which features to include and tell the Developers when they need to be finished.
C. Create a roadmap from the Product Backlog without implying certainty.
D. Use velocity to give them an exact date.
Correct Answer
C. Create a roadmap from the Product Backlog without implying certainty.
Explanation
Correct Answer
C. Create a roadmap from the Product Backlog without implying certainty:
The Product Owner should create a roadmap that outlines the planned features and approximate timelines based on the current state of the Product Backlog. It is crucial to communicate that these dates are tentative and subject to change based on the progress and any unforeseen circumstances. This approach maintains transparency and keeps stakeholders informed without making concrete promises that could be difficult to uphold.
Why the Other Options Are Incorrect
A. Use flow-based metrics to calculate the exact delivery date:
While flow-based metrics can provide insights into the team’s progress, they should not be used to calculate exact delivery dates. The inherent uncertainty in complex projects makes it challenging to predict exact dates accurately.
B. Decide which features to include and tell the Developers when they need to be finished:
This approach undermines the collaborative nature of Scrum and places undue pressure on the Developers. It also does not account for the variability and complexity of the work, which can lead to missed deadlines and reduced quality.
D. Use velocity to give them an exact date:
Velocity can help estimate the team’s capacity, but it should not be used to provide exact dates. Velocity can fluctuate due to various factors, and relying on it for precise predictions can lead to inaccurate commitments.
Relevance to the PSPBM Skills Exam
Understanding how to manage stakeholder expectations and communicate effectively about release planning is crucial for the PSPBM Skills exam. It demonstrates the Product Owner’s ability to balance transparency with the inherent uncertainty of complex product development.
Key Takeaways
- Creating a roadmap provides a clear plan while allowing flexibility.
- Avoid making definitive promises about release dates and features.
- Use velocity and flow-based metrics as guiding tools, not for exact predictions.
- Effective communication with stakeholders is essential for managing expectations.
Conclusion
Managing stakeholder expectations involves creating a transparent and flexible roadmap.

Get ready for the official PSPBM exam
140+ PSPBM practice questions, each with an in-depth explanation like the one above.
- Practice Mode: study at your own pace and choose the test length.
- Mock Exam Mode: 20 random questions in 30 minutes, like the real exam.
$29 is ScrumPrep's one-time price. The official PSPBM exam fee is paid separately to Scrum.org.
More PSPBM exam questions
- As the Product Owner, you have identified an opportunity for a new product. What is a valuable initial step for developing the Product Backlog?
- How do you know if a Product Backlog item is valuable?
- During a Product Backlog refinement session, Developers ask a question about a Product Backlog item. Answering that question will require the Developers to set up a session with stakeholders from outside the Scrum Team. What is a helpful course of action to take during the Product Backlog refinement session?
- You are the Scrum Master on a Scrum Team that is experiencing difficulty during Sprint Planning. The Scrum Team is always unclear about Product Backlog items and frequently argue about scope. Which of the following would help improve Sprint Planning?
- The Product Owner has identified a need to split a large user story in the Product Backlog into smaller, more manageable pieces. What should the Product Owner do to manage this change in the Product Backlog?
