Agile Anti-Patterns: Sprint Review Anti-Patterns Part III

Content:

• What is a Sprint Review?

1. Missing Stakeholders in the Review
2. Missing Customers and Users in the Review
3. Changing Stakeholders
4. Passive Stakeholders in the Review
5. Presenting Unfinished Features
6. Collecting and Hiding Technical Debt

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
Scrum 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
- Refinement-Anti-Patterns
- 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 a Sprint Review?

The Sprint Review Meeting takes place at the end of the Sprint. At the end of the Sprint, each developer presents the results to the Product Owner and the key stakeholders (users, internal stakeholders from other departments). The presentation takes…