6 Reasons *not* to have a Retrospective

Retrospectives are a great way for teams to inspect and adapt their methods and teamwork after each iteration and release. And they’re a great way for teams to build on success, learn from hard times, or bring closure when a project ends. But they’re not for good for everything. Don’t do a retrospective if you want…

  • another group to fix the way they do their work
  • to show that someone isn’t doing his/her job
  • to find who is to blame for bad design, missed deadlines, disappointing projects etc
  • to force two individuals to solve a long standing conflict
  • to give feedback on poor performance
  • to prove that if those people had done better, everything would be fine.

    On the other hand, if you want to learn from experience, build on what works, gain perspective, and decide what to do differently, a retrospective can work for you.