13 Jul The C-suite at Intuit, Inc. is pushing to change their system to a cloud-based system in a 12-month project with a budget of $1,000,000. As either an IT team member or a c-suite l

CMGTCB/545 v1

Project Plan Template

CMGTCB/545 v1

Page 2 of 2

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

Define the purpose, scope, and objectives of the project and its delivered products. Briefly state the business needs to be satisfied and the methods by which satisfaction of those needs will be determined. Define the criteria by which key stakeholders will judge how successful the project is. State the relationship of this project to other projects and the integration of this product with other products.

Section 2: Phasing

Include the project timeline based on the phases listed below. You may use a Gantt Chart or any other visuals to depict the timeline.

· Phase I: Scoping and Planning

· Phase II: Order/Install Equipment

· Phase III: Install/Test Software

· Phase IV: Conduct Hardware/Software Testing

· Phase V: Conduct Training

· Phase VI: Implementation and Roll out

· Phase VII: Evaluation and Post Implementation

Section 3: Schedule – Milestones 

List the major items to be delivered to the customers, subcontractors, integrators, or other parties. As appropriate, list the deliverables, their recipients, interim and final delivery dates, and delivery method.

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

2. Test

3. Production

Section 5: Organization 

List the major project team roles and the individuals who will fill these roles, along with the specific responsibilities those individuals will have. Identify the organizational units or project team roles that are responsible for all major work activities and supporting processes.

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.

Section 7: Risk Management  

This section specifies the plan for identifying, analyzing, prioritizing, and controlling project risks. Document the risks in a separate risk list (possibly an appendix to this Plan), not in this section. A large project should create a separate risk management plan. Identify the risk management tasks to be performed, who is responsible for each, and the target date for completion of each task.

Appendix

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

Copyright 2021 by University of Phoenix. All rights reserved.

Copyright 2021 by University of Phoenix. All rights reserved.