Paper
8
Data Center Migration Project
Student Name
Course Instructor
Institutional Affiliation
Date
Overall project budget
Task Name |
Planned Value |
Earned Value |
Actual Cost to Date |
Start Date |
Estimated completion Date |
Actual Completion Date |
Planning |
|
|
|
|
|
|
Vendor and supplier acquisition |
||||||
System and environmental Assessment |
||||||
Organization and staff assessments |
||||||
Employee Training |
||||||
Migration Process |
|
|
|
|
|
|
Hiring contractors |
||||||
Data Migration Costs |
||||||
Labor Costs |
||||||
Employee training costs |
||||||
After Migrations |
|
|
|
|
|
|
System Audits |
||||||
System tests and approval |
||||||
Project requirements
The project requirement will be divided into the following areas:
Financial requirements: The financial resources will not require any changes since the estimated budget was already approved to meet the required needs and is within the financial budget and expectation of the business.
Human resources: There will be a change in the training resources needed: There is a new development in terms of the levels of training needed by the employees. The new trainings will focus on team aspects to ensure the new teams consisting of various employees from various departments can work together as a team. The human resources will also change due to the acquisition of data analysis team: the new team will be responsible for data cleaning to ensure the organization does not have redundant data and all the relevant data are converted into the necessary format to ensure compatibility. The new team will also be responsible for data analysis before transferring them to the new cloud systems.
There is also be a change in the vendors and suppliers required: the new vendors are required to provide training resources the company currently lacks. This is due to the new demand for employee training simulator to give employees a new glimpse of the new operation system to ensure success. They will maintain their resources provision roles and also provide any new resources that may be needed to ensure compatibility and system efficiency.
Cost management plan
The costs currently available are projected to meet the demands however in case of any changes there are various cost management plans. One of them include reduction in overtime payments by engaging other employees in other departments to help with other tasks such as data cleaning, editing and verification (Jayaraman, 2016). However, the organization will maintain costs for certain system such as software and hardware to ensure authenticity.
The second costs management plan is reduction in project duration by increasing the size of the project team to ensure costs due to project duration are minimized (Jayaraman, 2016). This is also necessary to ensure the organization saves certain costs in the process of data migration.
In case the costs exceed and there are new emergencies that require additional costs. There are three financing method namely equity, loans and organization capital (Jayaraman, 2016)
. In case of shortage, the organization can sue the loans or its own cash to finance the sudden and new changes and financial requirements.
Risk management plan
The migration risk management plan will ensure the potential risks are minimal and the changes of occurrences are minimized. Here is a framework to manage and mitigate the risks.
Challenge |
Sources |
Mitigation |
Migration underestimation |
Limited budgeting, too much time on the budget, inflation, limited resources to accomplish the task in time. |
Contingency financial sources for resource acquisition. Project milestone and schedule to ensure every activity is completed in time |
Data loss |
Data redundancy, employee omission and scattered data |
Data cleansing, analysis and mapping |
System errors during data migration |
Improper system phasing, multiple system operations and system age. |
Data control software that will manage the migration process from old to new system |
Date incompatibility |
Wring data format, omission of certain content, skipping certain procedures and poor data quality |
Data test software to ensure the new data and system meets the anticipated benefits. |
System crash and errors |
Lack of skills and knowledge System. |
Employee training and certification Employee new staff to manage the system. System audits Ensure uniform communication to avoid confusion. |
Communications challenges |
Lack of uniform communication platform |
Develop a uniform communication platform Divide projects into teams for easy communication Review meetings to ensure the milestones are achieved and the data is correct. |
Risk response plan
To avoid the risks within the pan, the project already has effective mitigation measures. However, in case of any risks the organization has a response plan based on the following criteria.
Risk |
Source |
Response plan |
Limited resources Time lapse and extension Lack of expertise and human resources |
Inflation Data and process underestimation Employee increased turn over limited knowledge |
Project budget adjustments to meet the new costs. |
New changes New data Need for system updates |
Technology changes Market changes System diagnosis and trouble shooting |
Change in system and project scope Changi in budgeting and provision of additional finance |
Time lapse System errors and unresponsiveness |
Employee delay due to lack of skills Data errors System incompatibility |
Hire expert Outsource some migration procedures and processes Introduce new workflow and processes |
Risk mitigation plan
The risk mitigation plans are the procedures currently implemented to avoid the occurrence of risks:
Review meetings: One of the mitigation plans include the weekly, monthly group and managers’ meetings. The purpose of these meetings is to review the project success and development to avoid risks of delays or certain errors (Ward & Chapman, 2018). These meetings also focus on the potential errors during the project and implementing instant mitigation measures.
Data migration checklists: The checklist contain issues related to data formatting, cleansing, testing before migrating to a new system. It also covers any errors that may occur ad how to resolve them (Ward & Chapman, 2018). Finally, it contains all the essential elements that must be included in the process to ensure system compatibility and efficiency.
Project milestone and KPIS: this covers the project objectives and the activities to be performed under every milestone and the duration required to accomplish the project (Ward & Chapman, 2018). This minimizes system risks, data omission and any related errors.
Change management process
The change management process is conducted through various adjustments. This include change in the workflow to cover the present changes. Teamwork which makes implementing the changes efficient and easy.
Budget and milestone changes: Whenever there are new changes, the project budget, milestones will also be adjusted to ensure the new changes reflect in the review meetings and are implemented.
Strategic communication: Every change is a subject of communication. The changes will include minor changes within the team to ensure that making such changes dies not affect other teams and activities.
Managing project RAID
The risks will be subject to the mitigation plans to avoid occurrence. In case of the occurrence then they will be a part of the response plan. Every assumption will be subjected to a test to ensure they do not have effect on system operations and data migrations. The assumptions will be captured and treated as potential risks to avoid being ignored. The dependencies and issues will be reviewed in the weekly meetings and be a part of the communication process to ensure the details are not left. The dependencies will be shared amongst the teams to avoid potential errors that may spread across the teams.
References
Jayaraman, R. (2016). Project cost control: a new method to plan and control costs in large projects. Business process management journal.
Ward, S., & Chapman, C. (2018). Transforming project risk management into project uncertainty management. International journal of project management, 21(2), 97-105.