Yip...have been off the blogging world for a bit longer than usual as I've been quite busy trying to catch up and finish off various businesses in 'me' life!
During my 'off blogging' period...of coz I'm still relatively active on the web....and I have so many so many so many blog posts that have accumulated for the past couple of months or so....so, let me see if I can slowly catch up! : P
Meanwhile let me move on to "Postmortems"!!!
What is "Postmortems"?
Typing in "define: postmortem" on Google gives me the following:
Came across this article today at work:Occurring after death.
www.dabney.com/wacomuseum/library/medterms.htmlAfter death. Often used to describe an autopsy.
www.stjude.org/glossaryComplete exam of chicken after death
www.geocities.com/KelliAnn293/definitions.htm
Gave Development Postmortem
which talks about what can and should be discussed after a software project has come to an end.
Obviously this rarely happens in reality, but I reckon and agree it is very important to have 'some sort of postmortem' no matter how short it takes. By having communication and discussions, everyone and those participated can all 'learn' from the experience....so that the next project will be better to manage, better to develop and more efficiently completed!
My conclusion:
If I am a manager or a project leader one day.....I'll definitely look into this!!! : P
*P.S. - Inside the article there, there is a link to another article "The Value of Project Postmortem"
haha sounds like you will be a very 稱職 project manager =P
ReplyDelete