📋Sprint Retrospective
Also known as Retrospective, Retro
The meeting at the end of each sprint where the team improves the way it works.
Think of it like
It is like a team talk after a match. Not about the score. It is about how you played.
Example
Emma's team finds that half its bugs came from rushed code reviews. They agree that in the next sprint, no code goes in without a second reader.
Why it matters
A team that never looks at how it works repeats the same mistakes. Small fixes each sprint add up fast.
Definition
Common mistake
Key takeaways
- 1How, not what. Look at the way of working.
- 2Pick a change. Choose a few things to improve.
- 3Every sprint. Small fixes, made often.