Checklist Post Implementation Review (PIR): Difference between revisions

From IT Process Wiki
No edit summary
 
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
'''ITIL Process''': [[Service Support]] - [[Change Management - ITIL V2|Change Management]]
<itpmch><title>Checklist Post Implementation Review (PIR) | IT Process Wiki</title>
<meta name="keywords" content="post implementation review, post implementation review itil, post implementation review template, pir itil, itil pir" />
<meta name="description" content="An investigation takes place during the Post Implementation Review (PIR), as to whether the following information related to the implementation ..." />
</itpmch>
<imagemap>
Image:ITIL-Wiki-deutsch.jpg|right|Checklist Post Implementation Review (PIR) - Template Post Implementation Review (PIR)
default [https://wiki.de.it-processmaps.com/index.php/Checkliste_Post_Implementation_Review_-_PIR diese Seite auf Deutsch]
desc none
</imagemap>
<br style="clear:both;"/>


'''Checklist Category''': [[ITIL-Checklists#Checklists for Change Management|Checklists for Change Management]]
<p>&nbsp;</p>


'''ITIL Process''': [[ITIL Service Transition]] - [[Change Management]]


An investigation takes place during the PIR, as to whether the following information related to the implementation is entered into the Change Record:
'''Checklist Category''': [[ITIL-Checklists|ITIL Templates]] - Change Management
 
'''Source''': Checklist "Post Implementation Review - PIR" from the ITIL Process Map V2 &nbsp;| &#11208;&nbsp; [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map V3]
 
<p>&nbsp;</p>
 
An investigation takes place during the Post Implementation Review (PIR), as to whether the following information related to the implementation is entered into the Change Record:


* Functional and operational tests
* Functional and operational tests
Line 30: Line 46:
* Findings arising from the implementation and lessons in order to avoid future mistakes
* Findings arising from the implementation and lessons in order to avoid future mistakes
* Closure date of the Change Record
* Closure date of the Change Record
<p>&nbsp;</p>
<html>By:&#160;&#160;Stefan Kempter&#160;<a rel="author" href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/images/bookmarking/linkedin.png" width="16" height="16" title="By: Stefan Kempter | Profile on LinkedIn" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>, IT Process Maps.</html>
<!-- This page is assigned to the following categories: -->
[[Category:Checklist (ITIL)|Post Implementation Review PIR]]
[[Category:Change Management|Post Implementation Review PIR]]
<!-- --- -->

Latest revision as of 19:01, 29 March 2019

Checklist Post Implementation Review (PIR) - Template Post Implementation Review (PIR)
Checklist Post Implementation Review (PIR) - Template Post Implementation Review (PIR)


 

ITIL Process: ITIL Service Transition - Change Management

Checklist Category: ITIL Templates - Change Management

Source: Checklist "Post Implementation Review - PIR" from the ITIL Process Map V2  | ⯈  ITIL Process Map V3

 

An investigation takes place during the Post Implementation Review (PIR), as to whether the following information related to the implementation is entered into the Change Record:

  • Functional and operational tests
    • Operational tests
      • Begin
      • End
    • User tests
      • Begin
      • End
    • Summary of Test results
  • Actual implementation
    • Begin
    • End
  • Acceptance Tests
    • Begin
    • End
    • Date of acceptance
    • Where necessary, with which restrictions?
  • Time and effort
    • Actual time and effort for the implementation
  • Statements as to the achievement of objectives
    • Objectives of the Change achieved?
    • Where necessary, with which restrictions?
  • Cost, time and effort adhered to for the implementation?
  • Findings arising from the implementation and lessons in order to avoid future mistakes
  • Closure date of the Change Record

 

By:  Stefan Kempter , IT Process Maps.