HKSM
Retrospective
A recurring session where participants review how the work was done and what was delivered to identify practical ways to improve both the process and the product.
Key Points
- Occurs at regular intervals, typically at the end of an iteration or milestone.
- Centers on team learning about methods and outcomes, not assigning blame.
- Results in a short list of prioritized, actionable improvement items for the next period.
- Works best with psychological safety, honest data, and clear facilitation.
Example
After a two-week sprint, the team meets for 60 minutes to inspect collaboration, tooling, and Definition of Done. They agree to add pair testing for high-risk stories and implement a pipeline check that blocks merges without unit tests.
PMP Example Question
Which event is intended for the team to examine how they worked and what they delivered, and to agree on specific actions to improve both process and product?
- Sprint Review
- Daily Standup
- Retrospective
- Backlog Refinement
Correct Answer: C — Retrospective
Explanation: A retrospective is a recurring workshop focused on reflecting on work and outcomes to identify concrete improvements for the next cycle.
