TEMPLATE Project Implementation Plan

8/12/2019 TEMPLATE Project Implementation Plan

1/15

Department or Program Name

[SYSTEM/APPLICATIONNAME]

Implementation Plan


2/15

SYSTEM/APPLICATIONNAME IMPLEMENTATIONPLAN

Project Implementation PlanTemplate Guidelines

To aid in the completion of a Project Implementation Plan please adhere to the following guidelines. For

specific information regarding project deliverables, please refer to the University ervices Program

!anagement "ffice. #emove te!e g"i#eline! $rom te complete# #oc"ment.

P"rpo!e The Project Implementation Plan describes the strategy involved in preparing the end

users and the target product, service, or system into daily use or production. This can

include introducing a new product into the mar$etplace for customer consumption,

installing and propagating a new technology, or carrying out a new process%business

line. The objective of producing an Implementation Plan is to reduce ris$ of

implementation failure by planning the impact to the business when the product,

service, or system is implemented. Its intent is to have a centrali&ed reference

document that organi&es all of the information needed for implementation 'i.e.,

identifies all the tas$s that must be completed and the responsible parties that must be

involved to implement the project successfully(.

The Project Implementation Plan is a master plan that summari&es all of the individual

plans to be performed to implement the project. These plans may be documented as

part of the implementation plan or as separate project plans, depending on the type,

comple)ity, and si&e of the project.

O%ner!ip The Project !anager is responsible for completion of the Implementation Plan, with

input from project leads and the Project *ustomer as necessary.

&en

Phase+ )ecute

-*+ -evelop

The Implementation Plan is completed during the -esign 'planning of the document(

and -evelop 'physically create the document( Phases of olution -elivery ife *ycle.

It is a re/uired deliverable on all !edium and arge projects, and a best practice for

mall projects.Template

Completion

0ote+ Te)t

within ' (

brac$ets needs

to be replaced

with project1

specific

information.

2. -o not include the Template Guidelines in your final document. nter the project

information in the page header and footer, title page, and document contributors

and version control.

3. *omplete the document utili&ing suggested te)t where applicable and entering

te)t%fields where shown within 4blue te)t5brac$ets. Note tat te )l"e te*ti!

NOT to )e incl"#e# in +o"r $inal #oc"ment, Its purpose is to either provide

guidance for completing the document, or to show where te)t%fields are to be

input.

6. "nce changes are made to your document and you7re ready to finali&e, ensure

that you update your Table of *ontents 'T"*( section. To Update the T"*+ If

you are unsure how to do this, place your mouse arrow to the left of the first entry

in the Table of *ontents section and clic$ the left button once. "nce the entire

section is highlighted, move the mouse arrow anywhere within the highlightedsection and clic$ the right button once. In the drop1down menu, choose Update

Field and Page 0umbers "nly or ntire Field as needed. 0ote that you might

need to repeat the aforementioned steps to change the font bac$ to Tahoma 28

pt.

9. If changes are to be made, update the #evision :istory information accordingly.

;. The Implementation Plan is to be retained with other project1related

documentation and maintained in accordance with the business line7s records

retention policy.


3/15


Empo%erment

- Scala)ilit+

This template is provided as a g"i#elineto follow in producing the minimum basic

information needed to successfully complete a Project Implementation Plan in meeting

P! guidelines and illustrates the art and science of project management. Project

!anagers are empowered to use this template as needed to address any specific

re/uirements of the proposed project at hand. The amount of detail included in the

template will depend on the si&e and comple)ity of the project. -epending on projector business line needs, categories can be added, but cannot be deleted. If a category

does not apply, do not delete it, but rather mar$ it as s this template may change, it is igl+ recommen#e#that you access a blan$

template from the ?F Program "ffice ?ebsite each time you need one for a new

project and not merely use one from a previous project by changing the old te)t.


4/15


5/15


TA3LEOCONTENTS

Overvie%,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,8

@ac$ground............................................................................................................................................ . ;"verall >pproach.....................................................................................................................................;"rgani&ational Perspective......................................................................................................................;

Involved User Groups..............................................................................................................................;

Implementation Comm"nication! ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,8

!anagement........................................................................................................................................... ;User%*ustomer upport...........................................................................................................................;"perations............................................................................................................................................... ;Technical................................................................................................................................................. ;

Organi9ational Cange Plan,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,8

Preparation.............................................................................................................................................. ;)ecution.................................................................................................................................................AFollow1up................................................................................................................................................. A

Sta$$ Planning,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,:"perations............................................................................................................................................... ATechnical................................................................................................................................................. A

Inter#epartmental 0ole! an# SLA;!


6/15


Overvie%

3ac?gro"n#

Provide a system overview, any re/uirements to use the system, re/uired locations, and methodto implementing the proposed project solution. This section is intended to be completed at a veryhigh level. It may be as long as necessary, but most information should be contained in a half ofa page. This section is intended to provide the bac$ground information necessary to place theindividual plans that follow into perspective.

Overall Approac

Include the underlying rationale for using the approach described above and describe the overallschedule for implementing the plan.

Organi9ational Per!pective

-escribe all the modifications that will be necessary in the organi&ational structure, wor$ flow, andpersonnel plans in order to support the new product, service, or system.

Involve# .!er ro"p!

-escribe all the sta$eholders, users or other parties impacted by the delivery of this solution.

Implementation Comm"nication!

Management

Identify the audience who will receive the management communications and describe the type ofcommunications medium to be used and the purpose for the communications message.

.!er/C"!tomer S"pport

Identify the audience who will receive the user%customer support communications and describe

the type of communications medium to be used and the purpose for the communicationsmessage.

Operation!

Identify the audience who will receive the operations communications and describe the type ofcommunications medium to be used and the purpose for the communications message.

Tecnical

Identify the audience who will receive the technical communications and describe the type ofcommunications medium to be used and the purpose for the communications message.

Organi9ational Cange Plan

Preparation

ist all the steps that are needed to prepare for the organi&ational change. 'The necessaryorgani&ational change was to be described earlier in the overview section.( For each step,describe the actions to be ta$en, all individuals or groups affected by the step, the individual's( orgroup's( responsible for e)ecuting the step, and the start and end date for the step. ist steps ina logical se/uence of events.


7/15


E*ec"tion

ist all the steps that are needed to actually move the organi&ation from its current state to thenew state. For each step, describe the actions to be ta$en, all individuals or groups affected bythe step, the individual's( or group's( responsible for e)ecuting the step, and the start and enddate for the step. ist steps in a logical se/uence of events.

ollo%@"pist all the steps that are needed to follow1up the organi&ational change to determine the successof the change, address any problems, concerns or issues arising from the change, and to ensurethe organi&ation has not reverted to its prior state. For each step, describe the actions to beta$en, all individuals or groups affected by the step, the individual's( or group's( responsible fore)ecuting the step, and the start and end date for the step. ist steps in a logical se/uence ofevents.

Sta$$ Planning

Operation!

ist the number, job description, and roles and responsibilities of business personnel needed 1 bylocation 1 during actual implementation and the ongoing operations of the new system in order torecover the business benefit described by the project.

Tecnical

ist the number, job description, and roles and responsibilities of business personnel needed 1 bylocation 1 during actual implementation of the new system and the subse/uent post1implementation production support.

Inter#epartmental 0ole! an# SLA;! s re/uired. Ifseparate > document's( are not to be prepared 'i.e. falls within e)isting master >documents, include $ey information in this section and >ppendi) 2 otherwise refer to the new> document.

Acco"nting an# 3illing

-escribe any changes to >ccounting and @illing re/uired to implement the proposed solution, ifapplicable.

Polic+ Management

ist the changes to e)isting policy or procedures re/uired to implement the proposed solution, ifapplicable.


8/15


Implementation/0elea!e Sce#"le

Prepare a detailed implementation schedule. Include all of the sub1plans contained within theImplementation Plan 'training, documentation, organi&ational change, and installation(. For eachactivity listed on the schedule, include assigned personnel resources, start date, end date, andthe estimated duration of the activity.

.!er 0ea#ine!! Plan

Management

Identify the audience who will receive the management training and describe the purpose for thetraining. Identify all of the individual courses that will be prepared and presented for this training.For each identified course, include+ 'a( the course name, 'b( the type of training 'classroom,*@T, etc.(, 'c( the course content, and 'd( the estimated duration. Identify all of the supportingmaterials that will be re/uired for the training, such as+ training manuals teachers guidesoverheads etc. Prepare a tentative schedule and indicate what courses will be offered when andwho from the management audience will attend each course offering.

.!er/C"!tomer S"pport

Identify the audience who will receive the user%customer support training and describe thepurpose for the training. Identify all of the individual courses that will be prepared and presentedfor this training. For each identified course, include+ 'a( the course name, 'b( the type of training'classroom, *@T, etc.(, 'c( the course content, and 'd( the estimated duration. Identify all of thesupporting materials that will be re/uired for the training, such as+ training manuals teacher7sguides overheads etc. Prepare a tentative schedule and indicate what courses will be offeredwhen and who from the user%customer support audience will attend each course offering.

Operation!

Identify the audience who will receive the operations training and describe the purpose for the

training. Identify all of the individual courses that will be prepared and presented for this training.For each identified course, include+ 'a( the course name, 'b( the type of training 'classroom,*@T, etc.(, 'c( the course content, and 'd( the estimated duration. Identify all of the supportingmaterials that will be re/uired for the training, such as+ training manuals teacher7s guidesoverheads etc. Prepare a tentative schedule and indicate what courses will be offered when andwho from the operations audience will attend each course offering.

Tecnical

Identify the audience who will receive the technical training and describe the purpose for thetraining. Identify all of the individual courses that will be prepared and presented for this training.For each identified course, include+ 'a( the course name, 'b( the type of training 'classroom,*@T, etc.(, 'c( the course content, and 'd( the estimated duration. Identify all of the supportingmaterials that will be re/uired for the training, such as+ training manuals teacher7s guides

overheads etc. Prepare a tentative schedule and indicate what courses will be offered when andwho from the technical audience will attend each course offering.

Data Migration/Conver!ion Plan

Preparation

#efer to any business re/uirement definition document's( and any architectural or designdocument's(, or meet with the conversion team for the project to provide input for this section.


9/15


Act"al Conver!ion

*onversion info goes here

Conver!ion 1eri$ication ssessments 'appendi) 3(.

Pro#"ct Sta)ili9ation/&arrant+ Perio#

The stabili&ation period is a scheduled one1wee$ period in which resources will be dedicated tomonitor, identify, troubleshoot, and respond to $nown issues affecting the ability to re/uest,process, print, and manage ecurity I- badges.

Product stabili&ation will be managed by the departmental IT !anager who will own the

product%system after transition to production support, but will rely on the following contacts toassist+

Proce!! O%ner 0ole/0epre!entation Contact

Project !anager

Project Technical ead


10/15


Tran!ition to Pro#"ction S"pport

-escribe the steps to be followed for final $nowledge transfer and transition to productionsupport.

Transition Planning Schedule:

Activit+ e+ Delivera)le 0ole/0epre!entation Date

#eview Implementation#eadiness >ssessment

Implementation #eadiness>ssessment '>ppendi) 3(

P! with @usiness andTechnical Team

#eview @usiness *ontinuityPlanning

Implementation Plan P! and @usinessponsor

#eview and transitionTechnical upport

Technical -esignpecification andImplementation Plan

P! and Technicalead%Productionupport Team

#eview Testing Transition Test Plan and Test cripts P! and P!" H>

ead#eview Training Transition User guides, /uic$

reference material andtraining outlines

P! and P!"Technical Trainer

#eview -ocument >rchiving Project harePointwebsite

P! and P!" P!

>fter the product stabili&ation period, the department will formally ac$nowledge client acceptanceof the application and the system transitions to production support mode. The Project moves toProject *lose1out and is no longer involved in the ongoing administration of the project or system.

"wnership of the technical support of agreed up modifications, changes, enhancements, or fi)esfalls to the departmental technical manager and as defined in the ervice evel >greement

'>(. The technical manager also wor$s with others as defined in the Product !anagement:ierarchy -iagram 'below( and the Production upport !odel 'appendi) 2(.

Product !anagement :ierarchy -iagram+


11/15


Le!!on! Learne#

-escribe how lessons learned from the project will be gathered, documented, and made availableas a learning e)perience for each new departmental implementation.

#efer to the standard templates for lessons learned surveys and summary documents.

The P!" can facilitate any lessons learned surveying, meeting facilitation and summarydocumentation.

Signo$$/ac?no%le#gement

I agree that the Project 0ameJ Implementation Plan is complete as is $nown today, accuratelyreflect the strategic and operational direction of -epartment ponsorJ regarding the project, andwhen delivered fulfill the business needs of my department within the broader project goals asdefined by the project @usiness *ase and *harter.

I understand that by agreeing to the Project Implementation Plan, I approve of the activitiesdefined and authori&e my department to participate as documented for the successful

implementation of the project solutionJ in our department.

KKKKKKKKKKKKKKKKKKKKKKKK -ate+ KKK%KKK%KKK0ameTitle

KKKKKKKKKKKKKKKKKKKKKKKK -ate+ KKK%KKK%KKK0ameTitle

KKKKKKKKKKKKKKKKKKKKKKKK -ate+ KKK%KKK%KKK0ame

Title


12/15

SYSTEM/APPLICATION NAME IMPLEMENTATIONPLAN

Appen#i* 4 @ Propo!e# Pro#"ction !"pport mo#el

L 3823 #egents of the University of !innesota. >ll rights reserved. #evised Mune 2B, 3829 Page 22


13/15


Appen#i* B Implementation rea#ine!! a!!e!!ment

5 Da+! Prior to La"nc

Project !anager7s summary of the readiness to launch to#a+.

core '2 to ; with ; being completely ready( KKKKThoughtfulcommentary+

ummary 'score and commentary( of the readiness of+

The application as determined by the Tec lea# or software architect


The application as determined by the 3A lea#


The application as determined by the FA lea#


3"!ine!! Partnerassessment.


The launch materials as determined by the 3"!ine!! lea#


The operational%user readiness as determined by the 3"!ine!! lea#core '2 to ; with ; being completely ready( KKKKThoughtfulcommentary+

ist and describe the most significant obstacles to launch. >ssess each obstacle for impact andli$elihood. ?here the impacts are high, what mitigation 'e.g. agreed on ll rights reserved. #evised Mune 2B, 3829 Page 23


14/15


45 Da+! Prior to La"nc

Update the 68 day assessment above with status of things identified and any new information % concerns %ris$s on top.

Project Manager;!summary of the readiness to launch on !ce#"leH

core '2 to ; with ; being completely ready( KKKK

Thoughtfulcommentary+

Project Manager;!summary of the readiness to launch to#a++



Project Manager;!recommendations for launch.KK *omplete, unaltered launch on scheduleKK "n schedule launch but with conditions 'e.g. certain features absent(KK -elay 'If the determination is to delay the launch be sure that is decided now so communication canbegin >>P. > no1go decision needs to be communicated in person to the sta$eholders. (

3"!ine!! Partner;!summary of the readiness to launch on !ce#"leH



3"!ine!! Partner;!summary of the readiness to launch to#a++



3"!ine!! Partner;!recommendations for launch.KK *omplete, unaltered launch on scheduleKK "n schedule launch but with conditions 'e.g. certain features absent(KK -elay 'If the determination is to delay the launch be sure that is decided now so communication canbegin >>P. > no go decision needs to be communicated in person to the sta$eholders. (

"!t Prior to La"nc A!!e!!ment

Update the 28 day assessment above with status of things identified and any new information % concerns %ris$s on top.

:as the PM signed offN KK

:as FA Lea# signed offN KK

:as 3A Lea# signed offN KK



15/15


:as the Tec Lea#signed offN KK

:as the 3"!ine!! Partner

ris$s and absent features are documented and s%he has approvedN KKK

If there is significant concern, involve the Program !anagement "fficeO


Documents

TEMPLATE Project Implementation Plan