Study guide
2.3 Anti-Patterns in Accountabilities
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.3 Anti-Patterns in Accountabilities
Key Takeaways Explain This Topic AI
Accountability anti-patterns undermine psychological safety, disguise systemic bottlenecks, and transform empirical Scrum into ceremonial command-and-control.
The Scrum Master acting as a project manager or taskmaster induces learned helplessness, destroys developer self-management, and degrades the Daily Scrum into a status update.
Proxy Product Owners lack authentic fiscal and scope decision mandate, causing crippling decision latency, diluted product vision, and feature-factory churn.
Intra-sprint mini-waterfalls—sequencing analysis, coding, and testing across the Sprint timebox—back-load risk, subvert collective ownership, and compromise the Definition of Done.
Advanced Scrum Masters resolve anti-patterns not through superficial enforcement, but by acting as organizational change agents who make delay costs and quality risks transparent to leadership.
Last updated: October 2026
2.3 Anti-Patterns in Accountabilities
When organizations undergo agile transformations, they rarely abandon their historical hierarchies and cultural habits overnight. Instead, traditional management reflexes, risk aversion, and functional silos frequently co-opt Scrum terminology, producing subtle yet destructive accountability anti-patterns . These anti-patterns preserve the illusion of agile adoption while reinforcing command-and-control behavior, eroding psychological safety, and severing empirical feedback loops.
An advanced Scrum Master (PSM II) must possess the diagnostic acuity to identify these systemic dysfunctions beneath their superficial symptoms and deploy nuanced, long-term coaching interventions to realign the organization with true Scrum principles.
- Anti-Pattern 1: The Scrum Master as Project Manager or Taskmaster
- Observable Symptoms
The Scrum Master leads the Daily Scrum like an interrogation, asking each developer: "What did you do yesterday? What are you doing today? Are you on schedule?"
Team members direct their updates to the Scrum Master rather than talking to each other.
The Scrum Master assigns tasks to Developers, estimates story points, updates burndown charts on behalf of the team, and manages Jira tickets.
Individual developers are held accountable by the Scrum Master for task-level hour estimates.
Systemic Consequences
This anti-pattern completely dismantles developer self-management. When the Scrum Master acts as an administrative overseer, Developers disengage their proactive problem-solving faculties and adopt a posture of passive compliance. If a roadblock arises, they wait for the Scrum Master to assign them a workaround. Furthermore, if the Scrum Master is absent, the Daily Scrum either collapses or devolves into awkward silence because the team lacks peer accountability.
Diagnostic & Coaching Intervention
Step Back and Silence: During the Daily Scrum, the Scrum Master physically or virtually steps outside the circle, refraining from speaking or making eye contact. If Developers look to the Scrum Master, the Scrum Master redirects their gaze toward the Sprint Backlog board and their peers.
Hold Up the Mirror in Retrospectives: The Scrum Master brings objective data to the Retrospective: "I noticed that during the last two Sprints, all board transitions were executed by me, and 80% of Daily Scrum comments were directed at me. What impact is this having on our collective ownership?"
Transition Board Ownership: The Scrum Master ceases updating tasks or managing workflow tools, making it clear that the Sprint Backlog is owned exclusively by the Developers.
- Anti-Pattern 2: The Proxy Product Owner
- Observable Symptoms
The named Product Owner cannot make definitive decisions during Sprint Planning, refinement, or Sprint Reviews without consulting an external steering committee, department head, or executive sponsor.
Frequent scope churn mid-Sprint because an external executive rejects the work prioritized by the Product Owner.
The Product Owner answers developer questions with: "I will check with the business and get back to you next week."
Backlog items represent a raw aggregation of stakeholder wish-lists without unified strategic vision or cohesive Product Goal alignment.
Systemic Consequences
The Proxy Product Owner is an administrative buffer rather than a value optimizer. This structure creates crippling decision latency . In complex product environments, Developers require rapid, contextual trade-offs to keep work flowing. When decisions take days or weeks to navigate corporate approval layers, developer velocity plummets, work-in-progress (WIP) explodes, and the resulting Increment fails to reflect coherent value.
Diagnostic & Coaching Intervention
Quantify Decision Latency and Delay Costs: The Scrum Master tracks the cycle time of product decisions—from the moment a clarification is raised until an authoritative response is received—and models the economic cost of delay (e.g., idle developer hours, context switching, blocked features, and lost market opportunities), using the organization's own numbers rather than generic estimates.
Executive Coaching on Empirical Governance: The Scrum Master works directly with executive leadership, explaining that true agility requires delegating fiscal and product authority to a single empowered Product Owner. The Scrum Master presents leadership with a clear choice: either grant the current Product Owner full decision-making mandate, or have the actual decision-maker step into the Product Owner accountability directly.
- Anti-Pattern 3: Committee or Distributed Product Ownership
- Observable Symptoms
The organization assigns a "Product Ownership Committee" or multiple co-Product Owners to a single product.
Backlog refinement sessions become battlegrounds of political horse-trading, where stakeholders compromise by including a little bit of everyone's pet features.
The Product Backlog lacks a clear ordering; instead, hundreds of items are marked as "High Priority" or "Urgent."
Developers receive conflicting instructions from different business sponsors, resulting in conflicting code implementations.
Systemic Consequences
When product ownership is distributed across a committee, nobody is truly accountable for product value . Decisions stall in endless consensus-building cycles. The resulting product becomes a bloated, fragmented "feature factory" that attempts to satisfy every internal stakeholder while delivering negligible cohesive value to actual end users.
Diagnostic & Coaching Intervention
Reinforce the Scrum Guide Mandate: The Scrum Master reminds leadership and stakeholders of the core rule: the Product Owner is one person, not a committee.
Establish Stakeholder Governance Channels: The Scrum Master helps the Product Owner design structured forums (such as regular Product Backlog refinement workshops and collaborative Sprint Reviews) where stakeholders can voice their perspectives, review empirical market feedback, and provide input. However, the Scrum Master coaches stakeholders that the Product Owner retains the ultimate, unquestioned authority on final ordering.
- Anti-Pattern 4: The Intra-Sprint Mini-Waterfall
- Observable Symptoms
Developers spend Days 1 through 6 of a two-week Sprint purely writing code, without executing integration or end-to-end tests.
On Day 7 or 8, code is "thrown over the wall" to dedicated QA testers on the team.
Testers are completely overwhelmed during the final 48 hours of the Sprint, logging defects that cannot possibly be resolved before the Sprint Review.
Backlog items routinely carry over to the subsequent Sprint for "testing and bug-fixing," or the team requests separate "Hardening Sprints."
Systemic Consequences
The mini-waterfall inside the Sprint timebox completely negates empiricism. Risk is back-loaded to the very end of the Sprint, precisely when there is zero time left to inspect and adapt. If testing fails on Day 9, the entire Sprint Goal is compromised. Furthermore, this dynamic perpetuates an adversarial "us versus them" mentality between programmers and testers, directly violating collective accountability and the Definition of Done.
Pattern Days 1–3 Days 4–7 Days 8–10 Outcome
Mini-waterfall (anti-pattern) Analysis and design; testers idle Coding; testers idle Testing and panic; testers overwhelmed Carryover, hidden defects, no usable Increment
Healthy flow (vertical slices) Story A designed, coded, tested, Done Story B Done; Story C in progress Story C Done Usable value accumulates throughout the Sprint
Diagnostic & Coaching Intervention
Promote Vertical Story Slicing: The Scrum Master coaches the Product Owner and Developers to slice large requirements into thin, end-to-end vertical slices that deliver a tiny slice of real functionality across all layers (UI, logic, database, test) within 1 to 2 days.
Introduce Swarming and Test-First Practices: The Scrum Master encourages Developers to pair and swarm on one or two stories at a time, limiting work-in-progress (WIP). Programmers and quality specialists collaborate from Day 1, defining automated acceptance tests before and during code implementation, ensuring continuous integration and immediate verification.
- Anti-Pattern 5: The Rescuing Scrum Master and Learned Helplessness
- Observable Symptoms
The Scrum Master handles all administrative overhead: booking conference rooms, updating calendars, configuring board filters, ordering team snacks, and resolving every interpersonal friction.
If two Developers disagree on an API design, they run to the Scrum Master to mediate.
When an external team fails to deliver an API dependency, the Scrum Master immediately assumes personal responsibility for chasing down the external team's manager.
Systemic Consequences
While the Scrum Master believes they are "servant leading" by clearing paths, they are actually fostering learned helplessness . The team remains infantilized and fragile, incapable of navigating healthy conflict or asserting itself within the organization. When the Scrum Master is on vacation or leaves the organization, the team's ability to operate independently completely collapses.
Diagnostic & Coaching Intervention
Embrace Productive Discomfort: The Scrum Master exercises deliberate restraint, resisting the reflex to fix every discomfort immediately. Allowing the team to feel the productive friction of an unresolved challenge motivates them to collaborate and formulate internal coping mechanisms.
Coach Peer-to-Peer Resolution: When a developer complains to the Scrum Master about a teammate's code quality or behavior, the Scrum Master asks: "Have you shared this feedback directly with them? How can I support you in having that conversation safely?"
Empower Team Dependency Management: Instead of acting as an administrative courier between teams, the Scrum Master facilitates direct, engineer-to-engineer communication channels between interdependent teams.
Summary Diagnostic Matrix
Anti-Pattern Primary Indicator Underlying Root Cause Strategic SM Intervention
Taskmaster SM Daily Scrum is a status report directed to SM Management muscle memory; lack of trust in developer self-management Step back; maintain silence; hold up mirror in Retrospectives; transition board ownership
Proxy PO PO must ask permission from executive sponsors Fear of delegating fiscal authority; risk aversion in leadership Measure and visualize decision latency; coach executives on cost of delay; demand empowerment
Committee PO Conflicting priorities; bloated backlog; endless debate Political diffusion of responsibility; inability to make trade-offs Reinforce one-person rule; structure stakeholder advisory channels while upholding PO final say
Mini-Waterfall Testers swamped on last days; defects carried over Horizontal component thinking; large horizontal batch sizes Coach vertical slicing; implement swarming and pair programming; embed test automation
Rescuing SM Team paralyzed when SM is absent; cannot resolve conflict Hero complex; confusing service with administrative servitude Embrace productive struggle; coach peer feedback; guide team to resolve own technical impediments