Pre Mortem Retrospectives
Upcoming SlideShare
Loading in...5
×
 

Pre Mortem Retrospectives

on

  • 3,625 views

Pre Mortem Retrospectives are a powerful way to prevent project failures before they occur. ...

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

Statistics

Views

Total Views
3,625
Views on SlideShare
3,594
Embed Views
31

Actions

Likes
9
Downloads
89
Comments
0

3 Embeds 31

https://twitter.com 23
http://www.linkedin.com 7
http://paper.li 1

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • note: premortem is not risk analysis
  • Innovation Games: Remember The Future

Pre Mortem Retrospectives Pre Mortem Retrospectives Presentation Transcript

  • Pre-Mortem Retrospectives G.Mazzanti @mgaewsj
  • 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
  • + ( ) Gary Klein, “ Performing a Project Premortem”, 2007, HBR
  • agile retrospective a special meeting held throughout a project where a team inspect and review events, methods and teamwork and immediately learn and adapt
  • 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
  • Retrospective Structure
    • Set the Stage
    • Gather Info
    • Generate Insights
    • Decide Actions
    • Close
    • time-travel to a date after the scheduled release date
    • assume that the project has failed miserably
    welcome state purpose everybody speaks outline approach 5’
  • 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
  • team identify key events good , bad and neutral (but relevant) 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’
  • 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’
  • generate quick ideas what 25’
  • how who & when pick 2 or 3 actions (dot vote), elaborate two dots per person top priority second choice 15’ 15’
  • pick 2 or 3 actions (dot vote) two dots per person top priority second choice 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’
    • ROTI Return On Time Invested
    • Take Visual Records
    • Plan for Follow-Up
    • Appreciation for everyone
    5’
    • time-travel to a date after the scheduled release date
    • assume that the project has been a huge success
    variant see also Tim Mackinnon http://www.planningcards.com/iterex/papers/Futurespectives.pdf
  • Gaetano Mazzanti Gama-Tech @mgaewsj [email_address]