Risk and Quality Management

• Topic 01

  Risk Identification and Risk Register

  15 questions
• Topic 02

  Qualitative Risk Analysis

  15 questions
• Topic 03

  Quantitative Risk Analysis

  15 questions
• Topic 04

  Risk Response Strategies

  15 questions
• Topic 05

  Risk Monitoring and Residual Risks

  15 questions
• Topic 06

  Quality Planning and Quality Standards

  15 questions
• Topic 07

  Quality Assurance and Process Audits

  15 questions
• Topic 08

  Quality Control Tools and Techniques

  16 questions
• Topic 09

  Compliance and Regulatory Management

  15 questions
• Topic 10

  Process Improvement and Kaizen

  15 questions

A few questions from this unit, with the answer and a full explanation. The complete bank is available when you start practising.

1. A project sponsor decides that a low-probability, low-impact risk requires no contingency reserve and no planned response. If it occurs, the team will deal with it at the time. Which type of acceptance is this, and what documentation is required?

   • A
     This is not a recognised PMI response strategy; all risks must have an active response or be escalated
   • B
     Passive acceptance; the risk should be removed from the register since no action is planned
   • C
     Passive acceptance; the risk should still be documented in the risk register with a note that passive acceptance was the chosen strategy
     Correct answer
   • D
     Active acceptance; a contingency reserve must always be set aside even for low-priority risks
   Explanation

   Passive acceptance is a legitimate PMI-recognised strategy — it consciously decides to take no proactive action. It is appropriate for low-probability, low-impact risks where the cost of any response outweighs the risk's expected value. However, passive acceptance is not the same as ignoring the risk: the risk must remain documented in the risk register with the acceptance decision recorded. If the risk materialises, the team responds with a workaround at that point.

2. A project manager is planning monitoring activities and wants to ensure both that individual risks are up to date AND that the risk management process is functioning effectively. Which two activities should they schedule?

   • A
     Risk reporting and status meetings — both communicate risk status to the team and sponsor on an ongoing basis
   • B
     Risk reassessment (to update individual risk data) and risk auditing (to verify the quality and adherence of the risk management process)
     Correct answer
   • C
     Risk auditing and reserve analysis — both evaluate the financial adequacy of the risk management approach
   • D
     Reserve analysis and technical performance analysis — both measure the effectiveness of risk responses quantitatively
   Explanation

   Risk reassessment answers: 'Are our individual risk assessments still accurate?' It updates probability, impact, and response effectiveness in the register. Risk auditing answers: 'Are we doing risk management properly?' It checks adherence to the risk management plan and process quality. Both are required for comprehensive risk monitoring. Using only reassessment could miss process failures; using only auditing could miss changes in individual risk profiles.

3. A PM is developing quality metrics for a project delivering three distinct types of deliverables: software, documentation, and training materials. A team member proposes using a single generic quality metric (customer satisfaction score ≥ 4/5) for all three. The quality advisor disagrees. What is the STRONGEST argument for deliverable-specific metrics?

   • A
     Different deliverable types have different quality dimensions requiring different metrics; software needs defect density and availability metrics, documentation needs accuracy and completeness metrics, and training materials need comprehension and knowledge retention metrics — a single generic score masks performance variations
     Correct answer
   • B
     A single metric is preferred by PMI because it simplifies quality reporting and reduces administrative overhead
   • C
     Deliverable-specific metrics are only required if the customer has explicitly requested them in the scope statement
   • D
     A single satisfaction score is sufficient because it captures the customer's overall view, which is the ultimate measure of quality
   Explanation

   Quality metrics should be appropriate to what is being measured. Software quality (correctness, reliability, performance) requires technical metrics like defect density, mean time between failures, and test pass rate. Documentation quality requires accuracy, completeness, readability, and currency metrics. Training quality requires comprehension test results, knowledge retention scores, and completion rates. A single customer satisfaction score can be low even when one deliverable type is excellent — masking where the real problem lies. Deliverable-specific metrics enable targeted quality improvements and are a sign of mature quality planning.