Analyze Project Critical Paths and Optimize Schedules

This skill covers critical path method (CPM) analysis and project-schedule optimization - project network diagrams, dependency relationships, duration estimation, resource allocation, and schedule-compression techniques, analyzing complex project structures to identify bottlenecks, calculate critical paths, and provide actionable schedule-optimization recommendations. Network-diagram construction: Activity-on-Node (AON, the preferred method - activities are nodes, arrows represent dependencies), the Precedence Diagram Method (PDM) supporting four dependency types (Finish-Start, Start-Start, Finish-Finish, Start-Finish), a forward pass (computing early-start and early-finish times), a backward pass (computing late-start and late-finish times), and float calculation (total float = LS - ES = LF - EF). Critical-path rules: activities with zero total float form the critical path; any delay on a critical-path activity delays the whole project; complex projects can have multiple critical paths; and near-critical paths (minimal-float activities) need monitoring.

Duration estimation is shown via a three-point PERT formula (expected duration = (optimistic + 4 times most-likely + pessimistic) / 6, standard deviation = (pessimistic - optimistic) / 6, worked with a 4/6/14-day example yielding a 7-day expected duration and 1.67-day standard deviation) and a critical-path-calculation algorithm performing the forward pass (early start and finish per activity in topological order) and backward pass (late finish and start, and total float), then filtering to activities with zero float. Advanced techniques cover resource-constrained critical-path analysis (delaying non-critical activities when period resource demand exceeds capacity, then recalculating the critical path) and schedule-compression analysis: crashing (adding resources to critical-path activities, sequenced by lowest crash-cost-per-day) and fast-tracking (overlapping sequential activities, with a risk factor combining rework probability and rework impact).

Practical implementation patterns cover a Monte Carlo schedule simulation (sampling each activity's duration from a triangular distribution across 10,000 iterations, then reporting p50/p80/p90 completion times, mean, and standard deviation) and a baseline-schedule configuration:

project_schedule:
  baseline_date: "2024-01-01"
  working_calendar:
    working_days: ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"]
    holidays: ["2024-01-15", "2024-02-19", "2024-05-27"]
    daily_hours: 8
  
  activities:
    - id: "A001"
      name: "Requirements Gathering"
      duration: 5
      predecessors: []
      resources: ["BA", "PM"]
      constraints:
        type: "must_start_on"
        date: "2024-01-01"

Risk-aware critical-path analysis covers path convergence (identifying merge points where multiple paths meet), path divergence (synchronization risk across parallel paths), resource conflicts (mapping resource-overload periods), and external dependencies (tracking critical vendor or stakeholder dependencies), plus critical-chain buffer management (a project buffer sized at 50% of the critical path's summed variance, and feeding buffers for non-critical paths sized the same way).

Performance-optimization strategies cover schedule-acceleration options (resource reallocation to critical activities, scope reduction by removing secondary deliverables, converting sequential activities to parallel execution, technology or automation improvements, and process-waste elimination) and a critical-path monitoring dashboard tracking schedule performance index (earned value divided by planned value), critical-path delay (actual versus baseline duration), float-consumption rate, resource utilization, and milestone adherence, with alerts triggered when float consumption exceeds 80% or the schedule performance index drops below 0.9.

Use it when analyzing or optimizing a project schedule via CPM - building the network diagram, calculating the critical path and float, running Monte Carlo schedule risk analysis, or deciding between crashing and fast-tracking to compress a timeline. It is not a general project-management or agile-planning guide - it is scoped specifically to critical-path scheduling analysis and optimization.

Given a project's activities, durations, dependencies, and resource constraints, it produces the critical path and float per activity, a compressed-schedule recommendation (crash or fast-track), Monte Carlo completion-time percentiles, and a schedule-health dashboard with alerts.

Code samples use Python (numpy for Monte Carlo simulation, topological sorting for the forward and backward pass) and YAML for baseline-schedule configuration.

Project managers and schedulers running CPM analysis, schedule-risk simulation, or timeline-compression decisions.