PMGT5820 Execution and Acceptance
The Complete Study & Assessment Guide · S2 2026PMGT5820 Overview
- University of Sydney
- Semester 2 2026
- Postgraduate
- Project Management
PMGT5820 Execution and Acceptance is a postgraduate University of Sydney unit about the part of project management where approved plans meet operational reality.
- Assessment profile Project work, participation and a timed in-semester test
- Core control Compare current evidence with an authorised baseline
- Quantitative method Interpret PV, EV and AC at one status date
- Closing move Separate verification, acceptance, handover and closure
How PMGT5820 is assessed
| Component | Weight | Format |
|---|---|---|
| Group Presentation | 20% | Update project performance and closure activities to the Project Sponsor, with questions and answers; 15 to 20 minutes across multiple weeks; AI allowed |
| Early Feedback and Reflection | 0% | Week 3; 500 words; feedback and reflection on learning to date; AI allowed |
| Project Baseline | 15% | Week 4; 1,000 words plus Microsoft Project file; AI allowed |
| Project Status Dashboard | 20% | Week 7; video presentation, 500-word summary and Microsoft Project file; AI allowed |
| In-Semester Test | 20% | Week 8; 50 minutes; learning up to Week 8; AI prohibited |
| Project Closure and PIR Report | 15% | Week 13; 4,000-word report on closure, post-implementation review, acceptance and handover; AI allowed |
| Class participation | 10% | Weekly class activities, discussion and reflection; AI allowed |
The weighted rows total 100%. The Early Feedback and Reflection task is published at 0% and remains listed as part of the official assessment design. The captured unit material states that students are expected to participate in at least 85 percent of all timetabled activities; failure to meet this level may result in a fail grade. This condition sits outside the assessment table and should be checked against the current unit information. The phrase minimum attendance requirement is used. A separate numeric threshold is not published beyond the percentage already stated. The current unit outline and Canvas control operational instructions.
Current PMGT5820 dates
| Date | Item | Control |
|---|---|---|
| 23 August 2026 at 23:59 | Early Feedback and Reflection | Published Week 3 deadline for the 0% task |
| 30 August 2026 at 23:59 | Project Baseline | Published Week 4 deadline for the 15% group task |
| 20 September 2026 at 23:59 | Project Status Dashboard | Published Week 7 deadline for the 20% task |
| 8 November 2026 at 23:59 | Project Closure and PIR Report | Published Week 13 deadline for the 15% group task |
Dates are as published in the current University of Sydney unit outline. Confirm exact deadlines and submission settings in the live LMS.
What PMGT5820 covers
The nine-chapter route follows the unit from project start-up and scope control through teams, stakeholders, procurement, risk, change, quality and progress reporting, then closes with acceptance, handover and agile delivery. Each chapter links an artefact to a decision, the evidence needed to support it and the authority required to act.
Project Start-Up and Scope Baselines
Kick-off alignment, scope boundaries, work breakdown and the integrated baselineProject execution becomes controllable only after the team shares an authorised reference.
- Kick-off meetings as alignment and control interventions
- Scope statements with inclusions, exclusions, assumptions and constraints
- Deliverables versus the activities used to create them
- Work breakdown structures, ownership and dependency logic
- Integrated scope, schedule and cost baselines
- Acceptance criteria and delegated approval authority
Leading Project Teams Through Execution
Team structures, adaptive leadership, virtual collaboration and decision rightsExecution leadership is a changing choice about direction, support, decision rights and relationships. This chapter compares team structures, leadership responses, virtual collaboration and high-performance conditions.
- Traditional, distributed and virtual project team structures
- Leadership response matched to capability and task clarity
- Team charters, roles, meeting rhythms and escalation routes
- Decision rights, advisory roles and stable commitment
- Psychological safety combined with delivery accountability
- Conflict diagnosed by task, relationship and status dynamics
Stakeholders, Communication and Conflict
Stakeholder analysis, engagement, communication design, negotiation and dispute handlingStakeholder management during execution links influence, impact, information need and project decisions. This chapter uses power-interest mapping as a starting hypothesis, then corrects it for legitimacy, urgency and harm.
- Primary and secondary stakeholders during execution
- Power, interest, impact, legitimacy and urgency
- Communication designed around decisions and feedback
- Sponsor dashboards versus team and client information
- Task, relationship and status conflict
- Negotiation, dispute handling, escalation and decision logs
Resources, Procurement and Supplier Decisions
Capacity choices, sourcing routes, weighted evaluation, negotiation and contract controlResource and procurement management connect capability, timing, sourcing, supplier evidence and contract risk. This chapter moves from a defined need through make-or-buy and market-route choices to weighted evaluation, negotiation, award and supplier control.
- Resource types, capacity, loading and competing priorities
- Make-or-buy reasoning and procurement planning
- Quotation, tender and proposal routes
- Supplier criteria, evidence, weighting and scoring
- Contract types, negotiation and risk allocation
- Procurement registers, milestones, acceptance and closure
Risk Analysis and Project Resilience
Cause-event-effect statements, prioritisation, response ownership and recovery capacityRisk management turns uncertainty into attention, ownership and readiness. This chapter uses cause-event-effect wording, distinguishes risks from realised issues, and evaluates probability-impact scoring without pretending it is a precise forecast.
- Risk statements linking cause, uncertain event and consequence
- Threats, opportunities, issues and assumptions
- Probability, impact, proximity, detectability and connectivity
- Avoid, mitigate, transfer, accept and escalate responses
- Risk owners, action owners, triggers and contingencies
- Residual, secondary and common-mode exposure
Integrated Change and Quality Control
Change authority, configuration, quality planning, process improvement and verificationChange and quality are integrated control systems.
- Sources of change and the importance of clear communication
- Change requests, boards, delegated authority and decision records
- Impact analysis across scope, time, cost, quality and risk
- Configuration control and linked document updates
- Quality planning, managing quality and controlling quality
- Defects, root causes, process improvement and verification
Progress Monitoring and Earned Value
Status dates, work-performance flow, PV, EV, AC, dashboards and conditional forecastsProject control begins with a consistent status date and ends with an authorised response. This chapter distinguishes raw work-performance data, analysed information and decision-focused reports.
- Monitoring, controlling and the status-date boundary
- Work-performance data, information and reports
- Planned value, earned value and actual cost
- Schedule variance and schedule performance index
- Cost variance and cost performance index
- Conditional estimates at completion
Acceptance, Closure and Handover
Verified deliverables, client sign-off, operational transition, closeout and PIREnd-of-project states are related but not interchangeable. This chapter separates technical verification, authorised client acceptance, operational handover, administrative closure and later post-implementation review.
- Verification against requirements and quality evidence
- Acceptance criteria, sign-off and decision authority
- Provisional acceptance and residual defects
- Operational readiness, training and support transfer
- Contract, finance, records and administrative closure
- Lessons with context, cause, consequence and action
Agile Delivery and Adaptive Execution
Backlog decisions, sprint commitments, feedback, retrospectives and hybrid governanceAgile delivery replaces one long prediction cycle with bounded commitments and frequent learning, not with an absence of planning or control. This chapter maps the flow from prioritised backlog to inspectable increment, review and adaptation.
- Adaptive delivery and the value of early feedback
- Fixed boundaries and delegated solution choices
- Backlog ordering by value, risk and dependency
- Sprint goals, increments and definitions of done
- Review, feedback and future reprioritisation
- Retrospective experiments on the delivery system
The unit begins with project start-up, scope and baselines, then follows the manager through team leadership, stakeholder communication, procurement, resource pressure, risk, resilience, change, quality and progress reporting.
It finishes by distinguishing verified deliverables from client acceptance, operational handover, administrative closure and post-implementation review, while also introducing agile delivery as a way to manage contexts where feedback is more valuable than long-range prediction. The strongest thread is integration.
A supplier decision can alter schedule risk; a quality failure can block acceptance; a change request can invalidate a dashboard if the baseline is silently rewritten. This guide therefore treats each artefact as part of one control system.
The current Semester 2 2026 outline assesses students through a group presentation, early feedback and reflection, a project baseline, a project status dashboard, a fifty-minute in-semester test based on learning through Week 8, a project closure and PIR report, and weekly class participation. The weighted rows total 100%, while the early feedback task is published at 0%.
The captured unit material states that students are expected to participate in at least 85 percent of all timetabled activities; failure to meet this level may result in a fail grade. This condition sits outside the assessment table and should be checked against the current unit information. The phrase minimum attendance requirement is used. A separate numeric threshold is not published beyond the percentage already stated.
Worked examples in this guide are original and use fresh organisations and numbers. They rehearse the taught decision forms without reproducing assessment prompts. For operational details, use the current unit outline and Canvas task pages.
The most reliable study routine is to ask four questions for every topic: what is authorised, what evidence shows the current condition, who can decide the response, and which linked record must change after that decision.
Worked example · free
Interpret earned value before recommending corrective action
- +1Schedule variance is $100,000 minus $120,000, or negative $20,000. Less work has been earned than planned at the status date.
- +1Cost variance is $100,000 minus $125,000, or negative $25,000. Completed work has cost more than its budgeted value.
- +1Schedule performance index is $100,000 divided by $120,000, or 0.83, which is below 1 and unfavourable.
- +1Cost performance index is $100,000 divided by $125,000, or 0.80, which is below 1 and unfavourable.
- +1If current cost efficiency continues, estimate at completion is $300,000 divided by 0.80, or $375,000. State the assumption.
- +1Investigate the operational cause and compare authorised corrective options before changing the baseline or forecast.
Key terms
- Acceptance criteria
- Observable conditions a deliverable must meet before an authorised client or sponsor accepts it.
- Approved baseline
- The authorised scope, schedule and cost reference used to compare current project performance.
- Change control
- The governed process for logging, assessing, deciding, implementing and verifying proposed changes.
- Cost variance
- Earned value minus actual cost, used to interpret the cost position of completed work.
- Earned value
- The budgeted value of work actually completed at the status date.
- Handover package
- The verified information, training, access, support and records transferred to the operational owner.
- Planned value
- The budgeted value of work scheduled to be complete at the status date.
- Post-implementation review
- A structured review of delivery performance, operational results, benefits and lessons after implementation.
- Residual risk
- The exposure remaining after a risk response has been implemented.
- Schedule variance
- Earned value minus planned value, expressed in budget-value units rather than elapsed time.
- Stakeholder engagement
- Purposeful involvement designed around a stakeholder's influence, impact and project decision needs.
- Work performance report
- Analysed project information presented to create a decision, action or awareness.
PMGT5820 FAQ
How is the unit assessed?
The current Semester 2 2026 outline publishes a group presentation at 20%, early feedback and reflection at 0%, a project baseline at 15%, a project status dashboard at 20%, an in-semester test at 20%, a project closure and PIR report at 15%, and class participation at 10%. The weighted rows total 100%.
What should I expect from the timed test?
The current outline states that the in-semester test lasts fifty minutes in Week 8 and covers learning up to Week 8. It does not publish detailed question types in the material used here, so prepare flexible responses for scope, stakeholders, procurement, risk, change, quality, progress and acceptance.
Is the unit mathematically difficult?
The material contains applied project calculations rather than advanced mathematics. Earned Value Management requires careful comparison of planned value, earned value and actual cost, with correct signs, units and assumptions. The harder step is usually interpreting the number and choosing an authorised response rather than performing the arithmetic.
How should I prepare the project baseline?
Begin with observable deliverables, exclusions, assumptions, constraints and acceptance criteria. Decompose the result into owned work packages, link dependencies and resources, and confirm who can approve the reference. The schedule file should express the same scope and authority as the written baseline, not a separate version of the project.
How should a project status dashboard be structured?
Build the first view around decisions: baseline position, cost and schedule status, trend, top risks or issues, forecast, actions and sponsor requests. Keep detailed task evidence available behind the summary. Use one status date and distinguish actual data, forecast assumptions and approved changes.
What is the difference between acceptance and handover?
Acceptance is the authorised client or sponsor confirmation that deliverables meet agreed criteria. Handover transfers the result, knowledge, documentation, access and operational responsibility to the receiving owner. A deliverable can pass technical checks while still lacking client acceptance or operational readiness.
Are the worked questions official?
No. Every scenario, number, practice task and model response in this guide is independently authored by AskSia. They are designed around the concepts and decision forms taught in the University materials, but they do not reproduce official assessment questions, past papers, rubrics or model solutions.
Is there an attendance requirement or separate pass condition?
The captured unit material states that students are expected to participate in at least 85 percent of all timetabled activities; failure to meet this level may result in a fail grade. This condition sits outside the assessment table and should be checked against the current unit information. The phrase minimum attendance requirement is used. A separate numeric threshold is not published beyond the percentage already stated.
Questions students ask in each PMGT5820 chapter
- When is a project plan ready to become a baseline?
- It is ready when deliverables and exclusions are clear, work packages have owners, dependencies and resources are coherent, acceptance criteria are observable, and the correct authority approves the integrated scope, schedule and cost reference. A saved schedule without that authority is still a working plan. Chapter 01 · Project Start-Up and Scope Baselines
- How do I choose an appropriate leadership response?
- Diagnose the task, capability, clarity, motivation, conflict and coordination risk. Add direction where the work or authority is unclear, coaching where confidence or capability is developing, and delegation where the team can own the decision within explicit boundaries. Chapter 02 · Leading Project Teams Through Execution
- Why is a power-interest grid not enough?
- The grid can hide people with low formal power but high exposure to harm. Add impact, legitimacy and urgency, then ask which decision needs their evidence. Stakeholder position also changes as incidents, approvals and operational effects emerge. Chapter 03 · Stakeholders, Communication and Conflict
- How should supplier criteria be chosen?
- Start from the required outcome, interface, timing, quality evidence and constraints. Use criteria that separate meaningful supplier strengths without double-counting. Define the evidence and scale before proposals arrive, and screen mandatory requirements before calculating a weighted ranking. Chapter 04 · Resources, Procurement and Supplier Decisions
- What makes a useful risk statement?
- It separates an existing cause, an uncertain event and the consequence for a project objective. That wording exposes where prevention, mitigation, contingency or recovery can act. Vague labels such as supplier risk do not provide the same decision route. Chapter 05 · Risk Analysis and Project Resilience
- How can I distinguish a defect from a change?
- Compare the current output or request with the authorised requirement. Failure to meet that requirement is a defect. Added or altered capability is a change. Ambiguous wording needs documented interpretation and escalation if the interpretation changes the committed boundary. Chapter 06 · Integrated Change and Quality Control
- Why must earned-value inputs share one status date?
- The measures become comparable only when they describe the same reporting boundary. Combining a current cost record with an older completion estimate can produce precise-looking ratios that do not represent one project state. Confirm the cut-off before calculating or interpreting variance. Chapter 07 · Progress Monitoring and Earned Value
- Can operational use count as formal acceptance?
- Not automatically. Check the contract, acceptance criteria and required authority. Continued use may be relevant evidence, but it does not replace a required sign-off. If provisional acceptance is allowed, record every residual defect, owner, due date, retention and route to final acceptance. Chapter 08 · Acceptance, Closure and Handover
- Does agile delivery mean there is no project plan?
- No. Agile delivery still plans objectives, boundaries, dependencies, capacity, quality and near-term commitments. It deliberately leaves some future detail open so evidence can improve later choices. External milestones, contracts and safety obligations may continue to require predictive planning and formal control. Chapter 09 · Agile Delivery and Adaptive Execution
How to prepare for the assessments
Study PMGT5820 as one connected control system. Begin each topic by naming the artefact and the decision it supports: a baseline authorises comparison, a stakeholder plan shapes involvement, a procurement matrix supports supplier selection, a risk register directs attention, a change record protects authority, a dashboard drives action, and an acceptance record permits transition.
After reading a chapter, close the guide and reconstruct the chain from current evidence to authorised response. For quantitative work, keep one status date, write the relationship before substituting values, label every unit and translate the sign into words. For written tasks, use an original project scenario and make each recommendation traceable to scope, stakeholder, supplier, risk, quality or closure evidence.
Rehearse sponsor explanations aloud because a correct analysis can still fail if the requested decision is buried. During the final review, search for broad labels such as complete, approved and on track, then replace them with the specific state and authority. Confirm dates, submission settings, group arrangements and task instructions in the current University of Sydney unit outline and Canvas.
Use AI only within the published task rules, and verify its output against the unit materials and your own project evidence.
Your AI Project Management tutor for PMGT5820
Stuck on a hard PMGT5820 question? Sia is AskSia’s AI Project Management tutor — ask any PMGT5820 Execution and Acceptance question and get a clear, step-by-step explanation grounded in how the course is actually taught and assessed. Read this whole study guide free, then take your hardest questions to Sia.
