From Fedora Project Wiki
No edit summary
mNo edit summary
Line 1: Line 1:
{{draft}}
This document describes experiences on how to conduct effective retrospectives leading to process improvements
This document describes experiences on how to conduct effective retrospectives leading to process improvements



Revision as of 10:28, 18 September 2015

Warning.png
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.

This document describes experiences on how to conduct effective retrospectives leading to process improvements

Offline Process

  • Use sticky notes (red for items which need improvement, green for positive items from the sprint).
  • Every team member notes down a small sentence on the sticky notes, using one sticky note for each item.
  • The sticky notes are all attached to a whiteboard or surface for discussion.
  • Every team member explains its sticky notes.
  • The team agrees on common good points and common problems from the sticky notes.
  • What action items from the last retrospectives are solved, needs revisiting.
  • Solutions/Action points are derived from the noted down problems.

Digital Process

This is what worked for us:

  • Use a system which allows comments underneath a document.
  • Every team member starts with adding a comment with a list of good points and things which need improvement (sticky notes).
  • Now let every team member explain their notes.

More to come