SkarpChapter 20 of 21
Integrating Scrum Theory, Values, and Practice for Exam Scenarios
Bring together theory, values, events, and roles to reason through nuanced PSM I-style questions where more than one answer looks plausible at first glance.
Scrum-Consistent vs. Plausible-Sounding Answers
Why Many Answers Look Right
PSM I questions often include several options that sound reasonable. Your edge is spotting which one is most Scrum-consistent, not just "not wrong".
Empiricism First
Remember: Scrum is founded on empiricism and lean thinking. Look for answers that increase transparency, inspection, and adaptation in complex work.
Framework, Not Methodology
Scrum defines accountabilities, events, artifacts, and commitments, but leaves many practices open. Beware answers that add rules as if they were part of Scrum.
The 3-Question Lens
Ask: 1) What does the Scrum Guide actually say? 2) What aligns with empiricism and Scrum values? 3) Which option reduces self-management or adds non-Scrum rules?
Anchor: What Scrum Explicitly Defines (For Exam Reasoning)
Why Canonical Phrases Matter
The exam is based on the current Scrum Guide. Options that closely match its wording usually beat vague or organization-specific language.
Core Accountabilities
Memorize these exact lines: Product Owner, Scrum Master, Developers definitions. They are frequent exam anchors and eliminate many distractors.
Core Artifacts & Commitments
Remember the exact phrases for Product Backlog, Sprint Backlog, Increment, Product Goal, Sprint Goal, Definition of Done.
Using Definitions in Questions
If an option contradicts or rewrites these definitions, reject it. If it aligns and supports empiricism and values, it is usually strong.
Using Scrum Values to Break Ties
Scrum Values as a Filter
When multiple answers fit the Scrum Guide, use the five values: commitment, focus, openness, respect, courage to pick the best fit.
Protecting Goals and Quality
Prefer options that support commitment to the Product Goal, Sprint Goal, and Definition of Done, rather than encouraging shortcuts or side work.
Self-Management and Respect
Respectful answers treat the Scrum Team as professionals and keep them self-managing, instead of micromanaged or blamed.
Spotting Anti-Values
If an option hides problems, manipulates metrics, or pushes overtime as default, it clashes with openness, respect, and courage.
Scenario 1: Sprint Scope Change and Self-Management
Scenario Setup
Mid-Sprint, a new urgent PBI appears. Sprint Goal is still valid. The Product Owner asks the Scrum Master what to do. Several answers look plausible.
Key Scrum Facts
Sprint Goal is fixed; scope is negotiable. Developers own the Sprint Backlog. Scrum Master facilitates; they do not command the Developers.
Option Analysis
1: Scrum Master commands work. 2: Claims scope cannot change (false). 3: Facilitated negotiation. 4: Scrum Master edits Sprint Backlog alone.
Why Option 3 Wins
Option 3 supports empiricism and values, respects self-management, and follows the Guide's rule: scope can be adjusted with PO–Developer collaboration.
Thought Exercise: Spot the Hidden Non-Scrum Rule
Your Task
For each statement, decide: A. Explicit Scrum rule, or B. Common practice but not defined by Scrum. Then compare with the explanations.
Statements 1–2
- Daily Scrum must be standing and exactly 15 minutes. 2. Only the Product Owner can cancel a Sprint. Which are true Scrum rules?
Statements 3–5
- Team must use story points. 4. Sprint length fixed, at most one month. 5. Scrum Master personally removes all impediments.
What This Trains
You are training your eye to spot non-Scrum rules. On the exam, prefer options that stick to the framework and its intent.
Scenario 2: Transparency vs. Local Optimization
Scenario Setup
Management wants per-person velocity targets. Developers consider gaming the system. Product Owner is worried about quality. What should the Scrum Master do?
Key Scrum Concepts
Scrum stresses transparency and quality via the Definition of Done. Velocity is optional; per-person velocity often harms empiricism.
Option Analysis
1: Supports gaming. 2: Coaches against misusing metrics. 3: Weakens Definition of Done. 4: Avoids an important conversation.
Why Option 2 Wins
Option 2 shows courage and openness, supports transparency and quality, and fulfills the Scrum Master's accountability to establish Scrum.
Quiz 1: Events and Adaptation Edge Cases
Apply Scrum theory and values to tricky event-related questions.
During the Sprint, the Developers realize they will not complete all selected Product Backlog items, but the Sprint Goal is still achievable. What is the BEST action according to Scrum?
- Ask the Product Owner to extend the Sprint by a few days so all planned items can be completed.
- Update the Sprint Backlog, collaborate with the Product Owner on which items to drop, and continue focusing on the Sprint Goal.
- Cancel the Sprint because the original plan cannot be met.
- Work overtime to complete all items, since the Sprint Backlog cannot change after Sprint Planning.
Show Answer
Answer: B) Update the Sprint Backlog, collaborate with the Product Owner on which items to drop, and continue focusing on the Sprint Goal.
Sprints have a fixed length and are not extended (so A is wrong). The Sprint Backlog is a living plan owned by Developers and can be updated throughout the Sprint. If the Sprint Goal is still achievable, the Sprint is not cancelled (so C is wrong). Working overtime as a default solution conflicts with respect and sustainability (D). The best Scrum-consistent answer is to adapt the Sprint Backlog, collaborating with the Product Owner, while keeping focus on the Sprint Goal (B).
Quiz 2: Accountabilities and Decision Rights
Check your understanding of who decides what in Scrum.
A stakeholder insists that the Scrum Master should approve all changes to the Product Backlog to ensure technical feasibility. Which response is MOST aligned with Scrum?
- Agree, because the Scrum Master protects the Developers from unrealistic Product Backlog items.
- Decline, explaining that the Product Owner is accountable for the Product Backlog, while Developers ensure feasibility through collaboration.
- Suggest that the Scrum Master and Product Owner share accountability for the Product Backlog to improve decision quality.
- Accept temporarily, because stakeholders must be satisfied first, then coach them later.
Show Answer
Answer: B) Decline, explaining that the Product Owner is accountable for the Product Backlog, while Developers ensure feasibility through collaboration.
The Product Owner is accountable for maximizing product value and for the Product Backlog. Developers collaborate to ensure feasibility. The Scrum Master is accountable for establishing Scrum, not for approving Product Backlog changes. So B correctly reflects accountabilities. A and C reassign Product Backlog accountability. D trades clear Scrum accountabilities for stakeholder comfort.
Key Concept Flashcards: Theory, Values, and Practice
Use these flashcards to solidify core ideas that help you choose Scrum-consistent answers.
- Empiricism in Scrum
- Scrum is founded on empiricism and lean thinking. Empiricism means decisions are based on transparency, inspection, and adaptation in complex, uncertain environments.
- Definition of Done (exam importance)
- The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. Options that weaken or bypass it are usually wrong.
- Sprint Backlog ownership
- The Sprint Backlog belongs to the Developers. It includes the Sprint Goal (why), selected PBIs (what), and plan (how). Others can influence, but Developers decide how to achieve the Sprint Goal.
- Scope change during a Sprint
- While the Sprint Goal is fixed, scope can be negotiated between Product Owner and Developers during the Sprint, as long as the Sprint Goal remains achievable.
- Scrum Master accountability
- The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, primarily through coaching, facilitation, and enabling organizational change, not command-and-control.
- Scrum vs. organization-specific practices
- Scrum defines accountabilities, events, artifacts, and commitments. Practices like story points, standing meetings, or specific tools are optional and must not be treated as Scrum rules in exam answers.
- Using Scrum values to choose answers
- When multiple options fit the Guide, prefer the one that best supports commitment, focus, openness, respect, and courage, especially around transparency and self-management.
- Product Owner accountability
- The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team, including ordering the Product Backlog and managing stakeholders.
A Repeatable 4-Step Method for PSM Scenario Questions
Step 1: Find the Core Topic
Ignore fluff. Ask: Is this really about events, artifacts, accountabilities, or values/behavior? That narrows which Scrum rules matter.
Step 2: Recall the Rule
Mentally quote the relevant Scrum Guide line: Sprint length, who owns what, who can cancel a Sprint, what each artifact is, etc.
Step 3: Values & Empiricism
Among rule-consistent options, choose the one that boosts transparency, inspection, adaptation, and the five Scrum values.
Step 4: Spot Extra Rules
Reject options that add non-Scrum rules, reduce self-management, hide problems, or weaken the Definition of Done.
Key Terms
- Scrum
- Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
- Sprint
- Sprints are the heartbeat of Scrum, where ideas are turned into value.
- Increment
- An Increment is a concrete stepping stone toward the Product Goal.
- Developers
- Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.
- Scrum Team
- The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal.
- empiricism
- Scrum is founded on empiricism and lean thinking.
- Sprint Goal
- The Sprint Goal is the single objective for the Sprint.
- Product Goal
- The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against.
- Scrum Master
- The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide.
- Scrum values
- The five values of Scrum are commitment, focus, openness, respect, and courage; they guide behavior and decision-making within the Scrum framework.
- Product Owner
- The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
- Sprint Backlog
- The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).
- Product Backlog
- The Product Backlog is an emergent, ordered list of what is needed to improve the product.
- Definition of Done
- The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.