1 of 16

Slide Notes

DownloadGo Live

Retrospectives

Published on Aug 25, 2016

No Description

PRESENTATION OUTLINE

Retrospectives

a retrospective
Photo by jasonepowell

AGenda

  • What are they
  • How do we get the most
  • Ways, means and methods

The Retro

Photo by Great Beyond

What was a good retro

Photo by stevendepolo

What was a not so good retro

Photo by drweisgerber

Why?

What was the difference between the two
Photo by Dean Hochman

Discuss with you a Partner

Write down what you think makes a good retro
Photo by CIMMYT

First Principal

  • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

First Principal CONT.

  • Because Agile stresses the importance of continuous improvement, having a regular Agile retrospective is one of the most important of Agile development practices.
Photo by Paul A. Rizer

Second Principal

  • Held at the end of an iteration in Agile software development.
  • During the retrospective, the team reflects on what happened in the iteration and identifies actions for improvement going forward.
Photo by wili_hybrid

third Principal

  • "Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."
Photo by DVIDSHUB

Different Stages

  • Set the stage - get the team ready to engage in the retrospective, perhaps with a warm-up activity
  • Gather data - create a shared picture of what happened during the retrospective
  • Generate insights - discuss what was successful and identify any roadblocks to success
  • Decide what to do - identify highest priority items to work on and put measurable goals on those items so they can be completed (15 minutes)
  • Close the retrospective - reflect on the retrospective and how to improve it, and to appreciate accomplishments of the team and individual interactions
Photo by Phil Denton

Basic

  • What worked well for us?
  • What did not work well for us?
  • What actions can we take to improve our process going forward?

PMI

  • • What are the positive things about this iteration? (1 min.) • What are the negative (minus) things about this iteration? (1 min.) • What was interesting about this iteration? (1 min.)

5 Whys

  • If you are doing a 5 times why retrospective you can ask “Why did something happen?” or “What caused it?” (if you prefer not to use the “why” word) to get to the root causes of problems.
Photo by weesen