I'm preparing a Lessons Learned paper and I wonder what such paper should contain. I found this post: http://www.ehow.com/how_8014106_write-lessons-learned-report.html, some of the points listed there ...
I'm conducting a Post-Mortem Review with Senior Management, regarding a project that had multiple unfulfilled/half-fulfilled deliverables that caused issues for clients. The deliverable for the ...
It might be a silly question for non-latin speakers, but it's odd to hear about a post-mortem meeting for a successful project since this expression means 'after death'. I know that this can be also ...
In my current project team, I try to encourage an open atmosphere and discussions. In general, I have the impression that we are on a good road in that regard. The idea of a post-mortem after each ...
(Related Q). I have recently landed myself a product engineer role. The software product is a server based product with a front end GUI in the browser. We have a number of clients, but the product is ...
I'm currently studying the "death march" phenomenon, as it relates to project management. (From my understanding, the term "death march" refers to a project which is evidently at high risk of ...
One of the things I wish I did more often and better is follow through with the data collected during a Postmortem. I'm looking for input on "How do you ensure the postmortem data is followed up and ...
Running a project post-mortem (or post-implementation review) is a valuable way to identify and document lessons learned from the project. After doing so, how to best share (and act upon) those ...
I was thinking of tagging resolved cases by their (probable) cause, e.g. incomplete feature specification last-minute fix after test typo ... Maybe common causes might show up in this, so we get ...
I'd like to do a post mortem ("lessons learned") analysis of a recent feature development. It would be the first formal post mortem we do. It was a comparedly small project (roughly 3 weeks), but ...