- What is the Sprint Planning?
- Capacity Overload
- Work package allocation in planning
- Neglect of Technical Debt
- No buffer times
- Too detailed planning
- Too little planning
INFO: This article is part of the series on agile anti-patterns.
For more agile anti-patterns see the entire series.
Agile Anti-Pattern Series:
- General Agile Anti-Patterns
- Daily Scrum/ Daily Standup Anti-Patterns
- Sprint Anti-Patterns Part I
- Sprint Anti-Patterns Part II
- Sprint Anti-Patterns Part III
- Backlog Anti-Patterns Part I
- Backlog-Anti-Patterns Part II
- Sprint Review Anti Patterns Part I
- Sprint Review Anti Patterns Part II
- Sprint Review Anti Patterns Part III
- Retrospective Anti Patterns Part I
- Retrospective Anti Patterns Part II
- Retrospective Anti Patterns Part III
- Sprint Planning Anti-Patterns Part I
- Sprint Planning Anti-Patterns Part II
- Sprint Planning Anti-Patterns Part III
- Role Anti-Patterns Part I
- Role Anti-Patterns Part II
- Role Anti-Patterns Part III
- Role Anti-Patterns Part IV
If you don’t want to miss any updates on this series click the Follow button.
What is the Sprint Planning?
The Sprint Planning is the first Meeting within a Sprint which starts the Sprint and creates a Sprint Goal, a Sprint Backlog, and a Plan for how to achieve the Sprint Goal.
During the Sprint Planning, we answer the following questions: