cmgt 545 pro stat

Cnwofia
cmgt545_v1_project_plan_template3b.pdf

CMGT/545 v1

Copyright 2020 by University of Phoenix. All rights reserved.

Project Plan Template

Instructions

Complete the sections below. An explanation of content to add in each section is provided in italics. You may remove these instructions as you add your content.

Section 1: Summary

The C-suite at Intuit, Inc. wants to convert their system to a cloud-based system in a 12-month project with a budget of $1,000,000. A meeting between the IT group and the C suite was arranged to determine the timeline, brake down the budget, set goals, and plan for the risk of the project

Section 2: Phasing

Section 3: Schedule – Milestones

 The fist milestone will be marked at month 3 after all the equipment needed should be installed and ready for software

phase VII

Evaluation and Post Implementation 3 months

Phase VI

Implementation and Roll out 2 months

Phase V

Conduct Training 2 months

Phase IV

Conduct Hardware/Software Testing 1 month

Phase III

Install/Test Software 1 month

Phase II

Order/Install Equipment 2 months

Phase I

Scoping and Planning 1 month

Project Plan Template CMGT/545 v1

Page 2 of 4

Copyright 2020 by University of Phoenix. All rights reserved.

 The second milestone will be marked at month 5 when all the testing of the software and hardware is complete and its time to move on to training.

 The third milestone will be set to month 7 when all the training is complete

 The last milestone will be set to month 9 when the new cloud-based system is rolled out

Section 4: Resources

This section specifies the plan for acquiring the resources and personnel needed to successfully complete the

project. Specify the points in the project schedule when the various acquisition activities will be needed. List any constraints, such as contention for shared resources (e.g., test facilities). Address any known resource issues. Include both human and non-human resources (stakeholders). Non-human resources include computers, operating systems, databases, software, network, tools for test, technical and user documentation.

You may divide the resources into three different phases.

1. Development

 Project manager

 IT Team

 C suite

 network administrators

 server, router

 switches firewall

 operation system keys for every computer on the network

2. Test

 Project manager

 IT Team, C suite

 network administrators

 ethical hackers

 business analyst

 quality analyst

3. Production

• Project manager

• IT Team

• users

Section 5: Organization

Each team member will oversee one or two phases

Project Plan Template CMGT/545 v1

Page 3 of 4

Copyright 2020 by University of Phoenix. All rights reserved.

Bennie Gray- Order/ Install Equipment

Chukwuemeka Nwofia - Install/Test Software

Marvin Patton- Conduct Hardware/Software Testing

/ Conduct Training

Nathan B.- Implementation and Roll out

Shekita Brimer- scoping and planning/ Evaluation and Post Implementation

Section 6: Change Management

Effective change management is critical to project success. Change management concerns changes to the project scope and to all baselines and milestones. Change can affect budget, schedule, quality of work, human resource requirements, and risks. By monitoring and controlling change, you give your projects more opportunities to succeed.

Briefly define your change management strategy and plan. You may use Kotter's eight-stage model plan as guidelines to help your organization to succeed at implementing change.

The company is going through a big change to a cloud-based system and it is important to understand that this will take time and the staff must be engaged. It is important to properly train the staff on the new system and provide them with incentives. It is also important to communicate with your staff to make sure that they are progressing throughout the project.

Section 7: Risk Management

Limited control – the users will have less control over the system because a lot of the management is done on the cloud-based servers. The users will have to have a open path of communication with the IT team are cloud based administrators.

Web access is required- if there is a internet outage, the company will lose productivity because web access is needed to communicate with the cloud servers. The best way to combat internet outages is to have two different types of services. Having two ISP will allow the company to have a backup

Security risk – there will be a higher security risk when utilizing a cloud-based system. The IT team will ensure that the system is properly tested during the testing phase. The team will also contract a ethical hacker to test the system.

Learning curve – The project could fail if the users are unable to learn the cloud-based system. To motivate the staff to learn the new system, some incentive will be put in place. The staff will also be evaluated to make sure that they are retaining the information provided.

Project Plan Template CMGT/545 v1

Page 4 of 4

Copyright 2020 by University of Phoenix. All rights reserved.

Appendix

Use this section for any supplementary information. Add additional appendices as needed.