Department or Program Name

[SYSTEM/APPLICATION NAME]
Implementation Plan
SYSTEM/APPLICATION NAME IMPLEMENTATION PLAN
Project Implementation Plan
Template 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)t5 brac$ets. Note tat te )l"e te*t i!
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 highlighted
section 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.
SYSTEM/APPLICATION NAME IMPLEMENTATION PLAN
Empo%erment
- Scala)ilit+
This template is provided as a g"i#eline to 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 project
or 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 <0on1applicable= and provide a
brief e)planation as to why it does not apply to the project.
Important
Notice
>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.
SYSTEM/APPLICATION NAME IMPLEMENTATION PLAN
DOC.MENT IN/O0MATION AND APP0O1ALS
VERSION HISTORY
1er!ion 2 Date 0evi!e# 3+ 0ea!on $or cange
4,5 6/47/56 Aaron Demenge PMO 0evie%
DOCUMENT APPROVALS
Approver Name Project 0ole Signat"re/Electronic Approval Date
SYSTEM/APPLICATION NAME IMPLEMENTATION PLAN
TA3LE O/ CONTENTS
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................................................................................................................................................. A
Follow1up................................................................................................................................................. A
Sta$$ Planning,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,:
"perations............................................................................................................................................... A
Technical................................................................................................................................................. A
Inter#epartmental 0ole! an# SLA;! <Service Level Agreement!= Planning,,,,,,,,,,,,,,,:
Acco"nting an# 3illing ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,:
Polic+ Management,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,:
Implementation/0elea!e Sce#"le,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,7
.!er 0ea#ine!! Plan,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,7
!anagement........................................................................................................................................... B
User%*ustomer upport........................................................................................................................... B
"perations............................................................................................................................................... B
Technical................................................................................................................................................. B
Data Migration/Conver!ion Plan,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,7
Preparation.............................................................................................................................................. B
>ctual *onversion................................................................................................................................... C
*onversion Derification '*lean1up(.......................................................................................................... C
In!tallation Plan,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,>
Preparation.............................................................................................................................................. C
,)ecution................................................................................................................................................. C
*lean1up teps........................................................................................................................................ C
Go%0o Go -ecision.................................................................................................................................. C
Product tabili&ation%?arranty Period..................................................................................................... C
Transition to Production upport............................................................................................................. E
.essons .earned................................................................................................................................... 28
Signo$$/ac?no%le#gement,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,45
Appen#i* 4 @ Propo!e# Pro#"ction !"pport mo#el,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,44
Appen#i* A B Implementation rea#ine!! a!!e!!ment,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,4A
SYSTEM/APPLICATION NAME IMPLEMENTATION PLAN
Overvie%
3ac?gro"n#
Provide a system overview, any re/uirements to use the system, re/uired locations, and method
to implementing the proposed project solution. This section is intended to be completed at a very
high level. It may be as long as necessary, but most information should be contained in a half of
a page. This section is intended to provide the bac$ground information necessary to place the
individual plans that follow into perspective.
Overall Approac
Include the underlying rationale for using the approach described above and describe the overall
schedule for implementing the plan.
Organi9ational Per!pective
-escribe all the modifications that will be necessary in the organi&ational structure, wor$ flow, and
personnel plans in order to support the new product, service, or system.
Involve# .!er Cro"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 of
communications 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 communications
message.
Operation!
Identify the audience who will receive the operations communications and describe the type of
communications 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 of
communications 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 necessary
organi&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( or
group's( responsible for e)ecuting the step, and the start and end date for the step. .ist steps in
a logical se/uence of events.
SYSTEM/APPLICATION NAME IMPLEMENTATION PLAN
E*ec"tion
.ist all the steps that are needed to actually move the organi&ation from its current state to the
new state. For each step, describe the actions to be ta$en, all individuals or groups affected by
the step, the individual's( or group's( responsible for e)ecuting the step, and the start and end
date for the step. .ist steps in a logical se/uence of events.
/ollo%@"p
.ist all the steps that are needed to follow1up the organi&ational change to determine the success
of the change, address any problems, concerns or issues arising from the change, and to ensure
the organi&ation has not reverted to its prior state. For each step, describe the actions to be
ta$en, all individuals or groups affected by the step, the individual's( or group's( responsible for
e)ecuting the step, and the start and end date for the step. .ist steps in a logical se/uence of
events.
Sta$$ Planning
Operation!
.ist the number, job description, and roles and responsibilities of business personnel needed 1 by
location 1 during actual implementation and the ongoing operations of the new system in order to
recover the business benefit described by the project.
Tecnical
.ist the number, job description, and roles and responsibilities of business personnel needed 1 by
location 1 during actual implementation of the new system and the subse/uent post1
implementation production support.
Inter#epartmental 0ole! an# SLA;! <Service Level Agreement!=
Planning
.ist the $ey contacts by department and e)pected escalation and response .>s re/uired. If
separate .> document's( are not to be prepared 'i.e. falls within e)isting master .>
documents, include $ey information in this section and >ppendi) 2F otherwise refer to the new
.> document.
Acco"nting an# 3illing
-escribe any changes to >ccounting and @illing re/uired to implement the proposed solution, if
applicable.
Polic+ Management
.ist the changes to e)isting policy or procedures re/uired to implement the proposed solution, if
applicable.
SYSTEM/APPLICATION NAME IMPLEMENTATION PLAN
Implementation/0elea!e Sce#"le
Prepare a detailed implementation schedule. Include all of the sub1plans contained within the
Implementation Plan 'training, documentation, organi&ational change, and installation(. For each
activity listed on the schedule, include assigned personnel resources, start date, end date, and
the estimated duration of the activity.
.!er 0ea#ine!! Plan
Management
Identify the audience who will receive the management 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 supporting
materials that will be re/uired for the training, such as+ training manualsF teachers guidesF
overheadsF etc. Prepare a tentative schedule and indicate what courses will be offered when and
who 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 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
supporting materials that will be re/uired for the training, such as+ training manualsF teacher7s
guidesF overheadsF etc. Prepare a tentative schedule and indicate what courses will be offered
when 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 supporting
materials that will be re/uired for the training, such as+ training manualsF teacher7s guidesF
overheadsF etc. Prepare a tentative schedule and indicate what courses will be offered when and
who from the operations audience will attend each course offering.
Tecnical
Identify the audience who will receive the technical 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 supporting
materials that will be re/uired for the training, such as+ training manualsF teacher7s guidesF
overheadsF etc. Prepare a tentative schedule and indicate what courses will be offered when and
who 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 design
document's(, or meet with the conversion team for the project to provide input for this section.
SYSTEM/APPLICATION NAME IMPLEMENTATION PLAN
Act"al Conver!ion
*onversion info goes hereG
Conver!ion 1eri$ication <Clean@"p=
*onversion info goes hereG
In!tallation Plan
Preparation
.ist all hardware, software, e/uipment, environmental, supply, and other application systems
re/uirements needed for installation of the new system as applicable. Include both e)isting and
new hardware, software or e/uipment, and identify which is which. For environmental, include
such items as construction of special rooms, installation of cooling systems, electrical rewiring,
etc.
E*ec"tion
-escribe the $ind of testing that will ta$e place in interim operations. .ist the activities to be
performed for the actual system installation. .ist the activities to be performed to verify the
system installation is correct. .ist the contingency activities to be performed if the installation
should fail. -escribe the procedure to be used to resolve problems encountered during
installation.
Sec"rit+
Application
Fall bac$ plan to 'to re1enable the legacy system in the event of catastrophic failure(
Clean@"p Step!
-escribe the steps to be followed to turn off the old system, obtain feedbac$ on the
implementation process, and measure initial use of the new system.
Co/No Co Deci!ion
-escribe the process to engage sta$eholders in a process to commit to product%service release.
This should be added with the .aunch #eadiness >ssessments 'appendi) 3(.
Pro#"ct Sta)ili9ation/&arrant+ Perio#
The stabili&ation period is a scheduled one1wee$ period in which resources will be dedicated to
monitor, 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 to
assist+
Proce!! O%ner 0ole/0epre!entation Contact
Project !anager
Project Technical .ead
SYSTEM/APPLICATION NAME IMPLEMENTATION PLAN
Tran!ition to Pro#"ction S"pport
-escribe the steps to be followed for final $nowledge transfer and transition to production
support.
Transition Planning Schedule:
Activit+ De+ Delivera)le 0ole/0epre!entation Date
#eview Implementation
#eadiness >ssessment
Implementation #eadiness
>ssessment '>ppendi) 3(
P! with @usiness and
Technical Team
#eview @usiness *ontinuity
Planning
Implementation Plan P! and @usiness
ponsor
#eview and transition
Technical upport
Technical -esign
pecification and
Implementation Plan
P! and Technical
.ead%Production
upport Team
#eview Testing Transition Test Plan and Test cripts P! and P!" H>
.ead
#eview Training Transition User guides, /uic$
reference material and
training outlines
P! and P!"
Technical Trainer
#eview -ocument >rchiving Project harePoint
website
P! and P!" P!
>fter the product stabili&ation period, the department will formally ac$nowledge client acceptance
of the application and the system transitions to production support mode. The Project moves to
Project *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)es
falls 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+
SYSTEM/APPLICATION NAME IMPLEMENTATION PLAN
Le!!on! Learne#
-escribe how lessons learned from the project will be gathered, documented, and made available
as 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 summary
documentation.
Signo$$/ac?no%le#gement
I agree that the IProject 0ameJ Implementation Plan is complete as is $nown today, accurately
reflect the strategic and operational direction of I-epartment ponsorJ regarding the project, and
when delivered fulfill the business needs of my department within the broader project goals as
defined by the project @usiness *ase and *harter.
I understand that by agreeing to the Project Implementation Plan, I approve of the activities
defined and authori&e my department to participate as documented for the successful
implementation of the Iproject solutionJ in our department.
KKKKKKKKKKKKKKKKKKKKKKKK -ate+ KKK%KKK%KKK
0ame
Title
KKKKKKKKKKKKKKKKKKKKKKKK -ate+ KKK%KKK%KKK
0ame
Title
KKKKKKKKKKKKKKKKKKKKKKKK -ate+ KKK%KKK%KKK
0ame
Title
SYSTEM/APPLICATION NAME IMPLEMENTATION PLAN
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
SYSTEM/APPLICATION NAME IMPLEMENTATION PLAN
Appen#i* A B Implementation rea#ine!! a!!e!!ment
E5 Da+! Prior to La"nc
Project !anager7s summary of the readiness to launch to#a+.
core '2 to ; with ; being completely ready( KKKK
Thoughtful commentary+
ummary 'score and commentary( of the readiness of+
The application as determined by the Tec lea# or software architect
core '2 to ; with ; being completely ready( KKKK
Thoughtful commentary+
The application as determined by the 3A lea#
core '2 to ; with ; being completely ready( KKKK
Thoughtful commentary+
The application as determined by the FA lea#
core '2 to ; with ; being completely ready( KKKK
Thoughtful commentary+
3"!ine!! Partner assessment.
core '2 to ; with ; being completely ready( KKKK
Thoughtful commentary+
The launch materials as determined by the 3"!ine!! lea#
core '2 to ; with ; being completely ready( KKKK
Thoughtful commentary+
The operational%user readiness as determined by the 3"!ine!! lea#
core '2 to ; with ; being completely ready( KKKK
Thoughtful commentary+
.ist and describe the most significant obstacles to launch. >ssess each obstacle for impact and
li$elihood. ?here the impacts are high, what mitigation 'e.g. agreed on <plan b=( might be in the wor$sN
O)!tacle to La"nc 0ea!on /
3ac?gro"n#
Impact / 0i!? Mitigation
.ist any features that are candidates for not being included with the initial launch. -escribe the effect of
the absence.
/eat"re at 0i!? &+G o% ar# to !"ppl+ Impact o$ la"ncing %ito"t
L 3823 #egents of the University of !innesota. >ll rights reserved. #evised Mune 2B, 3829 Page 23
SYSTEM/APPLICATION NAME IMPLEMENTATION PLAN
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
Thoughtful commentary+
Project Manager;! summary of the readiness to launch to#a++
core '2 to ; with ; being completely ready( KKKK
Thoughtful commentary+
Project Manager;! recommendations for launch.
KK *omplete, unaltered launch on schedule
KK "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 can
begin >>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
core '2 to ; with ; being completely ready( KKKK
Thoughtful commentary+
3"!ine!! Partner;! summary of the readiness to launch to#a++
core '2 to ; with ; being completely ready( KKKK
Thoughtful commentary+
3"!ine!! Partner;! recommendations for launch.
KK *omplete, unaltered launch on schedule
KK "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 can
begin >>P. > no go decision needs to be communicated in person to the sta$eholders. (
I"!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
L 3823 #egents of the University of !innesota. >ll rights reserved. #evised Mune 2B, 3829 Page 26
SYSTEM/APPLICATION NAME IMPLEMENTATION PLAN
:as the Tec Lea# signed offN KK
:as the 3"!ine!! Partner<!= accepted the product%application and the terms of the launchN The
ris$s and absent features are documented and s%he has approvedN KKK
If there is significant concern, involve the Program !anagement "fficeO
L 3823 #egents of the University of !innesota. >ll rights reserved. #evised Mune 2B, 3829 Page 29