Sprint Retrospective
Sprint Retrospective is a Scrum event held at the end of a sprint where the team reflects on how they worked and identifies improvements for the next sprint.
Sprint retrospective answers: “How can we work better next time?”
1. Definition
Sprint Retrospective is a Scrum event held at the end of a sprint where the team reflects on how they worked and identifies improvements for the next sprint.
Sprint retrospective answers: “How can we work better next time?”
2. Purpose of Sprint Retrospective
- Inspect team processes
- Identify what went well and what didn’t
- Define actionable improvements
- Promote continuous improvement
3. Participants
- Scrum Team (PO optional)
- Facilitated by Scrum Master
4. Typical Retrospective Structure
- What went well
- What didn’t go well
- What can be improved
- Action items for next sprint
5. Manual Tester’s Role in Retrospective
- Share testing challenges and successes
- Highlight defect trends and root causes
- Suggest improvements in test planning, data, or environment
- Propose better collaboration practices
6. Example Retrospective Inputs (Tester)
- Late build availability impacted testing
- Good collaboration reduced defect turnaround time
- Need earlier acceptance criteria clarification
7. Sprint Retrospective vs Sprint Review
| Aspect | Sprint Retrospective | Sprint Review |
|---|---|---|
| Focus | Process | Product |
| Outcome | Improvements | Feedback |
| Audience | Scrum team | Stakeholders |
8. Common Mistakes
- Blaming individuals
- No follow-up on action items
- Repeating same issues every sprint
9. Interview-Ready Answers
Short answer:
Sprint retrospective is a meeting where the team reflects on the sprint process and identifies improvements.
Detailed answer:
Sprint retrospective enables the Scrum team to evaluate their way of working and agree on actionable improvements for future sprints.
10. Key Takeaway
Sprint Retrospective drives continuous improvement, making each sprint better than the last.