PSPO II Practice Question
Mastering the Scrum Sprint Forecast for Agile Success
Question
A Sprint forecast is:(choose the best answer)
Options
- A A. Useful for the stakeholders to know what will be included in future releases.
- B B. The amount of work the Developers believe they can complete in that Sprint.
- C C. A useful tool for management to understand team performance and capacity.
- D D. A commitment the Developers make to deliver a particular set of Product Backlog items.
Answer
- B. The amount of work the Developers believe they can complete in that Sprint.
Explanation
A Sprint forecast is primarily the amount of work the Developers believe they can complete in that Sprint (Option B). It serves as a planning tool that helps the team assess their capacity and align on expectations for the upcoming Sprint. This forecast is based on the Developers' past performance and their understanding of the tasks at hand. Option A is misleading; while stakeholders may find the forecast useful for understanding future releases, the forecast specifically pertains to the current Sprint's workload. Option C suggests that the forecast is primarily a tool for management, which is incorrect as it is primarily for the team’s internal planning. Option D is also incorrect; while the Developers commit to delivering potentially releasable increments of the Product Backlog items, the Sprint forecast does not equate to a commitment to deliver specific items, but rather an estimation of what is feasible within the Sprint timeframe.
Expert Author
MR
Marcus Rodriguez
Product Owner & Business Analyst
Backlog management, stakeholder collaboration, user stories
Why Other Options Are Wrong
Option A is incorrect because the Sprint forecast does not explicitly indicate what will be included in future releases; it only focuses on the current Sprint. Option C is also misleading, as the Sprint forecast is not designed as a management performance tool but rather a collaborative estimate by the team. Option D misrepresents the nature of the forecast; while it informs what the team aims to achieve, it is not a formal commitment. The team's commitment is expressed in the Sprint Goal and the Definition of Done.
Real-World Application
In a Scrum team working on a software project, during the Sprint Planning meeting, the Developers assess their velocity based on previous Sprints and agree they can complete 20 story points worth of tasks in the upcoming Sprint. This forecast helps them prioritize work accordingly and ensures alignment on what they can realistically achieve.
Common Pitfalls
Students often confuse the Sprint forecast with a commitment to deliver specific items, or they may misunderstand its purpose as solely for management rather than for the Developers' internal planning.
Key Concepts
Sprint Planning Sprint Goal Developer Commitment Capacity Estimation Product Backlog
Scrum Guide Reference
Scrum Guide 2020, Section 3.3 - The Sprint Forecast
More PSPO II Questions
PSPO II
When to Release a Scrum Product Increment: Key Considerations
A Product Increment is released when:(choose the best answer)
PSPO II
Scrum Essentials: One Product, One Backlog
A separate Product Backlog is needed for every:(choose the best answer)
PSPO II
Bridging the User Satisfaction Gap in Agile and Scrum
A user satisfaction gap exists when there is a difference between:(choose the best two answers)