11.1 Project Planning and Scheduling Techniques

Project planning and scheduling techniques give engineers a structured way to organize tasks, allocate resources, and keep complex projects on track. Whether you're building a bridge or launching a product, these methods help you figure out what needs to happen, in what order, and how long it'll all take. This unit covers the core tools: Gantt charts, network diagrams, PERT, CPM, and the Work Breakdown Structure (WBS).

Project Scheduling Techniques

Gantt Charts and Network Diagrams

Gantt charts are horizontal bar charts where each bar represents a project task, stretched across a timeline. The length of the bar shows the task's duration, and you can layer in dependencies (arrows showing which tasks must finish before others can start). They're especially useful for communicating schedules to stakeholders because they're visually intuitive.

That said, Gantt charts have limits. They don't handle complex dependency logic very well on their own, which is where network diagrams come in.

Network diagrams represent activities as nodes (or arrows, depending on the convention) connected by their logical relationships. They form the backbone of both PERT and CPM analysis. Where a Gantt chart shows you when things happen, a network diagram shows you why they happen in that order.

PERT and CPM Methods

These two methods both use network diagrams, but they handle time estimates differently.

Program Evaluation and Review Technique (PERT) is designed for projects where you're uncertain about how long activities will take. For each activity, you estimate three durations:

• Optimistic time ($a$): best-case scenario
• Most likely time ($m$): the realistic estimate
• Pessimistic time ($b$): worst-case scenario

PERT then calculates an expected duration using a weighted average:

$t_e = \frac{a + 4m + b}{6}$

This gives you a probabilistic view of the schedule, which is why PERT is common in R&D projects where durations are hard to pin down.

Critical Path Method (CPM) assumes activity durations are known with reasonable certainty. Its main goal is to identify the critical path, the longest sequence of dependent tasks through the network. The critical path determines the minimum possible project duration. Any delay to a critical path activity delays the entire project.

Resource Management and Schedule Compression

Even a perfect schedule falls apart if resources aren't managed well. Resource leveling adjusts task timing so that no person or piece of equipment is overloaded at any point. This sometimes extends the project duration, but it keeps workloads realistic.

When you need to shorten the schedule without changing scope, you have two main schedule compression techniques:

1. Fast-tracking: Perform activities in parallel that were originally planned sequentially. This saves time but increases risk, since overlapping tasks can cause rework if something changes.
2. Crashing: Add resources to critical path activities to reduce their duration. For example, authorizing overtime or bringing in additional crew. Crashing typically increases cost, so you target the critical path activities where extra resources give you the most time savings per dollar spent.

Project Scheduling Software

• Microsoft Project is widely used for creating schedules with task dependencies, resource assignments, and built-in critical path analysis.
• Primavera P6 handles large-scale and multi-project environments, with advanced features for risk analysis and resource management. It's standard in heavy construction and infrastructure.
• Lighter tools like Asana or Trello work for smaller projects or teams that need simple task tracking without the overhead of full scheduling software.

Critical Paths and Durations

Critical Path Identification

The critical path is the longest path through the project network, measured by total duration. It determines the shortest possible time to complete the project.

Activities on the critical path have zero total float, meaning there's no flexibility in when they start or finish. If any of them slips, the project end date slips.

Near-critical paths have only small amounts of float. These deserve close monitoring because even minor delays can push them onto the critical path, creating new schedule risks you didn't plan for.

Network Calculations

Finding the critical path requires two passes through the network:

Forward Pass (earliest times):

1. Start at the first activity. Set its Early Start (ES) to 0.
2. Calculate Early Finish: $EF = ES + Duration$
3. Move forward. Each successor's ES equals the largest EF of all its predecessors.
4. Continue until you reach the last activity. Its EF is the project duration.

Backward Pass (latest times):

1. Start at the last activity. Set its Late Finish (LF) equal to the project duration.

2. Calculate Late Start: $LS = LF - Duration$

3. Move backward. Each predecessor's LF equals the smallest LS of all its successors.

4. Continue until you reach the first activity.

Float (Slack) Calculations:

• Total Float $= LS - ES$ (or equivalently, $LF - EF$). This tells you how much an activity can be delayed without delaying the project.
• Free Float $= ES_{\text{successor}} - EF_{\text{activity}}$. This tells you how much an activity can be delayed without affecting the next activity's earliest start.

Activities with zero total float are on the critical path.

Project Duration and Extensions

The project duration is the sum of activity durations along the critical path:

$\text{Project Duration} = \sum_{i=1}^{n} Duration_{i}$

where $i$ represents each activity on the critical path.

The Critical Chain Method (CCM) extends CPM by factoring in resource constraints. Instead of just looking at task dependencies, it also considers who is doing the work and whether they're available. CCM uses buffers to manage uncertainty:

• Project buffer: Added at the end of the critical chain to protect the overall completion date.
• Feeding buffers: Placed where non-critical chains feed into the critical chain, preventing delays from propagating.

Importance of WBS

WBS Structure and Components

The Work Breakdown Structure (WBS) is a hierarchical decomposition of the entire project scope into smaller, manageable pieces. Think of it as an outline of everything the project needs to deliver.

A typical WBS has several levels:

• Level 1: The project itself
• Level 2: Major deliverables or phases
• Level 3: Work packages (the lowest level of the WBS, small enough to estimate and assign)

The 100% rule is the key principle: the WBS must capture all of the work defined by the project scope, and nothing more. Every element at a lower level must roll up completely to its parent.

A WBS dictionary accompanies the chart and provides detailed descriptions for each element, including scope of work, responsible parties, resource requirements, and acceptance criteria. It's the reference document that keeps everyone aligned on what each work package actually includes.

WBS Applications in Project Management

The WBS isn't just an organizational chart for tasks. It serves as the foundation for almost every other planning activity:

• Cost estimation: You estimate costs at the work package level, then roll them up for the total project budget.
• Scheduling: Activities are defined from work packages, which feed directly into your network diagram and Gantt chart.
• Progress tracking: You can measure completion and performance at each level of the WBS.
• Risk identification: Breaking work into smaller pieces makes it easier to spot where risks might hide within specific deliverables.
• Communication: The WBS gives stakeholders a clear, visual map of project scope, so everyone agrees on what's being delivered.

Integration with Other Project Management Tools

The WBS connects to several related breakdown structures:

• Organizational Breakdown Structure (OBS): Maps WBS elements to the teams or individuals responsible for them. Crossing the WBS with the OBS clarifies accountability for every work package.
• Cost Breakdown Structure (CBS): Aligns WBS elements with budget categories, enabling accurate cost tracking and supporting earned value management (a technique for measuring project performance against the plan).
• Risk Breakdown Structure (RBS): Categorizes potential risks by source or type, and links them to specific WBS elements for targeted risk management.

Project Scheduling Methods vs Applications

Traditional Scheduling Methods

Different methods suit different project types:

• Gantt charts work best for projects with well-defined tasks and relatively linear progression, like construction or manufacturing. They're less effective when dependencies get complex or durations are uncertain.
• PERT fits projects with significant uncertainty in activity durations, such as research and development. It gives you probabilistic completion estimates rather than a single fixed date.
• CPM excels when activity durations are well-known and the focus is on optimizing the schedule. It's a staple in construction and engineering, where historical data makes duration estimates reliable.

Agile and Iterative Approaches

Not all projects follow a traditional plan-then-execute model. Agile methods break work into short cycles:

• Scrum uses iterative sprints (typically 2-4 weeks) where teams plan, execute, and review a set of work. Sprint burndown charts track remaining work within each sprint. Priorities can shift between sprints based on feedback.
• Kanban visualizes workflow on a board with columns (e.g., To Do, In Progress, Done) and limits the number of items in progress at any time. It's well-suited for continuous flow processes like manufacturing or service operations, where the focus is on reducing cycle time and eliminating bottlenecks.

Advanced Scheduling Techniques

• Rolling wave planning details near-term work precisely while keeping future work at a higher level. As the project progresses, you elaborate the next phase in detail. This is practical for long-term projects where requirements evolve.
• Critical Chain Project Management (CCPM) builds on CPM by explicitly managing resource constraints and using buffer management (project buffers and feeding buffers) to handle uncertainty. It's particularly effective in multi-project environments where teams share resources.
• Last Planner System (LPS) is used in complex construction projects. It emphasizes collaborative planning at multiple levels: milestone schedules, look-ahead plans (typically 6 weeks out), and weekly work plans. Teams commit to what they will complete, not just what they should complete.

Simulation and Hybrid Approaches

• Monte Carlo simulation runs thousands of scenarios with randomized inputs to show the probability distribution of possible project outcomes. It's valuable when a project has many uncertain variables and you need to understand the range of likely completion dates or costs.
• Hybrid approaches combine elements of different methods to fit a project's specific needs. For example, Scrumban blends Scrum's sprint structure with Kanban's flow-based workflow, which can work well for software maintenance where both planned and unplanned work coexist.