9 minute read · Original practice exercise included
Before you start: Understand scope and finish-to-start dependencies.
Read the lesson Explore tools and references
Next: Cost, budget and finance
Watch this lesson
Schedule
Watch on YouTubeOpen the planning and control playlist
YouTube connects when you play a video or follow its links. Playback depends on the video’s availability on YouTube. Its own privacy and storage practices then apply. Voices are AI-generated.
See the calculation
This extends the A–B–C–D practice question below: A–B–D controls the 12-day finish. It is a separate teaching example from the project described in the transcript.
Scroll sideways to see the full chart. Exact values are available in the chart data below.
Read the chart data
| Activity | Start (day) | Finish (day) | Total float (days) | Critical |
|---|---|---|---|---|
| A | 0 | 3 | 0 | Yes |
| B | 3 | 8 | 0 | Yes |
| C | 3 | 5 | 3 | No |
| D | 8 | 12 | 0 | Yes |
Tools and references for this lesson
Use these resources to practise and extend the topic. Further applications may go beyond the lesson transcript; source pointers lead to the original author or publisher.
Calculators (5)
- Critical-path network calculator
Calculate earliest and latest dates and total float, then draw an activity-on-node (AON) diagram with critical paths highlighted. · Calculator + guide
- Work in progress and cycle time
Relate average work in progress, throughput and time in a stable system. · Calculator + guide
- Completion-rate release estimate
Explore how observed delivery rates change a remaining-work estimate. · Calculator + guide
- Schedule crashing cost slope
Compare additional activity cost per unit of possible duration reduction. · Calculator + guide
- Three-point fixed-path estimate
Combine weighted activity means and approximate variances on one defined path. · Calculator + guide
Conceptual models (2)
- Milestone plan
A milestone marks a verifiable state or decision in delivery. It helps coordinate commitments without pretending to be the detailed schedule. · Guide
- Schedule compression
Schedule compression seeks an earlier finish by changing how critical work is performed, overlapped or resourced. · Guide
Formulas (1)
- Three-point estimation
Use optimistic, most likely and pessimistic estimates to make uncertainty explicit. · Guide
Step-by-step methods (2)
- Find what controls the finish
The critical path is the longest duration chain through a valid dependency network under the schedule’s assumptions. It can change as durations and logic change. · Guide
- Estimate with a range
Discuss distinct scenarios before calculating a weighted average. The explanation for the range is often more useful than the middle number. · Calculator + guide
Further applications (7)
- Analogous and parametric estimating
Use comparable historical work or a defensible quantity-rate relationship to estimate new work. · Guide
- Dependencies and lags
Represent the actual conditions that allow work to begin or finish. · Guide
- Burndown, burnup and scope change
Track completed and remaining work while keeping changes in total scope visible. · Guide
- Cumulative flow and WIP limits
Observe how work accumulates in different workflow states and make overload visible. · Guide
- Estimate maturity and uncertainty
Explain how scope definition, evidence and estimation method affect the confidence in an estimate. · Guide
- Milestone trend analysis
Track how successive forecasts of the same milestone change over time. · Guide
- Software size and effort estimation
Keep product size, team-relative effort and elapsed duration distinct. · Guide
Original framework and research sources (2)
- Reference class forecasting
Challenge an estimate using outcomes from a defensibly comparable class of completed projects. · Source pointer
- Critical chain and constraints
Investigate resource constraints and schedule protection through the originating author’s work. · Source pointer
Check your understanding
A takes 3 days. B (5 days) and C (2 days) follow A. D (4 days) waits for both. What controls completion?
Show answer and reasoning
A–B–D takes 3 + 5 + 4 = 12 days; A–C–D takes 9. The earliest finish is 12 under the stated assumptions. C has 3 days of total float. Resource limits or different dependencies can change this.
Apply the same reasoning to your own example. State one assumption you would need to check.
Chapters
Jump to the corresponding passage in the transcript.
- OpeningWatch on YouTube
- One topic, three lensesWatch on YouTube
- The core in plain wordsWatch on YouTube
- Models and methods: the milestone planWatch on YouTube
- Models and methods: crashing and fast-trackingWatch on YouTube
- Mid-level and SeniorWatch on YouTube
- Exam drillWatch on YouTube
- RecapWatch on YouTube
Study materials
Open the original practice sheet · print or save as PDF

Anki package not yet available.
Key terms
The series’ own explanations. Official sources and edition pointers are below.
- Activity
- A piece of work with a clear end and an owner, taken from a work package. The schedule puts activities in order and in time.
- Dependency
- A link between two activities: finish-to-start, start-to-start, finish-to-finish or start-to-finish. Hard links come from the work, the law or a contract; soft links are a choice.
- Milestone
- A key point or event with no duration, such as the end of a stage. This series names each one as a state reached, with a check and a person who decides.
- Critical path
- The longest chain of dependent activities. It sets the earliest finish, so a delay on it delays the project. Activities off it have float.
- Crashing and fast-tracking
- Two ways to shorten a schedule without cutting scope: add resources to critical activities (it costs money), or overlap activities (it risks rework). PMI®: schedule compression.
- Timebox and release plan
- A timebox is a fixed period, often two weeks, in which the scope flexes. A release plan groups several timeboxes and shows what each should deliver.
About the lesson’s level labels
Levels (this series' labels): Mid-level = moderately complex projects (IPMA Level C, PMI's PMP®); Senior = complex projects and people (IPMA Level B, APM's Chartered Project Professional).
These are the series’ teaching labels, not a declaration that the certifications are equivalent.
Read the transcript
Timed from the episode captions.
Open episode transcript
Sara: Welcome to Project Management Exam Prep.
This episode is about the schedule: what happens when, and what to do when the plan
is too long. Every project management exam tests it.
Leo: You will learn how the three bodies frame it, how activities become a schedule,
how to set milestones, and how to shorten a plan.
We finish with a drill, so keep a pen ready.
Sara: Let us start with the three lenses. What does IPMA® say?
Leo: IPMA®, the International Project Management Association, sets out its standard in
the Individual Competence Baseline, the ICB4.
Its element on this topic is called time.
It asks you to turn work packages into activities, choose stages that fit the uncertainty,
and build, watch and adjust the schedule.
Sara: And PMI®?
Leo: PMI®, the Project Management Institute, publishes the PMBOK® Guide,
its guide to the project management body of knowledge.
The eighth edition has a schedule performance domain.
The outline of PMI®'s Project Management Professional exam, the PMP®,
asks you to plan and manage the schedule: fit it to the delivery approach,
baseline it, and analyse variation.
Sara: And APM?
Leo: APM, the Association for Project Management, publishes the APM Body of Knowledge.
Its section on schedule management runs from a plan on a page to a detailed control
schedule. The syllabus of APM's Project Management Qualification,
the PMQ, asks how links to business as usual affect the schedule,
and why you re-estimate and optimise it.
Sara: Where do the words differ?
Leo: In three places. First, hard and soft links.
PMI® says mandatory and discretionary. APM says logical and preferential,
and adds resource dependencies: two activities that need the same person.
Sara: Second?
Leo: Shortening the plan. PMI® calls it schedule compression, by crashing or fast-tracking.
The ICB4 names crashing. APM's PMQ speaks of schedule optimisation.
Sara: And third?
Leo: The approved schedule. PMI® calls it the schedule baseline.
For APM, it is part of the deployment baseline, the integrated plan agreed before
the work is delivered. The ICB4 says baseline.
Sara: What is the core, whichever exam you take?
Leo: Three ideas. One: activities come from the work packages.
Each work package becomes a few activities, each with an end and an owner.
You estimate each one's effort, duration and people; the episode on estimation covers
the methods.
Sara: Two?
Leo: Activities depend on each other. The usual link is finish-to-start:
training starts when testing ends. Start-to-start lets two activities start together,
and finish-to-finish makes them end together.
Start-to-finish is rare: the old system stops only after the new one starts.
Some links are hard, set by the work, the law or a contract.
Only soft links can change.
Sara: And three?
Leo: The schedule puts it all in time. Link the activities in a network and add the durations.
The longest chain is the critical path.
It sets the earliest finish, so a delay on it moves the end date.
Other activities have float, some room to slip.
Show the result as a Gantt chart, bars on a timeline, and agree it as the baseline.
The calculation has its own episode: Critical path and resource levelling.
Sara: Does that change in agile work?
Leo: Yes. The team works in timeboxes, fixed periods of often two weeks,
and the scope flexes. A release plan groups the timeboxes, often over three to six
months, and shows which features each should deliver.
A hybrid keeps fixed milestones on top, with timeboxes inside.
Sara: Now the models. Both model sheets are free in the description.
What is a milestone?
Leo: A key point or event in the project. PMI®'s guide gives it zero duration,
and APM ties it to accepting a deliverable.
A milestone plan lists the few that matter, with dates, on one page for the sponsor
and the steering group. Detailed schedules sit below it.
Sara: Which milestones go on the page?
Leo: Stage ends, big decisions, and dates you do not control, such as a legal deadline.
Five to eight is enough. Our advice: name each one as a state,
not an activity. Not 'test the system', but 'end-to-end test passed'.
Give it a check, what must be true, and a person who decides that it is reached.
Sara: Why a state?
Leo: Because a state can be checked. An activity can be ninety percent done for weeks.
Sara: And when the schedule is too long?
Leo: First check the gap, and which date is really fixed.
Then there are two classic ways to shorten a plan without cutting scope.
The first is crashing: you add people, overtime or money to activities on the critical
path.
Sara: How do I choose where?
Leo: By the cost per day saved: what you pay extra, divided by the days you gain.
Harold Kerzner, author of a standard project management textbook,
sets the order. Only critical activities count, and the cheapest day comes first.
After each step, check the paths again, because another chain can become critical.
And crashing works only if more people really make the activity faster.
Sara: And the second way?
Leo: Fast-tracking. You overlap activities planned one after the other,
such as training and the last test. It costs little money, but if the test changes
the screens, some training is repeated.
So overlap only soft links, and price the rework.
Sara: Does compression fit agile work?
Leo: Rarely. The timebox is fixed, so the team moves scope instead.
In any approach, there is a third way: a smaller first release,
or a later date, through change control.
The sponsor decides.
Sara: How does this change between Mid-level and Senior?
Leo: First, the two levels. They are this series' own labels.
Mid-level means leading moderately complex projects, the level of IPMA® Level C and
PMI®'s PMP® exam. Senior means leading complex projects and people,
the level of IPMA® Level B and of APM's chartered status, Chartered Project Professional.
At Mid-level, you build and keep one schedule.
Take Parking Permits Online, a city project that moves resident parking permits
online in eight months. The project manager, Anna, gives the steering group five
milestones on one page. Below them, one schedule holds the work,
with the supplier's two-week timeboxes inside.
Sara: And at Senior level?
Leo: You design how others plan. Take One City Account, a thirty-month city project that
brings fourteen online services under one login, in three waves,
led by Anna some years later. The steering board sees one milestone plan,
with dates the city does not control. The national login service takes changes only
once a quarter, and the council election falls in month twenty.
Wave teams plan in timeboxes, and a master schedule joins their plans.
And only the board may move a baseline milestone.
Sara: So Senior is about the system: who decides, and which dates are fixed.
Sara: Now the drill. A city team is moving resident parking permits online,
and go-live must come before January, when most residents renew.
Six weeks before go-live, the forecast is five working days late.
Testing, then training, are on the critical path.
Two extra testers would save three days, for nine thousand euros.
Extra trainers would save two days, for four thousand.
Or training could overlap the last test, saving three days at no cost,
but screens may still change. What do you recommend?
Leo: Pause and write your answer. You have forty-five seconds.
Sara: First, the numbers.
Leo: Divide each extra cost by the days it saves.
Testing costs three thousand a day, and training two thousand.
So crash training first, then testing: five days for thirteen thousand euros.
The overlap saves the same three days as the testers, at no cost.
So it pays only if the expected cost of repeating training is below nine thousand.
Then choose, and say why. For example, crash both, paid from the contingency if
your limit allows, because repeating training weeks before January is the bigger
risk. Recheck the paths after each step.
Keep a fallback: residents can still renew at the service desk.
And tell the steering group this week.
Sara: What lifts that to Senior?
Leo: The date has no tolerance, so the choice is about risk, and the steering group makes
it. Offer three levers: money, overlap, or scope, such as business permits going
live after January. Ask why it slipped: other estimates may be low too.
Watch service-desk staff, who learn the new system while running the daily service.
And ask for a time buffer before go-live in the new baseline.
Sara: How do the exams ask this?
Leo: IPMA®'s written exam asks for open answers; at Level B it may be oral.
IPMA®'s certification also includes an interview, where assessors ask about your
own projects, so note one schedule you shortened.
The PMP® exam uses scenarios, and questions built on a case study or a chart:
practise reading a Gantt chart. APM's PMQ asks for short written answers,
such as why you re-estimate a schedule.
Sara: Let us recap.
Leo: One. Activities come from the work packages, each with an estimate.
Sara: Two. Links come in four kinds. Only soft links can change.
Leo: Three. The critical path sets the finish.
Milestones are states, with a check and a decider.
Sara: Four. To shorten a plan, crash the cheapest critical day first,
or overlap soft links and price the rework.
Leo: And five. In agile work, timeboxes fix the time, and a release plan shows what each
delivers.
Sara: The model sheets and the study handout are linked in the description.
Next time: cost, budget and finance.
Sources & further reading
Consult the original publications and authoritative references below. For certification requirements, use the current official documents. Edition-specific page references are included only when verified.
- IPMA® (2015). Individual Competence Baseline for Project, Programme and Portfolio Management, Version 4.0 (ICB4). Zurich: International Project Management Association. ISBN 978-94-92338-00-6 (print), 978-94-92338-01-3 (pdf). Free PDF from IPMA®: https://ipma.world/ipma-standards-development-programme/icb4/
- Project Management Institute (2025). A Guide to the Project Management Body of Knowledge (PMBOK® Guide), Eighth Edition, and The Standard for Project Management. Newtown Square, PA: PMI®. ISBN 9781628258295.
- Project Management Institute (2026). Project Management Professional (PMP®)® Examination Content Outline – 2026 (July 2026 exam update). Newtown Square, PA: PMI®. PDF on pmi.org, accessed 26 September 2026.
- Association for Project Management (2025). APM Body of Knowledge, 8th edition. Princes Risborough: APM. ISBN 9781913305390.
- Association for Project Management (2024, version 6 of April 2026). APM Project Management Qualification: Handbook. https://www.apm.org.uk/media/3r4jbodr/apm-project-management-qualification-handbook.pdf, and the PMQ page https://www.apm.org.uk/qualifications-and-training/project-management-qualification/, accessed 26 September 2026.
- IPMA® (2025). IPMA® International Certification Regulations (Public), Version 4.4, for the Assessment of Individuals in Project, Program & Portfolio Management. Zurich: International Project Management Association. https://ipma.world/app/uploads/2025/11/IPMA®-ICR-2025_v_4.4_digital.pdf, via https://ipma.world/ipma-certification/ipma-international-certification-regulations/, accessed 26 September 2026.
- Kerzner, H. (2013). Project Management: A Systems Approach to Planning, Scheduling, and Controlling, 11th ed. Hoboken, NJ: Wiley. ISBN 9781118022276.
Original and technical references for the related tools
- Kelley & Walker (1959): Critical-Path Planning and Scheduling
James E. Kelley Jr. and Morgan R. Walker; originating critical-path publication.
- GAO: Schedule Assessment Guide
Common scheduling practice. The critical-path method is associated with James E. Kelley Jr. and Morgan R. Walker; their 1959 paper is the historical reference.
- Malcolm, Roseboom, Clark & Fazar (1959): PERT
D. G. Malcolm, J. H. Roseboom, C. E. Clark and W. Fazar, Application of a Technique for Research and Development Program Evaluation (1959). This calculator uses a simplified fixed-path approximation, not the entire original procedure.
- John D. C. Little (1961): original proof
John D. C. Little, A Proof for the Queuing Formula: L = λW (1961).
- GAO: Cost Estimating and Assessment Guide
Standard estimating practice; the cited guide documents use rather than claiming invention.