Skip to main content

Sprint Retrospective and Product Backlog

Last post 11:21 am August 8, 2015 by Sushil Agarwal
5 replies
07:21 am March 29, 2015

Hi All.

The Sprint Retrospective results a plan of improvement that will be enacted during the next sprint.

Should this plan be added in the Product Backlog? How to track if the improvements are made?


12:25 pm March 30, 2015

> Should this plan be added in the Product Backlog?

The Retrospective should look at how the last Sprint went with regards to people, relationships, processes, and tools, as opposed to the product. It is therefore unlikely that the Retrospective plan would be accommodated on the Product Backlog. Instead, this is more likely to be adapted as a result of the Sprint Review.

> How to track if the improvements are made?

The Sprint Backlog includes a plan for delivering the agreed increment in accordance with the Sprint Goal. Improvements that are identified during a Retrospective will change the way the increment is developed and delivered, so the Goal can be better met. It would therefore be reasonable to include (or otherwise reflect) these actions on the Sprint Backlog. The effort involved in doing so should be considered when deciding how much work can be inducted into the Sprint.

08:25 pm March 30, 2015

I agree with what Ian has written.

Something else to consider is the(continued) evolution of the Definition of Done (DoD).

04:18 am March 31, 2015


I'am a scrum master for 2 teams and I can tell you about our experience.
For us the plan of improvements means a list of actions. What should we change or do in another why.
We keep the retrospective notes in Confluence. We have a list of What did we do well? What should we have done better?
but more important a List of Actions:
Each action has one or more owners/drivers/shepherds: dev, po or sm, or could be the entire team (@team)
Deciding is not doing.
So we try to keep a printed copy of Retrospective notes on the wall close to our physical SCRUM Board - and discuss the items at the end of Daily Scrum.
Sometimes we put the actions as individual items (like stories or tasks) on the Physical Scrum Board.
We start every Retrospective looking on the previous one - to see if we've implemented what we've decided, if the implementation has the desired output; if we have actions not implemented - and what can we do in this case.

hope this will help you,

09:11 am March 31, 2015

For the team around me, to show that the actions decided by the scrum teams are important, they are made highly visible.
Usually, the teams display the actions as sticky notes on their scrum-board.
This made it easy to reflect in the next retrospective how the teams deal with the former retrospective.

11:21 am August 8, 2015

Track improvement as a part of Daily Scrum meeting, Sprint retrospective meeting are meant to know what went well, what didn't go well and what could have been done better, ideally this meeting last for an hour and scrum master should track vital action items in daily scrum meeting.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by may have their access revoked at any time, without warning. may, but is not obliged to, monitor submissions.