Study guide
2.4 Self-Managing Teams & 2020 Scrum Guide Evolution
Professional Scrum Master I PSM I
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Scrum Fundamentals
About the PSM I Exam How to Use This Course 1.1 Scrum Theory & Empiricism 1.2 The Five Scrum Values 1.3 The Scrum Team Overview 1.4 Scrum Definition, Rules, & Boundaries
2 Chapter 2: Scrum Accountabilities & Team Dynamics
2.1 The Developers Accountability & Technical Ownership 2.2 The Product Owner Accountability & Value Maximization 2.3 The Scrum Master Accountability & True Leadership 2.4 Self-Managing Teams & 2020 Scrum Guide Evolution 2.5 Cross-Functional Teams & Skill Diversity 2.6 Leadership Stances of the Scrum Master
3 Chapter 3: Scrum Events & Timeboxing
3.1 The Sprint Event & Container Nature 3.2 Sprint Planning Event (Three Topics) 3.3 Daily Scrum Event & 15-Minute Timebox 3.4 Sprint Review Event & Stakeholder Feedback 3.5 Sprint Retrospective Event & Continuous Improvement 3.6 Event Facilitation & Conflict Resolution
4 Chapter 4: Scrum Artifacts & Commitments
4.1 Product Backlog Artifact & Refinement 4.2 Product Goal Commitment 4.3 Sprint Backlog Artifact & Ownership 4.4 Sprint Goal Commitment 4.5 Increment Artifact & Definition of Done Commitment 4.6 Definition of Done vs. Acceptance Criteria
5 Chapter 5: Agile Product Management & Team Leadership
5.1 Product Backlog Management & Ordering Strategies 5.2 Stakeholders & Customers 5.3 Product Value Metrics & Evidence-Based Management (EBM) 5.4 Agile Forecasting & Release Planning 5.5 Psychological Safety & Impediment Removal 5.6 Scaling Scrum Fundamentals & Nexus Overview
2.4 Self-Managing Teams & 2020 Scrum Guide Evolution
Key Takeaways Explain This Topic AI
The 2020 Scrum Guide evolved from 'self-organizing' to 'self-managing' teams, granting teams full internal control over who does what, when, and how.
Self-management operates within guardrails, including the Product Goal, Sprint Goal, Definition of Done, fixed timeboxes, and organizational standards.
Traditional management's role shifts from task assignment and micro-management to establishing strategic vision, boundary constraints, and resources.
Self-managing teams adapt faster during complex Sprints because they eliminate managerial approval bottlenecks and handoff delays.
The Product Owner manages what and why; Developers manage how and who; the team collectively manages when.
Last updated: July 2026
2.4 Self-Managing Teams & 2020 Scrum Guide Evolution
Scrum Guide Evolution: Prior to 2020, Scrum described teams as "self-organizing" (deciding who and how to do work). The 2020 Scrum Guide updated this terminology to "self-managing" , expanding team autonomy to include deciding who does what, when, and how .
The evolution to self-management represents one of the most significant conceptual refinements in modern Scrum. Understanding why this update occurred, how self-management functions in practice, and where organizational boundaries lie is critical for scoring high on the PSM I examination.
From Self-Organizing to Self-Managing
To appreciate the depth of self-management, consider how team autonomy evolved between the 2017 and 2020 editions of the Scrum Guide:
Dimension Self-Organizing (Pre-2020) Self-Managing (2020 Scrum Guide)
Scope of Autonomy Deciding who performs work and how technical tasks are completed. Deciding who does what, when, and how within the team.
Product & Sprint Alignment Often relied on external project managers for scheduling and task timing. Internally manages task scheduling, workload distribution, and execution tactics.
Accountability Focus Technical execution efficiency. End-to-end value delivery and continuous process improvement.
By empowering the entire Scrum Team (Developers, Product Owner, Scrum Master) to manage their work collectively, Scrum eliminates external handoffs, reduces administrative overhead, and maximizes responsiveness to change.
The Three Pillars of "Who, What, When, and How"
Self-management is not unbridled chaos or total absence of structure. It operates through distinct internal accountabilities within the Scrum Team: Scrum Team Self-Management
- / | \
- / | \
- WHAT & WHY WHO & HOW WHEN
- (Product Owner) (Developers) (Collective Team)
WHAT & WHY (Value & Direction): The Product Owner defines the Product Goal and orders Product Backlog items based on customer value and business priorities.
HOW & WHO (Technical Execution): The Developers decide the technical design, architecture, task breakdown, and who amongst them will work on specific components.
WHEN (Sprint Commitments & Delivery): The Developers assess their capacity to decide how much work to pull into a Sprint, creating the Sprint Backlog to reach the Sprint Goal.
Bounded Autonomy: Guardrails of Self-Management
A common PSM I exam misconception is believing that a self-managing team operates without restrictions. In empirical Scrum, self-management operates within strict guardrails :
Guardrail 1: Product Goal & Sprint Goal
Self-management is directed toward specific business outcomes. The Product Goal provides the long-term destination, while the Sprint Goal provides the overarching objective for each Sprint timebox. The team cannot arbitrarily abandon these goals.
Guardrail 2: Definition of Done
The Definition of Done establishes the quality threshold required for an Increment to be usable and releaseable. Self-managing Developers must work within this quality contract.
Guardrail 3: Fixed Timeboxes
Sprint length is strictly fixed (maximum 1 month). Teams cannot extend a Sprint timebox simply because work is incomplete; they must adapt their scope within the timebox.
Guardrail 4: Organizational Standards & Compliance
Scrum Teams must adhere to corporate governance, legal regulations, security mandates, and architectural benchmarks unless explicitly granted an exception.
The Shift in Management's Role
Transitioning to self-managing teams fundamentally transforms the role of traditional managers and executive leaders:
Traditional Management Activity Self-Managing Scrum Context
Assigning daily tasks to individuals Providing strategic vision, business context, and funding.
Controlling schedules and tracking Gantt charts Removing organizational systemic impediments.
Micro-managing technical implementation Supporting skill development, career progression, and environment setup.
Blaming individuals for missed targets Fostering psychological safety and empirical experimentation.
Management provides the environment, resources, and boundaries ; the Scrum Team manages its own operational execution within those parameters.
Real-World Benefits of Self-Management
Why does Scrum demand self-management? Empirical evidence demonstrates clear competitive advantages:
Speed of Adaptation: When unexpected technical challenges arise during a Sprint, a self-managing team adjusts its internal plan immediately without waiting for managerial approval.
Higher Ownership & Engagement: Team members who choose how to solve problems display significantly higher commitment, creativity, and morale than those executing delegated instructions.
Reduced Communication Overhead: Removing intermediate managers and coordinators eliminates translation errors, bureaucracy, and queue delays.
- Common PSM I Exam Traps for Self-Management
- Trap 1: Management Assigns Work Directly to Developers
Incorrect Scenario: A software director assigns an urgent task directly to a senior developer on the team without consulting the Scrum Team. Correct Scrum Behavior: External managers must respect team self-management. Requests must go to the Product Owner to be prioritized, and work is selected by Developers during Sprint Planning.
Trap 2: The Scrum Master Directs Team Decisions
Incorrect Scenario: The Scrum Master decides who works on frontend vs. backend tasks to ensure maximum efficiency. Correct Scrum Behavior: The Scrum Master coaches the team to decide for themselves. The team determines work assignments internally.
Trap 3: Self-Management Equals No Management
Incorrect Scenario: Self-management means upper management and executives have no right to set targets, budgets, or strategic constraints. Correct Scrum Behavior: Management establishes vision, strategic goals, and budget boundaries. The team self-manages how to achieve those goals within those boundaries.
Summary Checklist for PSM I Candidates
2020 evolution: Shifted from "self-organizing" to "self-managing" (who, what, when, and how).
Bounded by Product Goal, Sprint Goal, Definition of Done, timeboxes, and organizational standards.
Developers manage how and who does technical work; PO manages what and why .
Traditional management provides context, resources, and boundary conditions, not task assignment.