Pre-Mortem Analysis Core rule: Prospective hindsight beats "what could go wrong?" Assume the plan has already failed (past tense), generate concrete failure paths, reverse them into prevention requirements, and bind each top path to a verifiable plan change. When to Use - Before kickoff, major technical commitment, high-risk sprint work, launch, or release. - After a plan looks solid but before execution, especially when optimism or overconfidence is likely. - When a decision is costly to reverse and risks are still implicit rather than enforced. When NOT to Use - Work is small, local, and ch…