Get certified - Transform your world of work today


Why Not Push the Retrospective to the Next Sprint?

5 August 2013

Carlos Silva
INDT - Instituto de Desenvolvimento Tecnológico

This has been a discussion in a LinkedIn CSPO group that I would like to share with other people. Simple article, but strong message.

The question was, "Why not push the retrospective to the following sprint?"

The retrospective is an opportunity to raise facts, diagnose what needs to improve, and recognize what team did well, so this session is one of the two most important ceremonies in Scrum (the other is the daily Scrum). It has to be exactly on the last day of the sprint to give a chance for the team's reflections and follow-up on improvements.

Other important thing some guys don't do: They just leave the room without actions. What has been raised by the teammates as points of improvement categorized as "Under Team's Control" should be followed by those team members in their team backlog, and what has been raised as "Out of Team's Control" should be recorded in the ScrumMaster's impediment backlog. Both backlogs are live and subject to daily change, so they are reminders of things to be worked on.

At the end of the project it's important that the ScrumMaster invites everyone for a meeting that I call the "project retrospective," exactly the same as conducting each sprint retrospective. There, we look at the overall product development cycle's significant events, good things that could be repeated in future projects, and bad things that should be avoided forevermore.

This retrospective session is one powerful tool for any manager, even outside of the Scrum framework!

Opinions represent those of the author and not of Scrum Alliance. The sharing of member-contributed content on this site does not imply endorsement of specific Scrum methods or practices beyond those taught by Scrum Alliance Certified Trainers and Coaches.

Article Rating

Current rating: 0 (0 ratings)


Bhoodev Singh, CSP,CSM,CSPO, 8/5/2013 1:16:07 AM
If you don't have sprint retro at the end of every sprint, there's a high possibility that team may not improvise in the subsequent sprint because team members don't have the data points(good, bad, etc.)from the previous sprint.Then you would lose two sprints without any improvement, for example, and then there're very high chances that the same flow may be continued throughout the project. So, where's continuous improvement??

Project retro might confuse team with sprint retro. How about if we name it like project closing ceremony where team still can talk through the overall project performance.
Glen Wang, CSM, 8/5/2013 9:41:25 PM
This question is similar like to have daily stand in morning (starting of the day) vs afternoon (end of the day).

You must Login or Signup to comment.

The community welcomes feedback that is constructive and supportive, in the spirit of better understanding and implementation of Scrum.


Newsletter Sign-Up