Post-implementation Change Warranty
Document Release Notice
Revisions, if any, to this manual will be published to Process Assets Library. Users of this
process are responsible for using the most current version of the procedure.
Rev. Date Modification Page Previous Action Taken Addendum/ Author
# # Page # New Page
Revision Date: Page 1 of 6
The purpose of this document is to provide framework for the areas of coverage that will be
provided during the post implementation phase of a change.
This warranty period, as it relates to all changes, states that the â€œgiverâ€ (initiative team) of the
changes (i.e. project, initiative) is responsible for supporting the changes until they are stable in
the production environment, and that all new functionality is verified and working as designed.
The warranty should include support for Post install support, knowledge transfer, deferred
incidents and production turnover through hand over take over process.
The warranty should be a deliverable as part of the exit criteria of the Improve Phase. However,
the warranty should start in the Analyze Phase of the project were it should be included in the
estimates, and then each re-estimate thereafter.
The warranty should be specific as to what will be warranted, such as modules, JCL,PARMS,
JAVA appletâ€™s, entire application, new transaction flow etc. The coverage can be as general or
detailed but must be agreed upon by the project team (TDL) and the production support staff.
This warranty will begin on the date of installation into production of the change. The coverage
term will be provided until all the new functionality has been executed and verified that there are
no outstanding incidents (severity 1 or 2) in post-implementation, including all applicable pilots
and roll-out periods.
Throughout Knowledge transfer to
teams via reviews and
Measure/Analyze/Improve PIW support estimate
Analyze/Improve Installation Plan
Improve Document test defects,
Control Hand over/Take over
Control Production Turnover
Revision Date: Page 2 of 6