Study guide

1.3 Living the Scrum Values Under Pressure

Professional Scrum Master II PSM II

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview, Empiricism & Advanced Framework Mechanics

1.1 PSM II Assessment Architecture, Scoring, and Advanced Mindset 1.2 Empiricism in Complex Environments 1.3 Living the Scrum Values Under Pressure

2 Chapter 2: Scrum Accountabilities & Team Self-Management

2.1 The Three Accountabilities in Deep Context 2.2 Fostering Self-Managing & Cross-Functional Teams 2.3 Anti-Patterns in Accountabilities

3 Chapter 3: The 8 Stances of the Scrum Master

3.1 Core Enabling Stances: Servant Leader & Manager 3.2 Developing Stances: Teacher, Mentor & Coach 3.3 Delivery Stances: Facilitator & Impediment Remover 3.4 Transformational Stance: Change Agent & Ineffective Stances

4 Chapter 4: Advanced Team Dynamics & Psychological Safety

4.1 Building Psychological Safety & Trust 4.2 Navigating Team Development & Dysfunctions 4.3 Conflict Resolution & Liberating Structures

5 Chapter 5: Managing Products with Agility & Product Owner Coaching

5.1 Coaching the Product Owner on Vision & Product Goal 5.2 Product Backlog Health, Ordering & Splitting 5.3 Stakeholder Engagement & Collaboration Without Feature Factories

6 Chapter 6: Evidence-Based Management (EBM) & Agility Metrics

6.1 EBM Framework Architecture & Strategic Loop 6.2 Market Value: Current Value (CV) & Unrealized Value (UV) 6.3 Organizational Capability: Time-to-Market (T2M) & Ability to Innovate (A2I) 6.4 Designing Agility Metrics vs. Vanity Metrics

7 Chapter 7: Artifacts, Commitments & Definition of Done

7.1 The Three Commitments & Empirical Artifact Transparency 7.2 Crafting and Evolving the Definition of Done 7.3 Definition of Done in Regulated & Complex Environments 7.4 Managing Technical Risk, Technical Debt & Engineering Excellence

8 Chapter 8: Advanced Events & Facilitation in Practice

8.1 Advanced Sprint Planning & Meaningful Sprint Goals 8.2 The Daily Scrum & Sprint Review as Empirical Feedback Loops 8.3 Actionable Sprint Retrospectives & Continuous Improvement

9 Chapter 9: Scaling Scrum & Organizational Agility

9.1 Scaling Fundamentals & Nexus Framework 9.2 Nexus Events & Multi-Team Dependency Management 9.3 Organizational Design, Culture & Removing Impediments Beyond the Team 9.4 Agile Budgeting, Contracts & Governance

1.3 Living the Scrum Values Under Pressure

Key Takeaways Explain This Topic AI

The five Scrum Values—Commitment, Courage, Focus, Openness, and Respect—provide the ethical and behavioral foundation that enables the empirical pillars of Scrum to function.

Under acute organizational stress, traditional organizations reflexively abandon core values for command-and-control shortcuts, converting Scrum into empty mechanical rituals.

In Scrum, commitment means dedicating oneself to the Sprint Goal, professional quality, and team collaboration, not promising fixed scope under arbitrary deadlines.

Courage empowers practitioners to speak truth to power, say 'no' to unachievable mandates, surface technical debt, and halt work when quality standards are compromised.

Respect and Openness require treating team members as capable, autonomous professionals and making all impediments, trade-offs, and empirical realities completely visible to stakeholders.

Last updated: October 2026

Living the Scrum Values Under Pressure

Note

Successful use of Scrum depends on people becoming more proficient in living five values: Commitment, Focus, Openness, Respect, and Courage. When these values are embodied by the Scrum Team and the people they interact with, the empirical Scrum pillars of transparency, inspection, and adaptation come to life and build trust.

The Behavioral Foundation of Empirical Agility

Many organizations adopt the surface mechanics of Scrum—cadenced iterations, standup meetings, backlogs, and burn-down charts—yet fail to realize meaningful business agility. This condition, frequently termed "Mechanical Scrum" or "Zombie Scrum," occurs when framework ceremonies are executed in a cultural vacuum devoid of the five Scrum Values.

Without the Scrum Values, Scrum's empirical engine quickly breaks down:

Without Openness , transparency is impossible because team members conceal mistakes, roadblocks, and technical debt to protect themselves.

Without Courage , practitioners will not speak truth to power, challenge flawed architectural directives, or refuse unachievable deadlines.

Without Respect , management treats Developers as interchangeable cogs rather than autonomous knowledge workers capable of creative problem-solving.

Without Focus , the team's cognitive capacity is fragmented by context switching, endless side projects, and ad-hoc executive demands.

Without Commitment , the Sprint Goal is treated as a disposable suggestion rather than a shared professional objective.

The Scrum Values are not sentimental platitudes; they are the operational safeguards that keep empiricism alive when fear, corporate politics, and delivery stress threaten to derail the team.

The Five Scrum Values Deconstructed Under Pressure

To pass the PSM II assessment, a candidate must distinguish between superficial, traditional interpretations of these values and their principled application under pressure:

1. Commitment

Traditional Misconception: Committing to deliver 50 story points at all costs, working 70-hour weeks, and sacrificing testing to ensure every planned item is finished.

Empirical Application: Committing to achieving the Sprint Goal , adhering uncompromisingly to the Definition of Done , supporting fellow team members, and delivering the highest possible customer value within sustainable working limits.

Pressure Scenario: When unexpected technical obstacles make completing all items in the Sprint Backlog impossible, the team demonstrates commitment by swarming on the Sprint Goal and collaborating with the Product Owner to drop lower-value items, rather than cutting quality to finish everything poorly.

2. Courage

Traditional Misconception: "Heroic" martyrdom—accepting impossible deadlines without objection, working through illness, or keeping quiet when leadership mandates poor architectural choices.

Empirical Application: The courage to say "no" to unsustainable demands, speak truth to senior leadership, deliver bad news early, admit when an estimate was wrong, and halt deployment when software does not meet the Definition of Done.

Pressure Scenario: An executive demands an immediate off-cadence deployment of untested code to secure a contract. A courageous Scrum Master and Product Owner defend the Definition of Done, explain the systemic operational risks, and offer viable, empirical alternatives.

3. Focus

Traditional Misconception: Keeping every developer 100% busy on separate tasks so no resource has downtime.

Empirical Application: Directing the collective energy of the entire Scrum Team toward the Sprint Goal and completing high-priority items before starting new ones (limiting Work-in-Progress).

Pressure Scenario: Mid-Sprint, multiple departments flood Developers with urgent side requests. The Scrum Master guides the team to maintain focus on the Sprint Goal and routes all incoming requests to the Product Owner for transparent ordering in the Product Backlog.

4. Openness

Traditional Misconception: Sharing sanitized progress summaries that portray everything as smooth while hiding internal turmoil.

Empirical Application: Complete, unvarnished visibility into progress, impediments, architectural fragility, assumptions, and mistakes with both internal peers and external stakeholders.

Pressure Scenario: The team discovers mid-Sprint that a core third-party integration is fundamentally broken. Openness requires alerting the Product Owner and stakeholders immediately, rather than waiting for an unpleasant surprise at the Sprint Review.

5. Respect

Traditional Misconception: Polite deference to corporate hierarchy, never disagreeing with managers, and avoiding uncomfortable discussions.

Empirical Application: Treating team members as capable, intelligent, autonomous professionals; respecting the Developers' accountability for how work is built; respecting the Product Owner's accountability for what is built; and respecting customers by delivering dependable, well-tested software.

Pressure Scenario: When a release misses an ambitious delivery forecast, management resists the urge to micromanage or blame individuals, instead respecting the team's professional diagnosis and collaborating to eliminate systemic organizational impediments.

Values Under Normal Conditions vs. Under Pressure

The table below demonstrates how the Scrum Values manifest during ordinary operations versus how they must be defended during high-stress organizational crises:

Scrum Value Behavior Under Normal Conditions Anti-Pattern Under Severe Pressure Principled Scrum Master Stance

Commitment The team collaborates to complete selected backlog items and meet the Sprint Goal. Developers cut corners on unit tests, documentation, and reviews to claim all items are "Done." Reframes commitment around quality and the Sprint Goal; insists that work is only Done if it meets the Definition of Done.

Courage Team members share ideas and volunteer for complex user stories during Sprint Planning. Team members stay silent about fatal architectural flaws or impossible deadlines out of fear of executive reprimand. Cultivates psychological safety; models transparent, respectful dissent; encourages early disclosure of bad news.

Focus The team works on Sprint Backlog items sequentially with minimal outside interruption. Developers multitask across several side projects, handle unplanned ad-hoc tickets, and abandon the Sprint Goal. Protects team focus by routing unplanned requests to the Product Owner; helps Developers limit Work-in-Progress (WIP).

Openness Team members share standard daily progress updates during the Daily Scrum. Team conceals impediments and presents misleading "Green" status reports to external leadership. Surfaces reality on transparent physical or digital radiators; teaches leadership that early bad news is a valuable risk-reduction asset.

Respect Colleagues listen to each other's opinions during technical design discussions. Managers assign blame to specific individuals, mandate 14-hour days, or dictate exact technical implementation. Intervenes to uphold team self-management; coaches managers on treating Developers as creative knowledge workers.

  • In-Depth Case Studies: Scrum Values in the Crucible
  • Case Study 1: The Executive Weekend Crunch

Scenario: Two days before the end of Sprint 14, the Vice President of Marketing discovers that a major industry trade show was rescheduled two weeks earlier than expected. The VP approaches the Scrum Team and demands that the Developers work through the weekend to finish three additional high-priority marketing features that were not part of the Sprint Backlog. The VP warns that refusing will harm company revenue and will be viewed as a lack of dedication.

Analysis and Resolution:

Values at Stake: Commitment, Respect, Focus.

The Anti-Pattern: Submitting to executive intimidation, abandoning the Sprint Goal, working unsustainable hours, and delivering rushed, unverified code.

Principled Scrum Master Action: The Scrum Master steps in to protect the team from external disruption. The Scrum Master reminds the VP that the Developers are already committed to their agreed Sprint Goal and that sustainable pace is essential for long-term quality. The Scrum Master facilitates an immediate conversation between the VP and the Product Owner. The Product Owner can inspect what is currently "Done" in the Increment and determine whether a viable, high-quality subset of functionality can be showcased at the trade show, or negotiate what trade-offs can be made for the next Sprint.

Case Study 2: The Shortcut Dilemma

Scenario: The Developers encounter a severe performance latency issue in a new checkout microservice during Sprint 8. Fixing the issue properly requires refactoring the database indexing strategy, which will take three days and make it impossible to deliver two other customer-facing stories in the Sprint Backlog. The Product Owner argues: "The stakeholders only care about seeing the checkout flow work during tomorrow's demo. Comment out the latency validation checks just for the demo, call the items 'Done', and we will fix the database in the next Sprint."

Analysis and Resolution:

Values at Stake: Courage, Openness, Commitment.

The Anti-Pattern: Faking a demo, degrading the Definition of Done, hiding technical debt, and misleading stakeholders.

Principled Scrum Master Action: The Scrum Master coaches the Product Owner and Developers that presenting an illusion of functionality violates Openness and destroys the transparency required for empirical inspection. The Scrum Master supports the Developers in upholding their Definition of Done. The team demonstrates Courage by showing the working components honestly at the Sprint Review, openly explaining the latency impediment and the required database refactoring to stakeholders. This empirical transparency allows stakeholders to provide realistic guidance rather than making business decisions based on a false perception of progress.

Case Study 3: The Daily Scrum Interrogation

Scenario: An Engineering Manager joins the Daily Scrum. When a junior developer reports being stuck on an API authentication task for the second day, the Engineering Manager interrupts, sharply questioning the developer's competence in front of the team: "Why hasn't this been finished yet? I could have written this code in two hours. You are holding up the entire release schedule." The room falls silent, and team members look down at their desks.

Analysis and Resolution:

Values at Stake: Respect, Courage, Openness.

The Anti-Pattern: Micromanagement, public shaming, hijacking the Daily Scrum, and shattering psychological safety.

Principled Scrum Master Action: The Scrum Master immediately intervenes to restore safety and purpose. The Scrum Master politely reminds the manager that the Daily Scrum is an event for the Developers to inspect progress toward their Sprint Goal and plan their next 24 hours, not a status meeting or performance evaluation. After the Daily Scrum concludes, the Scrum Master meets privately with the Engineering Manager to coach them on Respect and the devastating impact of public reprimands on psychological safety. The Scrum Master then checks in with the junior developer and facilitates peer swarming to resolve the technical API blocker.