Day 1: Building Scope That Can Be Scheduled

Work Breakdown Structure (WBS)

• Break deliverables into manageable work packages
• Apply complete scope coverage without duplication
• Choose level of detail for control
• Build WBS for a representative project

From Work Package to Activity

• Identify activities to produce each deliverable
• Define verifiable starts and finishes
• Avoid activities too long to measure
• Convert work package into activity list

Milestones and Progress Rules

• Choose milestones tied to acceptance/decisions
• Define progress measurement rules for activities
• Prevent unsupported estimated completion percentages
• Prepare a milestone and progress dictionary

Day 2: Schedule Network and Critical Path

Schedule Relationship Logic

• Define dependencies reflecting execution reality
• Use relationship types with professional restraint
• Avoid hard constraints that hide logic
• Build an interconnected schedule network

Estimating Activity Durations

• Use productivity quantity and historical evidence
• Record assumptions underlying estimates
• Distinguish working duration from waiting time
• Review duration estimates for critical activities

Critical Path and Float

• Calculate the path governing project completion
• Distinguish total float from free float
• Identify near-critical paths requiring attention
• Analyze network response to duration change

Day 3: Resources and Baseline Development

Planning Resource Loading

• Connect activities with skills and quantities
• Expose demand periods exceeding available capacity
• Identify resources controlling the schedule
• Build a project resource-demand profile

Balancing Resource Leveling

• Record dates with completion evidence
• Protect critical milestones during leveling
• Show effect of decisions on float
• Level schedule under a constrained resource

Securing Baseline Approval

• Audit schedule logic before freezing
• Record data date and underlying assumptions
• Connect the schedule with approved scope
• Prepare a baseline approval pack

Day 4: Schedule Updating and Variance Analysis

Collecting Progress Data

• Establish data date for every update
• Record dates with completion evidence
• Check progress against schedule logic
• Apply update cycle to project schedule

Schedule Variance Analysis

• Compare current dates with baseline dates
• Identify causes of critical path movement
• Measure float consumption across schedule paths
• Prepare a schedule variance report

Forecast to Completion

• Recalculate the network using current conditions
• Forecast project completion from actual trends
• Test milestone sensitivity to new constraints
• Prepare an updated schedule forecast

Day 5: Schedule Recovery and Control Laboratory

Schedule Compression Options

• Compare fast-tracking, added resources, resequencing
• Estimate cost and risk per option
• Avoid compressing noncritical activities
• Build schedule recovery scenarios

Schedule Change Governance

• Define conditions for formal baseline changes
• Document schedule-amendment causes and effects
• Protect historical records for comparison
• Simulate a schedule change review board

Integrated Schedule Laboratory

• Build schedule from complete scope case
• Update schedule after real-world events
• Analyze path forecast and recovery options
• Present control recommendation to project manager

 

• Network and schedule development from an integrated project case
• Critical path float and resource exercises
• Recurring updates using changing progress data
• Recovery laboratory comparing time cost and risk