Study PSM I Forecasting, Release Thinking, and Sprint Goal Trade-Offs: key concepts, common traps, and exam decision cues.
Scrum teams still need to forecast, but PSM I draws a sharp line between forecasting and promising certainty. Stronger answers protect the Sprint Goal, use evidence to revise expectations, and avoid turning forecasts into fixed commitments that ignore learning.
| Item | Stronger interpretation |
|---|---|
| Forecast | best current expectation based on known evidence |
| Sprint Goal | the commitment that gives the Sprint coherence |
| Release thinking | value-aware planning that can adapt as evidence changes |
The exam usually asks whether the team should protect a useful Sprint Goal while learning, or whether it should pretend the original plan cannot change. Stronger answers allow adaptation without destroying focus.
During the Sprint, new information shows one selected item is larger than expected. The stronger answer is not to declare Scrum broken. It is to inspect progress against the Sprint Goal, adapt the Sprint Backlog, and keep stakeholders informed through transparent forecasting.
Which statement best reflects Scrum’s treatment of forecasting?
A. Forecasts are useful but may change as the team learns during delivery
B. Forecasts should not exist because Scrum only reacts to finished work
C. Forecasts are commitments that should not change once Sprint Planning ends
D. Forecasting belongs only to management, not to the Scrum Team
Best answer: A
Why: Scrum uses empirical learning, so forecasts remain valuable but revisable.
Why the others are weaker: B, C, and D either reject planning or confuse it with false certainty and external control.