Assessment Task: Project Review Report
Task Description: This is an individual assignment. Using the Miller Brown Engineering Consultancy Group as your case study, you’re required to prepare a post simulation project review report. Having participated in the start-up, execution and close of the simulation project, you have experienced hands-on project management process, teamwork and reporting and are now required to review the project and consider recommendations for future practice. The review report will communicate to the project Sponsors what worked well and what did not work well in terms of project process, project management and teamwork.
It’s good practice to review each project post its completion. The Project Review Report reviews the project to see how actual results compared to planned and it provides a good overview of the project’s and team’s performance and a meaningful input to future projects.
This assignment is due in week 12. Submission is via Turnitin in Canvas.
- Harvard Referencing style for Reference list
- Double-spaced, Times New Roman font size 12 or Arial size 11 font
- Cover page (with SID), title and date (month, year)
- Reference list, graphs, diagrams and appendices (can be single spaced, font size 10) and not included in the page count
- Page margins should be no less than 2.5cm on each side
- Submitted in Word Document or a PDF via Turnitin
This assignment is strongly oriented towards professional practice and normal business writing. Formal in-text citations are not sought. But a reference list is required.
SUGGESTED PROJECT REVIEW REPORT STRUCTURE:
- Project summary
This section of the Report should provide a summary of the Miller Brown case study project. It is important that this summary captures the scope of the project and contains enough detail to provide a full understanding of the project. Since this document will communicate what went right and wrong with the project, as well as lessons learned and recommendations for future projects, it is imperative that this section of the Report provides enough background information to base the details in the rest of the document on.
- Project Team and reflection on team performance
This section of the Report provides information about who the project team consisted of. It also provides reflection and information on how the team worked together and whether there were any team conflicts and if so, how were they resolved.
- Project deliverables (Planned vs Actual)
This section of the Report describes the expected outcomes of the project as it was originally planned (when planned by ABC Consulting before it was put on hold) and compares these outcomes against the actual outcomes. This is beneficial in defining any occurrences of scope creep or whether a project may not have been completed as planned. This is helpful information for lessons learned and for future project teams conducting similar projects.
- Project costs
This section of the Report describes how the planned or budgeted costs for the project compare with the actual costs. Costs may be affected by scope creep, poor planning, schedule delays, change requests and many other factors. This section should highlight whether or not costs were controlled adequately and if there were additional or excessive costs the reasons should be stated. It is important to communicate why costs were met or may have been higher than planned so future projects can benefit from this information in building a more effective project management methodology within the organisation.
Include a table of key costs as per example below or use the Procurement Plan from the Miller Brown project plan with budgeted costs, actual costs and comments:
- Project schedule
This section of the Report describes the project’s planned schedule or timeline and how the project measured against this plan. This information is helpful in identifying and understanding what may have contributed to project delays or allowed the project to complete early or on time. This can then be used by the team members on future projects or be referenced by other project teams for use on future projects. Archiving project information during the project closure phase is one of the best ways for an organisation to improve its project management methodologies and effectiveness.
Include a table of key timelines as per example below or use the key milestones from the Miller Brown project plan:
- Key Recommendations
This section of the Report highlights key recommendations and lessons learned which would be of use on future projects. This is a valuable part of the project closeout phase and organisational project archives. In the project planning phase one of the first steps is to research organisational archives to identify useful information for planning and executing a project. These recommendations and lessons learned are one of the most important pieces or project success in any effective project management group. Include 3-5 key recommendations in this section:
o Recommendation 1
o Recommendation 2
o Recommendation 3
- Reference List (not included in word count)
- Appendices (not included in word count)
The Appendices could include copies of:
o the Final Gantt Chart o the Final Project Progress Report