Self-Managing Teams
Self-managing teams are tested through accountability, decision rights, and the Scrum Master's stance. Self-management is not the absence of structure; it is the team's authority to decide how to do its work.
Core rules
- Self-managing Scrum Teams decide who does what, when, and how.
- They are accountable for the Increment and for managing their own work.
- The Product Owner sets value direction; the Scrum Master coaches the team and removes impediments; Developers own delivery decisions.
- Boundaries exist: organizational policies, the Definition of Done, and the Sprint Goal.
- Self-management grows through transparency, feedback, and practice.
Worked example
A Scrum Master sees Developers waiting for the tech lead to assign tasks. Instead of assigning work, the Scrum Master asks the team how they will choose the next item and what blocks them from deciding. The team agrees to pull work by skill and capacity. Reasoning: the Scrum Master coaches self-management rather than replacing it with direction.
Traps
Treating self-managing as no leadership; letting the Product Owner assign technical tasks; having the Scrum Master direct daily work; assuming self-management means consensus on every decision; removing all constraints.