Tutorial

CMGT/545 v1

New Group 2

University of Phoenix

CMGT/545

Aviv Raveh

August 30, 2021

Project Plan Template

Copyright 2020 by University of Phoenix. All rights reserved.

Project Plan Template CMGT/545 v1

Page 2 of 7

Section 1: Summary

The purpose of the project is to convert the system of Intuit, Inc. to a cloud-based system.

The cloud-based system is expected to allow the firm to respond immediately to inquiries from

customers. We prefer using a third party system instead of developing one because of security.

Also, we intend to have a private cloud rather than relying on a third party. The C-suite group

intends to undertake the project within 12 months at a budget of $1,000,000. The budget will

involve enhancing information security to ensure the cloud-based system is secure. Therefore, the

deliverable is a cloud-based system. The business needs to be satisfied are the need to have an

effective system that enhances fast delivery of services and a system that can safeguard all data.

The satisfaction of the business needs will be determined by using internal and external surveys to

determine whether the method of delivering services has improved as well as getting feedback

from the information technology team. Key stakeholders will judge the success of the project by

checking the profits of the firm. The firm will ask questions such as: Is the company making more

money? Are we gaining new customers and lots of referrals? Are we retaining current customers?

The relationship between this project and other projects is that its budget is larger, and it will be

integrated with other company systems such as the Enterprise Resource Planning System.

Section 2: Phasing

The project is expected to take 12 months. Working days are from Monday to Friday,

which means 20 days in a month. Therefore, a month is equivalent to 20 working days. The

timeline of the phases is demonstrated below.

Copyright 2020 by University of Phoenix. All rights reserved.

Project Plan Template CMGT/545 v1

Page 3 of 7

Section 3: Schedule – Milestones

Deliverable Recipients Delivery Date Delivery Method

A cloud-based system Customers 30/8/2022 Through company website.

The old system that needs conversion to cloud-based

Subcontractors 29/9/2021 Face to face where it will be handed over.

New system to be integrated with the cloud.

Integrators 19/1/2022 Face to face where it will be handed over.

The cloud-based system and user manual.

Management 20/7/2022 Face to face during the post- implementation phase

Section 4: Resources

Non-Human

 Cloud Contract and Licenses - Phase I

 Access to Windows Azure Services - Phase II

 Palo Alto Hardware and licensing procurement - Phase II

Copyright 2020 by University of Phoenix. All rights reserved.

Project Plan Template CMGT/545 v1

Page 4 of 7

 Engineering Computer procurement - Phase II

 Switch procurement and upgrades - Phase III

 User Training - Phase V

 SOP - Phase VI and VII

Personnel

 Hire Project Manager - Phase I

 Hire Cloud Engineers x 2 – Phase I & II

 Hire Cloud Manager - Phase I & II

 Hire Service Desk Cloud Support personnel - Phase I & II

Constraints

 Hiring qualified engineers and Managers

 Palo Alto firewall provisioning

 Switch Upgrades and downtimes

 Training Facilitation resources

 Equipment procurement lead times - Possible delays.

 Financial budget fluctuation

 Software and Hardware implementation issues

 Training resources with old documentations

 Vendor support resources

Section 5: Organization

 Organization Project Manager: The project manager develops the project plan, recruit staff,

lead and manage the teams, assign tasks, establish a timeline and schedule, and provide

regular updates to upper management.

Copyright 2020 by University of Phoenix. All rights reserved.

Project Plan Template CMGT/545 v1

Page 5 of 7

 Project Sponsor: Typically, a member of senior management and their responsibility is to

approve the budget, avail the needed resources, communicate the goals throughout the

organization and remove obstacles that are hindering the goal.

 Project Team Member: (Company Staff or Consultant) Responsible for contributing to the

overall objectives, providing expertise since they have knowledge of everyday operations.

 Business Analyst: The role of the business analyst is to document requirements, verify the

deliverables and make sure that the project meets its requirements, test solutions to validate

the objectives, assess current systems.

 Executive Sponsor: Is usually a high-ranking member of management. Their responsibility

is to approve the project scope and deliverables.

 Business Analyst: The role of the business analyst is to document requirements, verify the

deliverables and make sure that the project meets its requirements, test solutions to validate

the objectives, assess current systems.

Section 6: Change Management

Intuit Inc. is transitioning to a cloud-based system to better assist our customers. The

Change Management Board is responsible for reviewing the change request, which consists of an

initial review of configurations, software installed, firewall requests and outstanding missing

requirements. Once the Change Management Board reviews all documentation for the

implementation of the new system, they will either sign off on the system being implemented or

deny the request due to missing information, configuration settings or unauthorized ports or

protocols being used. Once the Change Management Board approves the change request, the IT

department will put the server online. After the server is online, a final review by the Security

Copyright 2020 by University of Phoenix. All rights reserved.

Project Plan Template CMGT/545 v1

Page 6 of 7

Department, IT department and Network Department will be conducted to assure all functionality

and compliance of the server are met.

Section 7: Risk Management

Risk Management for this project will consist of a very detailed analysis of every decision

made and the possible outcomes that follow. For this project, depending on our decision to either

go with the third-party cloud system or utilize our own cloud system, the risks differ.

When weighing the risks, it is necessary to locate the technical, environmental, legal, and

security risks as well as many others. Although there are many risks involved, outlined in the

Appendix are some immediate risks to consider. These risks mostly have immediate actions that

could be taken to avoid detrimental consequences. Assigned are roles that these risks relate to,

although the entire team can be on the lookout for these risks and assist in mitigation.

Copyright 2020 by University of Phoenix. All rights reserved.

CMGT/545 v1

Appendix

Risk Consequences Probability Impact Priority Response plan Assignee

Third-Party Information Loss

Loss of all data Medium High High Avoid- Create offline backup and update once a day Business Analyst

Business Analyst

Personal Cloud Information Loss

Loss of all data Medium High High Avoid- Create offline backup and update once a day

Business Analyst

Budget Management Not enough money

allocated

Low High High Spending Plan with allocated habits and

expectations

Project Sponsor

Delay in project stages Not meeting project

deadline

Low Medium Medium Project Manager keeping track of each team and team members ensuring they are meeting deadlines

with enough space for rework and mistakes

Project Manager,

Team Members

Copyright 2020 by University of Phoenix. All rights reserved.