PMGT5871 Project Planning
PMGT5871 Overview
- University of Sydney
- Semester 2 2026
- Postgraduate
- 6 credit points
- Evening and online offerings
PMGT5871 Project Planning is a postgraduate unit of study at the University of Sydney, offered in Semester 2 2026 as an evening class at Camperdown/Darlington and as an online offering.
- Final assessment A one-hour written exam in the formal exam period on the content of Weeks 1 to 8.
- Group work Two group assignments: a project management plan and an Agile plan built in Jira.
- Core method Name the planning tool, apply it with real entries or numbers, then check it against a rule from the unit.
- Calculations to practise Forward and backward passes, float, cost roll-ups, time-phased budgets, cost of quality and risk exposure.
How PMGT5871 is assessed
| Component | Weight | Format |
|---|---|---|
| Final Exam · hurdle | 30% | Written exam in the formal exam period; 1 hour; Weeks 1 to 8; AI prohibited |
| Early Feedback Task | 0% | Short response analysing a project scenario; 200 to 400 words; due Week 3 |
| Group Assignment 1 (Project Management Plan) | 25% | Case study plan prepared in groups; due Week 9 |
| Group Assignment 2 (Agile Planning using JIRA) | 25% | Group project plan built in Jira; due Week 13 |
| Individual Assignment (Reflection on Agile Planning) | 10% | Portfolio or journal; 1,000 to 1,200 words; due Week 13 |
| Class Participation | 10% | Workshop activities, discussions and weekly quizzes |
The graded rows sum to 100%, and the Early Feedback Task carries 0%. The unit outline marks the Final Exam as a hurdle task and states that submitting all assignments is compulsory; students who fail to submit all assignments may fail the unit. Students are expected to attend at least 85 percent of timetabled activities, and failing this minimum attendance requirement may result in a fail grade. An earlier Canvas assessment page for this unit stated a 90 percent attendance expectation and used a 20% Week 13 online quiz in place of the final exam, so rely on the Semester 2 2026 outline and check Canvas for any update.
What PMGT5871 covers
The guide follows the weekly schedule of the unit: traditional planning from project types, scope and the work breakdown structure through scheduling, cost, quality, MS Project, human resources, procurement, risk and stakeholder communication, then Agile planning with Scrum, user stories and Jira.
Project Types and Planning Methodologies
projects versus operations, the planning types, PRINCE2, the 10-step method, the project lifecycle and Agile valuesThe unit begins by separating projects from routine operations: a project is temporary, unique, team-based and constrained by time and money.
- Projects compared with operational work
- Four planning types and the approach each suits
- What a project management methodology contains
- PRINCE2 principles, themes and processes
- The 10-step project management methodology
- Initiation, planning, execution and closure
Project Scope, Requirements and the WBS
product and project scope, requirements versus specifications, the scope statement, scope creep and WBS rulesScope defines what the project will and will not deliver.
- Product scope compared with project scope
- Requirements compared with specifications
- Requirement gathering techniques
- Elements of the scope statement
- Business, technological and customer-pleasing scope creep
- Work breakdown structure formats and levels
Activity Scheduling and the Critical Path
schedule formats, sequencing, forward and backward passes, float, Gantt charts and duration estimatesScheduling turns the WBS into time through five steps: define activities, sequence them, estimate resources, estimate durations and develop the schedule.
- Schedule tables, milestone charts, network diagrams and Gantt charts
- Dependencies, milestones, float and the critical path
- The five-step scheduling process
- Merge and burst activities
- Forward pass and backward pass
- Effort compared with duration
Cost Estimates, Contingency and Budgets
direct and indirect cost, contingency and reserves, estimating techniques and the time-phased budgetCost planning produces three sub-plans: the project cost estimate, the time-phased budget and the cash-flow plan.
- Project cost estimate, time-phased budget and cash flow
- Direct cost compared with indirect cost
- Contingency, known unknowns and management reserve
- Direct-cost estimating techniques
- Setting indirect cost and contingency
- Cost baseline, budget at completion and bid price
Quality Planning and the Cost of Quality
quality versus grade, quality assurance and control, the cost of quality and the quality planQuality planning decides how fit for purpose each deliverable must be and how the team will prove it.
- Quality compared with grade and gold plating
- Quality considerations and standards
- Four principles of quality management
- Cost of conformance and cost of non-conformance
- The 1:10:100 rule
- Quality assurance compared with quality control
Building a Project Plan in MS Project
project set-up, calendars, tasks and links, task mode, resources, levelling, cost and progressWeek 5 moves the hand-built plan into Microsoft Project.
- Project information and start date
- Timescale, working time and public holidays
- Tasks, durations, predecessors and summary tasks
- Manual compared with automatic task mode
- Resource sheet and assignments
- Over-allocation and resource levelling
Human Resource Planning and the RACI Chart
the HR management plan, organisation breakdown structure, RACI chart and make, team or buy decisionsPeople are planned like any other resource. This chapter sets out where project staff come from, the elements of human resource planning and the HR management plan, and the sub-plans that support it.
- Sources of project staff
- Elements of human resource planning
- The HR management plan and its sub-plans
- Organisation breakdown structure
- Roles and responsibilities table
- Responsibility assignment matrix and RACI
Procurement Planning and Contract Types
procurement law, essential contract elements, fixed price, cost plus, time and materials and the procurement planAnything the team will not produce itself must be procured, including every team and buy decision. This chapter explains why procurement has legal consequences, the golden rules for running a tender and the six essential elements of a contract.
- What must be procured
- Procurement law and acting as a legal agent
- Golden rules for running a tender
- Six essential elements of a contract
- Fixed price, cost plus, and time and materials
- The procurement statement of work
Risk Identification, Assessment and Treatment
risk vocabulary, identification techniques, qualitative and quantitative assessment, exposure and treatment strategiesRisk planning identifies events that might happen, rates and quantifies them, and decides how to respond.
- Uncertainty, sources, hazards, risks and issues
- Cascading risk and its treatment
- Risk identification techniques
- Qualitative risk assessment and the risk matrix
- Quantitative assessment and exposure
- Pre-treatment and post-treatment risk profiles
Stakeholder Engagement and Communication Plans
stakeholder identification, the power and interest grid, communication methods, channels and tailored reportingA stakeholder is anyone who affects or is affected by the project, and the slides note that most of a project manager's time goes on communicating with them.
- Defining and identifying stakeholders
- The power and interest grid
- Communication compared with engagement
- Elements of the communication management plan
- Interactive, push and pull methods
- Direct and indirect channels and mechanisms
Agile Values and the Scrum Framework
Agile values and principles, waterfall versus iterative delivery, Scrum events and Scrum rolesWeek 9 begins the Agile half of the unit. This chapter explains Agile as iterative delivery in small, consumable increments, reads the four Agile values with their qualifier and highlights the principles most often tested.
- What Agile delivery means
- The four Agile values and their qualifier
- Agile principles
- Waterfall compared with iterative delivery
- Scrum team size and roles
- Discovery, sprint planning, daily scrum, sprint review and retrospective
Product Backlogs, User Stories and Estimation
product and sprint backlogs, epics, personas, user stories, acceptance criteria, story points and prioritisationThe product backlog is the requirements source of an Agile project. This chapter explains the product and sprint backlogs, epics and personas, then the user story template with acceptance criteria and the INVEST checks.
- Product backlog and sprint backlog
- Epics and their breakdown into stories
- Personas and how they guide priority
- User story template and acceptance criteria
- The INVEST model
- T-shirt sizes, Fibonacci points and planning poker
Sprint Planning and Agile Control in Jira
Jira backlogs, epics, sprints and versions, burndown charts, velocity forecasts and Agile cost estimatesWeeks 11 to 13 put the Scrum plan into Jira, the tool used for the second group assignment.
- Agile performance review without status reports
- Task board and sprint burndown chart
- Jira issues, epics, sprints and versions
- Road maps and release planning
- Velocity and forecasting
- Agile cost estimation
The unit outline describes project planning as a key element of successful delivery and promises the tools a planner needs in a traditional project: the work breakdown structure, the precedence diagram, Gantt charts and the critical path, used to plan time, cost and resources and to manage risk. It also introduces software used in industry. The weekly schedule follows that promise closely.
After an introduction to project types and planning approaches, Weeks 2 to 8 each build one part of a project management plan: scope, time, cost and quality, a schedule in MS Project, human resources and procurement, risk, and stakeholder engagement and communication. Weeks 9 to 13 turn to Agile planning, first the Scrum framework and its artefacts, then Scrum planning in Jira.
Tutorials apply each week's tool to a case study, so the group assignments are assembled piece by piece rather than written at the end. The Semester 2 2026 assessment combines a 30% final exam, which is a hurdle task on Weeks 1 to 8, with two group assignments worth 25% each, a 10% individual reflection on Agile planning, 10% for class participation and a 0% early feedback task.
The outline makes submission of all assignments compulsory, and students who miss this may fail the unit. Students are also expected to attend at least 85 percent of timetabled activities, and failing that minimum attendance requirement may result in a fail grade. This guide follows the same order, with original worked examples for every planning tool.
Worked example · free
Find the critical path of a six-activity network
- 1Forward pass with ES plus duration equals EF: A 0 to 4, B 4 to 10, C 4 to 9.
- 1At each merge take the highest predecessor EF: D 10 to 13, E 9 to 11, F 13 to 15, so the project takes 15 days.
- 1Backward pass with LF minus duration equals LS: F 13 to 15, D 10 to 13, E 11 to 13, B 4 to 10.
- 1At the burst activity C take the lowest successor LS, 10, so C has LS 5; A has LS 0.
- 1Float equals LS minus ES: C 1 day, E 2 days, all others 0, giving the critical path A, B, D, F.
Key terms
- Project
- A temporary undertaking that produces a unique product, service or result, unlike repeating operational work.
- Work breakdown structure
- A hierarchy that unpacks the project deliverables into increasingly detailed items of work, inclusions only.
- Scope creep
- The incremental expansion of a project's scope by requirements that were not part of the initial plan.
- Critical path
- The chain of activities with no float, whose delay would delay the project end date.
- Float
- The time an activity can slip without delaying the project end date, found as late start minus early start.
- Contingency
- Money set aside in the estimate for unknown work such as overruns or issues, not for new scope.
- Time-phased budget
- A week-by-week or month-by-month spread of direct costs that places each cost in the period when its work is scheduled.
- Cost of quality
- The sum of the cost of conformance and the cost of non-conformance.
- RACI chart
- A responsibility matrix that marks who is responsible, accountable, consulted and informed for each work item.
- Fixed-price contract
- A contract whose total price for a defined product or service is set at the outset.
- Risk exposure
- The financial impact of a risk multiplied by its probability.
- Power and interest grid
- A stakeholder map that places each party by its power to affect the project and the degree to which it is affected.
- Product backlog
- The prioritised list of features, defects, issues and infrastructure needed to deliver the final product.
- Velocity
- The mean number of story points, or hours, a Scrum team finishes per sprint, used to forecast the rest of the backlog.
PMGT5871 FAQ
How hard is Project Planning at the University of Sydney?
The challenge is breadth. The final exam lasts one hour, is a hurdle task and draws on eight weeks of content, from scope and scheduling to procurement, risk and communication. Several topics involve arithmetic, such as critical path passes, cost roll-ups and risk exposure, and every week's tutorial builds a piece of the group plan, so steady weekly work matters more than last-minute reading.
How is the unit assessed in Semester 2 2026?
The outline lists six tasks. A final exam carries 30%, Group Assignment 1, a project management plan, and Group Assignment 2, an Agile plan in Jira, carry 25% each, an individual reflection on Agile planning carries 10%, and class participation including weekly quizzes carries 10%. An early feedback task in Week 3 carries no weight but gives early feedback.
What is the format of the final exam?
According to the unit outline, it is a written exam held in the formal exam period, lasting one hour, covering the content of Weeks 1 to 8, and AI use is prohibited. The outline does not describe the question types or permitted materials, so read the exam notice on Canvas and prepare both quick recall of definitions and short planning calculations.
Is the final exam a hurdle and what else must I do to pass?
Yes, the outline marks the final exam as a hurdle task. It also makes submitting all assignments compulsory and warns that students who fail to submit all of them may fail the unit. Separately, students are expected to attend at least 85 percent of timetabled activities, and missing that minimum attendance requirement may result in a fail grade.
Are past exam papers available for this unit?
No past final exam or sample paper appears among the materials behind this guide. In the earlier offering, the same eight weeks were tested by a supervised, closed-book online quiz of 30 multiple-choice questions in 30 minutes, with one attempt and locked questions, so practise fast, precise recall alongside calculations. The practice in this guide is original and modelled on those question types.
Which calculations should I practise for the final?
Practise the forward and backward pass with float and the critical path, cost estimates built from direct cost plus percentage-based indirect cost and contingency, time-phased budgets with a cumulative total, the cost of quality as conformance plus non-conformance, and risk exposure as probability times impact before and after treatment. Write every intermediate line so errors can be traced.
Are the Agile weeks examined in the final?
The outline states that the final exam covers Weeks 1 to 8. The Agile weeks, covering Scrum, user stories, backlogs and Jira, are assessed through Group Assignment 2, an Agile project plan built in Jira, and the individual reflection on Agile planning, both due in Week 13. Check Canvas in case your exam notice says otherwise.
Questions students ask in each PMGT5871 chapter
- What separates a project from operational work?
- A project is temporary and creates something unique, with a team assembled for one objective, limited funds, a fixed timeframe and high levels of risk and opportunity. Routine operations such as a fortnightly payroll run repeat indefinitely, even when they have deadlines. Chapter 01 · Project Types and Planning Methodologies
- What goes into a scope statement?
- The slides list objectives and success criteria, deliverables and acceptance criteria, inclusions, exclusions, constraints and assumptions. Together they document the project boundaries and progressively elaborate the charter and the requirements documentation. Chapter 02 · Project Scope, Requirements and the WBS
- How is float calculated?
- Float is the late start minus the early start, which equals the late finish minus the early finish. It is the time an activity can slip without moving the project end date, and activities with zero float form the critical path. Chapter 03 · Activity Scheduling and the Critical Path
- What are the three cost sub-plans?
- The project cost estimate states the total cost, the time-phased budget spreads that cost over the periods in which work occurs so it can be monitored and controlled, and the cash-flow plan shows when access to funds will be needed. Chapter 04 · Cost Estimates, Contingency and Budgets
- What is the difference between quality and grade?
- Quality is how far a deliverable's inherent characteristics fulfil its requirements, in other words whether it is fit for purpose. Grade, by contrast, is a class of deliverables with the same use but different technical features. A low-grade product can be high quality. Chapter 05 · Quality Planning and the Cost of Quality
- Why does a task not move when its predecessor changes?
- It is probably manually scheduled, so it keeps typed dates and ignores the logic. Changing it, or the default for new projects, to Auto Scheduled makes the software recalculate it from durations and predecessors. Chapter 06 · Building a Project Plan in MS Project
- What does each letter in RACI mean?
- Responsible is the person who does the work, Accountable gives approval and sign-off, Consulted contributes to the work, and Informed must be kept up to date. A RACI chart is one form of the responsibility assignment matrix. Chapter 07 · Human Resource Planning and the RACI Chart
- When is a fixed-price contract the best choice?
- When the scope of work is known and risk is low. The buyer must specify the product or service, its scope and its quality requirements precisely, and payments are usually tied to milestones with penalties or rewards for timing and performance. Chapter 08 · Procurement Planning and Contract Types
- How is risk exposure calculated?
- Where the impact of a risk is quantified financially, it is multiplied by the probability to give the exposure. Summing the exposures of the high-priority risks gives the pre-treatment profile, and repeating the calculation on residual risks gives the post-treatment profile. Chapter 09 · Risk Identification, Assessment and Treatment
- What are the two questions on the power and interest grid?
- Power asks to what extent a stakeholder can affect the project. Interest asks to what extent the stakeholder is impacted by it. The position on the grid decides how much engagement each stakeholder needs and how often. Chapter 10 · Stakeholder Engagement and Communication Plans
- Does Agile reject documentation and planning?
- No. The four values rank individuals and interactions, working product, customer collaboration and responding to change above processes and tools, documentation, contract negotiation and following a plan. The slide is explicit that the lower-ranked side keeps its worth, so documentation and plans still exist in Agile projects. Chapter 11 · Agile Values and the Scrum Framework
- What is the user story template?
- As a [persona], I want to [goal], so that [benefit], followed by acceptance criteria. The want-to part describes intent rather than interface features, and the so-that part explains the overall benefit the user is trying to achieve. Chapter 12 · Product Backlogs, User Stories and Estimation
- How does Scrum track progress without status reports?
- Progress is tracked continuously through the daily scrum and the sprint review, supported by the task board and the sprint burndown chart. Deviations are corrected immediately under the principle of inspect, adapt and learn. Chapter 13 · Sprint Planning and Agile Control in Jira
How to study for the exam
Treat each week as one section of a project management plan and keep a single running case for all of them.
After the Week 2 scope statement and WBS, sequence the same items into a network in Week 3, cost them in Week 4, write their quality criteria, load them into MS Project in Week 5, assign them with a RACI chart and procurement plan in Week 6, register their risks in Week 7 and plan who hears about them in Week 8. Seeing one case flow through every tool shows why each plan depends on the one before.
For the exam, build a short sheet of rules that are easy to reverse: the highest early finish at a merge and the lowest late start at a burst, QA versus QC, one accountable person per row, fixed price for known scope, and transfer versus mitigation. Then rework each calculation in this guide with new numbers, timing yourself against a one-hour paper, and check every answer with the arithmetic test given beside it.
For the Agile weeks, practise writing stories with acceptance criteria and forecasting sprints from velocity, because both feed the Jira assignment and the reflection.
Your AI Project Management tutor for PMGT5871
Stuck on a hard PMGT5871 question? Sia is AskSia’s AI Project Management tutor — ask any PMGT5871 Project Planning 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.