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

1. Pre-Mortem Retrospectives G.Mazzanti @mgaewsj

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. + ( ) Gary Klein, “ Performing a Project Premortem”, 2007, HBR

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. 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

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. team identify key events good , bad and neutral (but relevant) 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. 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. generate quick ideas what 25’

13. how who & when pick 2 or 3 actions (dot vote), elaborate two dots per person top priority second choice 15’ 15’

14. pick 2 or 3 actions (dot vote) two dots per person top priority second choice 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’

18. Gaetano Mazzanti Gama-Tech @mgaewsj [email_address]