Sprint Retrospective
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 ?
Would inspection of any of these things be irrelevant to finding an improved way of working?
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.
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 ?
New PBI does not make sense, will it be an action item to be taken up in the upcoming sprints.
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).