2007 Post-Mortem

Post-Mortem: discussion of an event after it has occurred.

In the tech industry this term is used primarily to describe the meeting that takes place after a code release. All those involved (Developers, QA, Product, Etc.) get into a room and talk about every aspect of the last release cycle. The cool things about these meetings is that not only is every aspect talked about, but all perspectives have representation in the meeting. During this meeting everyone has a voice to discuss what went right and what went wrong.

Sometimes - in poorly organized meetings - it becomes a blame game and everyone points fingers. In environments where employees are able to check their pride at the door and accept "constructive criticism" these meetings can be incredibly useful.

The whole point of the Post-Mortem is to take an honest look and see where strengths are and where areas of improvement are needed. Both are equally important to recognize in yourself.

It is easy to gloss over success stories, but time should be given in order fully understand why those were success stories. This analysis will help you learn your strengths and as importantly, where there were breakdowns that could be further optimized. Looking at strengths will also reconfirm that things are going well. As humans we tend to need that reassurance.

Areas of improvement can be a touchy subject, but the thing to remember is that nobody and no process is free from its scope. Even the best success story has ways in-which it can be improved the next time. This is where egos need to be checked at the door and a willingness to learn has to take front and center. Plus, it only does good if you are willing to tell it how you see it. At times people are too sheepish to express how they feel; thinking that it will cause a ripple in the pond. However, during the next cycle they will most likely see it happen again until they face the deprecated process, analyze it, then optimise it.

So why am I telling you all of this?

Go back and read this again, but this time apply it to cycling. Think of your last release as the 2007 cycling season. It is time to look back at your past success and failure. Only then, if you are honest with yourself, will you be able to begin to plan for next season.

There is more to a Post-Mortem meeting than analysing strengths and weaknesses. There are action items and goals, but i think I will be taking this in stride. In fact, I'll be taking baby steps and my first step will be to analyse my 2007 cycling season.

More to come...