Dead and Hopefully Not Buried
It’s an interesting term, “post-mortem”. For most people it conjures up images of criminal investigators digging up clues on some poor person who died from mysterious causes, but not a closure process used by project managers to help review what went wrong or right during the course of a project. Just as you might wince from another late night cop drama doctor chopping up someone in a morgue, you could feel the same about going to yet one more meeting about a project you wish would just fade away and leave you alone without going over some of its stomach-turning details.
And yet, there is something to be learned from these examinations. Want to solve a mystery on your next project before it becomes a show-stopper? Make sure you’re a contributor to the next project post-mortem you’re a part of and don’t sit on you hands waiting for the clock to reach the hour. Otherwise, everyone will assume that what happened on the project was wrong and that nothing right came from it.
And by the way, nothing’s perfect. If it were, there would be no need for any projects beyond version 1.0. To think you can walk away from a project and assume that everything went right is either ignorance or arrogance. Bugs, last minute changes, conniptions in software and hardware, personnel changes, etc.--the list of problem spots goes on. What
Please log in or sign up below to read the rest of the article.
ADVERTISEMENTS
|
"One man alone can be pretty dumb sometimes, but for real bona fide stupidity there ain't nothing can beat teamwork." - Mark Twain |




