Wk 6 – Apply: Signature Assignment: Project Plan Assignment Content Throughout the past few weeks, you have learned about the type of leader you’d like

Wk 6 – Apply: Signature Assignment: Project Plan Assignment Content

Throughout the past few weeks, you have learned about the type of leader you’d like

Click here to Order a Custom answer to this Question from our writers. It’s fast and plagiarism-free.

Wk 6 – Apply: Signature Assignment: Project Plan Assignment Content

Throughout the past few weeks, you have learned about the type of leader you’d like to be and how you can use your leadership skills in project management. This week’s reading discussed Kotter’s eight-step model of planned organization, appreciative inquiry, and the psychological and emotional processes involved in successful change. Leading an IT project will require you to use all these skills when working with stakeholders. One of the most important project tasks is to present the scoping information to the stakeholders.

For this assignment, you will revise your team’s project plan to present to stakeholders. Access your team’s draft of the Project Plan Template from the Wk 3 Team – Apply: Project Scope, Budget, and Timeline Stakeholder Meeting Role Play assignment, and re-save it so you can work on it individually.

Using information from the previous weeks’ assignments and instructor feedback, revise the Project Plan Template. In Section 1 of the Project Plan, you must define the scope of the project. In the following sections, you will explain how you will implement the scope of the project and how you will manage change within the project. 

Specifically, your new project plan should include the following revisions and additions:

A summary of the project in Section 1: Summary
A revision of the timeline from the Wk 3 Team – Apply: Project Scope, Budget, and Timeline Stakeholder Meeting Role Play assignment in Section 3: Schedule – Milestones 
A revision of the list of stakeholders (refer to the Wk 3 – Apply: Project Management Flowchart and Summary assignment document) in Section 4: Resources
An analysis of impact of change that should occur based on the risk assessment in Section 6: Change Management
An explanation and justification for the changes made in your revision of your group’s decisions in an Appendix section
Cite two sources other than Intuit, Inc. company documents.

Format your citations according to APA guidelines.

Submit your assignment. CMGT/545 v1

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.

By: Jared Baer, Lynne Welch, Britney Jackson, Gurbir Mangat & Tina Johnson

Section 1: Summary

This project will consist of converting Intuit, Incorporated current system to a cloud-based system. The
project will be completed within a 12-month period. The conversion of the onboarding, intranet, hosting, and
finance systems is desired for business to be more efficient with option to lock things down if necessary.
The project will be determined a success if the company is able to host their own cloud space platform that
is secured. To develop a system that lessen chances of ransomware attacks and hacking.

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

See Attachment

Section 3: Schedule – Milestones

Major items to be delivered to the contractors and sub-contractors are hardware installation, and maybe hire
a programming engineer just to help with the software and transition. IT will have a role in participating in
utilizing the new software and how to navigate it. Also, there will be a step to receive and deliver feedback
and adjustments to the IT leadership team. Milestones along the way would be.

Milestone 1 – Establish Hardware in appropriate locations – 2 Months Estimated Time of Completion

Milestone 2 – Software Completion – 6 months ETC

Milestone 3 – Fully Transitioned – 12 Months ETC

Copyright 2020 by University of Phoenix. All rights reserved.

Project Plan Template
CMGT/545 v1

Page 2 of 3

Milestone 4 – Feedback Review and Adjustments – 15 months ETC

Section 4: Resources

1. Establishing relationships and communication lines with Amazon AWS and Dell, as well as

ServiceNOW, SentinelOne and Forcepoint – This will be the IT head’s role | At the same time
contractors and sub-contractors will be called for installation of hardware and communication
equipment, as well as an outside help with software development

2. Software Development will be handled with the Systems Administration team and the developers,
they will coordinate with the infrastructure team as to what requirements needs to be put into place
for security as well as quality of life.

3. Testing will happen in the lab and software will be deployed into small, controlled phases at a time
for tweaks and more development.

4. Full Deployment to all resources will utilize Tanium or Microsoft’s SCCM. That way all devices can
transition properly

5. A survey and or links will be provided for all team members to report any bugs and or feedback

Section 5: Organization

Lynne Welch-Morris & Britney Jackson – C-Suite

Jared Baer – IT Leader

Gurbir Mangat – IT Group

Section 6: Change Management

If there is a necessity for change, we can follow Dr. Kotter’s 8 step process for change.

Create a Sense of Urgency – We will identify the issues that arose and find the best cost-effective solutions
available. Then we will instill a sense of urgency for all team members on hos to implement this change.

Build a Guiding Coalition – As an IT leader I will take the lead and may recruit other department heads.

Form a Strategic Vision and Initiatives – The department heads and I will develop a plan and a redundant
plan to ensure a clean victory with this project.

Enlist a Volunteer Army – This is where the heads and my self will break into specific groups with our
specific missions to accomplish to make sure the tasks get done.

Enable Action by Removing Barriers – We will empower the department heads to make decisive choices
within their own scope, that way we can eliminate unnecessary lag time.

Generate Short-Term Wins – After each completed task we can celebrate and jump onto the next target.

Sustain Acceleration – Once more and more heads complete the tasks that momentum will build, and each
can help each other out once those tasks are completed.

Institute Change – This will be the final step in the process, and how the backup plan would take into effect.

Copyright 2020 by University of Phoenix. All rights reserved.

Project Plan Template
CMGT/545 v1

Page 3 of 3

Section 7: Risk Management

Possible risks would be overspending and CEOs or a financial bind would happen during the purchase
which would delay the cloud transition. More risk would be company and customer data being hacked and
breached and released on the internet. This is mitigated by proper technologies as well as employee
training. Do not click on phishy emails!!

I added some stuff that I think fits in here as well. Another risk would be budgeting and requirements. To
mitigate this there needs to be clear, concise requirements, as well as a flexible projected budget.

Appendix

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

Copyright 2020 by University of Phoenix. All rights reserved.

Instructions
Section 1: Summary
Section 2: Phasing
Section 3: Schedule – Milestones 
Section 4: Resources 
Section 5: Organization
Section 6: Change Management 
Section 7: Risk Management  
Appendix

Looking for this or a Similar Assignment? Click below to Place your Order