Retrospect Sprint Log(s)
A Retrospect Sprint Log is a documented summary of team feedback, conversations, decisions, and agreed improvement actions from the sprint retrospective. The Scrum Master typically facilitates compiling this log based on input from Scrum Core Team members.
Key Points
- Captures observations, concerns, ideas, decisions, and concrete action items from the retrospective.
- Facilitated by the Scrum Master, with content provided by Scrum Core Team members; ownership is shared by the team.
- Tracks action items with owners, due dates, and status; items may flow into the next sprint or an improvement backlog.
- Provides a historical reference to measure and sustain continuous improvement across sprints.
Example
After a 2-week sprint, the team holds a retrospective and notes slow code reviews and flaky tests. They agree to set a 24-hour review SLA and to prioritize stabilizing test suites. The Scrum Master records the discussion, assigns owners and dates to each action, and adds them to the Retrospect Sprint Log for follow-up in the next sprint.
PMP Example Question
Which artifact documents the team's reflections and specific improvement actions from a sprint retrospective and is often compiled with Scrum Master facilitation?
- Sprint Backlog
- Retrospect Sprint Log
- Product Backlog
- Increment
Correct Answer: B - Retrospect Sprint Log
Explanation: The Retrospect Sprint Log records opinions, discussions, and actionable items from the retrospective. The other options serve different purposes (work for the sprint, product needs, or the delivered product increment).
