Assignment Content Project rollout begins after a project has been implemented, tested, and judged stable and functional enough to be moved into production. The project rollout process comprises specific steps that must be scheduled carefully to enable the project to hit production deadlines and meet business expectations. For this assignment, you will create an implementation project plan, which outlines the steps involved in implementing your project. This document is sometimes called a work-back schedule because you begin with the date that your project needs to go live, and then work back from there to determine what needs to be done when. You will also conduct a post-mortem on the work you have submitted to date. Post-mortem (from the Latin for after death, but referring to it in the context of business) is the analysis of a projects process and results conducted by key project stakeholders after the project has been moved into production, which means its functionally complete. The goal of a post-mortem is to identify what went right and what went wrong post-implementation so that project managers can apply these lessons learned to future projects. For this three-part assignment, you will: Construct a work-back schedule that presents the steps involved in implementing your project. Construct a post-mortem using the template on the work you have submitted to date in this course. Create updated project documents based on the results of your post-mortem. Review the Project Implementation Plan Example. Create a project implementation plan for your project based on the example document. You may use Microsoft Word or other software to create your project implementation plan. Complete the Post-Mortem template based on your experiences with completing the course project over the last five weeks. Update the project documents you have submitted thus far in the course based on your completed post-mortem.

Project rollout begins after a project has been implemented, tested, and judged stable and functional enough to be moved into production. The project rollout process comprises specific steps that must be scheduled carefully to enable the project to hit production deadlines and meet business expectations.

For this assignment, you will create an implementation project plan, which outlines the steps involved in implementing your project. This document is sometimes called a work-back schedule because you begin with the date that your project needs to go live, and then work back from there to determine what needs to be done when.

You will also conduct a post-mortem on the work you have submitted to date. Post-mortem (from the Latin for after death, but referring to it in the context of business) is the analysis of a projects process and results conducted by key project stakeholders after the project has been moved into production, which means its functionally complete. The goal of a post-mortem is to identify what went right and what went wrong post-implementation so that project managers can apply these lessons learned to future projects.

For this three-part assignment, you will:

• Construct a work-back schedule that presents the steps involved in implementing your project.
• Construct a post-mortem using the template on the work you have submitted to date in this course.
• Create updated project documents based on the results of your post-mortem.

Review the Project Implementation Plan Example.

Create a project implementation plan for your project based on the example document. You may use Microsoft Word or other software to create your project implementation plan.

Complete the Post-Mortem template based on your experiences with completing the course project over the last five weeks.

Update the project documents you have submitted thus far in the course based on your completed post-mortem.

Submit your project implementation plan, post-mortem, and updated project documents.

Post-Mortem

Use the table to list the things that went well during the completion of this 5-week project and the things that didnt go well.

Date:

Project Manager (your name):

Project Name:

5 Things that Went Well During the Project

5 Things that Could Have Been Done Better

Below, discuss all 10 things from the list above in detail. As a project manager, or participant, what processes might you put in place to ensure the same things go well on future projects youre involved in? What processes can you put in place to improve the not-so-great things on future projects? Be specific. Project Implementation Plan Example

Replace the italicized information with information relevant to your project.

Project Name:

Implementation Phase:

Project Plan:

Task	Activity Name	Resource	Schedule Start Date	Schedule Finish Date	Schedule Comments
Prepare for Implementation	Identify the implementation team	CIO/Project Sponsor	6/4/2018	6/8/2018
	Order server hardware for production environment and test/QA environment	IT Manager/CIO	6/4/2018	6/29/2018
	Order client hardware for production environment and test/QA environment	IT Manager/CIO	6/4/2018	6/29/2018
	Order Cloud Computing Services and software subscriptions	IT Manager/CIO	6/4/2018	6/29/2018
	Obtain on premise software applications	IT Manager/CIO	6/4/2018	6/29/2018
	Create user IDs and groups for on premise technology	System Admin	7/2/2018	7/13/2018
	Create security infrastructure for production and test/QA environment	System Admin	7/2/2018	7/13/2018
Prepare Test Environment	Install test/QA servers and software	System Admin	7/16/2018	7/20/2018
	Install test/QA client machines and software	System Admin	7/16/2018	7/20/2018
	Configure test/QA environment	System Admin	7/16/2018	7/20/2018
Prepare Production Environment	Install production servers and software	System Admin	7/23/2018	7/27/2018
	Install production client machines and software	System Admin	7/23/2018	7/27/2018
	Configure production environment/ integrate with cloud service architecture	System Admin	7/23/2018	7/27/2018
Data Conversions	Perform data conversions and loading into the test/QA environment	Data Specialists	7/13/2018	8/10/2018
	Perform data conversions and loading into the production environment	Data Specialists	7/13/2018	8/10/2018
Documentation	Ensure all documentation applicable to implementation is available	Documentation Specialists/Technical Writers	6/11/2018	8/17/2018
Training	Provide administrator training	Trainers	8/13/2018	8/17/2018
	Provide support training	Trainers	8/13/2018	8/17/2018
	Provide end-user training	Trainers	8/13/2018	8/17/2018
Go-Live	Production Go-live	CIO/Project Sponsor	8/27/2018	8/27/2018