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 team decided to go ahead with the release and address this missing feature at a later date. One of the end users learned about this and strongly opposed the planned release.
What should the risk manager have done to prevent this situation?
A risk manager and relevant stakeholders have completed a risk response plan for a project. They have identified and planned responses to the known risks; however, a risk owner has identified and reported some residual risks not previously addressed.
What should the risk manager do first?
While performing risk identification exercises, the risk manager often encounters biases from the project team. How can the risk manager accurately identify what will trigger a risk?
An experienced and the only developer on a software implementation project will be on leave for several weeks. The risk of this critical resource ' s availability was added to the risk register. Contingencies were made for a support developer to job shadow this resource, depending on how things go prior to their leave. The project team was pleased with the backup plan and the new resource was able to shadow for a few weeks.
What should the risk manager do next?