<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/platform.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d9051860177815514007\x26blogName\x3dNamefulless\x26publishMode\x3dPUBLISH_MODE_BLOGSPOT\x26navbarType\x3dSILVER\x26layoutType\x3dCLASSIC\x26searchRoot\x3dhttps://namefulless.blogspot.com/search\x26blogLocale\x3den\x26v\x3d2\x26homepageUrl\x3dhttp://namefulless.blogspot.com/\x26vt\x3d845398891234413308', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>
Post Mortem

Saturday, October 24, 2009 @ 4:54:00 PM
The dust has settled. Okay, shake the computer screen to unsettle the dust. Ah choo! The dust has got into my nose, so stop shaking it. hahah

Now that the dust has really settled, it's time to do some post mortem. Post what mortem? Is it the cutting up of dead bodies and studying them? Of course not... hahaha

Post mortem is an analysis or review of a finished event, or an investigation of a corpse to determine the case of death. In this post, I will be referring to the first meaning. So analysing of what event? I'm sure you can guess; it's your exam results.

What's the purpose of a post mortem?

According to my source, it formalizes the learning of a past experience, identifying what went well and what went wrong during a project; which is preparation of the examinations, in this case. One shouldn't hold a post mortem too early, or too late, because in the former, one might focus more on the later parts on the project, while in the latter, one might forget the details.

So what should be in a post mortem?

Firstly, what went right. Then, what went wrong. Lastly, what can be done to prevent it from happening again. While ending on the “right” might make one feel better at the end, studies have shown that right-first/wrong-last structure is better at eliciting the right information.

For things that went well, one simply needs to list down what he/she thought went well, and record why was it successful. While some things listed “right” might contradict with the “wrong” part thought about later, it's okay.

In things that went wrong, it can be done by simply listing what they went wrong. Think about whether there were any signals or flags that might have warned something could be a problem. This is an important question, as one will be able to keep a lookout during the next project.

Also, wrap up each issue with what could have been done differently to make it more successfully. For each issue, one should think of the following:



At things that could have changed for the future, look back at the information collated from the "good" and "bad" issues. "

To record the post mortem, one can write on sheets of paper, and then organizing it into different topics. (Although I don't think there are different topics in our case) One good way to do that is to use different colours for different topics. For example, red could be for negative comments, green for positive, and yellow for things that need to be changed.
~~~
With this, you are done with your post mortem. But, one of the biggest trap people always fall into after a post mortem, is to chuck it away and never referring it again.

That's a mistake. One should make use from the recommendations from the post mortem as a "self-check". At various time, it's effective to take out the list of recommendation, and evaluate how you are doing in those areas....

Credits:
  • http://stackoverflow.com/questions/38066/whats-your-post-mortem-meeting-format
  • Document I downloaded from the internet
  • Journey to the East

    Saturday, October 17, 2009 @ 5:45:00 PM
    LuLuLu
    LaLaLa
    LiLiLi

    Back to the main subject. HELLO! ahhahaha

    I'm sure you've heard about "Journey to the West". What about "Journey to the East"?
    I've been there.

    East Coast Park, that is. (lame..... -.-)

    I want to break free from the bondage of the HOUSE!
    (Sounds claustrophobic)

    Anyway, back to the main point again. As said, I wanted to break free from the bondage of the house. So I schemed this operation called "Project Runway" (Project Run away), to get out from the house and run away. HAHAHA
    ~~~~~~

    Nah. That's an exaggeration. The truth was that I wanted to get out of the house. So I decided to cycle out of the house, without knowing where to go. I was at Sun Plaza Park, before deciding to go East Coast Park (ECP). So I detoured and went to ECP, following the park connector. It went past Bedok Reservior, and so coincidental, I met Hai Xin. He was also going with his friends, but they weren't there yet. So we went together.

    hahaha

    I soon reached ECP, and cycled all the way to area D (the park connector reached ECP at area G). So I followed the route I walked after the 2.4 run and reached Kembangan. But this time round, it was different. I didn't cycle to the interchange; I followed the connector fully, ending my journey back at Bedok reservior. Cycled back home.

    Just in case you are curious, the whole thing took 3hours+

    All in all, it proves that I AM CRAZY, resulting in being WEIRD.

    PAULA THE WEIRDO~

    Signing off,
    Namefulless

    I cycled Part 'A' , 'B' and 'G'