PMGT1865 Project Time, Cost and Resources
PMGT1865 Overview
- The University of Sydney
- Semester 2, 2026
- Level 1, 6 credit points
- Blended, two hour weekly workshops
- Six weighted assessment components
PMGT1865 Project Time, Cost and Resources is a first year, six credit point unit taught at the University of Sydney by its School of Project Management.
- Assessed by Class participation, a one per cent early feedback task in Week 3, an individual case study report of about 3,500 words, a group project plan, a group presentation and a two hour final quiz sat in the workshop in Week 13.
- Where the weight sits The group project plan and the group presentation together carry 40 per cent and both land in the same fortnight at the end of semester, so group formation in the first weeks matters more than it looks.
- Hardest step Carrying one project through every method in order, so that the network, the resource plan, the budget and the earned value report all describe the same work with the same identifiers.
- How to prepare Work one small project of your own invention through every method by hand. Almost nothing here is recall: each task gives you a table and asks for a number and then for what the number means.
How PMGT1865 is assessed
| Component | Weight | Format |
|---|---|---|
| Class and online participation | 9% | Marks awarded for participation in discussions across multiple weeks, alongside an attendance check |
| Early feedback task | 1% | A short individual submission built from the in class activities of Weeks 2 and 3, due Week 3 (23 August 2026) |
| Individual assignment | 20% | A case study worked up into an individual report of about 3,500 words, due Week 8 (20 September 2026). The unit's own course schedule places this on the Week 7 row, so confirm the week for your session |
| Group assignment | 15% | Project plans developed for a set case study, in groups of five, about 3,500 words, due Week 12 (1 November 2026) |
| Group presentation | 25% | The group presents its project and answers questions, 10 to 20 minutes. The unit outline records a Week 12 deadline while the course schedule runs presentations across Weeks 11 and 12, so your session and group number decide which |
| Final quiz | 30% | An in person written or creative task of two hours, sat during your own workshop in Week 13. Generative AI is prohibited for this component |
The six weights come from the University's unit outline for the Semester 2, 2026 offering and are repeated on the unit's own assessment page; they sum to exactly 100 per cent. The hurdle column carries a sentence rather than a flag because the word hurdle appears nowhere in either source, and an absence of a statement is not a published rule either way. Attendance is a published pass condition sitting outside this table: the outline sets a minimum of 85% of timetabled activities, with exceptions granted only by the Dean or the Head of School, and says that failing to meet the minimum attendance requirement may result in a fail grade; the unit's Canvas introduction page states 90% instead, so plan to the stricter figure. Two due dates also differ between sources and both are flagged in the dates table. Confirm all of it, and your own group allocation, on the unit's assessment page.
Current PMGT1865 dates
| Date | Item | Control |
|---|---|---|
| 23 August 2026, 23:59 | Early feedback task due | Week 3, built from the Week 2 and Week 3 activities |
| 20 September 2026, 23:59 | Individual assignment due | Week 8 in the unit outline; the course schedule shows it on the Week 7 row |
| Weeks 11 and 12 | Group presentations | Your session and group number decide which week you present |
| 1 November 2026, 23:59 | Group assignment due | Week 12 |
| Week 13 | Final quiz | Two hours, sat in your own workshop; generative AI prohibited |
Dates are as published in the University's published unit outline for the Semester 2, 2026 offering. Confirm exact deadlines and submission settings in the live LMS.
What PMGT1865 covers
PMGT1865 organises itself into three topics, Time, Cost and Resource, taught across ten workshop weeks. This guide follows the teaching order instead, because each method is built out of the one before it: the network needs the work breakdown structure, the passes need the network, the probability work needs the passes, resource levelling needs the float, and earned value needs the time phased budget.
Assessment is six weighted components with no final examination, ending in a two hour quiz sat in the workshop in Week 13.
Project Planning, Life Cycles and Project Scope
Five phase life cycle, ten knowledge areas, planning in different contexts, product and project scope, scope creep and the scope statement (Week 1)Week 1 sets the vocabulary every later calculation assumes.
- A project as coordinated activities producing a unique product, service or result, and what a methodology adds to that
- The five phase life cycle: initiating, planning, executing, monitoring and controlling, and closing
- What each phase hands the next, and why the fifth runs alongside the third rather than after it
- The two curves under the life cycle: resource commitment per period, and the rising cost of a change
- The ten knowledge areas, and the four this unit works inside
- How the process group and knowledge area grid relates to the newer performance domains
Building a Work Breakdown Structure
Deliverable oriented decomposition, indented list and tree formats, the level ladder to work package and activity, five structural rules, and how far to decompose (Week 2)A work breakdown structure takes everything the project team has to execute and splits it, level by level, into deliverables inside deliverables.
- Decomposition as a definition exercise, and why working downwards makes completeness structural
- The two formats: an indented list and a tree, carrying identical information
- Grouping a flat list into sub-categories, and the four ways a top level can legitimately be organised
- Why chronology and resources belong to the schedule and the responsibility matrix rather than here
- The level ladder: phase or deliverable, control account, work package, activity, task
- Which level a budget attaches to, and which level becomes a network node
Sequencing Activities into a Precedence Network
The five step schedule process, node anatomy, placement rules, merge and burst activities, and duration against effort based estimating (Week 2)Fixing the dependencies and then building the schedule are the two steps that convert a bare task list into a timeline somebody can work to.
- Dependency as a claim about what physically or contractually stops work starting sooner
- The four factors that cap how fast a project can go, including resource availability at a specific point
- The five step process, and why activity resources are estimated before activity durations
- Step one: selecting a planning level and assigning unique identifiers from the breakdown
- The six cell node, which cells are given and which are computed
- Why networks run on elapsed working periods counted from zero rather than on calendar dates
Forward Pass, Backward Pass and the Critical Path
The two passes and their choice rules, float as late start minus early start, free against total float, and diagnosing a pass that will not close (Week 2)Step five of the schedule process is six moves long: transfer the durations onto the network, run the forward pass, run the backward pass, calculate float on every activity, determine the critical path, and convert the result into a chart.
- The three lines of arithmetic every schedule question in the unit reduces to
- The vocabulary this chapter is graded on: dependencies, milestones, float, critical activities, critical path
- The forward pass, and the highest early finish rule at a merge
- The backward pass, and the lowest late start rule at a burst
- Why the last node's late finish is seeded with its early finish, and what a different seed would mean
- Float computed two ways, and what a disagreement between them reveals
Schedule Formats, Gantt Charts and Planning Software
Schedule table, milestone chart, network and bar chart compared, drawing float on a bar, the three stated limitations, and what planning software automates (Weeks 2 and 8)Once both passes are done you hold a complete schedule. What you do not hold is anything somebody outside the project will read.
- Four schedule formats, what each is best at, and what each discards
- Placing the formats on two axes: how readable they are and how much logic they show
- Matching the format to the decision the reader is about to make
- Why the schedule table is the format everything else is generated from
- Building a bar chart from the forward pass, one bar per activity at its early start
- Drawing float as an extension to the late finish, and why that is what makes the chart usable
Overlapping Relationships and Link Lag
Finish to start, start to start, finish to finish and start to finish, the compound link, link lag against lead time, and the four forward pass rules (Week 3)Everything up to Week 3 assumed a finish to start world in which nothing may begin until the activity in front of it has finished entirely. That assumption was made to keep the critical path method simple, and real projects break it constantly.
- Why overlapping is drawn: shorter schedules, earlier resource deployment, visible concurrency
- Overlap as a claim about the work, and the physical reason that has to sit beside every one
- Finish to start, start to start, finish to finish and start to finish, and what each constrains
- The compound link, and the pairing this unit takes as its default
- Link lag as a measured gap after the forward pass, and the formula that defines it
- Lead or lag time as a planner's input, and why the two are confused on simple chains
Float and the Critical Path in Overlapped Schedules
Free and total float computed from lags, end against terminal activities, the notional finish node, the validity check, and redundant links (Week 3)In a finish to start network, float is late start minus early start and the last activity sets the duration. Both statements weaken once links can attach to starts as well as finishes.
- Free float as the minimum lag on the outgoing links, and what it protects
- Total float as the minimum of lag plus the successor's total float, rolled back from the finish
- Why total float is shared along a chain and free float is not, and which one a decision needs
- End activities against terminal activities, and why they diverge once links overlap
- The notional finish node, and how it honours the no dead ends rule
- The four stage procedure: forward pass, terminal activity, lags, floats, path
Three Point Estimating and Expected Duration
Deterministic against probabilistic, the beta assumption, optimistic, most likely and pessimistic estimates, the weighted mean and standard deviation, and expected project duration (Week 4)The programme evaluation and review technique is a statistical tool for analysing and representing the tasks in a project, developed in parallel with the critical path method from the late 1950s.
- Deterministic against probabilistic, and what each technique is actually able to answer
- The stated advantages, including usefulness where there is little or no previous schedule data
- The stated disadvantages, including subjective time analysis and the cost of maintaining the diagram
- Why the beta distribution is assumed at activity level and a normal distribution at path level
- The three estimates, and the one in a hundred rule that stops the range collapsing
- Why the most likely value is not the mean, and what the weighting in the formula is doing
Probability of Completion and Target Dates
Project variance as a root sum of squares, the Z statistic, reading the normal table including negative values, and scheduling for a chosen confidence (Week 4)An expected project duration on its own is a single number with the uncertainty stripped back out of it, which is precisely what three point estimating existed to avoid.
- Steps four and five: variances on the critical activities, and the root of their sum
- Why variances add and standard deviations do not, and what adding deviations costs
- Why only the critical path enters the sum, and where that simplification is unsafe
- The Z statistic, and reading its sign before reading the table
- The probability as an area under the curve to the left of a target date
- Reading a two decimal Z, and using symmetry for a negative one
Estimating Project Resources
Consumed against applied resources, the three step resource plan, deterministic and probabilistic method families, and parametric, analogous and bottom-up estimating (Week 5)Project resources fall into four groups, people, technology, materials and consumables, and financial, and a distinction cuts across all four: some resources are consumed and gone, while others are applied and available again afterwards.
- Four resource types, and the consumed against applied distinction that cuts across them
- Why a timetable drawn without asking who will do the work is rarely deliverable
- Resource management defined in four verbs, and its inputs, tools and outputs
- The three step sequence, and why the third step is the one with a lead time attached
- Deterministic against probabilistic families, and what each assumes about risk
- The seven deterministic methods and the three probabilistic ones, and choosing by available information
Resource Levelling, Smoothing and Utilisation
Why time schedules over promise, unlimited against limited levelling, the seven step trial and error method, the utilisation factor, and the three costs of levelling (Week 5)A time schedule assumes resources are unlimited and can be allocated whenever needed.
- Why time schedules over promise, and the two failures the assumption produces
- The four conditions efficient resource use requires, and what each one rules out
- Levelling as a rearrangement bounded by the float already in the schedule
- Unlimited against limited levelling, and which quantity each holds constant
- How the two approaches map onto the words levelling and smoothing
- Why heuristics displaced linear programming, and what a heuristic does not guarantee
Roles, Responsibilities and the RACI Matrix
The nine elements of a human resource plan, its five sub-plans, seven organisational structures, and the matrix where work and organisation intersect (Week 5)Managing the human side of a project means organising, directing and leading the people doing the work, and the team is defined widely: everyone who contributes to the project work, including internal staff, contract staff, suppliers and volunteers.
- Who the project team includes, and why suppliers and volunteers have to appear in the plan
- The nine elements of a human resource plan, and the verb most projects forget
- The five sub-plans, and where each one surfaces elsewhere in this guide
- Why the make, team or buy plan is filed with the people plan rather than with procurement
- The organisation breakdown structure and the two directions of reporting clarity it produces
- Seven organisational structures ordered by where project authority actually sits
Cost Estimation and the Project Cost Estimate
The four objectives of cost management, three cost documents, direct, indirect and contingency layers, the two reserves, bid price, and the five accuracy classes (Week 7)Cost management on a project covers estimating, budgeting, financing, funding, managing and controlling what gets spent, with the object of finishing inside the approved figure, and its four stated objectives all tie cost to something outside cost: the business case, the schedule and resourcing plan, the scope, and the financial viability review that follows any change to the estimates.
- The four objectives of cost management, and what they all have in common
- Three cost documents and the three questions they answer
- The estimate costs process, covering labour, materials, equipment, facilities and services
- Why estimates are reviewed and refined as the project progresses
- Direct, indirect and contingency layers, and where profit sits relative to them
- Fixed against variable components inside the direct costs
Time Phased Budgets and Cash Flow
The determine budget process, the two budget identities, funding limit reconciliation, proportional spreading and the goods rule, and cash flow with a running balance (Week 7)Setting the budget means rolling the estimated costs of each activity, or of each work package, up into one authorised project budget, and the word authorised matters: a budget is an estimate somebody has approved and against which performance will be measured.
- The determine budget process, its five inputs and its three distinct outputs
- Why the schedule is an input to a budget rather than an output of one
- The two budget identities, and which reserve sits inside the baseline and which outside
- Funding limit reconciliation, and why it binds on every period rather than on the total
- The five steps for building a time phased budget
- Proportional spreading for activities that straddle periods
Procurement Planning and Contract Types
Make, team or buy, the procurement schedule and its seven columns, the four procurement processes, the six essential elements of a contract, and three contract types (Week 9)Procurement means getting hold of goods or services, whether by purchase or otherwise.
- Procurement management defined, and the two reasons a project buys rather than builds
- Make, team or buy, and how the decision cascades into four other plans
- Why buying changes who you argue with rather than removing the work
- The procurement plan and schedule, and the source of each of its seven columns
- Why the evaluation criteria column is filled before the market is approached
- The four processes: planning, conducting, administering and closing procurements
Earned Value Measurement and Forecasting
Planned value, earned value and actual cost, the two variances and their signs, what schedule variance cannot tell you, the indices, and forecasting the finish (Week 10)Earned value management is a way of taking the measure of a project, reporting where it stands, and projecting where it will end up from how it has behaved so far.
- The three comparisons the method rests on, and the four defined quantities
- Earned value priced at budget rather than at actual cost, and why that is the whole idea
- Planned value as the cumulative cost baseline, and what a straight baseline does to the numbers
- Cost variance and schedule variance, both computed from earned value, both negative when unfavourable
- Why schedule variance is expressed in money rather than in time
- Seven things schedule variance does not address, including the critical path
It teaches the tools and methods project managers use to balance the three quantities in its title: breaking work down, planning to milestones, building and calculating schedules, tracking performance against a baseline, costing the work, calculating a budget, planning the people and plant, and buying in what the team will not build.
The framing throughout is the traditional waterfall tradition, using the Project Management Body of Knowledge as its map, and the unit works through it as a single continuous method rather than as ten separate topics. The unit is unusual for a first year unit in how little of it is recall.
Almost every assessable task hands you a table of activities, durations, estimates or costs and asks you to produce a number, then to say what that number means for a decision about the schedule, the budget or the resource plan.
Four of the eight learning outcomes begin with a verb that produces a quantity: develop a precedence network and determine the critical path, determine the work effort of activities, cost the work and calculate a budget, and work out what a given risk would do to the dates, the spending and the staffing.
Delivery is blended: students read and watch material before class, then attend a two hour workshop each week where the methods are worked on a running case study, with six to eight hours of self study expected alongside. Attendance is a published pass condition that sits outside the assessment table.
The University's unit outline for this offering states that students are expected to attend a minimum of 85% of timetabled activities, that exceptions may be granted only by the Dean or the Head of School, and that failure to meet the minimum attendance requirement may result in a fail grade; it also allows additional assessment items to be set where the attendance requirement differs from 85%.
The unit's own Canvas introduction page instead states a minimum of 90%. Both figures are published by the University and this guide does not choose between them: plan to the stricter one and confirm which applies to your session. Assessment is six weighted components summing to 100 per cent, with no final examination.
Written work submitted late loses five per cent of the maximum mark per calendar day and scores zero after ten calendar days, and applications for special consideration must be submitted within three working days of the due date.
Worked example · free
Reading a critical path, and answering the question behind it
- +1Forward pass from the start. A runs 0 to 4. B, C and E all start at 4 and finish at 10, 12 and 14 respectively.
- +1Resolve the first merge. D waits for both B and C, so it takes the higher early finish, 12 from C, and runs 12 to 17.
- +1Resolve the second merge. F waits for D at 17 and E at 14, takes 17, and runs 17 to 20. G then runs 20 to 22, so the project duration is 22 working days.
- +1Backward pass. G is 20 to 22, F is 17 to 20, D is 12 to 17, E is 7 to 17, B is 6 to 12 and C is 4 to 12. A takes the lowest successor late start, which is 4 from C, so A is 0 to 4 and its late start returns to zero.
- +1Float is late start minus early start: A 0, B 2, C 0, D 0, E 3, F 0, G 0. The connected chain of zero float activities is A, C, D, F, G, and 4 plus 8 plus 5 plus 3 plus 2 is 22, matching the forward pass.
Key terms
- Work breakdown structure
- A structure that takes everything the project team has to execute and splits it, level by level, into deliverables sitting inside deliverables. It defines scope in operational terms and must capture everything the project plans to do and everything it plans to buy, because the schedule, the budget and the resource plan are all built on top of it.
- Float
- How long an activity can sit idle before the whole job finishes later than promised. It is computed as late start minus early start once both passes are complete, and an activity with zero float is critical.
- Critical path
- The connected chain of activities that carry no float, running from the start of the network to the activity that determines the project duration. Delaying any one of them delays the whole project by the same amount.
- Link lag
- The gap between the early finish of a preceding activity and the early start of the one that follows it. It is measured after the forward pass rather than set in advance, and in an overlapped network the floats are computed from it.
- Expected duration
- The weighted mean of three estimates, counting the most likely value four times and each extreme once over six shares. It differs from the most likely value whenever the estimates are skewed, which for activity durations is almost always.
- Resource levelling
- Reshuffling work inside available float so that busy days flatten and quiet days fill. It buys a lower peak with the schedule's remaining slack, so a levelled plan uses its crew efficiently and absorbs future delay poorly.
- Responsibility assignment matrix
- The intersection of the work breakdown structure and the organisation breakdown structure, defining who is responsible for each item of work. In its RACI form it also records who approves, who contributes and who is kept informed.
- Contingency
- Funds held for work the project has already agreed to going worse than planned, such as activities running long. It is split into project contingency for known unknowns and management reserve for unknown unknowns, and it is never a funding source for new scope.
- Cost baseline
- The time phased direct cost of the project, built by allocating each activity's estimated cost to the period in which it occurs. It is the curve that performance is measured against once the work starts.
- Earned value
- The value of completed work expressed in the budget assigned to it, computed as percent complete multiplied by the budget allocated. It is always priced at planned cost rather than at actual cost, which is what allows a cost variance to exist at all.
PMGT1865 FAQ
Is Project Time, Cost and Resources a hard first year unit?
It is not conceptually difficult and it is unforgiving of carelessness. Very little of it is recall: each week hands you a table and asks for a quantity, and a single reversed subtraction or a factor applied the wrong way round propagates through everything downstream.
Students who work the methods by hand on a project of their own tend to find it manageable, while those who read worked solutions without reproducing them tend to discover in Week 13 that recognising a method is not the same as being able to run one.
The other demand is administrative rather than intellectual: two of the six components are group work and both land in the same fortnight, so the semester has to be planned, not merely attended.
Is there a final examination, and what is the quiz?
There is no formal examination in the University's examination period. The largest single component is a two hour in person written or creative task called the final quiz, worth 30 per cent, sat during your own workshop in the final teaching week.
It is the one component for which generative AI is prohibited, and because it is run in the workshop rather than centrally timetabled, the room and time are your usual class rather than an examination venue. Confirm the arrangements for your own session on the unit's assessment page.
Where are the weightings published, and is anything a hurdle?
The six weights appear in the University's unit outline for the offering and are repeated on the unit's own assessment page, and they sum to exactly 100 per cent. The word hurdle does not appear in either source, so this guide records a sentence rather than a flag against each component: an absence of a statement is not a published rule in either direction.
Attendance is a published pass condition that sits outside the assessment table.
The University's unit outline for this offering states that students are expected to attend a minimum of 85% of timetabled activities, that exceptions may be granted only by the Dean or the Head of School, and that failure to meet the minimum attendance requirement may result in a fail grade; it also allows additional assessment items to be set where the attendance requirement differs from 85%.
The unit's own Canvas introduction page instead states a minimum of 90%. Both figures are published by the University and this guide does not choose between them: plan to the stricter one and confirm which applies to your session.
What is the difference between the critical path method and three point estimating?
They are the same technique run on different kinds of number. The critical path method is deterministic: each activity carries one duration treated as known, and the answer is a date. Three point estimating is probabilistic: each activity carries an optimistic, a most likely and a pessimistic estimate, from which a weighted mean and a standard deviation are computed, and the answer is a date together with a confidence in it.
Everything else, the network, the two passes, the merge and burst rules and the float subtraction, is identical. The practical consequence is that three point estimating is useful even where there is little or no previous schedule data, which is exactly the situation a single point estimate handles worst.
Why can resource levelling make a schedule worse?
Because it pays for a lower resource peak with the schedule's remaining slack. Levelling pushes activities that are not critical into their own spare time and away from the busy periods, and an activity that has spent all of its float is critical in resource terms even if it still looks free in time terms.
Three consequences follow: the amount of float in the schedule falls, work shifts towards the end of the project where coordination is hardest, and every activity acquires a fixed start and finish it must hold or the demand goes out of balance with the committed crew. The trade off is real and it should be stated rather than hidden, especially where the risk of overrun is high.
What can earned value not tell me?
Quite a lot, and the list is examinable. A schedule variance is measured in money, not in time, so it cannot say how many days late a project is. It does not address the sequence of the work, the importance of the work or the critical path, it does not identify whether the variance came from labour or from materials, and it does not indicate what recovering the slippage would cost.
What it does very well is act as an early warning: it reports that something is behind or overspent, quantitatively and without bias, and prompts you to go back to the network to find out whether it matters.
How may generative AI be used in this unit?
The unit outline marks it as allowed for the participation task, the early feedback task, both assignments and the presentation, and prohibited for the final quiz.
Where it is allowed, five responsibilities apply: you take full responsibility for everything you submit, you acknowledge any use including the tool names and their purpose, the submission must reflect your own independent thinking, use is optional, and it should support or extend your thinking rather than replace it.
The acknowledgement goes in a short endnote or footnote of two or three sentences and is not counted in the word limit. Unapproved use, or use that is not acknowledged, is treated as a breach of academic integrity.
Questions students ask in each PMGT1865 chapter
- Which phase do students most often leave out when listing the five?
- Monitoring and controlling, because it runs alongside execution rather than after it and so does not feel like a stage. It is also the phase this unit finishes on: earned value management is monitoring and controlling expressed as arithmetic. If you can only hold four in your head, make the fifth the one that compares plan against reality while there is still time to act on the difference. Chapter 01 · Project Planning, Life Cycles and Project Scope
- Should the top level be organised by phase or by deliverable?
- Either, and two other options as well. It does not matter how the top level is structured provided the five rules hold, so phase, deliverable, technical domain, cost account and supplier are all legitimate. Choose the one the people doing the work already think in, because a structure that matches how a team talks gets maintained and one that does not gets abandoned. The only common trap is grouping by time, which duplicates the schedule and cannot carry a budget. Chapter 02 · Building a Work Breakdown Structure
- How do I tell a real dependency from a preference?
- Ask what physically or contractually stops the second activity starting sooner. If two activities could genuinely run at the same time given the people available, they are parallel, and drawing them in series invents a longer project and hides the real critical path. The most common source of false dependencies is the resource plan: two activities linked because the same person does both is a resource constraint, and it belongs in the levelling chapter rather than in the logic. Chapter 03 · Sequencing Activities into a Precedence Network
- What does it mean if the first node's late start does not come back to zero?
- One of two things, and both are local. Either a merge or a burst was resolved with the wrong rule, which is the more common cause, or a duration was used inconsistently between the two passes. Stop and find it before filling in any float, because every number after the error inherits it. Recheck every node with more than one arrow first, then compare the durations cell by cell against the source table. Chapter 04 · Forward Pass, Backward Pass and the Critical Path
- Which format should I hand to which reader?
- Match it to the decision they are about to make. A sponsor at a stage gate needs a milestone chart, because the question is whether to release the next tranche. A work package owner needs a bar chart filtered to their branch, because the question is what to do this fortnight. A planner assessing a change needs the network with float, because that question is about slack and slack lives in the logic. A marker or an auditor needs the table, because that is the only form in which every number can be traced to the one before it. Chapter 05 · Schedule Formats, Gantt Charts and Planning Software
- What is the difference between lead time and link lag?
- One is an input and one is an output. Lead or lag time is the offset a planner writes on the link before any pass, either because the work forces a wait or because the successor is being deliberately delayed. Link lag is computed afterwards from the calculated dates, as the successor's early start minus the predecessor's early finish. They can carry the same value on a simple chain, which is exactly why they get confused. Label the diagram so a reader can tell which is which. Chapter 06 · Overlapping Relationships and Link Lag
- Why can I not just use late start minus early start here?
- Because that subtraction is correct in a pure finish to start network and stops being equivalent as soon as a link attaches to a start rather than a finish. In an overlapped schedule float is built from lags, and the two approaches diverge. Using the familiar subtraction on an overlapped network is the single most common way this question is answered confidently and wrongly, because it produces numbers that look reasonable and are not. Chapter 07 · Float and the Critical Path in Overlapped Schedules
- Why is the most likely value multiplied by four?
- Because the formula is a weighted average over six shares in which the middle estimate carries most of the information and the two extremes still pull the answer towards whichever side has the longer tail. On a symmetric set of estimates the formula returns the most likely value exactly; on a skewed set it returns something between the most likely and the pessimistic value, which is the behaviour you want when work can run late by more than it can run early. Chapter 08 · Three Point Estimating and Expected Duration
- What happens if I add the standard deviations instead of the variances?
- The spread roughly doubles and every probability is dragged towards fifty per cent. In the worked example the five deviations sum to 4.167 while the correct project deviation is 2.193, barely half of that. It is the single most expensive error in this material because it produces a number that looks entirely reasonable, and the only defence is the habit of squaring first, adding second and taking the root last. Chapter 09 · Probability of Completion and Target Dates
- Which estimating method should I use?
- Whichever the information you hold supports, since the methods are not ranked. Parametric needs a productivity rate. Analogous needs a genuinely comparable past project. Bottom-up needs a complete decomposed breakdown. Vendor bid analysis needs a market and historical data needs records. If you have none of those, expert judgement or a structured process such as Delphi is not a cop out but the only honest option, and saying so is a stronger answer than inventing a rate you cannot source. Chapter 10 · Estimating Project Resources
- Why is the utilisation factor computed before the move rather than only after it?
- Because the method uses it to evaluate alternatives rather than to report a result. A histogram can look better after a rearrangement and be worse: spreading a spike across two extra days at a slightly higher baseline raises the average without lowering the peak, and the peak is what determines the crew you have to carry. The factor forces both numbers into a single figure, which is why step six sits between plotting the histogram and moving anything. Chapter 11 · Resource Levelling, Smoothing and Utilisation
- Why can there only be one accountable entry per row?
- Because accountability is the right to approve, and two people who can both approve means neither has to. The sign off can then be claimed by either and owned by neither, which is precisely the situation the letter exists to prevent. If a row genuinely needs two approvals, the work package is really two packages, and the fix belongs back in the decomposition rather than in the matrix. Chapter 12 · Roles, Responsibilities and the RACI Matrix
- Can contingency be used to fund extra scope?
- No, and this is the substantive judgement question in the topic. Contingency covers work the project already agreed to going worse than expected, such as activities running longer or issues arising. New scope is a change and is funded as one, with its own approval. Spending contingency on new work quietly removes the cover for risks that have not yet been retired, and it does so invisibly, because the total looks unchanged right up until the moment the retained risk actually occurs. Chapter 13 · Cost Estimation and the Project Cost Estimate
- Why do the two allocation rules contradict each other?
- Because they track different things. Labour is spread across the periods the activity occupies, since that is when the effort happens. Materials are lumped into the period of receipt, even if the activity consuming them runs for weeks afterwards, because that is when the commitment lands. Applying the proportional rule to a delivery is the commonest way a phased budget comes out smooth and wrong, since it hides the single largest step in the curve. Chapter 14 · Time Phased Budgets and Cash Flow
- Why is over specification a legal problem rather than just an inefficiency?
- Because it narrows what you are lawfully able to accept. The golden rule is to describe the need rather than over specify the solution: if you tender for one thing you may not accept an offer for something else, or even for that thing plus extras. Competition only produces better answers if suppliers are free to propose them, so describing the outcome and the constraints leaves the market room while describing the solution reduces it to whoever can build your drawing. Chapter 15 · Procurement Planning and Contract Types
- Why is earned value priced at budget rather than at what the work actually cost?
- Because pricing it at actual cost would make earned value and actual cost identical, every cost variance would be zero, and the method would report that no project has ever overrun. Valuing completed work at what you said it would cost is what creates the gap that a cost variance measures. It is the least intuitive idea in the topic and the one everything else depends on. Chapter 16 · Earned Value Measurement and Forecasting
How to prepare for the assessments
Treat this unit as one continuous method rather than ten topics, and carry a single project of your own invention through all of it. Ten or so activities is enough.
Draw its work breakdown structure, sequence it into a network, pass it forwards and backwards, put an overlapping relationship on two of its links and recompute, replace the durations with three point estimates, level one resource across it, price it, phase the budget across three periods, and then report it at the halfway point with earned value.
Every join between chapters becomes visible when the same project has to survive all of them, and the joins are where the assessment questions live.
Work the arithmetic by hand and never by reading, because the errors this unit punishes are procedural: a merge resolved with the lowest rather than the highest early finish, an efficiency factor multiplied instead of divided, standard deviations added instead of variances, a subtraction reversed in an earned value calculation. Each of those produces a plausible number, which is the expensive kind of mistake.
Build the habit of running the checks the methods already give you: the backward pass must return the first node to zero, the durations along the critical path must sum to the project duration, the phased budget periods must reconcile to the cost baseline. Each takes seconds and each converts a wrong answer into a corrected one.
Keep one page of the unit's own numbers, since the weightings, the late penalty, the three working day window for special consideration, the five accuracy classes and the RACI letters are what make an answer specific rather than generic. Finally, practise the second half of every question.
Almost every task here is a calculation followed by an interpretation, and the interpretation carries roughly a third of the marks: say what the number tells a project manager to do differently, and name what the method cannot see.
When something will not stick, ask Sia to explain it a different way and to set you a fresh version of the same calculation to work; it teaches the method and checks your reasoning, and it never substitutes for your own graded work. Confirm your semester's dates and weightings on the unit's own pages in your first week.
Your AI Project Management tutor for PMGT1865
Stuck on a hard PMGT1865 question? Sia is AskSia’s AI Project Management tutor — ask any PMGT1865 Project Time, Cost and Resources 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.