Customize this training

Get a certificate — $15$5

Project Scheduling Fundamentals: PMI-SP Concepts and Primavera P6

Project Scheduling Fundamentals: PMI-SP Concepts and Primavera P6

Build a logic-driven schedule, read the critical path and float, set up and update a project in Primavera P6, and report schedule status the way PMI-SP and GAO best practice expect.

What you will learn

  • Explain what a schedule model is, what the PMI-SP credential covers and what a schedule management plan must define.
  • Build a schedule from the WBS: define activities, link them with the right relationships and estimate durations.
  • Calculate the critical path and float, and check a schedule against recognised quality criteria.
  • Set up a project in Primavera P6: EPS, WBS, calendars, activity types, constraints and scheduling.
  • Load resources, set a baseline and update progress correctly in P6.
  • Analyse variance and schedule risk, communicate status to stakeholders and close out the schedule.

Modules

  1. Scheduling foundations and the PMI-SP
  2. Building the schedule: activities, logic and durations
  3. Critical path, float and schedule quality
  4. Setting up a project in Primavera P6
  5. Resources, baselines and progress updates
  6. Analysis, risk, reporting and closeout

Course facts

Level
Awareness
Estimated study time
about 45 minutes
Final assessment
24 questions · Pass mark 80%
Available in
English, العربية
Price
Free. Optional verifiable certificate: $5
Last updated
Published by
AMAADOR ACADEMY

Who this course is for

Junior planners, site and project engineers, project coordinators and PMP holders in construction, oil and gas, infrastructure and engineering who want a solid base in scheduling before using P6 daily or preparing for PMI-SP.

Prerequisites

None required. Basic project vocabulary helps. Access to Primavera P6 is useful but not needed to follow the course.

Course content

1. Scheduling foundations and the PMI-SP

A project schedule is not a bar chart. The bar chart is only one view. PMI's Practice Standard for Scheduling talks about a schedule model: a dynamic network of activities, durations, logic links, calendars, constraints and resources that a scheduling tool can calculate. When something changes, the model recalculates every date that depends on it.

That is the whole point. A drawn Gantt chart with typed dates cannot tell you what happens to handover if the steel delivery slips two weeks. A logic-driven model can, in seconds.

The five ingredients of a schedule model.

The U.S. Government Accountability Office (GAO) says a reliable schedule has four characteristics in its Schedule Assessment Guide (GAO-16-89G): comprehensive (all the work, resources and durations), well-constructed (complete logic, a valid critical path, reasonable float), credible (traceable and risk-tested) and controlled (updated with real progress and measured against a baseline).

Case: In Completing Crossrail (HC 2106, 3 May 2019), the UK National Audit Office found that delivering by the December 2018 opening date meant many activities ran in parallel, which created vulnerability on the critical path · from 2015 Crossrail Ltd managed the programme against an aspirational plan that it presented as the critical path, but that plan did not adequately reflect interdependencies across the programme · as a result Crossrail Ltd had a gap in its understanding of delivery risks and of the likelihood of opening on time; it only began a detailed, realistic, bottom-up plan in late 2018.

2. Building the schedule: activities, logic and durations

The work breakdown structure (WBS) divides the project scope into deliverables: Building A, then Substructure, Superstructure, MEP, Finishes. The lowest WBS level is the work package. Activities are the actions needed to produce each work package. GAO's first best practice is capturing all activities: if work is in the scope but not in the schedule, the finish date is optimistic by definition.

  1. Decompose — break each work package into activities a supervisor can plan and measure, such as "Pour slab Level 3 Zone B".
  2. Name clearly — verb plus object plus location. "Concrete" is a topic, not an activity.
  3. Size sensibly — many specifications cap activity duration (often around 20 working days, or one or two update periods) so progress can be measured.
  4. Include all work — design, approvals, procurement, fabrication, delivery, construction, testing, commissioning and handover, plus client and authority activities.
  5. Add milestones — zero-duration events such as "Building permit received" or "Mechanical completion".

Do

  • Keep procurement chains: submittal, approval, order, fabricate, deliver.
  • Use activity codes for area, trade and contractor.
  • Agree activity lists with the people who will do the work.

3. Critical path, float and schedule quality

The critical path method (CPM) calculates four dates for every activity. The forward pass runs from the start and gives the early start (ES) and early finish (EF). The backward pass runs from the finish and gives the late finish (LF) and late start (LS).

  1. Forward — EF = ES + duration. A successor's ES is the latest EF of its predecessors.
  2. Backward — LS = LF − duration. A predecessor's LF is the earliest LS of its successors.
  3. Float — total float = LF − EF (or LS − ES).

Worked example, durations in days, all links Finish to Start: A (5) starts the project; B (3) and C (6) both follow A; D (4) follows both B and C.

ActivityDurESEFLSLFTotal float
A505050
B3588113
C65115110
D4111511150

D cannot start until both B (EF 8) and C (EF 11) are done, so its ES is 11, the larger value. On the way back, A's LF is the smaller of B's LS (8) and C's LS (5), so 5. The project takes 15 days and the critical path is A–C–D. B can slip 3 days without delaying the finish.

4. Setting up a project in Primavera P6

Primavera P6 is an enterprise tool: many projects live in one database. Before you add activities, you need to know where your project sits and which data belongs to the whole company and which to your project only.

ElementWhat it isLevel
EPS (Enterprise Project Structure)Folder tree for all projects, e.g. Company / Region / ClientEnterprise
OBS (Organizational Breakdown Structure)Who is responsible; also controls access to EPS nodes and WBS elementsEnterprise
ProjectHolds its WBS, activities, relationships and baselinesProject
WBSDeliverable tree inside the projectProject
Activity codesTags such as Area, Discipline, Contractor for grouping and filteringGlobal, EPS or project
Calendars and resourcesWorking time and the resource dictionaryGlobal or project (calendars); enterprise (resources)
  1. Create the project under the right EPS node, with a planned start and, if required, a must-finish-by date.
  2. Build the WBS to match the schedule management plan.
  3. Create activity codes at the right level: project codes for one job, global codes only if the whole company uses them.
  4. Assign the project calendar and check its working days and holidays.
  5. Add activities under each WBS element, then link them.

5. Resources, baselines and progress updates

A schedule without resources assumes unlimited people and plant. GAO's third best practice is assigning resources to all activities, so the plan can be checked against what the project can actually supply.

P6 resource typeExamplesUnits
LabourSteel fixers, electricians, plannersHours
NonlabourCrane, excavator, concrete pumpHours
MaterialConcrete, rebar, cablem³, tonnes, metres

In P6, Units = Units/Time × Duration. If a rebar crew of 4 works 8 hours a day for 5 days, Units/Time is 32 hours per day and Units is 160 hours. The duration type decides which value P6 holds fixed when you change another:

Duration typeWhat P6 holds constant (Oracle P6 help)
Fixed Duration and Units/TimeDuration stays constant and remaining units change; used for task dependent work and the usual default for new activities
Fixed Duration and UnitsDuration and total units stay constant; units/time (the rate) changes
Fixed UnitsTotal units stay constant; adding resources shortens duration (effort-driven)
Fixed Units/TimeUnits/time stays constant when duration or units change

6. Analysis, risk, reporting and closeout

After each update, the planner answers three questions: where are we, why, and what can we do? Start with the critical and near-critical paths, then the float trend, then earned value if the project uses it.

MeasureFormulaReading
Schedule variance (SV)EV − PVNegative: less work done than planned
Schedule performance index (SPI)EV ÷ PVBelow 1.0: behind plan
Finish varianceBaseline finish vs forecast finishDays late or early on a key date
Float trendTotal float on key milestones, update by updateFalling float warns before the date moves

EV is earned value, PV is planned value. Example: PV = 400,000 and EV = 340,000 gives SV = −60,000 and SPI = 0.85. SPI measures work volume, not the critical path: a project can have SPI near 1.0 while the critical activities are late, so always read both.

When the forecast misses a key date, look at recovery options with the people who will deliver them:

Recovery levers

  • Fast-tracking: overlap activities that were in sequence (more risk of rework).
  • Crashing: add resources or shifts to critical activities (more cost).
  • Change method or sequence, re-zone the work, resolve the blocking issue.

The full lesson continues in the interactive course on this page.

Sources and references

Fundamentals course, not an official exam prep or software training. Not affiliated with, endorsed by or sponsored by PMI or Oracle. PMI-SP and PMI are marks of the Project Management Institute; Primavera P6 is a trademark of Oracle. Check the current PMI-SP exam content outline on pmi.org before you book, and your contract's scheduling specification before you submit a programme.

All courses · Leadership & Professional Skills - Free courses, certificate $5 | AMAADOR ACADEMY