Line 185: |
Line 185: |
| |- | | |- |
| |'''RISK''' | | |'''RISK''' |
− | |If the SCED re-architecture goes ahead, then SCED implementation for 370+ other applications/platforms by March 2023 may be delayed. | + | |If the project isn't able to sufficiently resource the Disaster Recovery (DR) role, then a DR program will not be implemented, negatively impacting the recovery of critical IT applications. |
| |- | | |- |
| |'''Impact''' | | |'''Impact''' |
Line 194: |
Line 194: |
| |- | | |- |
| |'''Mitigation''' | | |'''Mitigation''' |
− | |Ongoing assessment of project schedule as SCED implementation develops, and continue to migrate non-SCED dependent apps. | + | |Find resources to create and implement a DR program for the project. |
| |} | | |} |
| | | |
Line 200: |
Line 200: |
| |- | | |- |
| |'''RISK''' | | |'''RISK''' |
− | |If net new applications/platforms are added to project scope, then work on other priority applications/platforms must stop, negatively impacting the project schedule. | + | |If the project team doesn't create and implement a change management process, then they won't be able to effectively navigate project impacts, which will put the overall project at risk. |
| |- | | |- |
| |'''Impact''' | | |'''Impact''' |
− | |Medium | + | |High |
| |- | | |- |
| |'''Probability''' | | |'''Probability''' |
Line 209: |
Line 209: |
| |- | | |- |
| |'''Mitigation''' | | |'''Mitigation''' |
− | |Assess and prioritize new applications/platforms and adjust project schedule accordingly. Submit change request if end date of project needs to move. | + | |Find resources to create and implement a change management process for the project. |
| |} | | |} |
| | | |
Line 230: |
Line 230: |
| |- | | |- |
| |'''ISSUE''' | | |'''ISSUE''' |
− | |The team has recently lost two resources, who were the only automation resources, which means the team is currently unable to deliver on its planned workload migration schedule. | + | |The TC3oE team is in re-build mode, hiring, onboarding, and training new resources, which will impact their ability to deliver on the planned schedule. |
| |- | | |- |
| |'''Impact''' | | |'''Impact''' |
Line 236: |
Line 236: |
| |- | | |- |
| |'''Resolution Plan''' | | |'''Resolution Plan''' |
− | |Escalate to executive team to secure necessary resources and re-prioritize workload. | + | |Adjust schedule to accommodate onboarding of new resources. |
| |} | | |} |
| | | |
Line 242: |
Line 242: |
| |- | | |- |
| |'''ISSUE''' | | |'''ISSUE''' |
− | |Identify critical success factors to prioritize workload then communicate new direction to all key stakeholders. | + | |With the delay in SCED General Availability (GA) until November 2021, the migration of 370+ applications/platforms by March 2023 will be delayed. |
| |- | | |- |
| |'''Impact''' | | |'''Impact''' |
Line 248: |
Line 248: |
| |- | | |- |
| |'''Resolution Plan''' | | |'''Resolution Plan''' |
− | |Create and implement stakeholder engagement plan. | + | |Initiate change request process to adjust project end date to align with MCDC shutdown in 2025. |
| |} | | |} |
| | | |