Sprint Retrospectives
This directory contains retrospective documents for each sprint of the WatchTower project.
Purpose
Retrospectives are dedicated time for the team to reflect and improve. They help us:
- Celebrate wins – Recognize what went well and why
- Identify blockers – Understand what prevented progress
- Share learnings – Capture insights for the team
- Drive improvement – Commit to specific, actionable changes
- Build team culture – Foster psychological safety and collaboration
Retrospectives are held at the end of each sprint, typically during the sprint review meeting.
Each retrospective should capture:
What Went Well ✨
- Positive aspects of the sprint
- Successes and achievements
- Effective processes or decisions
- Great team moments or collaboration
What Didn’t Go Well 🚧
- Challenges encountered
- Blockers or frustrations
- Process breakdowns
- Incomplete work or scope issues
Action Items 🎯
- Specific improvements to implement
- Owner and deadline for each item
- How success will be measured
- Connection to sprint goals if relevant
Lessons Learned 💡
- Key takeaways for the team
- Technical insights or discoveries
- Process improvements to try
- Dependencies or constraints to remember
Retrospectives
Guidelines
- Be honest and constructive – Create psychological safety
- Focus on process, not people – Improve workflows, not individuals
- Identify patterns – Look for recurring issues across sprints
- Keep it actionable – Avoid vague complaints; suggest solutions
- Follow up – Review action items from previous sprints
- Celebrate wins – Don’t skip positive reflections
Facilitating a Retrospective
Before the Meeting
- Schedule 60–90 minutes with the team
- Prepare a template or whiteboard
- Set a constructive tone in the invitation
During the Meeting
- Check-in – How is everyone feeling? (2 min)
- What went well – Brainstorm positives (10 min)
- What didn’t go well – Identify challenges (15 min)
- Root causes – Why did issues happen? (10 min)
- Action items – What will we try next? (15 min)
- Commitments – Confirm ownership and deadlines (5 min)
After the Meeting
- Document findings in this folder
- Share with the team
- Reference action items in the next sprint planning
- Track progress on improvements