Hatari ni kitu ambacho huenda kitatokea na kingeumiza mradi ikiwa kilitokea. Kueneza hatari ni kutambua vitisho hivi mapema na kuamua nini cha kufanya juu yake kabla hayakuingilia. Ujuzi wa bei ya chini: matatizo ni rahisi sana kutunza wakati umeyakubali mapema.
Zana rahisi na inayotumiwa sana kufuatilia mitikitiki ya mradi na vipengele:
R — RISKS → might happen, would cause harm (manage proactively)
A — ASSUMPTIONS → things we're taking as true (validate them)
I — ISSUES → risks that have already materialized (deal with now)
D — DEPENDENCIES → things we rely on from others (track them)
For each risk, score:
LIKELIHOOD (how probable?) × IMPACT (how bad?)
→ focus effort on high-likelihood, high-impact risks
AVOID → change the plan so the risk can't occur
MITIGATE → reduce its likelihood or impact
TRANSFER → shift it (insurance, vendor SLA)
ACCEPT → live with it, but have a fallback ready
Mradi unategemea API ya pande tatu ambayo ni mpya na haijajaribiwa. Hatari: huenda isiwe inafanya kazi vizuri. Uwezekano wa kati, athari kubwa. Kupunguza: ijaribu mapema, jenga uandishi ili uweze kubadilisha wapatanishi, na kuwa na mkakati wa mbadala. Sasa haijulikani ni hatari iliyotozwa na mpango.
Kutibu kueneza hatari kama orodha ya kuangalia mara moja mwanzoni. Hatari huibuka — kagua kumbuku la RAID kwa kawaida na ongeza mpya kadri zinavyotokea.
Hatari zisizotozwa huwa matukio ya dharura, kawaida wakati mbaya zaidi karibu na tarehe ya kumaliza.
Gharama ya kutibu hatari mapema ni ndogo sana kulinganisha na kulipwa matata baada ya kufa.
Kulea hatari wazi pia kujenga imani — wanahusika wanapendelea "hapa kuna nini kinachoweza kuenda vibaya na mpango wetu" kuliko kushangilia kwa utupu ikifuatiwa na msururu mwenye mashari.