Skip to main content

Sprint Retrospective

Last post 01:12 pm April 17, 2018 by Timothy Baffa
5 replies
12:57 am April 16, 2018

The purpose of the Sprint Retrospective is to:

• Inspect how the last Sprint went with regards to people, relationships, process, and tools;

Does people here mean

1. individuals or individual performance or competencies.

2. Right expertise in the team.

3. Right combination in the team.

or is it anything else ?


10:44 am April 16, 2018

Would inspection of any of these things be irrelevant to finding an improved way of working?


01:02 pm April 16, 2018

Basic rule of thumb: If it happened or relates to anything that happened within the sprint, it is within the bounds to be discussed in the Retro. 


10:10 pm April 16, 2018

But then how will the individuals improvement's to be adapted in upcoming sprint look like, will there be a new PBI added for individual's improvements ?


12:46 am April 17, 2018

New PBI does not make sense, will it be an action item to be taken up in the upcoming sprints.


01:12 pm April 17, 2018

While individual improvement from sprint to sprint is desirable, I believe the focus in a Sprint Retrospective should be on potential improvements for the Scrum Team as a whole instead of identifying individual improvements.

The Scrum Guide provide some clarity regarding this:

The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint...

By the end of the Sprint Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint...

To ensure continuous improvement, (the Sprint Backlog) includes at least one high priority process improvement identified in the previous Retrospective meeting (i.e. - Kaizen).


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

Please note that the first and last name from your Scrum.org 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. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org 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 Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.