Study guide
1.4 Events, Artifacts, and Commitments Through the PO Lens
Professional Scrum Product Owner II PSPO II
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview, Scrum Foundations & The Advanced PO Role
1.1 PSPO II Exam Format, Competencies, and Passing Standards 1.2 Empiricism and First Principles in Advanced Product Ownership 1.3 Scrum Values and Accountabilities in Product Decision Making 1.4 Events, Artifacts, and Commitments Through the PO Lens
2 Chapter 2: The Six Product Owner Stances and Anti-Patterns
2.1 The Preferred Product Owner Stances: Visionary, Collaborator, Customer Representative 2.2 The Preferred Product Owner Stances: Decision Maker, Experimenter, Influencer 2.3 Misunderstood Stances: The Clerk, Story Writer, Manager, and Project Manager 2.4 The SME, The Gatekeeper, and Developing Stance Versatility
3 Chapter 3: Product Vision, Strategy, and Business Modeling
3.1 Crafting an Inspiring, Actionable Product Vision 3.2 Business Model Canvas and Lean Canvas for Agile Products 3.3 Strategic Alignment and Competitive Differentiation 3.4 Evolving Product Strategy in Complex Markets
4 Chapter 4: Product Discovery, Hypothesis-Driven Development, and Experiments
4.1 Continuous Product Discovery and Customer Evidence 4.2 Opportunity Solution Trees and Opportunity Mapping 4.3 Hypothesis-Driven Product Development and Experiment Design 4.4 MVPs, Pretotyping, and Pivot vs. Persevere Decisions
5 Chapter 5: Product Goal, Sprint Goal Craftsmanship, and Outcome Alignment
5.1 The Product Goal: Commitment, Scope, and Evolution 5.2 Sprint Goal Craftsmanship and Coherence 5.3 Connecting Strategic Goals, OKRs, and Sprint Goals 5.4 Escaping the Feature Factory: Outcome vs. Output Mindset
6 Chapter 6: Value Definition, Cost of Delay, and Prioritization Techniques
6.1 Multidimensional Product Value 6.2 Cost of Delay and Weighted Shortest Job First (WSJF) 6.3 The Kano Model and Customer Satisfaction Dynamics 6.4 Value vs. Cost Prioritization and Anti-Patterns
7 Chapter 7: Empirical Forecasting, Release Planning, and Agile Contracting
7.1 Empirical Forecasting Using Throughput and Flow Metrics 7.2 Probabilistic Forecasting and Monte Carlo Simulation 7.3 Adaptive Release Planning and Outcome-Based Roadmaps 7.4 Agile Contracting and Collaborative Procurement
8 Chapter 8: Stakeholder Management, Collaboration, and Governance
8.1 Stakeholder Identification and the Mendelow Matrix 8.2 Handling Conflicting Stakeholder Demands and The 'Evidence-Based No' 8.3 The Product Owner as Single Source of Truth for the Backlog 8.4 The Sprint Review as Strategic Working Session
9 Chapter 9: Evidence-Based Management (EBM) and the Four KVAs
9.1 Evidence-Based Management (EBM) Overview and Goal Hierarchy 9.2 Market Value KVAs: Current Value (CV) and Unrealized Value (UV) 9.3 Organizational Capability KVAs: Time-to-Market (T2M) and Ability to Innovate (A2I) 9.4 Applying EBM in Product Decisions and Key Value Measures (KVMs)
10 Chapter 10: Organizational Design, Culture, and Team Topologies
10.1 Organizational Design for Product Agility and Value Streams 10.2 Team Topologies in Product Development 10.3 Fostering an Experimental Culture and Psychological Safety 10.4 Decentralized Decision-Making and Team Autonomy
11 Chapter 11: Scaling Product Ownership (Nexus, LeSS, and Multi-Team Scrum)
11.1 Core Scaling Principles: One Product, One Backlog, One PO 11.2 The Nexus Framework: The Product Owner's Role 11.3 Large-Scale Scrum (LeSS) and Multi-Team Backlog Refinement 11.4 Scaling Anti-Patterns: Component Teams, Proxy POs, and Bureaucracy
12 Chapter 12: Product Lifecycle Management and Agile Portfolio Planning
12.1 Product Lifecycle Stages and Value Strategies 12.2 Dynamic Agile Portfolio Planning and Resource Allocation 12.3 Real Options and Economic Decision-Making in Portfolios 12.4 Product Sunset, Decommissioning, and Sustaining Agility
1.4 Events, Artifacts, and Commitments Through the PO Lens
Key Takeaways Explain This Topic AI
The 2020 Scrum Guide introduced an explicit 1-to-1 commitment for each artifact: the Product Backlog commits to the Product Goal, the Sprint Backlog commits to the Sprint Goal, and the Increment commits to the Definition of Done.
The Product Goal establishes the overarching strategic target for the Scrum Team; the team must fulfill or abandon one Product Goal before committing to the next.
In Sprint Planning, the Product Owner leads Topic 1 ('Why is this Sprint valuable?'), enabling the team to formulate an inspiring, outcome-focused Sprint Goal that guides selection in Topic 2 and technical planning in Topic 3.
The Sprint Review is an active, strategic working session where the Scrum Team and stakeholders collaboratively inspect the Increment, analyze external market shifts, and adapt the Product Backlog.
The Product Owner holds the exclusive authority to cancel a Sprint, which should occur only when the Sprint Goal becomes obsolete due to major market, legal, or strategic disruptions.
Last updated: September 2026
1.4 Events, Artifacts, and Commitments Through the PO Lens
Quick Answer: The 2020 Scrum Guide unified the Scrum framework by pairing each of the three artifacts with a singular, binding commitment : the Product Backlog commits to the Product Goal ; the Sprint Backlog commits to the Sprint Goal ; and the Increment commits to the Definition of Done . These commitments ensure empirical transparency. For the Product Owner, Scrum events are not mechanical ceremonies, but strategic feedback loops designed to inspect market evidence and adapt product direction.
The Triad of Artifacts and Commitments (Scrum Guide 2020)
A major breakthrough in the 2020 Scrum Guide was the formal introduction of Commitments attached to each artifact. These commitments provide clear focus, enhance transparency, and eliminate ambiguity regarding the purpose of each artifact: +-----------------------+-----------------------+---------------------------------+
- | SCRUM ARTIFACT | BINDING COMMITMENT | PRIMARY STRATEGIC LENS |
- +-----------------------+-----------------------+---------------------------------+
- | Product Backlog | Product Goal | Long-term strategic milestone. |
- | Sprint Backlog | Sprint Goal | Short-term Sprint objective. |
- | Increment | Definition of Done | Non-negotiable quality barrier. |
- +-----------------------+-----------------------+---------------------------------+
- 1. Product Backlog & The Product Goal
The Commitment: The Product Goal describes a future state of the product that serves as a target for the Scrum Team to plan against. It represents the overarching, measurable business or user outcome the team is currently striving to achieve.
Operational Rules: The Scrum Team must fulfill or abandon one Product Goal before taking on the next . This prevents the fragmentation of team focus across dozens of competing initiatives.
PO Strategic Lens: The Product Goal is the Product Owner's ultimate weapon against backlog bloat. It provides the objective filter for ordering items: does a proposed feature help achieve the current Product Goal? If not, it is deferred, de-prioritized, or eliminated.
2. Sprint Backlog & The Sprint Goal
The Commitment: The Sprint Goal is the single objective for the Sprint, formulated collaboratively during Sprint Planning.
Operational Rules: While the forecast of items (the What ) and the technical plan (the How ) may evolve as Developers learn more during the Sprint, the Sprint Goal does not change . If the work turns out to be different than expected, the Developers collaborate with the Product Owner to negotiate the scope of the Sprint Backlog without compromising the Sprint Goal.
PO Strategic Lens: A well-crafted Sprint Goal provides the team with coherence and autonomy . Instead of feeling bound to an arbitrary list of tickets, the Developers are empowered to find the most efficient path to deliver the business value represented by the Sprint Goal.
3. Increment & The Definition of Done
The Commitment: The Definition of Done (DoD) is a formal description of the state of the Increment when it meets the quality measures required for the product.
Operational Rules: The moment a Product Backlog item meets the Definition of Done, an Increment is born. Work cannot be released, or even presented at the Sprint Review, unless it strictly adheres to the DoD.
PO Strategic Lens: The DoD creates transparency and protects the product from hidden technical debt. An advanced PO never pressures Developers to compromise the Definition of Done to hit a date. Releasing undone work compromises stability, increases total cost of ownership, and destroys the empirical foundation of the product.
Sprint Planning Through the PO Lens: The Three Essential Topics
Sprint Planning initiates the Sprint by laying out the work to be performed. The 2020 Scrum Guide organizes Sprint Planning into three sequential topics: +------------------------------------------------+
- | TOPIC 1: WHY IS THIS SPRINT VALUABLE? |
- | PO proposes value; Team crafts Sprint Goal. |
- +-----------------------+------------------------+
- |
- v
- +------------------------------------------------+
- | TOPIC 2: WHAT CAN BE DONE THIS SPRINT? |
- | Developers forecast PBIs supporting the Goal. |
- +-----------------------+------------------------+
- |
- v
- +------------------------------------------------+
- | TOPIC 3: HOW WILL WORK GET DONE? |
- | Developers design architecture and plan work. |
- +------------------------------------------------+
Topic 1: Why is this Sprint valuable?
The PO's Leadership: The Product Owner opens Sprint Planning by explaining how the product could increase its value and utility in the current Sprint. The PO presents the business context, current market feedback, and target Product Goal.
Collaborative Output: The entire Scrum Team (PO, Developers, Scrum Master) collaborates to define a Sprint Goal that articulates why the Sprint is valuable to stakeholders and users.
Topic 2: What can be Done this Sprint?
Developer Forecasting: The Developers select items from the Product Backlog that support the agreed-upon Sprint Goal.
The PO's Role: The PO clarifies requirements, resolves ambiguities, and negotiates trade-offs. However, the Developers alone forecast how many items they can complete , basing their decision on past performance, upcoming capacity, and the Definition of Done. The PO never imposes a quota of story points or tickets.
Topic 3: How will the chosen work get done?
Developer Implementation Planning: For each selected Product Backlog item, the Developers plan the necessary work (often decomposing items into technical tasks of one day or less).
The PO's Role: The PO remains accessible to answer questions and negotiate scope adjustments if the Developers realize that the required technical effort exceeds their capacity.
The Strategic Sprint Review: Working Session vs. Passive Demo
The Sprint Review is perhaps the most misunderstood event in Scrum. In low-maturity organizations, it degenerates into a superficial "dog and pony show"—a one-way PowerPoint presentation or passive screen-share demo where Developers show completed code and stakeholders remain silent.
An authentic, advanced Sprint Review is an active, high-stakes strategic working session . Its purpose is to inspect the outcome of the Sprint and determine future adaptations .
The Five Essential Elements of an Advanced Sprint Review
Review of Value Delivered: The Product Owner summarizes what Product Backlog items have been "Done" and what has "Not Done." The PO explicitly links the completed Increment back to the Product Goal.
Hands-On Inspection of the Increment: Stakeholders and the Scrum Team interact with the functional software in a production-like environment, evaluating actual user experience and utility.
Inspection of External Market Conditions: The PO presents external context: changes in market conditions, competitor releases, budget and burn updates, organizational shifts, and telemetry data captured from previous releases.
Review of Evidence-Based Metrics (EBM): The PO shares key metrics across Current Value (customer satisfaction, usage trends) and Time-to-Market.
Collaborative Backlog Adaptation: The attendees collaborate on what to do next. The Product Backlog is adjusted on the spot to seize newly discovered market opportunities or address emerging risks.
Tip
The tangible output of an effective Sprint Review is not a polite round of applause; it is an updated Product Backlog that reflects the latest empirical reality.
The Product Owner in the Sprint Retrospective
The Sprint Retrospective is often incorrectly viewed as an "engineering-only" meeting where Developers discuss technical tooling. In Professional Scrum, the Product Owner is an essential, full participant in the Sprint Retrospective .
During the Retrospective, the Scrum Team inspects how the last Sprint went with respect to individuals, interactions, processes, tools, and their Definition of Done. The PO brings unique value to this event:
Inspecting Value Flow & Slicing: Investigating whether Product Backlog items were sliced too large, leading to bottlenecks during the Sprint.
Refining Collaboration Mechanisms: Examining friction between the PO, Developers, and external stakeholders during backlog refinement.
Addressing Quality & Technical Debt: Collaborating with Developers to understand how technical debt is eroding the team's Ability to Innovate (A2I), and allocating backlog capacity in future Sprints to pay down architectural debt.
Living the Scrum Values: Openly discussing whether the team had the Courage to raise impediments or if external stakeholders exerted undue pressure during the Sprint.
Sprint Cancellation: The Product Owner's Exclusive Authority
Sprint cancellation is the ultimate emergency brake in Scrum. Because Sprints are short, timeboxed intervals (1 to 4 weeks), cancellation is rare. However, understanding its mechanics is heavily tested on PSPO II: +--------------------------------------------------------------------------+
- | SPRINT CANCELLATION PROTOCOL |
- +--------------------------------------------------------------------------+
- | 1. TRIGGER: Sprint Goal becomes obsolete due to external disruption. |
- | 2. SOLE AUTHORITY: Only the Product Owner can cancel the Sprint. |
- | 3. INSPECTION: Review completed items meeting Definition of Done. |
- | 4. RECOVERY: Incomplete items return to Product Backlog. |
- | 5. RESTART: Immediately convene new Sprint Planning session. |
- +--------------------------------------------------------------------------+
- Legitimate Grounds for Sprint Cancellation
A Sprint can be cancelled ONLY if the Sprint Goal becomes obsolete . Examples of valid cancellation triggers include:
Radical Market Shifts: A competitor launches a disruptive technology that renders the feature being built entirely valueless.
Regulatory or Legal Interventions: A new government data-privacy ruling makes the system architecture currently being implemented illegal.
Strategic Corporate Pivots: The company is acquired or leadership terminates the entire product line.
Severe Technological Invalidation: A core third-party platform upon which the Sprint Goal depends goes bankrupt or permanently terminates its APIs.
Caution
A Sprint is NEVER cancelled simply because the Developers realize they cannot finish all planned items, because velocity is behind schedule, or because the team encountered unexpected technical complexity. In those cases, the Developers and PO collaborate to reduce the scope of work while continuing to pursue the Sprint Goal.
The Formal Cancellation Protocol
Exclusive Authority: Only the Product Owner has the authority to cancel a Sprint. Stakeholders, managers, and Developers may strongly advise the PO, but the final decision rests solely with the PO.
Disposition of Completed Work: Any Product Backlog items that meet the Definition of Done are inspected. If they represent valuable, releasable functionality, the PO may accept them.
Disposition of Incomplete Work: All incomplete items are put back onto the Product Backlog, re-estimated, and re-ordered in light of new market facts.
Immediate Re-Planning: The team does not wait for the original Sprint timebox to expire. They immediately hold a new Sprint Planning session to establish a new Sprint Goal and begin a fresh Sprint.