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.

Imagine you work in the IT department of a financial services company that sells investments to, and manages investment portfolios for, high net worth individuals. Your organization uses custom-built legacy software applications and systems to support its sales processes. The sales software applications and systems are not integrated, and they do not support an enterprise view of the sales processes throughout the organization. Management is frustrated because the sales applications and systems do not provide the information and reports necessary for them to measure, monitor, and manage sales production in the organization. Sales executives and account managers are frustrated because the sales software applications and systems do not support the sales cycle for the products and services that the organization sells.

You have been assigned to analyze your organizations sales processes and identify an IT system capable of improving the sales processes of your organization. In addition, your organization is looking for an easy-to-use, cloud-based Customer Relationship Management (CRM) solution to generate more leads, increase sales, improve customer service, reduce the cost of sales for the organization, and increase revenue.

Please fill in the boxes:

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