HKSM

The main deliverable from the Retrospect Sprint: a concise set of specific, owned actions the team commits to implement to resolve issues and refine processes, aiming to improve performance in upcoming sprints.

Key Points

• Created by team consensus during the Retrospect Sprint to address root causes and process gaps.
• Each item is concrete, achievable, time-bound, and has a clearly identified owner.
• Typically limited to a small number per sprint to ensure focus and accountability.
• Tracked in the next sprint and inspected for completion and impact on team performance.

Example

During the Retrospect Sprint, the team notices delays from inconsistent code reviews. They agree on three improvements: (1) adopt a 24-hour code review SLA with a rotating reviewer, (2) add an automated linting step to the CI pipeline, and (3) run a 30-minute design huddle at the start of complex stories. Each item has an owner and is scheduled for the next sprint.

PMP Example Question

Which artifact specifically lists the concrete improvement actions the team commits to after the Retrospect Sprint?

1. Sprint Backlog
2. Agreed Actionable Improvements
3. Product Increment
4. Impediment Log

Correct Answer: B - Agreed Actionable Improvements

Explanation: Agreed Actionable Improvements are the committed, specific changes from the retrospective. The Sprint Backlog is product work, the Increment is the product outcome, and the Impediment Log tracks current blockers.