Software Development
Sprint Retrospective
Definition
A sprint retrospective is a meeting held at the end of a sprint in which the team reflects on what went well, what didn't, and what they want to change in the upcoming sprint. It is a key part of the "inspect and adapt" philosophy of Scrum.
Why It Matters
The retrospective is the primary opportunity for a team to improve its own process. It fosters a culture of continuous improvement (Kaizen) and empowers the team to take ownership of its workflow.
Contextual Example
During a retrospective, team members might identify that their daily stand-up meetings are running too long. They decide to experiment with using a timer for the next sprint to keep the meeting focused.
Common Misunderstandings
- The retrospective is about the process, not the product. The "Sprint Review" is the meeting where the team demonstrates the product increment they built.
- It should be a blameless and constructive discussion.