PSPO II practice questions: Forecasting and Release Strategy

5 free questions from 16 on this area · answer and explanation for each · no sign-up

These 5 questions come from the Forecasting and Release Strategy section of our PSPO II bank (16 questions on this area, which carries 15% of the real exam). Every question is original, with the correct answer explained and linked to the source it is drawn from.

Start 6 free in study mode → All PSPO II sample questions

1/5 · Forecasting and Release Strategy · easy

Under the Evidence-Based Management (EBM) Guide, which Key Value Area (KVA) most directly measures an organization's ability to quickly turn a Product Backlog item into a working feature that generates value in customers' hands?

AAbility to Innovate

BTime-to-Market

CUnrealized Value

DCurrent Value

Show answer & explanation

B is correct. The EBM Guide defines Time-to-Market as one of four Key Value Areas, measuring the organization's ability to quickly turn a Product Backlog item into a delivered capability that customers can use, distinguishing it from Current Value, Unrealized Value, and Ability to Innovate.
↗ the Scrum Guide (2020) + Scrum.org's Product Owner Learning Path and the Evidence-Based Management Guide — Forecasting and Release Strategy

2/5 · Forecasting and Release Strategy

An enterprise HR software product requires customers' internal training teams to prepare materials before each new capability goes live, and stakeholders have repeatedly said unpredictable releases disrupt their change-management schedule. Which release strategy best fits this context?

AA fixed scope and fixed date "big-bang" release once a year, bundling all work regardless of Sprint Review feedback, to minimize disruption.

BRelease on demand for every completed Product Backlog item, since Scrum always prefers releasing value as soon as it is ready regardless of stakeholder context.

CA fixed release cadence, so stakeholders can plan training and communications around predictable, known release dates even though individual features may wait for the next scheduled release.

DNo release strategy at all; let the hosting infrastructure team decide releases independently of the Scrum Team, since release timing is an operations concern only.

Show answer & explanation

C is correct. Neither the Scrum Guide nor EBM prescribes a single correct release strategy; the Product Owner chooses the strategy that maximizes value in context. Here, stakeholders' dependency on scheduled training makes a predictable fixed cadence more appropriate than releasing on demand, without going to the extreme of an annual big-bang release.
↗ the Scrum Guide (2020) + Scrum.org's Product Owner Learning Path and the Evidence-Based Management Guide — Forecasting and Release Strategy

3/5 · Forecasting and Release Strategy

A product has grown to require four Scrum Teams. Leadership proposes giving each team its own separate Product Backlog and its own Product Owner so that each team can move faster independently. Per the Scrum Guide (2020), what is the concern with this proposal?

AThe concern is that Developers are not allowed to specialize across teams, so any multi-team structure violates the Scrum Guide regardless of backlog design.

BThe concern is only technical (merge conflicts in code), and the Scrum Guide has no position on Product Backlog structure for multiple teams.

CWhen multiple Scrum Teams work on the same product, they should share one Product Backlog and one Product Goal, with a single Product Owner accountable for ordering that Backlog, so value and priorities remain coherent; splitting Backlogs risks duplicated work and misaligned priorities.

DThere is no concern; the Scrum Guide requires a separate Product Backlog per team once a product exceeds three Scrum Teams.

Show answer & explanation

C is correct. The Scrum Guide (2020) states that when several Scrum Teams work together on one product, they should share the same Product Backlog and Product Goal, and that a single Product Owner remains accountable for the Product Backlog; splitting into separate backlogs and Product Owners risks duplicated effort and conflicting priorities that undermine coherent release forecasting.
↗ the Scrum Guide (2020) + Scrum.org's Product Owner Learning Path and the Evidence-Based Management Guide — Forecasting and Release Strategy

4/5 · Forecasting and Release Strategy · hard

A Product Owner has locked the next three releases into a fixed scope-and-date roadmap to satisfy long-term contractual commitments. As a result, the Developers report they have no slack to explore new technical approaches, run spikes, or respond to emerging opportunities uncovered in Sprint Reviews. Which EBM Key Value Area is most directly being eroded by this practice, and why?

ATime-to-Market, because fixed roadmaps by definition always slow down every single release compared to an unplanned approach.

BCurrent Value, because locking scope and date always causes immediate customer satisfaction to drop regardless of what is delivered.

CAbility to Innovate, because capacity consumed entirely by fixed, pre-committed scope leaves no room to experiment, learn, or pivot in response to new information, undermining the organization's capacity to deliver new value going forward.

DNone of the Key Value Areas are affected, since EBM only measures value already delivered to customers, not internal team practices like technical exploration.

Show answer & explanation

C is correct. Ability to Innovate measures the percentage of capacity available for new work versus maintenance/technical debt/fixed obligations; a roadmap that consumes all capacity in pre-committed fixed scope and dates leaves no slack for experimentation or responding to Sprint Review learning, directly eroding this Key Value Area.
↗ the Scrum Guide (2020) + Scrum.org's Product Owner Learning Path and the Evidence-Based Management Guide — Forecasting and Release Strategy

5/5 · Forecasting and Release Strategy

A B2C mobile app team can technically deploy to production multiple times per day. Adopting a release-on-demand strategy rather than a fixed release cadence would most directly support which EBM outcome, assuming quality and value criteria in the Definition of Done are still met for each release?

AImproved Time-to-Market, because valuable, Done increments can reach users as soon as they are ready rather than waiting for a scheduled release window, shortening the delay between completing value and realizing it.

BElimination of the need for a Definition of Done, since releasing on demand allows the team to ship incomplete work as long as it is released quickly.

CGuaranteed increase in Current Value, because any release, regardless of what it contains, always raises the value currently being delivered to customers.

DImproved Ability to Innovate, because releasing more frequently automatically increases the number of new ideas the Developers generate each Sprint.

Show answer & explanation

A is correct. Release on demand shortens the gap between an increment being Done and reaching users, which is precisely what the Time-to-Market Key Value Area measures, provided the Definition of Done's quality bar is still respected for every release rather than being bypassed for speed.
↗ the Scrum Guide (2020) + Scrum.org's Product Owner Learning Path and the Evidence-Based Management Guide — Forecasting and Release Strategy

Practise all 16 Forecasting and Release Strategy questions - start free → See the whole PSPO II bank

Other PSPO II areas

The same kind of free sample for every other section of the PSPO II bank:

Product Vision and Business Strategy15 q Product Value and Backlog Management at Scale16 q Stakeholder and Customer Engagement15 q Evidence-Based Management16 q Portfolio Planning14 q Organizational Design and Culture14 q

Study Forecasting and Release Strategy with instant feedback

6 free questions · filter study mode by area and difficulty · error log with spaced repetition · no card, no dumps, no ads.

Create your free account →