Release Planning and Forecasting Flashcards

Who decides when a product is released to customers in Scrum?

Answer: The Product Owner, based on value and business readiness

The Product Owner decides when to release, as they are accountable for maximizing value and determining when sufficient value exists to warrant a release.

What does 'potentially releasable' mean in Scrum?

Answer: The Increment meets the Definition of Done and could be released if the Product Owner chooses

Potentially releasable means the Increment satisfies the Definition of Done and is technically fit for release; the Product Owner decides whether to actually release it.

What is velocity, and how can a Product Owner use it for release planning?

Answer: The average amount of work a team completes per Sprint, used to forecast when backlog items will be done

Velocity measures the team's throughput per Sprint, enabling the Product Owner to create rough forecasts of when features or releases might be ready.

Why should velocity be used with caution in release forecasting?

Answer: Because it is a lagging, variable metric that cannot guarantee future performance

Velocity varies Sprint to Sprint based on team factors and item complexity, making it a useful trend indicator but not a precise predictive tool.

What is a release plan in Scrum, and how does it differ from the Sprint Backlog?

Answer: A release plan is a higher-level forecast of which features will be available by a certain date; the Sprint Backlog is the team's detailed Sprint-level plan

A release plan provides a strategic forecast for stakeholders, while the Sprint Backlog is the team's tactical, Sprint-level work plan.

How does the Product Owner balance a fixed release date with a variable scope?

Answer: By adjusting scope to protect quality and the release date, delivering the highest-value items first

Prioritizing high-value items ensures that if scope must be cut to meet a date, the most important value is delivered, a key PSPO practice.