Study guide
6.1 Self-Managing Teams
PSM I — Professional Scrum Master I Scrum.org
Track your progress as you read
Finished sections get a check mark.
1 Introduction & PSM I Exam Overview
1.1 Current PSM I Exam Facts 1.2 Scoring & Time-Management Strategy 1.3 The 2020 Scrum Guide Is The Single Source Of Truth 1.4 A Realistic PSM I Study Plan
2 Scrum Theory, Empiricism & Values
2.1 What Scrum Is (and Is Not) 2.2 Empiricism and Empirical Process Control 2.3 The Three Pillars: Transparency, Inspection, Adaptation 2.4 Lean Thinking: Reduce Waste, Focus on Essentials 2.5 The Five Scrum Values
3 The Scrum Team & Accountabilities
3.1 The Scrum Team 3.2 The Developers 3.3 The Product Owner 3.4 The Scrum Master 3.5 Scrum Master Services to Team, Product Owner, and Organization
4 The Scrum Events
4.1 The Sprint 4.2 Sprint Planning 4.3 The Daily Scrum 4.4 The Sprint Review 4.5 The Sprint Retrospective 4.6 Timeboxing and Empiricism Across the Events
5 Scrum Artifacts & Commitments
5.1 Artifacts & the Transparency Mandate 5.2 Product Backlog & the Product Goal 5.3 Sprint Backlog & the Sprint Goal 5.4 The Increment & the Definition of Done 5.5 Commitments Summary & Exam Traps
6 Developing People & Teams
6.1 Self-Managing Teams 6.2 Facilitation 6.3 Scrum Master Stances 6.4 True Leadership That Serves 6.5 Conflict & Organizational Change
7 Managing Products with Agility
7.1 Product and Value 7.2 Product Goal Management 7.3 Product Backlog Management 7.4 Forecasting and Release Planning 7.5 Stakeholders, Evidence, and Business Agility
8 Final Review & Exam Strategy
8.1 Common Misconceptions & PSM I Traps 8.2 2020 Scrum Guide Rapid Review 8.3 Question Tactics & Time Management 8.4 Last-Minute Checklist
6.1 Self-Managing Teams
Key Takeaways Explain This Topic AI
The 2020 Scrum Guide states Scrum Teams are cross-functional and self-managing: they internally decide who does the work, how, and what they work on.
Self-management is a Scrum Guide rule for the whole Scrum Team, not just the Developers; the Scrum Master grows this capability rather than directing it.
Managers and stakeholders may set goals and constraints, but they do not assign tasks inside the Sprint or override the team's internal organization.
The Scrum Master serves the team by removing impediments and coaching, never by acting as a task-assigning team lead.
Self-management is a capability that develops over time; new teams may need more teaching while mature teams need lighter-touch coaching.
Last updated: June 2026
Why This Matters for PSM I
The "Developing People and Teams" competency is roughly 20% of the Professional Scrum Master I (PSM I) assessment, and self-management sits at its center. The 2020 Scrum Guide replaced the older term "self-organizing" (which applied only to the Development Team) with "self-managing" (which applies to the whole Scrum Team — Product Owner, Scrum Master, and Developers together). This was a deliberate change: the 2020 Guide removed the idea of a separate "Development Team" inside the Scrum Team and removed all sub-teams and hierarchies.
PSM I questions test whether you can tell a Scrum Guide rule apart from a coaching technique , and whether you protect team self-management under pressure from managers and stakeholders.
What Self-Management Means in Scrum
The 2020 Scrum Guide defines the Scrum Team as cross-functional (members collectively have all the skills needed to create value each Sprint) and self-managing (they internally decide who does the work, how it is done, and what they work on). This is a hard framework rule, not optional advice. Crucially, the Guide adds that the Scrum Team is small enough to remain nimble and large enough to complete significant work , typically 10 or fewer people — small size is part of what makes self-management workable.
Self-management does not mean "no leadership" or "no accountability." The Scrum Team is still accountable for creating a valuable, useful, Done Increment every Sprint. It means decisions about the work are made by the people doing the work, inside the boundaries set by the Product Goal , the Sprint Goal , and any organizational constraints (budget, standards, regulations). Self-management is bounded autonomy, not anarchy.
Who Decides What
- Decision Owned By Note
- Which Product Backlog items are most valuable Product Owner Accountable for ordering the Product Backlog
Which items enter the Sprint and the Sprint Goal Whole Scrum Team collaborates; Developers decide how much The PO proposes value; Developers own capacity
How the work is broken down and done Developers No one tells them how to turn items into Increments
Who picks up which task during the Sprint Developers Work is pulled, never assigned by a manager or Scrum Master
Definition of Done quality bar Team, or organization standard if one exists Team conforms to org standard as a minimum
Contrast: Self-Managing vs Traditionally Managed Teams
A traditionally managed team has a manager or project lead who assigns tasks, sets the schedule, tracks individual utilization, and owns delivery decisions. Authority is concentrated; the team executes instructions.
A self-managing Scrum Team pulls work, distributes it internally, inspects and adapts each Sprint, and is collectively accountable for the outcome. Authority over how the work is done sits inside the team.
A common anti-pattern is a Scrum Master or manager acting as a task dispatcher in the Daily Scrum — handing out work item by item. This directly undermines a Scrum Guide rule and signals the team has not yet learned to self-manage.
How the Scrum Master Grows Self-Management
Growing self-management is professional coaching practice that supports the framework , not an extra Scrum rule. Effective behaviors include:
Coaching the team to make its own decisions instead of answering every question for them.
Removing impediments so the team can self-organize around the actual work, not around blockers.
Protecting the team from external task assignment, mid-Sprint scope changes, and interruptions.
Teaching new teams the Scrum framework, then deliberately reducing intervention as the team matures.
Asking powerful questions ("What options do you see?" "How will you decide?") rather than supplying solutions.
The exam trap is choosing an answer where the Scrum Master, Product Owner, or a manager decides for the Developers. On PSM I, the option that preserves the team's internal authority — while keeping the team accountable for a valuable Increment — is almost always correct.
Boundaries and Common Misconceptions
Self-management is frequently misread on the exam. Clarify these boundaries:
Self-managing is not leaderless. The Scrum Master leads on process and effectiveness; the Product Owner leads on value and Product Backlog order. What the team self-manages is who, how, and what they work on within those boundaries.
Self-managing is not consensus-on-everything. The team chooses how it makes decisions; it can delegate, vote, or defer to expertise. Endless consensus is itself an impediment.
No sub-teams or titles. The 2020 Guide is explicit: there are no sub-teams or hierarchies inside the Scrum Team, and there is one set of accountabilities, not job titles like 'tech lead' or 'team lead' who direct others.
Managers still matter. Line managers set strategy, budgets, hiring, and constraints, and they support the team's growth — they simply do not assign Sprint tasks or override the team's internal organization.
Capability, not a switch. A team does not become self-managing by decree; the Scrum Master grows the capability over time through teaching, coaching, and removing the impediments that force managers to step in.
When a question describes pressure to centralize control — a manager assigning tasks, a 'lead' dictating design, or the Scrum Master dispatching work — the Scrum-Guide-aligned answer protects the team's internal decision-making while keeping the team accountable for outcomes.