Agile teams use the retrospective to collect a set of start, stop, and continue actions at the end of each iteration. The point of this technique is to collect feedback as a team and focus it (through one of the above verbs) into actionable steps toward improvement.
But retrospectives often produce a dozen or more actionable steps, and teams can grow nauseous from seeing the same things show up retrospective after retrospective with little or no progress made. So, how does a team break this cycle?
By prioritizing only one or two activities as goals for the next iteration.
It’s hard to remember to work on a dozen (or even half a dozen) things at once, even when you don’t have an iteration of work to complete at the same time. Remembering to focus on one or two goals is much easier, especially when your entire team is also thinking about those same goals.
Finally, the team needs to close the loop by discussing the outcome of each goal in the next retrospective.
- Did everyone really take the agreed-to steps to meet the goal?
- Was there a beneficial outcome?
- Should the team focus on the same goal in the next iteration?
- Was the outcome different than expected?
- Should the team take different steps to achieve the goal?
And there you have it: continuous improvement.
 Author:Peter Schuh
Comments 
Write comment
 |
Show/hide comment form
I think the product backlog exists in multiple forms. You have the backlog that comes from the Product owner and testing, but also the product backlog from the experience of the team in the iteration. I think both are equally important and should be prioritised together for maximum benefit.
Regards,
David
http://www.jacksguides.com