Successfully reported this slideshow.
Your SlideShare is downloading. ×

Pre Mortem Retrospectives

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Upcoming SlideShare
Pre-mortem tool
Pre-mortem tool
Loading in …3
×

Check these out next

1 of 18 Ad

Pre Mortem Retrospectives

Download to read offline

Pre Mortem Retrospectives are a powerful way to prevent project failures before they occur.
Resting on the standard Agile Retrospective format you flash-forward to a date after the scheduled release date and assume that the project has failed miserably

Pre Mortem Retrospectives are a powerful way to prevent project failures before they occur.
Resting on the standard Agile Retrospective format you flash-forward to a date after the scheduled release date and assume that the project has failed miserably

Advertisement
Advertisement

More Related Content

Slideshows for you (20)

Similar to Pre Mortem Retrospectives (20)

Advertisement

More from Gaetano Mazzanti (19)

Recently uploaded (20)

Advertisement

Pre Mortem Retrospectives

  1. 1. Pre-Mortem Retrospectives G.Mazzanti @mgaewsj
  2. 2. catch ‘failure’ before it occurs circumvent any need for a painful postmortem “ You’ve seen your own future, which means you can change it if you want to.” Chief John Anderton, Minority Report
  3. 3. + ( ) Gary Klein, “ Performing a Project Premortem”, 2007, HBR
  4. 4. agile retrospective a special meeting held throughout a project where a team inspect and review events, methods and teamwork and immediately learn and adapt
  5. 5. agile retrospective a special meeting held throughout a project where a team inspect and review events, methods and teamwork and immediately learn and adapt premortem before prevent anticipate p
  6. 6. Retrospective Structure <ul><li>Set the Stage </li></ul><ul><li>Gather Info </li></ul><ul><li>Generate Insights </li></ul><ul><li>Decide Actions </li></ul><ul><li>Close </li></ul>
  7. 7. <ul><li>time-travel to a date after the scheduled release date </li></ul><ul><li>assume that the project has failed miserably </li></ul>welcome state purpose everybody speaks outline approach 5’
  8. 8. team identify key events & feelings good , bad and neutral (but relevant) who what when facts feelings 10’ mar apr may jun jul aug sep oct
  9. 9. team identify key events good , bad and neutral (but relevant) 10’
  10. 10. what didn’t work what worked well why causes & effects then each person writes 4 * sticky notes (2 for what worked well and 2 for what didn’t work ) *choose what suit best 25’
  11. 11. silent grouping items are grouped silently by the team each group is then given a name one or two groups are selected for action 25’
  12. 12. generate quick ideas what 25’
  13. 13. how who & when pick 2 or 3 actions (dot vote), elaborate two dots per person top priority second choice 15’ 15’
  14. 14. pick 2 or 3 actions (dot vote) two dots per person top priority second choice 15’ 15’
  15. 15. put actions on a task board, be sure there is commitment and energy to achieve goals to do in progress done 15’ 15’
  16. 16. <ul><li>ROTI Return On Time Invested </li></ul><ul><li>Take Visual Records </li></ul><ul><li>Plan for Follow-Up </li></ul><ul><li>Appreciation for everyone </li></ul>5’
  17. 17. <ul><li>time-travel to a date after the scheduled release date </li></ul><ul><li>assume that the project has been a huge success </li></ul>variant see also Tim Mackinnon http://www.planningcards.com/iterex/papers/Futurespectives.pdf
  18. 18. Gaetano Mazzanti Gama-Tech @mgaewsj [email_address]

Editor's Notes

  • note: premortem is not risk analysis
  • Innovation Games: Remember The Future

×