What is the Vacation Retrospective for Scrum teams?
Take a reflective trip down memory lane and share the highlights of the last sprint.
Like sprints, vacations seem to be over in the blink of an eye; and like successful sprints, good vacations require planning, time and resources. TeamRetro’s retrospectives aim to foster constructive conversations, so if you have observed your retrospectives are being used to vent and rant, a retrospective such as this could be for you.
As with many of our retrospectives, this theme-based retrospective has been shaped to position team members to adopt an optimistic view of the sprint (after all who doesn’t like a holiday?).
The Vacation Retrospective format
Participants describe either what they perceive to be the final destination (what they will see, experience, and feel) or what they will be able to show at the end of the sprint. This might be the current state or a re-statement of the end point of the sprint (rephrased sprint goal).
Participants are given the opportunity to call out challenges and risks that they faced during the sprint. Losing one’s luggage is a nuisance, but it’s only one element of the vacation (let’s face it, getting one’s luggage back is a far better story).
The “Packing” category sees participants review the effectiveness of their planning for the sprint just gone, and thus can be useful for the one ahead. They consider the actions they undertook and the resources they accessed that best positioned them for a happier holiday.
The “Vacation Snaps” are the high, and potentially low points that are significant, meaningful and that the team wants to share. They represent learning opportunities as well as the key aspects of the vacation trip that the team reminisces over.