Self-Organizing Teams

Definition

In Scrum, teams are responsible for deciding not just how they will do work, but which work they will attempt in a sprint and how they will divide it among themselves. No manager assigns tasks to programmers or orchestrates their dependencies. The team, given a goal and some requirements, collectively decides what is achievable and how to achieve it. This is fundamentally different from traditional project management, where a project manager creates a task list and assigns work to individuals.

In the Book

Schwaber contrasts this model with traditional waterfall, where managers assign tasks to specialists (analysts, designers, programmers, testers) based on a predetermined plan. He argues that this approach fails in complex projects because no one person has the full picture—the actual constraints, dependencies, and solutions emerge as the work unfolds.

In the Lapsec case study, a classified national security team was initially stuck. Schwaber couldn't see their actual work (security clearance denied), so he gave them a hypothetical product backlog and asked them to select what they could deliver in a sprint. The act of self-organizing around a concrete goal transformed the dynamic. Schwaber writes: "When the team members stop acting as many and adopt and commit to a common purpose, the team becomes capable of self-organization and can quickly cut through complexity and produce actionable plans. At that point, the members of a team no longer accept obstacles, but instead scheme, plot, noodle, and brainstorm about how to remove them."

In the Tree project, where multiple teams had to coordinate on interdependent components, Schwaber staffed each team with representatives from dependent areas (someone familiar with XML, someone with WebPub) so that each team could resolve its own dependencies without bottlenecks.

Why It Matters

Self-organization unlocks the distributed knowledge of the team. It replaces the bottleneck of a single project manager with the collective intelligence of multiple people who understand different pieces of the problem. This is especially valuable in R&D, product development, and any creative problem-solving. The model assumes that people are motivated by mastery and autonomy—they will work harder on problems they helped define than on tasks assigned to them.