A project can run into trouble even when its plan looks sound. Technical complexity, tight deadlines, and external factors can threaten the outcome. Risk management means identifying those uncertainties early, deciding which need attention, and checking whether the response is working. Risks can arise at any stage, so the work continues after kickoff. section 10.1 section 10.1.3
Use a simple team routine:
- Identify: bring the project team together to brainstorm potential risks. section 10.1.3
- Categorize: consider how severely each risk could affect the project. section 10.1.3
- Prioritize and assign: agree which risks to address and give each an owner and mitigation timeline. section 10.1.3
- Plan and act: owners develop mitigation plans and drive them to completion. section 10.1.3
- Check in: revisit progress during team sync-ups and confirm that plans remain aligned. section 10.1.3
ROAM offers a lightweight way to describe a risk’s status: Resolved means it is no longer open; Owned means someone is responsible for a time-boxed resolution effort; Accepted means the team will live with the consequences; and Mitigated means the team has acted to reduce its severity. Acceptance is a decision, not a claim that the risk has disappeared. section 10.1.3
A portfolio trade-off
An engineering manager overseeing two new-product projects and a legacy-system improvement may find that the new products face greater competitive urgency. Portfolio-level risk management can support assigning extra resources or adjusting timelines—for example, placing the legacy improvement in the background. That choice still needs deliberate assessment of the risks across all three projects. section 10.1
At the next team sync-up, ask: Which risks have changed, who owns the response, and does the current plan still reduce the threat to the project outcome? section 10.1.3
