During a status meeting, a functional manager complains that the server backup failed, impacting the department. This was a known risk documented in the risk register as an accepted risk. After…

Question

Options

• AQualitative analysis
• BSensitivity analysis
• CStakeholder analysis
• DQuantitative analysis

• A
  8% (2)
• B
  4% (1)
• C
  84% (21)
• D
  4% (1)

Explanation

Stakeholder analysis is the process of systematically identifying all parties who have an interest in, or are affected by, the project - and ensuring they are appropriately engaged in project processes, including risk planning. Had proper stakeholder analysis been performed, the functional manager would have been identified as a key stakeholder whose department is impacted by the server backup risk. Their inclusion in the risk planning phase would have ensured they were aware of the accepted risk and could have prepared contingency measures or at minimum been informed of the acceptance decision. Options A and B (qualitative and sensitivity analysis) are risk analysis techniques, not identification methods for stakeholder inclusion. Option D (quantitative analysis) is a risk analysis method. The root cause here was a gap in stakeholder identification and engagement - a deficiency corrected by thorough stakeholder analysis during the risk planning process.

No community discussion yet for this question.