I am working with my director to create a post-mortem template and process. Three of us have started ideating but I'd like some good suggestions to compile qualitative and quantitative questions as well as suggestions on how to run the post-mortem meetings. Links to reference will be greatly appreciated!
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Hey Rachel, there are quite a few post-mortems and post-implementation templates on this site. Simply click on the magnifying lens icon and it will take you to the Advanced Search Screen. Search on either post-mortem or post-implementation and you will have quite a few references. (You might have to use the filters to narrow it down to the type of information you're looking for.) Saving Changes...
Do you do regular reviews and frequently seek feedback during the project? If you capture those reviews in a standard way then the post-project review can be an aggregation of what you already learnt and the improvements made based on those learnings. It would seem to be a bad sign if you discovered anything new after the project finished. Saving Changes...
I'd recommend NOT calling it a post-mortem unless your project failed totally or was terminated prematurely before business value was realized.
Before coming up with a list of questions, you should define what you wish to get out of the event? A learning-focused event is quite different from a performance measurement/reporting-focused one.
Kiron
...
1 reply by Rachel Miller-Bradshaw
May 21, 2020 9:07 PM
Rachel Miller-Bradshaw
...
I agree. Calling it a "post mortem" so far as raised eyebrows or caused defensive behavior. I think I like "post-implementation" review.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Trying to add something to great comments above. 1-we call it post-implementation review. We do this understanding that we help in creating a solution and because the organization is a system then because we introduce something then we modified the system. 2-we carefully pay attention on not to include questions related to the product. Our focus is the project, not the product.
Some metris to be included (scores required, 1 to 4)
Scope : we delivered what we committeed
Budget : we did not overspend/underspend (+/- 10%) to implement
Time : we delivered the project successfully on time
Business Value approved in Business case was achieved
Minimum business disruption as a direct result from the project
Minimum systems disruption as a direct result from the project
Complexity of the IT systems landscape decreased (or did not increase)
Number of issues after implementation was at a manageable level
Change management efforts were appropriate (Training, Comm. …)
Out-of-scope tail was reasonable (reasonable #Scope change requests)
Estimates were in line with the actual costs (including Running costs / TCO)
Team was not adversely impacted by the project (burnout, turnover, …)
"Risks of the project were appropriately identified and mitigated and
unanticipated obstacles were properly managed (Escalation, resolution) "
...
3 replies by Camilo Reyes, Kwiyuh Michael Wepngong, and Rachel Miller-Bradshaw
May 21, 2020 9:06 PM
Rachel Miller-Bradshaw
...
Thank you for the great information!
I do have another question:
The metris you added that should be determined are included in the "post-implementation" review along with the processes implemented from the "lessons learned" from the questionaires and meetings?
Nov 19, 2020 1:19 PM
Camilo Reyes
...
Great answer Sergio, thank you very much for sharing such a bright insight.
Trying to add something to great comments above. 1-we call it post-implementation review. We do this understanding that we help in creating a solution and because the organization is a system then because we introduce something then we modified the system. 2-we carefully pay attention on not to include questions related to the product. Our focus is the project, not the product.
Some metris to be included (scores required, 1 to 4)
Scope : we delivered what we committeed
Budget : we did not overspend/underspend (+/- 10%) to implement
Time : we delivered the project successfully on time
Business Value approved in Business case was achieved
Minimum business disruption as a direct result from the project
Minimum systems disruption as a direct result from the project
Complexity of the IT systems landscape decreased (or did not increase)
Number of issues after implementation was at a manageable level
Change management efforts were appropriate (Training, Comm. …)
Out-of-scope tail was reasonable (reasonable #Scope change requests)
Estimates were in line with the actual costs (including Running costs / TCO)
Team was not adversely impacted by the project (burnout, turnover, …)
"Risks of the project were appropriately identified and mitigated and
unanticipated obstacles were properly managed (Escalation, resolution) "
Thank you for the great information!
I do have another question:
The metris you added that should be determined are included in the "post-implementation" review along with the processes implemented from the "lessons learned" from the questionaires and meetings?
...
1 reply by Sergio Luis Conte
May 22, 2020 3:33 AM
Sergio Luis Conte
...
You are welcome. Please take into account that metrics will depen on what you need to evaluate. In our case, lessons learned are a required deliverable to close the project.
I'd recommend NOT calling it a post-mortem unless your project failed totally or was terminated prematurely before business value was realized.
Before coming up with a list of questions, you should define what you wish to get out of the event? A learning-focused event is quite different from a performance measurement/reporting-focused one.
Kiron
I agree. Calling it a "post mortem" so far as raised eyebrows or caused defensive behavior. I think I like "post-implementation" review. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
May 21, 2020 9:06 PM
Replying to Rachel Miller-Bradshaw
...
Thank you for the great information!
I do have another question:
The metris you added that should be determined are included in the "post-implementation" review along with the processes implemented from the "lessons learned" from the questionaires and meetings?
You are welcome. Please take into account that metrics will depen on what you need to evaluate. In our case, lessons learned are a required deliverable to close the project. Saving Changes...
Camilo ReyesProject Manager| CBREVancouver, British Columbia, Canada
May 21, 2020 7:35 PM
Replying to Sergio Luis Conte
...
Trying to add something to great comments above. 1-we call it post-implementation review. We do this understanding that we help in creating a solution and because the organization is a system then because we introduce something then we modified the system. 2-we carefully pay attention on not to include questions related to the product. Our focus is the project, not the product.
Some metris to be included (scores required, 1 to 4)
Scope : we delivered what we committeed
Budget : we did not overspend/underspend (+/- 10%) to implement
Time : we delivered the project successfully on time
Business Value approved in Business case was achieved
Minimum business disruption as a direct result from the project
Minimum systems disruption as a direct result from the project
Complexity of the IT systems landscape decreased (or did not increase)
Number of issues after implementation was at a manageable level
Change management efforts were appropriate (Training, Comm. …)
Out-of-scope tail was reasonable (reasonable #Scope change requests)
Estimates were in line with the actual costs (including Running costs / TCO)
Team was not adversely impacted by the project (burnout, turnover, …)
"Risks of the project were appropriately identified and mitigated and
unanticipated obstacles were properly managed (Escalation, resolution) "
Great answer Sergio, thank you very much for sharing such a bright insight.
...
1 reply by Sergio Luis Conte
Nov 19, 2020 2:37 PM
Sergio Luis Conte
...
You are welcome. I am happy if this helps to people.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Nov 19, 2020 1:19 PM
Replying to Camilo Reyes
...
Great answer Sergio, thank you very much for sharing such a bright insight.
You are welcome. I am happy if this helps to people. Saving Changes...
