Everybody knows that in project management, not only in software but in every area, we should learn from one project to another. This means that we never do it perfectly, we always forget something and we never have the absolute knowledge about anything. The only solution is to minimize the mistakes along the way.
I first had to make peace with my ignorance to accept the learning process. While managing a team, no matter how small, this self awareness is more difficult, so the methods and check lists kick in.
Here, at Queo, we are now making efforts to always add something from one project to another and the "Post Mortem" task is the perfect solution (obviously). How to get there and how to measure the "improveness" is other subject. We can have many "Post Mortem" meetings with the same problems every time, which makes it rather useless.
But how do we guarantee that meeting, that learning process and the team commitment? This blog post is purposely part of my "message transmission" but it's very subtle. Is it possible to make it mandatory? Do we need to be born in another culture to always do this?
Anyway, implementing this rule, forcing the first "Post Mortem" meetings, adding a auto-task so we never forget, and more important, giving the opportunity for everyone to participate, are tasks that probably will always be around. The measuring system is still something to create: it could be something simple like pulling the last "Post Mortem" meeting and scratch the issues that didn't happen this time.
In the end, I hope that working is not just filling huge check lists and committing to boring tasks. But it certainly can't be making the same mistakes over and over.