48260 Engineering Project Management: Assessment Task 4 Post-Project Evaluation
Context
University of Technology Sydney delivers 48260 Engineering Project Management as a later-stage core subject in the Bachelor of Engineering and Bachelor of Engineering (Honours) programs. Assessment Task 4: Post-Project Evaluation carries a weighting of 30% and requires a 1500-word individual reflective report plus a team analysis document. The task asks students to evaluate their group project against project management theory, to account for team performance, and to identify what they would carry forward and what they would abandon. The 2026 iteration retains the individual report plus team analysis structure used in 2023 and 2024 while aligning the evaluation criteria with ISO 21513:2026 guidance on post-project evaluation. Submission is through Canvas as a PDF, with the team analysis document uploaded separately by each student.
Summary
- Title: Assessment Task 4: Post-Project Evaluation
- Due Date: 11.59pm on the Friday of Week 12
- Length: 1500 words (individual report, excluding appendix, references, and team analysis document)
- Weighting: 30%
- Format: Individual reflective evaluation plus team analysis document
- Submission: Two PDFs to Canvas
Subject Learning Outcomes Assessed
Successful completion demonstrates:
- SLO 2: Apply project management concepts such as scope, assumptions, risk, milestones, cost, resources, and work breakdown structures to manage and review a small engineering project.
- SLO 3: Reflect on project management experience to conduct a post-project evaluation.
- SLO 5: Evaluate team performance and individual contribution within an engineering project context.
Task Description
Evaluate the engineering project your group delivered across Tasks 1, 2, and 3. The report must assess whether the project met its objectives, how the team coordinated its work, where ethical and regulatory considerations shaped decisions, and what you personally learned about project management practice. The task is not a narrative of what happened week by week. It is an evaluation against explicit criteria drawn from project management literature and from the standard your group applied. Students who describe events without judging them against evidence will meet the lower rubric bands.
Task Instructions
Structure the report in five sections. Each section must connect specific project events to project management concepts and to relevant literature. Use the team analysis document to record contribution data and peer feedback; do not duplicate that data in the body of the report.
Section 1: Project Outcomes and Success Criteria
State the project’s intended objectives and the success criteria your group adopted. Evaluate the extent to which each objective was achieved. Distinguish between project management success (delivery on time, budget, and scope) and project success (benefits realised for the client or user). Maximum 300 words.
Section 2: Coordination and Time Management
Analyse how the group coordinated tasks, milestones, and dependencies. Identify one coordination decision that worked and one that failed or nearly failed. Explain the consequences of each with reference to scheduling, resource allocation, or communication structures. Maximum 350 words.
Section 3: Communication and Team Dynamics
Evaluate the group’s communication practices. Address how the team handled disagreement, how information moved between members, and how accountability was maintained. Use at least one specific incident from the project and connect it to team effectiveness literature. Maximum 350 words.
Section 4: Ethics, Regulation, and Professional Responsibility
Identify the ethical and regulatory considerations that shaped the project. Explain how the group responded to them. Evaluate whether the response met the standard expected of a professional engineering team, and state what should have been done differently. Maximum 300 words.
Section 5: Personal Learning and Transfer
State what you personally learned about project management. Identify two practices you will carry into future projects and one practice you will abandon. Justify each choice with reference to your experience in this project and to project management literature. Maximum 200 words.
Team Analysis Document
Complete the template supplied on Canvas. Record each member’s contribution against the agreed work breakdown structure, the percentage of tasks completed, and a brief peer assessment. The document must be signed by all members or accompanied by individual statements where consensus was not reached. Submit it as a separate PDF.
Marking Rubric
| Criteria | Weight | High Distinction (85–100) | Distinction (75–84) | Credit (65–74) | Pass (50–64) |
|---|---|---|---|---|---|
| Evaluation of project outcomes against success criteria | 25% | Precise distinction between project management success and project success; evaluation supported by specific evidence and theory. | Clear evaluation with appropriate evidence. | Adequate evaluation with some evidence. | Descriptive account with weak evaluation. |
| Analysis of coordination and time management | 20% | Insightful analysis of scheduling decisions and their consequences, linked to project management concepts. | Clear analysis with appropriate concepts. | Adequate analysis with limited conceptual grounding. | Narrative description without analysis. |
| Evaluation of communication and team dynamics | 20% | Nuanced evaluation of team interaction with specific incidents and relevant literature. | Clear evaluation with appropriate examples. | Adequate evaluation with some examples. | Generic or unsupported claims about teamwork. |
| Ethical and regulatory analysis | 15% | Sophisticated analysis of professional responsibility with concrete recommendations. | Clear analysis with appropriate recommendations. | Adequate analysis with limited depth. | Surface-level or inaccurate analysis. |
| Personal learning and reflective quality | 10% | Genuine, specific reflection that distinguishes transferable practice from situational luck. | Clear reflection with specific examples. | Adequate reflection with some specificity. | Generic or formulaic reflection. |
| Team analysis document and referencing | 10% | Complete, consistent contribution data; flawless APA 7 referencing. | Complete data with minor inconsistencies; accurate referencing. | Adequate data with some gaps; minor referencing errors. | Incomplete data or frequent referencing errors. |
Sample Response: Distinguishing Project Management Success from Project Success
A project can be delivered on time and still fail its users. Our group completed the design and prototype within the agreed schedule and budget, which satisfies the conventional project management success criteria. The client’s stated need was a low-cost monitoring solution for a small agricultural operation. The prototype worked in the workshop but required a power supply the client could not provide in the field. On the delivery measures we succeeded. On the benefit measure we did not. Research on “the responsibilities of the project owner in benefits realization” shows that this gap between output delivery and benefit realisation is common when the project owner does not test the operating assumptions with the user before design freeze (Zwikael et al., 2019). Our group treated the client’s brief as a specification rather than as a problem statement. A stronger approach would have been to test the power constraint during the requirements phase, when a change would have cost a week rather than a redesign. The post-project evaluation should name that decision and its consequences rather than congratulating the team on hitting deadlines.
Communication Failures That Do Not Look Like Failures
The most damaging communication problem in our project was not conflict. It was silence. Two members stopped raising concerns after week six because earlier suggestions had been absorbed into the plan without acknowledgement. The work continued, deadlines were met, and the group appeared functional. Research on team effectiveness suggests that this pattern, where members withhold input because the perceived cost of speaking exceeds the perceived benefit, erodes decision quality even when outputs look acceptable (Mathieu et al., 2019). Our team analysis document records contribution percentages, but percentages do not capture withheld expertise. A peer review that asks only whether someone completed their assigned tasks will miss the member who completed their tasks while disengaging from the group’s reasoning. The evaluation should therefore separate task contribution from decision contribution. That distinction is uncomfortable to write, particularly when the group received a good mark, but it is the difference between a reflective evaluation and a compliance document.
Why “We Communicated Well” Fails the Rubric
Students often write that their group communicated well because meetings were held and messages were answered. The rubric asks for evaluation, not reassurance. A defensible claim about communication needs three elements: a specific incident, an explanation of what the communication pattern produced, and a link to evidence about team performance. For example, the group might note that decisions were made in a group chat that two members checked only in the evening, which delayed the resolution of a design conflict by three days. That claim is specific, it explains a consequence, and it can be connected to literature on coordination costs and response latency. A claim that “communication was good overall” cannot be evaluated because it does not identify what was communicated, to whom, or with what effect. The same logic applies to the ethics section. Naming the relevant standard is insufficient. The report must show how the standard changed a decision or should have changed one.
Ethics as Design Constraint, Not Decoration
Engineering ethics often appears in student reports as a paragraph about safety and professional codes appended to the end. In this project, the ethical question was concrete: the monitoring device collected data from a site the client did not own, and the group had not established who would hold the data or for how long. The relevant obligation was not abstract. It concerned privacy, consent, and the professional duty to advise a client who may not have considered the implications. The group’s response was to add a data retention note to the final report, which informed the client but did not resolve the underlying issue. A stronger response would have raised the question at the requirements stage and documented the client’s decision. The evaluation should assess the response against the standard expected of a professional engineering team, not against the standard the group set for itself. That shift in benchmark is what the rubric’s higher bands reward.
Conclusion
This evaluation rewards honesty about decisions that did not work. The group received a mark for the project, and that mark is now fixed. The evaluation is a separate task with a separate purpose: to convert experience into transferable judgment. Students who write a success story will produce a document that satisfies nobody, least of all themselves. Students who identify the two or three decisions that shaped the outcome, explain why those decisions seemed reasonable at the time, and state what they would do differently will produce something useful. The team analysis document is evidence, not a verdict on peers. Keep the report focused on what the project teaches about managing work, and keep the reflection specific enough that a future employer could act on it.
References
Denicol, J., Davies, A., & Kelsey, S. (2021). The organizational architecture of megaproject delivery. International Journal of Project Management, 39(3), 237–249. https://doi.org/10.1016/j.ijproman.2020.09.006
International Organization for Standardization. (2026). ISO 21513:2026 Project, programme and portfolio management: Guidance on post-project and post-programme evaluation. ISO. https://www.iso.org/standard/21513
Mathieu, J. E., Gallagher, P. T., Domingo, M. A., & Klock, E. A. (2019). Embracing complexity: Reviewing the past decade of team effectiveness research. Annual Review of Organizational Psychology and Organizational Behavior, 6, 17–46. https://doi.org/10.1146/annurev-orgpsych-012218-015106
Zwikael, O., Meredith, J. R., & Smyrk, J. (2019). The responsibilities of the project owner in benefits realization. International Journal of Operations & Production Management, 39(4), 503–524. https://doi.org/10.1108/IJOPM-02-2018-0075
