FROM: Project Manager
DATE: May 13, 2014
SUBJECT: Postmortem Review
Now that the team has finally delivered the project, there is one more last thing before we disperse which is the project retrospective. In this memorandum, I will provide the advantages and disadvantages of a postmortem review of this training project. It will also show the people to take part in the project retrospective meetings and finally, it will show what the project team hopes to discover.
Benefits and Drawbacks of the Postmortem Review
This review is important in that, it will help the team members to better comprehend how they worked as a team thus, bringing all parties involved in the project one last time before going their separate ways. It will also list goals versus the achievements made from the project and state clearly the team members` participation. It is also obliging in that every detail of the project is acknowledged. This review will be of great help to team member in that, it will give them a chance to improve their project processes by putting major focus on project (O’Connell, 2011). The reviews is also beneficial in a way that; it will enable the project team members to better apprehend their weaknesses and strengths in the technical areas, celebrate their success and help them move and point out what they would like to do their next assignment. Lastly, postmortem review will ensure that there is collection of proposed solutions and suggestions, which will help in the improvement of future projects thus minimizing errors, and time spent working on the project.
The challenge of this review is that, the team has limited time to fix or correct possible mistakes made during the project process (O’Connell, 2011).
A meeting has been scheduled immediately after the training. That will be on May 15, 2014 at the office of the company manager. The meeting will focus on helping the team members formulate a postmortem report and discuss what they learned during the actual project process. The meeting will also enable stakeholders to take notes to enable them give accurate feedback about things that were carried out during the project (O’Connell, 2011). The feedback must entail what went wrong and what needs to be improved in case of another project. The meeting is scheduled to end on May 16, 2014. On this day, all available stakeholders must present their grievances. Their presentations will include, the budget and quality objectives of the project and general project description. The meeting will allow all members to air their complaints and compare views from different stakeholders (O’Connell, 2011).
This review will define what the project team has achieved and what has not been achieved. The results of this project must be promising. The crews’ ideas were found to work well in agile software development projects with tight schedules. Competence is needed for the team to work more effectively in the next projects (O’Connell, 2011). A method needs to be strategized to decide whether the team members want to focus on internal project affairs, which include relations to project stakeholders. Majorly, the post mortem review conclusion will contain details of what went wrong and what went right. An update of the company`s portfolio will also be made as well as the final documentation of the whole project.
O’Connell, F. (2011). What you need to know about project management. Chichester: Capstone.