A software development project team was preparing for a phased release when an unknown and unexpected risk occurred with potential for delaying one of the features for the planned release. The project

Question

Options

• AEngaged the sponsor and informed them of the decision to remove the planned feature.
• BEngaged the stakeholders more in risk management activities and decisions to get their buy-in and
• CPerformed proper risk identification at the project outset to ensure this risk was identified and
• DCreated a schedule buffer in the plan to deal with unknown risks if and when they occurred.

• A
  14% (3)
• B
  77% (17)
• C
  5% (1)
• D
  5% (1)

Explanation

The end user's opposition arose because they were not consulted or informed about the decision to defer the feature. This reveals a gap in stakeholder engagement throughout the risk management process. Had stakeholders been actively involved in risk identification, analysis, and response decisions, their concerns would have surfaced before the release decision was made - and the team could have obtained their buy-in or adjusted the plan accordingly. Option A (informing the sponsor) addresses only upward communication. Option C (better upfront identification) is partially valid but wouldn't have solved the lack of ongoing stakeholder involvement. Option D (schedule buffer) addresses unknown risks but not the stakeholder communication failure.

No community discussion yet for this question.