Skip to content

Self-Managing Scrum Teams

Step 11 of 18

Self-Managing Scrum Teams: Decisions, Boundaries, and Accountability

Introduction

Self-managing Scrum Teams decide how to organize their work. For example, when a database change blocks a Sprint item, the Developers can pair up, shift their plan, or discuss a scope change with the Product Owner. The Scrum Master helps them address obstacles while the relevant decisions stay with the team.

This PSM I lesson covers Self-Managing Teams in the Developing People and Teams focus area. You will identify which decisions Developers make, how goals and quality standards guide those decisions, and how the Scrum Master helps a team learn to manage its work.

Learning objectives

  • Explain which decisions the Scrum Team makes and how Scrum’s accountabilities shape them.
  • Explain the boundaries inside which a Scrum Team manages itself: the Scrum framework, the Product Goal, the Definition of Done and organisational constraints.
  • Describe cross-functionality and explain why job titles do not create a hierarchy within the Scrum Team.
  • Explain how the Scrum Master serves the Scrum Team, the Product Owner and the organisation through servant leadership.
  • Recognise typical anti-patterns such as an assigned task list, a manager picking the Sprint Backlog, or a Scrum Master acting as project manager.
  • Apply these ideas to realistic situations: conflict, a team that waits for permission, and a manager who wants status reports.

1. What self-managing means

A self-managing Scrum Team organizes its own work. The three Scrum Team accountabilities help determine who makes a particular decision. The Developers make decisions about planning and carrying out the work:

Question Who decides in Scrum
Who does the work? The Developers decide among themselves; nobody assigns Product Backlog items to individuals
When is it done? The Developers decide how to plan their Sprint and their day, within the Sprint timebox
How is it built? The Developers decide the design, tools, practices and technical approach, within the Definition of Done

Three elements must be understood together:

  1. Self-managing is not the same as unmanaged. The team operates inside a framework with fixed events, three accountabilities, three artifacts and their commitments, and a Definition of Done. The framework is the boundary; inside it the team decides.
  2. Self-management covers assignment and timing. The 2020 guide uses self-management to describe decisions about who does what and when, in addition to how to do it.
  3. Self-management comes with accountability. The whole Scrum Team answers for a valuable, usable Increment each Sprint. The Developers create and adapt the Sprint Backlog, meet the Definition of Done, and hold one another accountable for their work.

Example: the manager's task board

A software company moves a team of seven to Scrum. At the first Sprint Planning, the department manager arrives with a spreadsheet that assigns every Product Backlog item to a named person, with estimated hours. The Scrum Master asks the Developers what they think. They notice that the spreadsheet puts the only database expert on four separate items in the same week and assigns a front-end item to someone who has never touched the framework involved.

The Scrum Master does not argue with the manager in front of the team. After the event, they explain that the Developers are the only people who can judge their own capacity and skills, that outside assignment lowers ownership and hides the real obstacles, and that the manager can contribute better by clarifying priorities with the Product Owner and removing organisational blockers. The manager agrees to try one Sprint, and the team forecasts its own work around the Sprint Goal and pairs another Developer with the database expert, then checks whether the queue of blocked items shrinks.

This is the typical exam pattern: the "right" answer protects the team's right to decide how and who, and the Scrum Master teaches and coaches rather than confronting or complying.

2. The boundaries of self-management

A common misreading is that self-management means "anything goes". The Scrum Guide sets several limits, and the exam expects you to know them:

  • The Scrum framework itself. The team holds the prescribed events, preserves the Product Owner and Scrum Master as distinct accountabilities, and keeps each Sprint to a fixed length of one month or less. The guide says Scrum is a framework; the rules bind the team together, and changing the rules means the result is no longer Scrum.
  • The Product Goal. The Scrum Team commits to the Product Goal, which gives the whole team a long-term objective. The Developers decide how to reach it but do not choose a completely different product.
  • The Sprint Goal. The Developers commit to the Sprint Goal and adjust their plan as they learn. If the selected scope needs to change, they discuss it with the Product Owner.
  • The Definition of Done. The team uses its Definition of Done and any organisational standard that applies. Self-management never means lowering quality to look faster.
  • Organisational constraints. Laws, security policy, budgets, hardware or compliance rules are real constraints. The Scrum Team works within them, and it is the Scrum Master's role to help the organisation understand which constraints are genuine and which are habits that no longer serve anyone.

Comparison: command-and-control versus self-management

Aspect Command-and-control Self-management in Scrum
Work assignment A manager assigns tasks to individuals Developers choose the work together
Estimates Imposed deadlines per task The Developers forecast what they can do in a Sprint
Progress reporting Reports to a manager Transparency through the Sprint Backlog and the Increment
Problems Escalated upward Solved by the team; the Scrum Master helps remove impediments beyond the team's reach
Improvement Decided by management Decided at the Sprint Retrospective by the team
Role of the leader Directs and controls Serves, teaches, coaches and removes barriers

3. A cross-functional team without internal hierarchy

The guide says Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint. This is important for self-management: if the team must wait for a different department to test, deploy or approve, it cannot make its own decisions about when the work gets done.

This affects how the team organizes its work:

  1. There are no sub-teams and no hierarchies within the Scrum Team. The guide describes a cohesive unit of professionals focused on one objective, the Product Goal. A "front-end team" and a "back-end team" inside the Developers contradict this.
  2. Specialties are useful. A tester, designer, analyst, or architect can be a Developer. A specialty or job title does not give someone authority to direct the other Developers or create a separate accountability inside the team.
  3. Developers maintain one plan. Individuals can volunteer for tasks while the Developers remain responsible for adapting the plan. The Scrum Guide describes a typical Scrum Team as having ten or fewer people in total.

Example: the "tester at the end" pattern

A team of eight has five programmers and three testers who report to a separate quality department. Testing starts after programming, and every Sprint ends with a rush of defects. The Scrum Master asks the team to map the flow of one Product Backlog item and the time it waits between hand-offs. The Developers conclude that a tester working with a programmer from the start of the item would remove both the waiting and the rework.

The Scrum Master supports the experiment but does not decide for them. Over three Sprints the team moves to pairing, writes automated checks together, and the testers keep their expertise but stop being a separate step. A manager asks why the testers no longer report their own metrics; the Scrum Master explains that the Increment is the team's output and that individual hours are not a measure of value.

4. The Scrum Master as a servant leader

The Scrum Master helps the Scrum Team become more effective. The way to help depends on what is blocking progress and who has the authority to act.

Who needs help? Example of how the Scrum Master can help
The Scrum Team Help Developers work across specialties, address impediments, and make the events productive.
The Product Owner Help clarify the Product Goal and backlog items, or facilitate a conversation with stakeholders.
The organization Explain how to plan with evidence and help departments remove barriers that slow the team down.

For example, the Scrum Master might bring the team and security group together to improve access to a test environment. The Developers still decide how to integrate the checks into their plan.

Servant leadership in a conflict

Servant leadership does not mean avoiding difficult conversations. If two Developers disagree about an architecture decision, the Scrum Master does not impose the answer. The Scrum Master can facilitate a conversation, make sure each view is heard, help the team explore a time-boxed experiment, and then let the Developers decide. If the conflict is about a decision that belongs to the Product Owner, such as the order of the Product Backlog, the Scrum Master helps the group see that and guides them to the right conversation.

5. Self-management inside the events

Look at who makes decisions during Daily Scrum and Sprint Planning and how those decisions change as the team gets more evidence.

  • Sprint Planning. The Developers plan the work necessary to create an Increment that meets the Definition of Done. They decide how many Product Backlog items they can select and how to turn them into a plan. The Product Owner proposes how the product could increase its value, and the whole Scrum Team collaborates on the Sprint Goal, but the Developers decide the Sprint Backlog.
  • Daily Scrum. Developers choose a format that helps them check progress toward the Sprint Goal and agree on the next day’s work. The three questions are optional. The Product Owner or Scrum Master participates as a Developer when working on Sprint Backlog items.
  • Sprint Review. The Scrum Team presents results to stakeholders. The team and stakeholders inspect the Sprint outcome. Work that misses the Definition of Done stays outside the Increment and cannot be presented at the Review.
  • Sprint Retrospective. The team plans ways to increase quality and effectiveness. It decides which improvements to tackle; the most impactful ones may be added to the Sprint Backlog for the next Sprint.

Worked example: the manager attends the Daily Scrum

Situation. A line manager, who is not a member of the Scrum Team, starts attending every Daily Scrum. The Developers give status updates to the manager one by one, and the manager questions who is behind schedule. After a week, people stop talking about obstacles and tell the manager only good news. The Scrum Master is asked what to do.

Reasoning.

  1. The Daily Scrum is an event for the Developers. Its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog, not to report to management.
  2. The Scrum Master helps the Developers use the event well and keep it within 15 minutes. The Developers run the discussion and decide what to change in their plan.
  3. The behaviour of the manager has reduced transparency: the team is hiding problems, which is the opposite of what the event is for.
  4. The Scrum Master should talk with the manager outside the event, explain what the Daily Scrum is for, and offer other ways to stay informed, such as attending the Sprint Review and inspecting the Sprint Backlog and the Increment. The Scrum Master should also help the Developers feel safe raising problems again.

Solution. Teach the manager about the purpose of the Daily Scrum, agree on how to keep the event focused on the Developers’ plan, and offer the Sprint Review as a place to discuss progress with the manager when relevant. Do not cancel the Daily Scrum and do not switch to written status reports.

Why the other options are weaker. Letting the manager continue keeps the reporting dynamic and teaches the team to hide issues. Replacing the Daily Scrum with status e-mails removes inspection and adaptation. Asking the manager's boss to forbid attendance escalates before the Scrum Master has done their own job of teaching.

6. The Scrum Values and trust

Self-management depends on trust, and the Scrum Values are what make that trust possible. Courage to say that a Sprint Goal is at risk, openness about work and challenges, respect for each other as capable and independent people, focus on the Sprint's work and goals, and commitment to achieving the goals of the Scrum Team all appear in the guide, and they are exactly the behaviours a self-managing team needs. When Developers can raise doubts openly, the team can adjust its plan before the gap grows.

A frequent exam theme is what a Scrum Master should do when the team is passive and keeps asking "what should we do next?". The answer is rarely to give instructions. The Scrum Master asks questions, helps the team notice that the Sprint Goal and Sprint Backlog contain the answer, facilitates a retrospective on why they feel unable to decide, and works on the organisational causes (for example, a manager who punished mistakes in the past).

7. Common pitfalls and exam tips

  • "Assign" is a red flag. In answer options, a person assigning tasks to the Developers (Product Owner, Scrum Master, manager) is almost always wrong. The Developers decide who does what.
  • The Scrum Master does not decide for the team. Options like "the Scrum Master chooses the best solution" or "the Scrum Master decides which items go in the Sprint" are wrong. Good options coach, facilitate, teach, remove impediments.
  • Do not confuse removing impediments with doing the team's work. The Scrum Master causes the removal of impediments that the team cannot resolve; the Scrum Master does not solve every technical issue.
  • Check how authority works. Someone may bring deep expertise and help others learn. A separate sub-team or a job title that gives someone authority over other Developers conflicts with Scrum’s team structure.
  • A team of ten or fewer is typical. The guide says "typically 10 or fewer"; it is not a rigid limit, but it warns that larger teams should consider several cohesive Scrum Teams focused on the same product.
  • Self-management does not mean ignoring stakeholders. The Product Owner and the Scrum Team collaborate with stakeholders, and the Sprint Review is the structured moment for it.
  • Be careful with absolute words. "Never" and "always" in answer options often signal a trap, though the Scrum Guide itself uses absolutes in some rules, such as "cannot be extended".

Exam tip. When a scenario shows someone outside the Scrum Team controlling how the work is done, choose the answer where the Scrum Master helps that person and the organisation understand self-management, instead of the answer where the Scrum Master takes over, complies silently or complains to a superior.

8. Mini case study

Situation. A telecom company has a Scrum Team of six Developers, a Product Owner and a Scrum Master building a customer billing portal. A programme manager, who is not part of the Scrum Team, wants to guarantee a regulatory deadline in eight weeks. She asks the Scrum Master to give her a list of who will do which task over the next four Sprints, and to report weekly each person's percentage of completion. She says that without this plan she cannot sign off the budget. The Developers feel micromanaged and one of them asks whether the team can simply refuse.

Question. What should the Scrum Master do?

Solution.

  1. Understand the need. The programme manager needs confidence that the regulatory date can be met. That is a legitimate need from a stakeholder, even though the proposed solution (assigned tasks and per-person percentages) conflicts with self-management and with the Scrum idea of an Increment as the measure of progress.
  2. Explain and offer alternatives. The Scrum Master meets the programme manager and explains that Scrum provides frequent transparency through a usable Increment every Sprint, a visible Product Backlog ordered by the Product Owner, and the Sprint Review where progress toward the Product Goal is inspected. Individual percentages hide risk because partially done work is not part of the Increment.
  3. Involve the Product Owner. The Product Owner owns the order of the Product Backlog, so the regulatory items can be ordered first and a forecast based on the team's actual delivery can be given with its uncertainty. The Scrum Master helps the Product Owner use empirical release planning.
  4. Protect the Developers. The Developers do not refuse; they are invited to the conversation, and they continue to plan each Sprint themselves.
  5. Invite to the events. The programme manager is invited to the Sprint Reviews and can inspect the Sprint Backlog at any time.

Why not the alternatives. Giving the assigned plan complies with a command-and-control request and removes the team's ownership. Telling the programme manager "no" without an alternative leaves a legitimate need unmet and damages collaboration. Asking the Developers to refuse puts them in conflict with the organisation instead of helping the organisation change.

Key terms

  • Self-managing: the Scrum Team decides internally who does what, when and how.
  • Cross-functional: the team has all the skills needed to create value each Sprint.
  • Developers: the people in the Scrum Team who help create a usable Increment each Sprint.
  • Servant leader: a leader who serves the team and the organisation by teaching, coaching and removing impediments.
  • Impediment: anything that blocks the team's progress which the team cannot resolve alone.
  • Command-and-control: a management style where a manager assigns work and monitors individuals, contrary to Scrum.
  • Scrum Values: commitment, focus, openness, respect and courage.

Summary checklist

  • I can state that Scrum Teams decide who does what, when and how.
  • I can list the boundaries: the framework, Product Goal, Sprint Goal, Definition of Done and real organisational constraints.
  • I can distinguish a Developer’s specialty from a reporting hierarchy and explain the team’s shared responsibility for the Increment.
  • I can describe how the Scrum Master serves the Scrum Team, the Product Owner and the organisation.
  • I can spot command-and-control behaviour in a scenario and choose the answer that coaches and teaches.
  • I know the Daily Scrum is owned by the Developers and its format is theirs to choose.
  • I can explain why the Scrum Values are a precondition for self-management.

Sources