The Kama Sutra of Retrospectives<br />
Who are you to @#$%^& lecture me?<br />www.ciklum.net<br />2<br />Alexander Lutsaevsky <br /><ul><li>Ciklum Technical Cons...
Certified Scrum Product Owner, ISTQB Certified Tester, Certified Owner of Other Useless Papers
Founder and speaker at agile.kh.ua
Speaker at misc. conferences: PM Zone, Agile Base Camp, QA Club, Agileee, etc.</li></ul>Cross-functional Project Manager w...
Problems?<br />
Technique: Dot Vote<br />
6 Thinking Hats<br />
Goal: Effectively organize discussing emotional, rational, positive, negative feedbacks.<br />Time: approximately 1 hour<b...
Blue Hat – objectives for the session.
White Hat – generating facts from the last iteration.
Yellow Hat – focus on positive things.
Black Hat – focus on negative things.
Green Hat – ideas about improvement from the helicopter view.
Red Hat – emotive statements.
Conclusions and actions.</li></li></ul><li>Spider Web<br />
Goal: Measure important areas of the process by the team. <br />Time: approximately 1 hour<br />Spider Web<br /><ul><li>Ex...
Define important areas of discussion
Draw the spider web on the white board
Distribute the pieces of paper to everyone to draw the same spider web and rate the areas
Gather papers and accumulate the results from everyone
Discuss each area
Work out the improvement plan</li></li></ul><li>Appreciative Retrospective<br />
Goal: Focus on improvements, instead of fixing problems.<br />Time: approximately 1 hour<br />Appreciative Retrospective<b...
Gather information (group brainstorm or individual post-it notes):
Successes
Strength
Positive events
Group the post-its or facts
Generate plan</li></li></ul><li>Top 5<br />
Goal: Expose the most pressing issues in an anonymous manner<br />Time: approximately 45 minutes<br />Top 5<br /><ul><li>G...
Draw all the issues on the whiteboard
Ask the team to group the issues
Generate actions to solve problems (effective when working in pairs and then escalating the results to the group)
Upcoming SlideShare
Loading in...5
×

The Kama Sutra of Retrospectives

3,250

Published on

1 Comment
10 Likes
Statistics
Notes
  • Another very good set of slides ... simple, yet focused and effective. And can be used in many disciplines.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
3,250
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
83
Comments
1
Likes
10
Embeds 0
No embeds

No notes for slide
  • Прежде чем перейти к обсуждению различных методов ретроспектив, хотелось бы рассказать о технике голосования, которое я считаю достаточно эффективным и удобным при групповом принятии решения.При выборе нескольких лучших вариантов чего-либо в группе, мы пишем все эти варианты на доске. У каждого члена группы есть в запасе несколько черточек, например, три штуки, которыми он может пометить интересующие темы. Выбираются те темы, которые набрали наибольшее количество черточек.
  • Физик Эдвард де Боно, основатель теории о нестандартном мышлении, придумал организовать обсуждение в виде нескольких этапов, на которых за ограниченное время обсуждаются - Факты - Эмоции - Негативные вещи, которые имели место - Позитивные вещи, которые имели место - Творческие идеи по решению проблем - Подведение итогов и создание плана действий
  • Цель: необходимость измерить насколько мы хороши в определенных областяхРисуем на доске такую вот снежинку-паутину, каждая ветвь которой – шкала для определенной области от одного до пяти.Такие же снежинки у себя на листочке рисуют участники ретроспективы.Каждый отмечает у себя насколько он оценивает продвинутость группы в определенной области. Модератор ретроспективы собирает листочки, отмечает их на доске и после этого обсуждаются проблемные области.
  • Цель: сконцентрироваться на сильных сторонах и улучшении процесса, а не избавлении от негативных последствий.Собрать данные о сильных сторонах – брейнсторм о результатах, сильных сторонах и успехах. - Что мы делали хорошего до этого месяца. - Что мы изменили или начали делать хорошего в этом месяце.Брейнсторм об активностях, что поможет улучшить наши сильные стороны.Голосование черточками.
  • Что работает нормальноА что требует улучшений
  • Что надо изменять эволюционным путем, немного корректируяА что надо резко поменять
  • The Kama Sutra of Retrospectives

    1. 1. The Kama Sutra of Retrospectives<br />
    2. 2. Who are you to @#$%^& lecture me?<br />www.ciklum.net<br />2<br />Alexander Lutsaevsky <br /><ul><li>Ciklum Technical Consultant
    3. 3. Certified Scrum Product Owner, ISTQB Certified Tester, Certified Owner of Other Useless Papers
    4. 4. Founder and speaker at agile.kh.ua
    5. 5. Speaker at misc. conferences: PM Zone, Agile Base Camp, QA Club, Agileee, etc.</li></ul>Cross-functional Project Manager with more than 5 years of experience managing distributed and multinational teamsboth for agile and complex industry regulated projects.<br />Alexander has proven track record of successful on-time and on-budget project delivery from different business domains: accounting and finance controlling, healthcare informatics and medical devices, enterprise resource planning, transportation management and many more.<br />
    6. 6. Problems?<br />
    7. 7. Technique: Dot Vote<br />
    8. 8. 6 Thinking Hats<br />
    9. 9. Goal: Effectively organize discussing emotional, rational, positive, negative feedbacks.<br />Time: approximately 1 hour<br />6 Thinking Hats<br /><ul><li>Brief summary of De Bono’s Six Thinking Hats process.
    10. 10. Blue Hat – objectives for the session.
    11. 11. White Hat – generating facts from the last iteration.
    12. 12. Yellow Hat – focus on positive things.
    13. 13. Black Hat – focus on negative things.
    14. 14. Green Hat – ideas about improvement from the helicopter view.
    15. 15. Red Hat – emotive statements.
    16. 16. Conclusions and actions.</li></li></ul><li>Spider Web<br />
    17. 17. Goal: Measure important areas of the process by the team. <br />Time: approximately 1 hour<br />Spider Web<br /><ul><li>Explain idea and how to rate areas
    18. 18. Define important areas of discussion
    19. 19. Draw the spider web on the white board
    20. 20. Distribute the pieces of paper to everyone to draw the same spider web and rate the areas
    21. 21. Gather papers and accumulate the results from everyone
    22. 22. Discuss each area
    23. 23. Work out the improvement plan</li></li></ul><li>Appreciative Retrospective<br />
    24. 24. Goal: Focus on improvements, instead of fixing problems.<br />Time: approximately 1 hour<br />Appreciative Retrospective<br /><ul><li>Setting stage and check in
    25. 25. Gather information (group brainstorm or individual post-it notes):
    26. 26. Successes
    27. 27. Strength
    28. 28. Positive events
    29. 29. Group the post-its or facts
    30. 30. Generate plan</li></li></ul><li>Top 5<br />
    31. 31. Goal: Expose the most pressing issues in an anonymous manner<br />Time: approximately 45 minutes<br />Top 5<br /><ul><li>Gather top 5 issues from people via email
    32. 32. Draw all the issues on the whiteboard
    33. 33. Ask the team to group the issues
    34. 34. Generate actions to solve problems (effective when working in pairs and then escalating the results to the group)
    35. 35. Generate plan</li></li></ul><li>Plan of Actions Retrospective<br />
    36. 36. Goal: Focus on generating clear plan and taking actions<br />Time: approximately 40 minutes<br />Plan of Actions Retrospective<br /><ul><li>Gather information from the team members
    37. 37. Long-term goal: e.g. have test automation on acceptance-test level
    38. 38. Now-Action: e.g. Vasya will automate one test using Selenium
    39. 39. Objectives, Activities, Deliveries
    40. 40. Bass Vode’s (http://bit.ly/KamaSutra_ActionPlan) plan of action – individual action generation, pairs select top actions, whole group discuss top actions</li></li></ul><li>Start/Stop/Continue/More/Less<br />
    41. 41. Goal: Make the retrospective meeting short.<br />Time: 10-25 minutes.<br />Start/Stop/Continue/More/Less<br /><ul><li>Draw a circle on a poster, divide it into 5 sections and write the words "start", "stop", "continue", "more of" and "less of" around each section.
    42. 42. Gather information.
    43. 43. Generate action plan.</li></li></ul><li>Force Field Analysis<br />
    44. 44. Goal: Focus on specific area, discuss drivers and restrains<br />Time: approximately 60 minutes<br />Force Field Analysis<br /><ul><li>Pick a topic
    45. 45. Set the timer and give the team five minutes to list all the supporting/driving factors for the topic
    46. 46. Identify top drivers
    47. 47. List all the inhibiting/restraining factors for the topic.
    48. 48. Identify top restrains
    49. 49. Try to find relations between drivers and restrains factors
    50. 50. Generate action plan
    51. 51. Description is here http://bit.ly/KamaSutra_ForceField</li></li></ul><li>Pomodoro Retrospective<br />
    52. 52. Goal: Focus on specific topics, shorten the time for retrospective<br />Time: approximately 30 minutes<br />Pomodoro Retrospective<br /><ul><li>Generate the list of topics to discuss
    53. 53. 5 minutes to discuss each topic
    54. 54. 2-3 minutes to get summary
    55. 55. Plan actions</li></li></ul><li>Question Retrospective<br />
    56. 56. Goal: Focus on specific topics, shorten the time for retrospective<br />Time: approximately 30 minutes<br />Question Retrospective<br /><ul><li>Before the retro, prepare sheets of paper for each team member each having a different question on the top, for example:
    57. 57. In this sprint, what things happened that were unusual?
    58. 58. In this sprint, what things did we do well?
    59. 59. In this sprint, what did we do that we should avoid doing in the future?
    60. 60. The questions will be distributed at random to team members.
    61. 61. Each person writes something, then passes the sheet to their left, then writes something on the next sheet…</li></li></ul><li>
    62. 62. Actions: Same/More/Less<br />
    63. 63. Facts: Plus/Minus/Interesting<br />
    64. 64. Process: Works Well/Needs Improvement<br />MAX UPGRADE NEEDS TO BE UPGRADED<br />
    65. 65. Changes: Plus/Delta<br />
    66. 66. Who? How? When? How to verify?<br />
    67. 67. Retrospective of Retrospectives<br />
    68. 68. Self-Retrospective<br />
    69. 69. Decision Log<br />http://bit.ly/KamaSutra_Self<br />
    70. 70. Distributed Retrospectives<br />Separate individual vs. joint improvements<br />Individual meeting before joint<br />Offline part: use surveys<br />More time to check in<br />Use wiki to store results!<br />
    71. 71. References<br />Retrospective Plans http://bit.ly/KamaSutra_Plans<br />Lateral Thinking http://bit.ly/KamaSutra_DeBono<br />Self Retrospective http://bit.ly/KamaSutra_Self<br />
    72. 72. Let’s retrospect this presentation…<br />
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×