Risk management is the systematic process of identifying, analyzing, and responding to project risks. A risk is any uncertain event that could positively (opportunity) or negatively (threat) affect project objectives.
Risk Management Process
Plan Risk Management — Define approach, roles, and budget
Change management ensures that changes to project scope, schedule, or resources are formally reviewed and approved. Key components:
Change Control Board (CCB) — reviews and approves/rejects changes
Change Request Form — documents the proposed change
Impact Analysis — assesses effect on constraints
Change Log — tracks all change requests and their status
Conflict Management
Five approaches to resolving conflict (Thomas-Kilmann model):
Avoiding — Withdraw from conflict (low assertiveness, low cooperation)
Accommodating — Yield to others (low assertiveness, high cooperation)
Competing — Force your position (high assertiveness, low cooperation)
Compromising — Find middle ground (moderate both)
Collaborating — Find win-win solution (high both) — most effective
Crisis Management
When risks materialize into crises, follow these steps: assess the situation immediately, assemble a crisis team, communicate transparently with stakeholders, contain damage, develop a recovery plan, and conduct a post-mortem.
Practice Task: Identify 5 risks for a software development project. Perform qualitative analysis by rating each on probability (1-5) and impact (1-5). Create a risk response plan with mitigation strategies for each. Draft a change request template and a change log format.