When retrospective objectives stack up

In my last post on retrospectives I said that at the end of each retrospective the team should settle on an action that they believe will help improve the next sprint: the retrospective objective.

James Shore and Shane Warden’s advice on choosing a retrospective objective in The Art of Agile Development (2008) is two-fold:

  1. During the retrospective, don’t worry about the detail: a general direction is good enough at this stage.
  2. Choose just one objective: it helps the team focus, and improve incrementally without feeling overwhelmed.
Continue reading When retrospective objectives stack up