D- Discretionary dependencies are dependencies defined by the project management team. This may also encompass particular approaches because a specific sequence of activities is preferred, but not mandatory in the project life cycle. dependencies are dependencies that involve a relationship between project activities and E-External project activities such as purchasing/procurement M,D,E 1 New mainframe available for testing M, E 9.0 1 DoIT will have mainframe environment available for testing no later than May14, 2012 10.0 Risk 1 Probability Impact Description - Project will LOW High be at risk if all stakeholders Emphasize communication to all Mitigation Strategy: are not engaged at the stakeholders to be sure they understand the benefits of a beginning of the project successful project. This risk will be addressed during the planning Contingency Plan: phase so that necessary communication takes place throughout the project. Risk 2 Probability Impact Description - Project will Medium High be at risk if the DoIT and Continue to work with DoIT as they plan the Mitigation Strategy: their vendors have implementation and build out the hardware and software significant delays in environment implementation of the new Review the schedule regularly with DoIT to Contingency Plan: mainframe address any scheduling issues. Risk 3 Probability Impact Description - Project will Medium Medium be at risk if the scope of the Work with vendor selected for test and use Mitigation Strategy: case development and monitor progress.
project D- Discretionary dependencies are dependencies defined by the project management team. This may also encompass particular approaches because a specific sequence of activities is preferred, but not mandatory in the project life cycle. E-External dependencies are dependencies that involve a relationship between project activities and activities such as purchasing/procurement M,D,E 1 New mainframe available for testing M, E 9.0 1 DoIT will have mainframe environment available for testing no later than May14, 2012 10.0 Risk 1 Description - Project will be at risk if all stakeholders are not engaged at the beginning of the project Probability LOW Impact High Mitigation Strategy: Emphasize communication to all stakeholders to be sure they understand the benefits of a successful project. Contingency Plan: This risk will be addressed during the planning phase so that necessary communication takes place throughout the project. Risk 2 Description - Project will be at risk if the DoIT and their vendors have significant delays in implementation of the new mainframe Probability Medium Impact High Mitigation Strategy: Continue to work with DoIT as they plan the implementation and build out the hardware and software environment Contingency Plan: Review the schedule regularly with DoIT to address any scheduling issues. Risk 3 Description - Project will be at risk if the scope of the Probability Medium Impact Medium Mitigation Strategy: Work with vendor selected for test and use case development and monitor progress.
ONGARD%20Mainframe%20Stabilization%20Initiation%20and%20Implementation%20Project%20Charter%20041612%20v1.4%20FINAL.docx