← Back to blog

10 anti-patterns in agile teams

agile anti-patterns team-management

Does your team go through all the Scrum ceremonies but the results don’t show up? You’ve probably fallen into anti-patterns.

1. Zombie Scrum

Symptom: Ceremonies happen, but without energy, without purpose. “We do it because we have to.” Fix: Revisit the “why” with the team. Workshops on the value of each ceremony. Change meeting formats to increase engagement.

2. Sprint as mini-waterfall

Symptom: Design at the start of the sprint, coding in the middle, testing at the end, delivery on the last day. Fix: Parallel work. Testing from day 1. Complete features (frontend + backend + tests), not separate layers.

3. Daily as status report

Symptom: Each member reports to the Scrum Master, not to the team. Fix: Members talk to each other. Scrum Master stays silent. Walk the Board instead of “yesterday/today/blockers.”

4. Ghost PO

Symptom: Product Owner doesn’t show up to ceremonies or doesn’t answer questions. Fix: Escalate to management. A PO without time is a project risk. If there’s no dedicated PO, appoint someone.

5. Velocity as KPI

Symptom: Manager demands increasing velocity sprint after sprint. Team inflates estimates. Fix: Educate leadership. Velocity is for team planning, not a performance metric.

6. Sprint without a goal

Symptom: Team delivers random features with no connection. Fix: Every sprint needs a clear objective that guides priority choices.

7. Retrospective without action

Symptom: Team discusses problems, but nothing changes sprint after sprint. Fix: Maximum 2 actions per retrospective. Each action has an owner and deadline. Review actions at the start of the next retro.

8. Estimate as commitment

Symptom: Stakeholder demands “you said 5 points and it took 8.” Fix: Educate stakeholders. Estimates are predictions, not promises. Use confidence intervals.

9. Chronic carry-over

Symptom: 50%+ of items are carried over to the next sprint. Fix: Plan less. If we consistently deliver 20 points, don’t plan for 25.

10. Non-self-organizing team

Symptom: Scrum Master or manager assigns tasks. Team waits for orders. Fix: Stop assigning. Let the team self-organize. It may be uncomfortable at first, but it’s essential.

Diagnostic checklist

Check the ones that apply to your team:

  • Ceremony happens without energy
  • Testing only at the end of the sprint
  • Daily turns into a status report
  • PO rarely available
  • Velocity is demanded by management
  • Sprint without a defined goal
  • Retro actions never get done
  • Estimates turned into promises
  • Half the items don’t get delivered
  • Someone assigns tasks to the team

3+ checkmarks: Team needs urgent agile realignment. 5+ checkmarks: Consider an external Agile Coach. 8+ checkmarks: Scrum has become theater. Rethink from scratch.

Conclusion

Anti-patterns are signs that form cannot replace purpose. Every ceremony, every practice exists for a reason. If you’ve lost the reason, recover it — or drop the practice.