Change PIRs

[Draven]

Hello All

I currently control my programme's (operational) change mgt, currently using an RFC form created in Exchange, for my weekly CAB meetings I just use a spreadsheet format agenda (all very low tech!).

One area I want to pursue now is Post Change Implementation Reviews, and I was wondering if anyone out there could advise on a usefull template/structure for this?

[Ines]

This is what is used by my company, with company logo at the top. It's presented to the service providers within a table in a Word doc:

IT Change Post Implementation Review (PIR)

Please forward completed form to CIO IT Change Manager, within 5 business days of request to complete.

Change Number
Date of Change Implementation
PIR Owner/Contact Number
Change Owner/Contact Number
Service Provider
Responsible Team

******************
Change Description
Related Incident, Problem Nos.
Steps Taken (include timings)

******************
Results :
what went wrong,
what went right

******************
Learning Points

******************

Actions:
Who
When

[Draven]

Thanks Ines

[Ed]

We do ours electronically these days - our RFC is a word document with the 2nd last page as a set of basic review questions.

We mail the page to the person releaseing the change into live and they fill it in and send it back - the questions are listed below.

Has the Change had the desired effect & met its objectives? If No, detail shortfalls below.

Are the Users / Customers content with the result? If No, detail shortcomings below.

Have there been any unexpected/undesirable side effects? If Yes, input detail below

Were the resources required to implement the Change as planned? If No input detail below.

Did the Implementation plan work correctly/as planned? If No, detail differences below.

Was the Change implemented on time? If No, detail why not below

Was the Regression Plan needed? If Yes, detail reasons below

If Yes to question 7, Did the Regression Plan work correctly? If No detail errors/reasons below

We feed the 'wrong' answers into a simple excel spreadsheet and build a set of metrics showing how many problem / failed changes we have. We also look for common failings and attempt to educate the implementers to remove these errors.

Regards

Ed