Your SlideShare is downloading. ×
The Kama Sutra of Retrospectives
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

The Kama Sutra of Retrospectives


Published on

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

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

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

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