risk-assessment

Conduct a pre-mortem analysis by assuming project failure has occurred and working backward to identify the technical, dependency, scope, and execution risks that caused it. This surfaces assumptions and blockers before development begins.

Perform contingency planning for multi-team initiatives by identifying critical dependency and execution risks, assessing their likelihood and impact, and defining mitigation actions with clear ownership. This maintains traceability to decisions and delivery confidence.

Pre-mortem analysis is a technique to anticipate project failure by assuming the worst outcome and reverse-engineering the root causes. Use it during early scoping to surface technical and scope risks before committing to execution.

Yes, you can integrate risk mitigation into standard workflow planning by mapping contingency plans and owners directly into the execution timeline. This aligns risk registers with ongoing development tasks to track status and resolve blockers.

Structure a risk register by listing identified risks, their assigned categories, likelihood, impact scores, mitigation actions, and current status. This provides traceability and integrates risk tracking directly into project planning workflows.