Navigation Menu

Skip to content

Instantly share code, notes, and snippets.

@vanstee
Created September 18, 2014 16:44
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save vanstee/4e14e683881cdf5b10da to your computer and use it in GitHub Desktop.
Save vanstee/4e14e683881cdf5b10da to your computer and use it in GitHub Desktop.

Known as the "Sticky Shotgun" approach. The tactical steps are:

  1. Give everyone a pad of stickies and marker.
  2. Take 5 minutes to write down whatever comes to mind from the release.
  3. Stick each sticky in correct "zone" on whiteboard. (Keep Doing. Less Of. More Of. Stop Doing. Start Doing.)
  4. Give a very quick explanation while adding it.
  5. Group the stickies in each zone into into affinity groups.
  6. Discuss each affinity group and try to identify what needs to be done to solve the issues; or what was done that makes them worth keeping.
  7. Vote on 2-3 most important issues so the team can prioritize/know what needs to be addressed first.

That's probably a good style to use given your goals, but you might also want to consult this list of retrospective plans to see if there are others that would fit your needs. http://retrospectivewiki.org/index.php?title=Retrospective_Plans

One thing to do, if you can, is have a 3rd party facilitate the retrospective - that person can help keep the discussion on track, cut off tangents, move everything forward, and make sure the space is safe for everyone involved. If you can't get a 3rd party you just need to make sure that the person facilitating knows their role -- they are not to participate, but facilitate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment