- Focus on the 20% of risks causing 80% of potential impact (Pareto rule).
- Balance high-probability/low-loss vs. low-probability/catastrophic-loss threats in the Risk Register.
Prioritizing Risk Exposure
- Knowledge Risk: Deficient technical skills applied to a problem.
- Relationship Risk: Ineffective collaboration or team conflict.
- Process-Engagement Risk: Broken operational procedures reducing productivity & quality.
- Avoidance Strategies: Reduce probability the risk occurs (e.g., use mature framework).
- Minimization Strategies: Reduce impact if it hits (e.g., backups, cross-training).
- Contingency Plans: Ready-to-run fallback if disaster strikes.
Risk Categories & Identification
External
Infrastructure (networks/power), Economic (inflation/FX), Legal & Regulatory, Environmental, Political, Market, Acts of God.
Financial & Activity
Budgetary shortfalls, Fraud/Theft, Operational policy failures, Information loss, Reputational damage.
Technological & Human Resources
New/unproven innovation risks, Personnel shortfall (tracked via metrics!), Health & Safety.
Structured Discovery Tools
1. Assumptions Analysis: Stress-test every timeline assumption.
2. Checklists & Prompt Lists: Historical risk catalogs.
3. Brainstorming & Facilitated Workshops: Team risk surfacing.
4. Open-Question Interviews: Supportive, non-confrontational stakeholder interviews.
7-Step Continuous Cycle
Establish Context → Identify → Analyze → Evaluate → Treat → Monitor/Review → Communicate (never stop after one pass).
Decision Trees, Influence & Monte Carlo
- Flowchart comparing choices (e.g., Build vs. Buy) with probabilities and payoffs at each branch.
- Best for clear, bounded decisions; gets messy in huge systems.
- Nodes hold variables/decisions showing how an upstream risk ripples across downstream schedule or cost outcomes.
- Runs thousands of random trials across task duration distributions (like PERT a, m, b) to forecast completion date probabilities.
Managing Finite Resources
Finite Resources
A PM cannot always hire more staff mid-sprint (e.g., only 1 UI designer available across parallel tasks = resource conflict).
Resource Leveling / Smoothing
Delay non-critical tasks using their Float/Slack so daily staff & equipment usage stays realistic without delaying the project end date.
1. Identify Resource Requirements: Skills, roles, hardware & software tools per WBS package.
2. Schedule Resources: Map allocations onto timeline & resolve overlaps.
3. Publish Resource Schedule: Communicate exact staffing commitments to the team.
4. Publish Cost Schedule: Convert labor/tool hours into phased budget curves (PV baseline).
Visibility, Slip Charts & Control
- 1. Track Progress: Verify actual completion against WBS milestones.
- 2. Detect Variance: Spot schedule/cost slippage early (EVM & Slip Charts).
- 3. Take Corrective Action: Rebalance controls with risk (control and quality are positively correlated).
- Slip Charts & Timelines: Show how target milestone dates shift across review checkpoints.
- Status vs. Problem Meetings: Keep status reporting brief; dedicate separate focused meetings to solving blockers.
Completed Concept 7: Risk & Resource Management
Next up: Software Quality Management, ISO 9126, QA vs. QC, and Mr Bhuru's 6Ms Ishikawa Fishbone Diagram.