HKSM
The Retrospect Release Meeting
A release-level retrospective held to find ways to enhance team collaboration and performance on future work. The team reviews what went well, what did not, and where improvements are possible. This session has no fixed time limit and can be conducted either in person or online.
Key Points
- Focuses on improving collaboration and effectiveness for future projects or releases.
- Covers successes, problems, and concrete opportunities to improve.
- Not time-boxed; duration is flexible based on need.
- May be held in person or virtually and should yield actionable follow-ups.
Example
After delivering a major release of a banking app, the team meets to reflect. They note that early stakeholder demos helped quality (positive), late integration caused defects (negative), and propose a shared integration calendar and automated smoke tests (opportunities). The meeting runs for 90 minutes online and ends with owners and due dates for the top three actions.
PMP Example Question
Which meeting is held after a release to discuss what went well, what did not, and actionable improvements, has no fixed duration, and can be run in person or virtually?
- Daily Standup
- Retrospect Release Meeting
- Change Control Board Meeting
- Sprint Planning
Correct Answer: B — Retrospect Release Meeting
Explanation: The Retrospect Release Meeting is a post-release review of positives, negatives, and improvement opportunities. It is not time-boxed and can be conducted in person or online.
