6.1 Self-Managing Teams

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

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.