Work with Me

Esther Derby

Learn with Me

Esther Derby

6 Reasons *not* to have a Retrospective

The Rest

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.

    Share This

    • 0 Comments

    Submit a Comment

    Your email address will not be published. Required fields are marked *

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Related

    Perils of Part-time team membership

    My new article on Incorporating Part-Time Team Members is on Stickyminds.com. In one of my...

    Inflicting Help

    The other morning had an early flight from the west coast to Minneapolis. There wasn’t...

    No, we still aren’t plug and play.

    Interesting post from Bob Sutton on the obsession with individual talent, and the evidence that...

    A cover up? Perhaps not.

    Someone recently described this situation on the Scrum Development list: “…we’ve found some members of...

    Explore more in the Library

    Search by keyword or go to the Library to view content by topic or format.

    Explore the Library

    Search

    Explore more in the Library

    Search by keyword or go to the Library to view content by topic or format.

    Explore

    Search