I need plag report to every part and plag for whole report. Opened for 2 tutors
Part 1 – Project Charter: At the end of week two, you are to create and submit the project charter. This is the first official document to be reviewed and approved by the project sponsor.
The project charter will include the following components:
· Project title – this is the title of the project
· Purpose – notes why this project is occurring
· Description – what will occur (specifically) in this project
· Objective – the goals you hope to accomplish with this project
· Success criteria or expected benefits – what your outcomes will be (measurable)
· Funding – how will the project be paid for
· Acceptance criteria – what are the things the sponsor is looking for to accept the project
· Major deliverables – what are the key milestone deliverables
· Milestone schedule – calendar dates for Major Deliverable listed above.
· Key assumptions – what are some key things you can assume for this project?
· Constraints/risks – potential obstacles to consider during the project that must be accounted for
· Approval requirements – who approves the project and any changes?
· Reporting requirements – what is reports, how frequently, and by whom?
· Project manager – who is the PM?
· Sponsor designee – who is ultimately responsible (name and title)
Part 2
Scope and Schedule: At the end of week 4, you are to finalize the initially approved scope from week two and start building the project schedule. In this week, you are also to work on building the project Work-Breakdown Structure (WBS). Project scope and schedule will include the following components:
– Finalized project scope
– WBS structure
– Develop project schedule
– Identify key milestones and deliverables
– Outline project resources and assign them to tasks accordingly.
– Stakeholder engagement – communication plan
Part 3
Budget and Risk Management: At the end of this week, you are to finalize the overall project cost and clearly document project risks gathered throughout the project. As part of the risk management plan, you are expected to share a risk response plan. Project cost and risk management plans will include the following components:
– Overall project budget (utilizing EVM – share current and forecasted project status)
– Project requirements
– Cost management plan – outlining contingency plan for project changes
– Risk management matrix
– Change management process
– Project RAID (Risk, The assumption, Issues, and Dependencies)
Part 4
Final week, you are to finalize the overall project management plan (PMP) and to integrate all previously submitted components incorporated with instructor (project sponsor) feedback into a single project management plan. The project management plan will include the following components:
– Project quality management plan to include an updated scope, cost, schedule, communication, risk, resources, procurement, and quality)
– Project requirements – updated
– Stakeholder register – updated
– How project RAID (Risk, Assumption, Issues, and Dependencies)will be managed
– Project sponsor approval of the key project deliverables
Project Finalized Scope and Schedule
1.
Finalized project scope
The finalized scope of a project aimed at transforming legacy data centers and migrating a firm’s applications to the cloud is: creating a plan for transforming a client’s data center, both on-premise and IT infrastructure, assessing the requirements, identifying all the activities to transform the data center, identifying stakeholders and resources required to complete the project, creating WBS and project schedule (Watt, 2014). It also entails identifying significant milestones based on project phases, deliverables, and allocating resources to execute tasks, as well as arranging stakeholder interaction and choosing relevant communication channels.
2. Project requirements
The following are some of the high-level criteria for a project focused on modernizing three old data centers at a company:
· Within the $1.5 million budget, move 145 enterprise applications and infrastructure to the cloud, including 450 windows servers, 550 Unix servers, and 350 legacy AIX, VMWare, and ESX servers.
· Determine the characteristics and capabilities of a data center in order to store more data without compromising security or privacy, avoid data loss, carry out business operations, and fulfill the primary demands and expectations of stakeholders.
· Using common tools, such as Microsoft project management, to define the project’s core activities and build a timetable (Gido, Clements, & Baker, 2017)
· Using modern project financial management software to anticipate the cost and budget required to complete the project, conduct cost-benefit analysis, manage the budget, and achieve success.
· Using common tools such as the RACI matrix to analyze stakeholders, decide and plan resources, conduct activities, and execute projects according to the plan produced.
· Develop standard data backup strategies to retrieve information in the event of a disaster, as well as load and extract data without losing any data.
·
Improving a data center’s efficiency by storing data, providing faster access to resources and data, simplifying data center management, reducing expenses, and promoting production
These are the most important requirements for a project, and meeting them helps to avoid problems for the client and to meet their demands effectively.
3. WBS structure
A project’s work breakdown structure (WBS) for data center transformation and cloud migration entails breaking down a large project into smaller segments so that tasks can be managed more easily, and deliverables may be met (Watt, 2014). The project’s work breakdown structure is as follows:
WBS
Task Name
1
Transforming legacy data centers and move to cloud
1.1
Requirements analysis
1.1.1
Performing meetings
1.1.2
Recognizing problems
1.1.3
Creating plan
1.1.4
Review plan
1.2
Design
1.2.1
Data center designing
1.2.2
Software and hardware design
1.2.3
Design specification and review
1.3
Development
1.3.1
Obtaining resources
1.3.2
Training staff
1.3.3
Installing hardware and software
1.3.4
Data loading and extraction
1.3.5
Data conversion
1.3.6
Initial testing
1.4
Testing
1.4.1
Unit testing
1.4.2
System testing
1.4.3
Performance testing
1.4.4
Integration testing
1.5
Maintaining
1.5.1
Observing data center working
1.5.2
Identifying and making changes
1.5.3
Approval and project closing
Figure 1: WBS structure
4.
Developed project schedule and tasks assigning
The project timeline entails establishing all of the tasks and resources required to accomplish the project, as well as the time required to complete each work, allocating resources, and determining the overall duration to migrate legacy data centers and meet client needs (Gido, Clements, & Baker, 2017). The project’s schedule will be followed as follows:
Figure 2: Project schedule
5.
Key milestones and deliverables
Milestones are important components of a project that illustrate important events, track progress, and ensure that targeted deliverables are met. The following are the project’s major milestones and deliverables:
Milestone
Date of completion
Stakeholder
Acceptance criteria
Acquiring resources
7/1/21
Hardware specialist
Obtaining the software and hardware resources required to complete the project within the specified cost and scope
IT infrastructure setup
7/15/21
IT specialist
Infrastructure is put up in accordance with the transformation plan.
Information extraction
7/28/21
Project manager
Using rules and laws, data is extracted from the data center.
Data conversion
8/13/21
Algorithms are used to change data, match customer needs, and ensure scope.
Data loading and migration
8/31/21
Data center specialist
Data loading from legacy data centers to the cloud ensuring scope
Testing and approval
9/10/21
Data center specialist and compliance manager
Testing the plan developed for data center transformation and ensure it is aligned with the rules and regulations
6.
Stakeholder engagement
A communication strategy is created to help project stakeholders communicate effectively, share information, and complete tasks by using the most appropriate communication means. It is then followed by:
Name of communication
Frequency
Audience
Method
Team meetings
Daily
Project team
Meeting
Stakeholder update
Monthly
Project stakeholders
Newsletter
Board meeting
Weekly
Board of directors for project
Video conference
Discussing issues
Daily
Project team
Email, newsletter and socialmedial communication
References
Gido, J., Clements, J., & Baker, R. (2017). Successful Project Management. Boston,MA: Cengage Learning.
Watt, A. (2014). Project management.
image1.gif
PROJECT CHARTER
1.
High-level project scope
The project’s major goal is to change three existing traditional data centers by transferring applications to the cloud and satisfying the client’s core demands. The project’s goal is to develop an effective plan to transition legacy data centers to the cloud, both on-premise and in the cloud, by identifying a client’s requirements and business needs, determining the cost, creating a schedule, conducting stakeholder analysis, developing a high-level communication plan, resource plan, and identifying project risks early and creating a plan.
2.
High-level project requirements
The project’s high-level requirements for upgrading three data centers:
· Within the $1.5 million budget, move 145 business applications and infrastructure to the cloud, including 450 windows servers, 550 Unix servers, and 350 legacy AIX, VMWare, and ESX servers.
· Determine the characteristics and capabilities of a data center in order to store more data without compromising security or privacy, avoid data loss, carry out business activities, and fulfill the primary demands and expectations of stakeholders.
· Using common tools, such as Microsoft project management, to define the project’s core tasks and build a timetable.
· Using modern project financial management software to anticipate the cost and budget required to complete the project, conduct cost-benefit analysis, manage the budget, and achieve success.
· Using common tools such as the RACI matrix to analyze stakeholders, decide and plan resources, conduct activities, and execute projects according to the plan produced.
· Improving a data center’s efficiency by storing data, providing faster access to resources and data, simplifying data center management, reducing expenses, and promoting production
3.
Business needs
Manage a huge quantity of data connected to the business, minimize data loss, avoid security and privacy problems, access resources at any time, execute operations and deliver services to customers that match their expectations, and boost satisfaction in service offerings are among the business needs. It is also necessary to reduce efforts in handling data centers on which sensitive information related to the business is stored, reduce the cost of upgrading and managing data centers and provide higher-quality services by transforming data centers and shifting applications and infrastructure to the cloud.
4.
Early estimation and forecasted cost
It is necessary to identify essential resources required to complete the project in order to estimate and anticipate project costs early on. The following is the project’s estimated cost:
Project resource
Cost estimation
Purchasing data center infrastructure and systems
$1,85,000
Setup of infrastructure
$45,000
Hardware and software design
$10,000
Development of applications
$25000
Data center
$1,00,000
Total cost
$2,55,000
5.
Stakeholders
The following are the important stakeholders linked with the project:
Role in the project
Responsibility
Interest
Project manager
Create a project plan by identifying requirements.
High
Software engineer
Develop data center modules
High
Data center inspector
Examine whether the data center was built to fulfill the demands of the company.
High
IT analyst
Analyze the data center’s functional and non-functional requirements.
Medium
Testing engineer
Create test scenarios and put the data center to the test.
Medium
6.
High-level communication plan
The project’s high-level communication strategy focuses on enhancing engagement and information flow within it in order to connect with the team, convey changes, offer updates, and complete the project on time. It is then followed by:
Communication
Frequency
Audience
Mode
Stakeholder update
Monthly
Project stakeholders
Newsletter
Board meeting
Weekly
Board of directors for project
Video conference
Team meetings
Daily
Project team
Meeting
Discussing issues
Daily
Project team
Email, newsletter and social medial communication
7.
High-level resource plan
The resources required to complete the project and fulfill the business’s core needs are as follows:
Phase
Task
Resource
Design
Creating a detailed design for a data center.
Project manager
Analysis
Functional and non-functional analysis for data center and reporting
Data center and IT analyst and architect
Build
Build and test various data center modules such as login, administration, and reporting.
Software developer
Testing
Creating a test matrix, writing test cases, and performing data center testing
QA analyst
8.
Early risk indications
Early risk indications focuses on recognizing project-related risks early in order to establish their importance, impact on the organization, and generate management measures. The following are the early risk indicators for the project based on the demands and project requirements:
Risk type
Priority
Quality risk
2
Scope risk
2
Strategic risk
2
Schedule risk
1
Budget risk
1
Project Assignment: Budget and Risk Management.
Table of Contents
1. Overall project budget 2
2. Project requirements 3
3.
Cost management
plan 4
4. Detailed risk management plan 4
5. Risk response plan 5
6. Risk mitigation plan 6
7. Change management process 7
8. Project RAID 8
9. Stakeholder engagement 8
References 9
1.
Overall project budget
The entire budget required to transform old data centers and migrate a firm’s applications to the cloud at a firm, focusing on the many components and cost variables involved with it so that sufficient budget is available to complete all tasks and achieve success is as follows:
Task
Expenses ($)
Organize meetings
600.00
Identifying issues
900.00
Identifying issues
1,300.00
Plan a review
700.00
Designing data center
1,000.00
Designing software and hardware
1,500.00
Review and specification of the design
1,000.00
Obtaining resources
4,500.00
Training staff
1,500.00
Hardware and software installation
4,000.00
Extraction and loading of data
1,700.00
Conversion of data
1,000.00
Initial evaluations
700.00
Testing at the unit level
500.00
System evaluation
900.00
Performance evaluations
600.00
Testing for integration
8,00.00
Observing a data center in action
9,00.00
Detecting and implementing changes
1,200.00
Approval and completion of the project
8,00.00
Total
25,200.00
2.
Project requirements
The following are some of the high-level criteria for a project focused on modernizing three old data centers at a company:
· Within the $1.5 million budget, move 145 enterprise applications and infrastructure to the cloud, including 450 windows servers, 550 Unix servers, and 350 legacy AIX, VMWare, and ESX servers. (Gido, Clements, & Baker, 2017)
· Determine the characteristics and capabilities of a data center in order to store more data without compromising security or privacy, avoid data loss, carry out business operations, and fulfill the primary demands and expectations of stakeholders.
· Using common tools, such as Microsoft project management, to define the project’s core activities and build a timetable. (Gido, Clements, & Baker, 2017)
· Using modern project financial management software to anticipate the cost and budget required to complete the project, conduct cost-benefit analysis, manage the budget, and achieve success.
· Using common tools such as the RACI matrix to analyze stakeholders, decide and plan resources, conduct activities, and execute projects according to the plan produced.
· Develop standard data backup strategies to retrieve information in the event of a disaster, as well as load and extract data without losing any data. (Watt, 2014)
· Improving a data center’s efficiency by storing data, providing faster access to resources and data, simplifying data center management, reducing expenses, and promoting production.
These are the most important requirements for a project, and meeting them helps to avoid problems for the client and to meet their demands effectively.
3.
Cost management plan
Taking into account the project, the plan created for managing project costs, allocating and facilitating sufficient money to perform tasks, avoiding variance, managing staff, suppliers, and completing the project within the specified budget includes key elements such as project inputs such as the project charter, project management plan, environmental factors, tools and techniques, and project outputs (Athayde, Elswick, & Lombard, 2013).
4.
Detailed risk management plan
The following is the plan for managing project risks, considering the project, scope, and requirements:
Risk
Priority
Risk-avoidance measures
Person in charge
Deliverable
Risk schedule
1
Using modern tools to identify and schedule jobs
Project manager
The project’s schedule has been revised.
Risk budgeting
2
Allocating additional funds and calculating budgets with modern tools to accurately evaluate costs
Finance specialist
The budget plan has been updated.
Roles and resources
4
Identification of resources and creation of a plan for resource management
Project manager
Optimal resource allocation and improved performance
Quality
1
Reviewing the quality strategy and devising activities to mitigate quality risks, as well as implementing quality standards
Quality analyst
Modifications to the quality plan
Training
2
Advanced tool-use procedures are being taught to the personnel.
Technical specialist
Keeping technical concerns to a minimum and performing well
5. Risk response plan
The plan created to respond to the various risks associated with the project and achieve project success includes identifying key inputs for the project, such as a risk management plan and register to prioritize and manage risks effectively, tools and techniques to avoid negative effects of risks on data center transformation, and outputs, such as updates to the project management plan and documents created. The risk response process is depicted in the diagram below:
6.
Risk mitigation plan
The following is the plan prepared for limiting the impact of various hazards associated with the project and transforming the data center to meet the needs of a client:
Risk
Level
Risk mitigation plan
Slowing down of the server
High
Testing and monitoring the server to keep track of its condition and avoid delayed application processing.
Running a deficit
Moderate
Developing strategies and plans to maximize activity while keeping costs under control.
Technical
Extreme
Regularly designing and updating data centers, as well as utilizing advanced tools.
Resources
Low
Monitoring resources and assigning them appropriately allows you to manage and complete projects effectively.
7.
Change management process
Identification of significant changes that occur within a project, identifying the impact of changes on project performance, and developing effective strategies and actions to manage the changes and execute the project well are all part of the process for effective change management. It also entails going over the plan for dealing with changes and reporting them (Alotaibi, Sutrisna, & Chong, 2016). The following are the steps in the change management process:
8.
Project RAID
In a project, RAID focuses on identifying the project’s important risks, establishing assumptions, identifying key issues, and finding dependencies among the risks in order to develop appropriate plans and actions to manage them and complete the project successfully. This can be controlled by storing data on systems and managing duplicate copies relevant to the project in order to restore them in the event of data loss, building an effective risk management framework, and providing appropriate employee training (Gido, Clements, & Baker, 2017). This enables the project to collect data, monitor progress, track issues, and plan strategies to avoid issues and mitigate hazards, allowing the project to avoid risks and perform successfully. It also entails identifying essential characteristics that lead to hazards and determining dependencies among the risks in order to determine relationships and build effective steps to avoid them.
9. Stakeholder engagement
For the project focused on modernizing legacy data centers, a communication strategy is designed to promote effective communication among stakeholders, communicate information, and accomplish tasks using appropriate communication means. It is then followed by:
Communication
Frequency
Audience
Type
Meetings
with the team
Daily
Project team
Meeting
Stakeholder update
Monthly
Project stakeholders
Newsletter
Board meeting
Weekly
Board of directors for project
Video conference
Discussing issues
Daily
Project team
Email, newsletter and social media communication
References
Alotaibi, N. O., Sutrisna, M., & Chong, H.-Y. (2016). Guidelines of Using Project Management Tools and Techniques to Mitigate Factors Causing Delays in Public Construction Projects in Kingdom of Saudi Arabia . Journal of Engineering, Project, and Production Management, Vol.6, No.2, 90-103.
Athayde, W. P., Elswick, R., & Lombard, P. (2013). Project Management Essentials: A Quick and Easy Guide to the Most Important Concepts and Best Practices for Managing Your Projects Right. USA: Maven House.
Gido, J., Clements, J., & Baker, R. (2017). Successful Project Management. Boston,MA: Cengage Learning.
Watt, A. (2014). Project management.
Inputs
Plan for risk management
Tools and techniques
Strategies and actions to prevent negative risks
Outputs
Updates in project management plan
Risk register
Strategies to avoid positive risks
Contingency plan
Expert judgement
Updates in project documents
Process management
Finding key changes
Evaluating changes and impact on the project
Approval of changes and developing actions
Managing changes
Reviewing process and making changes
Inputs
Project charter
Tools and techniques
Meetings
Outputs
Cost management
Schedule and risk management plan
Environmental factors
Process assets
Data analysis
Expert judgement