Just One Change Per Retrospective

A core part of Scrum and many other Agile methodologies is ‘inspect and adapt.’ Retrospectives are a key practice in reviewing the last iteration. You toss up on stickies or a white board the ‘What Went Well’ and ‘What To Look Into.’

Diana Larsen held a session at the end of Agile Open California on retrospectives and suggested two key ideas on how to take action after a retrospective:

  • Pick one or at most two things on the list to work on for the next iteration.
  • Only pick something that at least one person in the room has the energy to take on. If no one has the energy for the next iteration don’t try to force change.