Scrum Anti-Patterns
An anti-pattern is a common habit that looks like Scrum but weakens its results. Many teams adopt the vocabulary of Scrum while keeping old behavior underneath. Recognizing anti-patterns helps teams correct course before small problems turn into lasting damage.
Why Anti-Patterns Appear
Teams start Scrum under pressure. Managers expect faster results, and people carry habits from earlier projects. Shortcuts feel efficient at first. Over several Sprints, the shortcuts erode trust, quality, and learning.
Scrum-But
"Scrum-but" describes a team that says, "We use Scrum, but we skip the Retrospective." Each "but" removes a source of feedback. Scrum is a framework with interlocking parts, so removing one part weakens the others. A team that skips the Retrospective loses its main tool for improvement.
Common Anti-Patterns and Fixes
| Anti-Pattern | Symptom | Healthy Fix |
|---|---|---|
| Status-report Daily Scrum | Everyone talks to the manager | Developers talk to each other about the Sprint Goal |
| Scrum Master as boss | Assigns tasks and tracks hours | Coach the team to self-manage |
| Absent Product Owner | Developers guess requirements | Product Owner joins events and answers questions daily |
| Overloaded Sprint | Half the items stay unfinished | Plan from real velocity |
| Skipped Retrospective | Same problems repeat | Protect the event and track actions |
| Hero developer | One person finishes everything | Share knowledge through pairing |
| Mid-Sprint scope changes | Goal shifts weekly | Hold new requests for the next planning |
| Weak Definition of Done | Bugs appear after release | Add testing and review to the definition |
Healthy and Unhealthy Daily Scrum
UNHEALTHY HEALTHY Manager Sprint Goal ▲ ▲ ▲ ▲ │ │ │ ┌──────┼──────┐ Dev Dev Dev Dev ◄──► Dev ◄──► Dev (each reports up) (talk to each other)
In the unhealthy version, information flows upward and nobody plans together. In the healthy version, Developers inspect progress toward the goal and adjust the plan among themselves.
Example: The Carry-Over Habit
A team building a recipe-sharing app plans ten stories each Sprint and completes six. The remaining four roll into the next Sprint. After three Sprints, the backlog shows constant carry-over and morale drops. The team studies the pattern in a Retrospective and discovers two causes: stories arrive too large, and testing starts only on the last two days. The team splits stories smaller and tests daily. Completion rises to nine of ten within two Sprints.
Anti-Patterns Around the Product Backlog
- The backlog holds hundreds of stale items that nobody reads.
- Stakeholders write items directly with no ordering by value.
- Items lack acceptance criteria, so Developers interpret them differently.
Cost of Ignoring Anti-Patterns
Anti-patterns rarely cause sudden failure. They drain quality, trust, and energy a little each Sprint. Defects rise, estimates lose meaning, and capable people leave for healthier teams. Stakeholders lose faith in Scrum itself and blame the framework for habits that the team created. Early correction protects both the product and the reputation of the method.
How to Detect Anti-Patterns
- Compare daily behavior against the Scrum Guide.
- Ask each member what they dislike about the current process.
- Track measures such as unfinished items and defects after release.
- Invite an outside coach for an honest observation.
- Discuss findings in the Retrospective without blaming individuals.
How to Respond
Change one habit at a time. A team that tries to repair everything at once loses focus. Pick the anti-pattern with the highest cost, set a small experiment for one Sprint, and measure the result. Keep the change if it helps and try another if it does not.
Anti-patterns signal opportunities to improve. A team that notices them early and responds with curiosity grows stronger with every Sprint.