PSPO Release Planning and Forecasting 2 — Questions and Answers
Question 1: What is the purpose of product backlog refinement in the context of release forecasting?
- To assign tasks to Developers for the upcoming Sprint
- To ensure items are well understood and estimated so the PO can forecast more accurately (Correct answer)
- To finalize the release date with stakeholders
- To eliminate items the team cannot complete
Correct answer: To ensure items are well understood and estimated so the PO can forecast more accurately
Refinement improves the clarity and estimation accuracy of backlog items, enabling more reliable forecasting for release planning.
Question 2: What is a burn-down chart, and how can it help the Product Owner?
- A chart showing remaining work over time, helping the PO track progress toward a release (Correct answer)
- A chart showing team satisfaction over time
- A financial report on project spending
- A tool used only by the Scrum Master
Correct answer: A chart showing remaining work over time, helping the PO track progress toward a release
A burn-down chart shows remaining work over time, giving the Product Owner a visual signal of whether the team is on track to meet release goals.
Question 3: How should a Product Owner communicate release forecasts to stakeholders?
- As firm commitments with guaranteed delivery dates
- As probabilistic forecasts based on current velocity trends, with appropriate uncertainty acknowledged (Correct answer)
- Only after the Scrum Master approves the communication
- In sprint increments only, never as release forecasts
Correct answer: As probabilistic forecasts based on current velocity trends, with appropriate uncertainty acknowledged
Release forecasts should be presented as informed estimates with uncertainty ranges, setting realistic stakeholder expectations rather than false commitments.
Question 4: What is a Minimum Marketable Feature (MMF) and why is it useful for release planning?
- The largest feature set that can be delivered in one Sprint
- The smallest feature slice that delivers enough value to be worth releasing to market (Correct answer)
- A feature approved by marketing before development
- A feature that requires no further development after release
Correct answer: The smallest feature slice that delivers enough value to be worth releasing to market
MMFs help the Product Owner identify the smallest releasable value increments, enabling earlier releases and faster market feedback.
Question 5: How does continuous delivery relate to the Product Owner's release strategy?
- It removes the Product Owner from release decisions entirely
- It enables the PO to release value more frequently, reducing time-to-market and increasing feedback opportunities (Correct answer)
- It requires the PO to approve every code commit
- It replaces Sprint-based delivery with daily releases only
Correct answer: It enables the PO to release value more frequently, reducing time-to-market and increasing feedback opportunities
Continuous delivery capabilities give the Product Owner greater flexibility to release when value is sufficient, supporting more responsive product decisions.
Question 6: What should a Product Owner do when a key feature will not be ready for a planned release date?
- Reduce the Definition of Done to allow partial completion
- Evaluate whether to delay the release, release without the feature, or negotiate scope with stakeholders (Correct answer)
- Cancel the Sprint and replan
- Force Developers to work overtime to meet the deadline
Correct answer: Evaluate whether to delay the release, release without the feature, or negotiate scope with stakeholders
The Product Owner must make a value-based decision: delay for completeness, release a valuable subset, or renegotiate with stakeholders — never compromise quality.
PSPO Release Planning and Forecasting 2
What is the purpose of product backlog refinement in the context of release forecasting?