PSPO I: Forecasting & Release Planning practice questions
50 questions on Forecasting & Release Planning, one of the 7 areas assessed in Professional Scrum Product Owner I. Untimed, with an explanation after every answer.
This topic covers empirical forecasting and release planning: velocity, throughput, cycle time, burn-down charts and Monte Carlo simulation, under one Scrum Guide rule: only what has already happened may be used for forward-looking decisions. An Increment that meets the Definition of Done can be released before the Sprint ends; the Sprint Review is not a release gate.
A forecast is not a commitment: give a range with a confidence level and update it as data arrives. Velocity is team-specific and never compared across teams. A fixed date is a legitimate constraint if scope stays flexible; fixing scope and date together is not. Weakening the Definition of Done to hit a date is never an option.
What is velocity in Scrum?
Ready for exam conditions? 80 questions, 60 minutes, 85% to pass.
Mock examA worked example
A question from the bank with its answer and the reasoning behind it. Every practice question comes with an explanation like this one.
Probabilistic forecasting uses:
- AGut feelings about delivery dates
- BHistorical data to predict likelihood of delivery(correct answer)
- CManagement mandates
- DFixed deadlines
Why
Probabilistic forecasting uses historical data to predict delivery likelihood (e.g., '85% chance by June'). It's empirical and acknowledges uncertainty rather than promising fixed dates.