Project Risk & Quality Management: Tools, Processes & Case Studies

Core Concepts

1. Project Risk Management: Definition & Framework

Risk in projects = uncertainty of outcome that may positively/negatively impact objectives. The PMBOK framework breaks it into 6 processes:

graph LR
    A["Risk Management Plan"] --> B["Risk Identification"]
    B --> C["Qualitative Risk Analysis"]
    C --> D["Quantitative Risk Analysis"]
    D --> E["Risk Response Planning"]
    E --> F["Risk Monitoring & Control"]
    F -->|"Feedback"| A

Key Terms:

• Risk Event: Single uncertain event (e.g., "delay in NTC approval for Khimti-I hydropower").
• Risk Impact: Financial, schedule, or quality effect (e.g., "3-month delay → $500K penalty").
• Risk Owner: Person accountable (e.g., "Project Manager for regulatory risks").

2. Risk Identification Techniques

Worked Example: Khimti-I Hydropower BOOT Risks

1. Political Risk: Government may change policy → Mitigation: Lobbying with Ministry of Energy.
2. Technical Risk: Unforeseen geological issues → Mitigation: Geological surveys + contingency budget.
3. Financial Risk: Currency fluctuation (USD to NPR) → Mitigation: Hedging contracts.

3. Qualitative vs. Quantitative Risk Analysis

Worked Example: eSewa’s Agile Risk Handling

• Qualitative: Daily standups flag "High" risks (e.g., "Payment gateway downtime") → Immediate fixes.
• Quantitative: For major updates (e.g., "New KYC module"), run Monte Carlo to estimate failure costs.

4. Risk Response Strategies

mindmap
  root((Risk Responses))
    Avoid["Eliminate the risk"]
      ex["Cancel Khimti-I phase if political risk too high"]
    Transfer["Shift to 3rd party"]
      ex["Insurance for Daraz warehouse fires"]
    Mitigate["Reduce probability/impact"]
      ex["Backup generators for NTC grid projects"]
    Accept["No action"]
      ex["Minor risks like 'printer failure'"]

Real-World Tie-In: Ncell’s 4G Rollout

• Avoided risks by phasing deployment (Pokhara → Kathmandu).
• Mitigated network congestion with dynamic spectrum allocation.

Quality Management in Projects

1. Quality Planning Process

flowchart TD
    A["Define Quality Standards"] --> B["Quality Assurance (QA)"]
    B --> C["Quality Control (QC)"]
    C --> D["Quality Improvement"]
    D -->|"Feedback"| A

Key Tools:

• Cost of Quality (COQ) Model:

  pie
    title Cost of Quality
    "Prevention Costs": 20
    "Appraisal Costs": 30
    "Failure Costs": 50

  • Prevention: Training (e.g., "ISO 9001 certification for Daraz suppliers").
  • Appraisal: Inspections (e.g., "NTC testing hydropower turbines").
  • Failure: Rework/liabilities (e.g., "Recalled defective Ncell SIM cards").

2. Quality Control Techniques

Worked Example: Kathmandu Traffic Management

• Problem: 60% delays due to "unplanned roadworks."
• Solution: Pareto Analysis → Focus on top 3 causes (e.g., "Lack of coordination between KUPA and local governments").
• Control Chart: Track "Average Daily Congestion Hours" before/after fixes.

3. Project Quality vs. Product Quality

In the Real World

1. eSewa’s Risk Management

   • Idea Used: Qualitative risk assessment in agile sprints.
   • How: Daily standups classify risks as "High/Medium/Low" using a Probability-Impact Matrix. Example: "High" = "Database breach"; "Low" = "Printer jam."
   • Outcome: Reduced major outages by 40% in 2023.

2. Daraz’s Supply Chain Quality Failures

   • Idea Used: Cost of Quality (COQ) and Pareto Analysis.
   • How: After 2022’s "missing orders" scandal, Daraz applied Pareto to find 80% of issues came from 3 warehouses (poor inventory tracking). Invested in RFID tags (Prevention Cost) to cut failure costs.
   • Lesson: Nepal’s e-commerce must balance appraisal costs (inspections) vs. failure costs (refunds).

3. NTC’s Power Grid Projects

   • Idea Used: Risk Register + SWOT Analysis.
   • How: For the West Seti Hydropower Project, NTC’s risk register listed:
     • Opportunity: "Government subsidies for renewable energy."
     • Threat: "Monsoon-induced landslides."
   • Tool: Monte Carlo simulation estimated a 75% chance of on-time completion with current mitigation.

Case Study: Khimti-I Hydropower BOOT Project

Background: Nepal’s first BOOT (Build-Own-Operate-Transfer) hydropower plant (60MW), funded by GMR Energy (India).

Risk Management in Action

1. Political Risk:

   • Identification: "Government may renegotiate tariffs."
   • Response: Transfer (hedging contract with World Bank guarantees).

2. Technical Risk:

   • Identification: "Unstable rock formations."
   • Response: Mitigate (spent $2M on geological surveys + contingency budget).

3. Quality Risk:

   • Tool: Control Charts tracked turbine efficiency weekly.
   • Outcome: Achieved 98% reliability (vs. industry average of 90%).

Quality Management Lessons

• PDCA Cycle:
  • Plan: Set ISO 9001 standards for construction.
  • Do: Built with Swiss-made turbines.
  • Check: Monthly inspections by Nepal Electricity Authority (NEA).
  • Act: Adjusted dam design after first monsoon data.

Exam Tip: How to Score Full Marks

1. Risk Management (30% of unit marks)

   • Must Include:
     • Definition of risk + PMBOK’s 6 processes.
     • One real Nepali example (e.g., "Ncell’s 5G rollout risks").
     • Comparison table (Qualitative vs. Quantitative).
   • Avoid: Generic answers like "risks can be positive/negative." Show calculations for quantitative risks (e.g., EMV = Probability × Impact).

2. Quality Management (40% of unit marks)

   • Must Include:
     • COQ model (Prevention/Appraisal/Failure costs).
     • PDCA cycle with a real project (e.g., "How Daraz improved order accuracy").
     • Quality tools: Draw a control chart or fishbone diagram in your answer.
   • Avoid: Confusing project quality (processes) with product quality (output). Use the table above to clarify.

3. Case Study (30% of unit marks)

   • Structure:
     1. Background: 1 paragraph on the project (e.g., Khimti-I BOOT).
     2. Risk Analysis: Use SWOT or risk register template.
     3. Quality Tools: Apply PDCA or Pareto.
     4. Lessons: Tie back to Nepal’s context (e.g., "BOOT projects need stronger regulatory risk planning").

Pro Tip: For short-answer questions (e.g., "Define quality planning"), use the acronym "QCQP":

• Quality Control (Inspections)
• Quality Assurance (Processes)
• Quality Planning (Standards like ISO 9001)

Visual Summary for Last-Minute Revision

classDiagram
    class Risk {
        +Identify()
        +Analyze()
        +Respond()
    }
    class Quality {
        +Plan()
        +Assure()
        +Control()
        +Improve()
    }
    Risk --> "Uses" Quality : "Risk to quality impacts project success"
    Risk --> "Influenced by" Environment : "Political, Economic, Social"
    Quality --> "Measured by" COQ : "Cost of Quality Model"