CSPO Release Planning and Sprint Goals

Question 1

What is the primary purpose of release planning in Scrum?

Accepted Answer

To forecast when product goals and features may be delivered based on current understanding

Answer

To lock down scope and dates for stakeholder contracts

Answer

To assign work packages to individual developers

Answer

To replace the Sprint Review ceremony

Question 2

Who is primarily responsible for release planning in a Scrum Team?

Accepted Answer

The Product Owner, because they own the Product Backlog and product value

Answer

The Scrum Master, because they facilitate all planning events

Answer

The Development Team, because they own the technical roadmap

Answer

An external project manager assigned by the organization

Question 3

How frequently should a Scrum Team produce a potentially releasable Product Increment?

Accepted Answer

At least once per Sprint

Answer

Only at the end of a release cycle

Answer

Once per quarter during a program increment

Answer

Whenever the Scrum Master approves the release

Question 4

What does a 'potentially releasable' Product Increment mean in the context of Scrum?

Accepted Answer

The increment meets the Definition of Done and could be released to users

Answer

The increment passed code review but still requires QA sign-off

Answer

The increment has been approved by the Product Owner for a future release

Answer

The increment includes at least 80% of the planned Sprint Backlog items

Question 5

Which artifact most directly supports the Product Owner in communicating the long-term release direction to stakeholders?

Accepted Answer

The Product Roadmap

Answer

The Sprint Backlog

Answer

The Definition of Done

Answer

The Sprint Burndown Chart

Question 6

What is the relationship between release planning and the Product Goal in Scrum?

Accepted Answer

Release planning helps chart a path toward achieving the Product Goal

Answer

Release planning replaces the need for a Product Goal

Answer

Release plans are created independently of the Product Goal

Answer

The Product Goal is set only after release planning is complete

Question 7

Which of the following best describes empirical release planning in Scrum?

Accepted Answer

Using historical velocity and current backlog size to forecast delivery ranges

Answer

Committing to fixed scope and fixed dates upfront using detailed estimates

Answer

Delegating all planning decisions to an external PMO

Answer

Creating a Gantt chart approved by all stakeholders before the first Sprint