Unlike a post-mortem—where you discuss what went wrong (and what you can learn from it)—in a pre-mortem, you get together earlier in a project’s lifecycle and ask the team to assume that the project has failed. And you prompt the team to come up with the reasons why.
-
-
The way I like to run pre-mortems now is to ask them to list out their concerns about the project in 3 different categories:
Prikaži ovu nit -
-
-
Why are you not worried about a Paper Tiger (even though others might be)? Usually because you’re responsible for the said area and have strong conviction that the ostensible Tiger is fully under control. You’ve got it!
Prikaži ovu nit -
-
An Elephant might not be a threat per se, but it’s the thing you’re worried no one is talking about. It’s the “elephant in the room”.
Prikaži ovu nit -
So, with this lexicon, here’s how I recommend running a pre-mortem meeting:
Prikaži ovu nit -
-
During the context setting part, I introduce the pre-mortem concept (it’s always *someone’s* first pre-mortem) and ask everyone on the team to come up with: 2 Tigers (at least), and any Paper Tigers and Elephants they can think of.
Prikaži ovu nit -
There is absolutely no talking during this time. Quiet time! It’s amazing how long & productive a 10 minute stretch of silence can be in a meeting, when no one is talking.
Prikaži ovu nit
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.