Successfully reported this slideshow.
Your SlideShare is downloading. ×

Facebook retrospective

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad

Check these out next

1 of 34 Ad

More Related Content

Slideshows for you (20)

Viewers also liked (20)

Advertisement

Similar to Facebook retrospective (20)

Recently uploaded (20)

Advertisement

Facebook retrospective

  1. 1. retrospective
  2. 2. Retrospectives are a crucial part of Scrum.
  3. 3. But... running the standard ‘3 questions’* setup can get boring. * what went well, what went bad, what should we improve
  4. 4. There are books about how to do retrospectives.
  5. 5. Here is a retrospective form I designed myself. I call it the “Facebook” retrospective.
  6. 6. Setup
  7. 7. My retrospectives are always timeboxed to one hour.
  8. 8. I always start with an energizer/ice breaker, to get everyone active and set the mood.
  9. 9. After the energizer, I start with the actual retrospective.
  10. 10. Like or Dislike
  11. 11. For the Facebook retrospective, I printed out different elements of our Scrum process on A4 paper.
  12. 12. Examples of these elements are: standup, demo, sprint planning, JIRA, team communication etc. There were 12 different topics.
  13. 13. Each of the pieces of paper had the topic written on it and two columns: Like and Dislike.
  14. 14. I introduced each of these topics briefly, so everyone understood what I meant with them.
  15. 15. Next, I asked everyone to get up and walk over to wall with the cards on it. Everyone had to decide if they ‘liked’ or disliked the topic on each card by putting their name in one of the columns.
  16. 16. After everyone was done, I added up the likes and the dislikes seperately. There turned to be two groups of cards:
  17. 17. Group 1 Those where the team seemed to agree.
  18. 18. Group 2 Those where the team seemed to disagree.
  19. 19. Define actions
  20. 20. After discussing the results, we focused on those where we disagreed.
  21. 21. Everyone took some post-its and wrote down actions for each of the topics where the team ‘disagreed’.
  22. 22. A lot of the actions overlapped, so the total amount of actions turned out to be limited. We decided to take them all into the next sprint.
  23. 23. Retro o’ retro
  24. 24. As always, we closed the retrospective with a small retrospective on the retrospective itself.
  25. 25. Suggestions for improvement coming out of the retrospective on the retrospective:
  26. 26. 1. People found having only Like and Dislike quite limited. They suggested to add up a ‘neutral’ field. (Allowing people not to pick any option would be another solution.)
  27. 27. 2. The team suggested to add a number of cards without predefined topics, so they add their own.
  28. 28. Time planning Energizer 5 min Explanation 5 min Choose Like or Dislike 10 min Discuss outcome 10 min Write down actions 10 min Discuss actions 10 min Retro 5 min End session 5 min
  29. 29. Did you like this retrospective setup? Try it out for yourself and let me know how it went!
  30. 30. I am Jasper Verdooren, founder of Sygmoid. Find me at www.sygmoid.nl about.me/jasperverdooren www.slideshare.com/jasperverdooren www.linkedin.com/in/jasperverdooren jasper.verdooren@sygmoid.nl
  31. 31. ‣Scrum Master Founded Sygmoid ‣Team lead PO ‣Consultancy ‣Product Owner ‣ Scrum trainer ‣Team lead PO ‣Training & coaching ‣Scrum trainer ‣Software development 2007-2010 2010-2011 2011
  32. 32. Thank you for your attention! Questions? Comments? Let me know!

Editor's Notes

  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

×