Study guide

2.1 The Three Accountabilities in Deep Context

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

2.1 The Three Accountabilities in Deep Context

Key Takeaways Explain This Topic AI

The 2020 Scrum Guide deliberately replaced the term 'roles' with 'accountabilities' to eliminate corporate title confusion, hierarchy, and internal team divides.

The Scrum Master is accountable for team effectiveness and establishing Scrum according to the Scrum Guide, operating as a true leader without managerial authority over tasks or people.

The Product Owner is the sole person accountable for maximizing product value and managing the Product Backlog; they are an individual, never a committee.

Developers are collectively accountable for creating a usable Increment that meets the Definition of Done each Sprint, sizing their work, and adapting their technical plan daily toward the Sprint Goal.

Crisp boundaries govern inter-accountability dynamics: Product Owners define value and priorities, Developers own technical execution and estimation, and the Scrum Master guards empirical process integrity.

Last updated: October 2026

2.1 The Three Accountabilities in Deep Context

In complex product delivery environments, organizational friction frequently stems from ambiguity over who decides what, who owns quality, and who is authorized to make trade-offs. The 2020 revision of the Scrum Guide introduced a deliberate and profound linguistic evolution: replacing the legacy term "roles" with "accountabilities." While some dismissed this as cosmetic semantics, the shift addresses a pervasive systemic failure in enterprise Agile adoptions—the conflation of Scrum roles with human resources job titles, corporate status hierarchies, and external command-and-control structures.

The Evolutionary Shift: From Roles to Accountabilities

Under previous editions of the framework, organizations routinely mapped Scrum roles directly onto existing corporate job descriptions. Project managers became Scrum Masters; lead business analysts or vice presidents were appointed Product Owners; and functional programmers were labeled Developers, while quality assurance testers, technical writers, and database administrators were treated as second-class adjuncts or retained in separate functional silos. This dynamic fostered destructive dysfunctions:

Title Conflation: Individuals clung to their functional identity ("I am a QA analyst, so I do not write automated unit tests, inspect configuration code, or help with deployments").

Sub-Team Hierarchies: Scrum Masters operated as line managers assigning tasks, or Product Owners functioned as remote steering committees dictating how technical work should be executed.

Diffused Ownership: When defects escaped to production, programmers blamed testers, testers blamed analysts, and the Scrum Master acted as an administrative referee rather than an agile coach.

By redefining the framework around three specific accountabilities within a single Scrum Team , Scrum establishes that there are no sub-teams, no corporate hierarchies, and no second-class contributors. The Scrum Team is a cohesive unit of professionals focused on one objective at a time: the Product Goal. Within this unified team, each accountability provides a necessary checks-and-balances counterweight to ensure empiricism thrives under pressure.

The Scrum Master: Accountable for Team Effectiveness

The Scrum Guide defines the Scrum Master as accountable for establishing Scrum as defined in the Scrum Guide and accountable for the Scrum Team's effectiveness . They accomplish this by enabling the Scrum Team to improve its practices, within the Scrum framework.

Crucially, the Scrum Master is a true leader who serves the Scrum Team and the larger organization . This differs radically from traditional management in several foundational ways:

Dimension Traditional Project Manager Scrum Master (True Leader)

Authority Basis Positional authority, task delegation, performance reviews Influence, coaching, facilitation, empirical transparency

Primary Focus Managing schedules, Gantt charts, budgets, status reports Cultivating team self-management, effectiveness, and continuous improvement

Impediment Handling Solving problems directly via directive intervention Empowering the team to solve their own challenges while removing organizational barriers

Team Relationship Directs who does what, when, and how Guards framework boundaries and facilitates empirical inspection and adaptation

The 2020 Scrum Guide lists the Scrum Master's service to three audiences (wording below follows the Guide closely):

Serving the Scrum Team: Coaching the team members in self-management and cross-functionality; helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done; causing the removal of impediments to the Scrum Team's progress; and ensuring that all Scrum events take place and are positive, productive, and kept within the timebox.

Serving the Product Owner: Helping find techniques for effective Product Goal definition and Product Backlog management; helping the Scrum Team understand the need for clear and concise Product Backlog items; helping establish empirical product planning for a complex environment; and facilitating stakeholder collaboration as requested or needed.

Serving the Organization: Leading, training, and coaching the organization in its Scrum adoption; planning and advising Scrum implementations within the organization; helping employees and stakeholders understand and enact an empirical approach for complex work; and removing barriers between stakeholders and Scrum Teams.

The Product Owner: Accountable for Maximizing Product Value

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team . How this is done may vary widely across organizations, domains, and teams, but the core mechanics remain invariant: the Product Owner is the sole person accountable for effective Product Backlog management .

This includes:

  • Developing and explicitly communicating the Product Goal;
  • Creating and clearly communicating Product Backlog items;
  • Ordering Product Backlog items to optimize value, risk, and dependencies;

Ensuring that the Product Backlog is transparent, visible, and understood.

Navigating Real-World Pressures

On the PSM II assessment, scenario questions frequently probe whether the Product Owner possesses authentic empowerment or merely functions as a puppet for executive stakeholders. Scrum mandates that:

"The Product Owner is one person, not a committee. The Product Owner may represent the needs of many stakeholders in the Product Backlog. Those wanting to change the Product Backlog can do so by trying to convince the Product Owner."

When organizations subvert this principle, predictability and value collapse:

Steering Committees and HiPPO Bias: When executive steering committees or the Highest Paid Person's Opinion (HiPPO) override the Product Owner's ordering, Developers are pulled in conflicting directions, and empirical forecasting becomes impossible.

The Proxy Trap: If the named Product Owner must seek external authorization from a business sponsor before answering developer questions or accepting an Increment, decision latency escalates sharply.

Delegation vs. Accountability: While the Product Owner may delegate certain backlog drafting activities to Developers or business analysts, the Product Owner remains strictly accountable for the decisions and the economic consequences.

Developers: Accountable for the Usable Increment and Quality

In Scrum, the term "Developers" does not refer exclusively to software engineers or programmers. It encompasses any professional committed to creating any aspect of a usable Increment each Sprint . In cross-functional environments, Developers include UX designers, quality engineers, database specialists, security analysts, technical writers, and domain researchers.

Developers are collectively accountable for:

Creating a Plan for the Sprint (the Sprint Backlog): Developers select how much work to pull from the Product Backlog and decide how to decompose that work into actionable items. No one outside the Developers—not even the Scrum Master or Product Owner—can dictate what is placed in the Sprint Backlog or how many hours a task will take.

Instilling Quality by Adhering to a Definition of Done: Quality is never an afterthought or a deferred phase. Developers own the technical integrity of the product. They cannot unilaterally lower or compromise the Definition of Done under schedule pressure.

Adapting Their Plan Daily Toward the Sprint Goal: During the Daily Scrum, Developers inspect their progress and adjust their upcoming work plan to optimize the likelihood of achieving the Sprint Goal.

Holding Each Other Accountable as Professionals: Peer accountability replaces managerial oversight. If a team member struggles or cuts corners, Developers address the issue directly within the team rather than waiting for an external supervisor to intervene.

Inter-Accountability Boundaries and Tension Points

The effectiveness of a Scrum Team relies on the dynamic tension generated across its three accountabilities. When these boundaries blur, the empirical feedback loop breaks down:

Accountability Owns Typical tension with the others

Product Owner What to build and why it creates value; Product Goal; Product Backlog ordering Value vs. feasibility with the Developers

Developers How to build it; how much fits in a Sprint; quality through the Definition of Done; the Sprint Backlog plan Feasibility and quality vs. scope pressure

Scrum Master How Scrum is used ; the Scrum Team's effectiveness; causing the removal of impediments Process integrity and team health vs. short-term shortcuts

All three sit inside one Scrum Team with no sub-teams or hierarchy; the tension between them is healthy as long as each respects the others' decisions.

Critical Boundary Rules:

The Scrum Master Never Dictates What or How: The Scrum Master never tells the Product Owner what to prioritize, nor do they tell Developers how to write code, test features, or allocate tasks. Doing so undermines self-management and relieves the respective accountabilities of their professional obligations.

The Product Owner Never Dictates Technical Execution or Estimates: The Product Owner sets the business context and defines value objectives. They have zero authority to dictate how technical tasks are built, how many hours work requires, or who executes a specific item. Velocity and sizing are solely determined by Developers.

Developers Never Unilaterally Drop the Definition of Done: While Developers own the implementation plan, they cannot dilute the Definition of Done to declare an incomplete feature "done" before a Sprint Review. A compromised Definition of Done introduces hidden debt, destroys transparency, and deceives the Product Owner and stakeholders regarding the true state of the product.