8.1 Scheduling Principles, Gantt Charts, and Milestones

8.1 Scheduling Principles, Gantt Charts, and Milestones

Definition (APM BoK7 glossary): Time scheduling is a collection of techniques used to develop and present schedules that show when work will be performed. A schedule is a timetable showing the forecast start and finish dates for activities or events within a project, programme or portfolio.

AC 6.1 asks you to state the purpose of scheduling: it shows when the work within a project is planned to be performed, and so provides the basis for coordinating resources, tracking progress and understanding the overall duration.

Every successful project requires a structured pathway from strategic intent to operational execution. While scope management tools like the Product Breakdown Structure (PBS) and Work Breakdown Structure (WBS) answer the question of what deliverables and work packages must be produced, they remain fundamentally static. They do not convey the passage of time, the sequence of operations, or the chronological commitments made to project stakeholders.

Scheduling provides this essential temporal dimension. By converting discrete work packages into an ordered, time-based operational plan, scheduling bridges the gap between scope definition and practical project control.

---

The Purpose of Scheduling in Project Delivery

In accordance with APM BoK7, scheduling fulfills several critical operational and governance functions:

1. Converting Scope into an Operational Model: Scheduling takes the lowest-level work packages from the WBS, decomposes them into discrete activities, and places them into an actionable, chronological sequence.
2. Determining Project Duration and Delivery Commitments: By estimating the duration of each individual activity and linking them logically, the project manager can determine the earliest and latest possible project completion dates, enabling realistic commitments to sponsors, clients, and end-users.
3. Identifying and Balancing Resource Demands: A schedule maps required human, equipment, and financial resources against calendar time. This reveals peak demand periods, resource bottlenecks, and downtime, allowing for informed resource smoothing and leveling.
4. Establishing the Performance Measurement Baseline (PMB): Once approved by the Project Sponsor, the schedule becomes the schedule baseline. This fixed reference point allows the project manager to track actual progress, calculate schedule variances (e.g., in Earned Value Management), and generate reliable completion forecasts.
5. Facilitating Scenario Modeling and Risk Analysis: A well-constructed schedule allows project managers to simulate "what-if" scenarios—such as supplier delays, adverse weather, or resource shortages—and quantify the impact of risks before they jeopardize project objectives.

+-----------------------------------------------------------------------------------+
|                         FROM SCOPE TO SCHEDULE BASELINE                           |
+-----------------------------------------------------------------------------------+
|  WBS Work Packages  --->  Activity List  --->  Precedence Logic & Dependencies   |
|  (What work to do)        (Discrete tasks)     (Order of execution: FS, SS, FF)   |
|                                                               |                   |
|                                                               v                   |
|  Approved Schedule  <---  Network Analysis <---  Durations & Resource Demands     |
|  Baseline (Locked)        (CPA, Float, Dates)    (Effort, calendars, availability)|
+-----------------------------------------------------------------------------------+

---

Activity Sequencing and Precedence Dependencies

Activities cannot occur in isolation; their execution is governed by physical, contractual, technical, or managerial relationships known as dependencies or precedence relationships. The APM framework recognizes four distinct logical relationships between a predecessor activity (the task that logically comes first) and a successor activity (the task that logically follows).

1. Finish-to-Start (FS)

• Definition: The predecessor activity must finish before the successor activity can start.
• Significance: Finish-to-Start is the most common, intuitive, and natural dependency type encountered in project management. It reflects physical or procedural necessity.
• Project Example: Foundations must be excavated and poured (Predecessor) before bricklaying of the walls can begin (Successor). In software delivery, code development must be completed before formal system testing can commence.

2. Start-to-Start (SS)

• Definition: The predecessor activity must start before the successor activity can start.
• Significance: Used when two activities can run concurrently (in parallel), but the successor cannot initiate until the predecessor has gotten underway.
• Project Example: Laying electrical cable (Predecessor) must start before backfilling the cable trench (Successor) can begin. Similarly, drafting a technical user manual can start once software feature coding has started.

3. Finish-to-Finish (FF)

• Definition: The predecessor activity must finish before the successor activity can finish.
• Significance: Emphasizes completion synchronicity. The successor activity may have been underway for days or weeks, but it cannot formally wrap up until the predecessor has reached completion.
• Project Example: Software development (Predecessor) must finish before technical documentation review (Successor) can finish. You cannot complete the testing of an electrical substation until the final physical installation is fully finished.

4. Start-to-Finish (SF)

• Definition: The predecessor activity must start before the successor activity can finish.
• Significance: The rarest, most counter-intuitive dependency in project scheduling. The successor activity is usually an ongoing legacy service or operation that cannot terminate until its replacement begins.
• Project Example: A legacy IT billing system (Successor) cannot be switched off and retired until the new cloud-based billing platform (Predecessor) has started live operational processing. Similarly, an outgoing security shift cannot finish until the incoming relief shift starts.

Summary of Dependency Types

---

Modifying Dependencies: Lead Time and Lag Time

In practical scheduling, pure logical relationships often require time offsets to reflect realistic physical constraints or delivery acceleration opportunities.

Lag Time (Mandatory Waiting Delay)

• Definition: A directed, non-working waiting period inserted between a predecessor and successor activity where no productive work takes place.
• Application: Represented mathematically as positive time added to a dependency (e.g., FS + 5 days).
• Project Examples:
  • After pouring concrete (Predecessor), a mandatory curing lag of 7 days must elapse before structural loads can be applied (Successor).
  • After applying primer paint to a vessel hull, a 24-hour drying lag is required before the topcoat can be applied.
• Management Insight: Lags consume calendar time without consuming labor or financial budget, but they directly extend the elapsed duration between activities and can push out project completion if situated on the critical path.

Lead Time (Acceleration / Overlap)

• Definition: An intentional acceleration of the successor activity that allows it to start before the predecessor activity has fully completed.
• Application: Represented mathematically as negative lag subtracted from a dependency (e.g., FS - 3 days).
• Project Examples:
  • In an office refurbishment project, interior painters begin work in finished rooms 3 days before the plasterers have completed all rooms in the building (FS - 3 days).
  • Technical authoring of the user manual begins 5 days before software coding finishes.
• Management Insight: While lead time compresses project schedules, it introduces operational risk. If the predecessor activity experiences errors, redesigns, or unexpected changes during its final stages, the successor work already completed under the lead will likely require substantial, expensive rework.

---

Gantt Charts (Bar Charts)

Developed by mechanical engineer Henry Gantt in the 1910s, the Gantt chart is the most widely recognized and utilized visual scheduling tool in modern project management.

Visual Anatomy of a Gantt Chart

A Gantt chart displays project activities along two primary axes:

• Vertical Axis: Lists the activities, tasks, work packages, and milestone events in sequential order, often reflecting the hierarchical structure of the WBS.
• Horizontal Axis: Represents calendar time divided into appropriate increments (e.g., hours, days, weeks, months, or quarters).
• Horizontal Bars: Each task is represented as a horizontal bar. The position of the bar indicates the planned start date, its length corresponds to the task's estimated duration, and its termination indicates the planned finish date.
• Progress Indicators: Shading or secondary color fills within each bar illustrate the percentage of work physically completed to date against the current calendar "time now" line.
• Dependency Links: Directed arrows connecting bars illustrate the logical precedence relationships (FS, SS, FF) linking predecessor and successor tasks.

Benefits of Gantt Charts

1. Exceptional Clarity and Visual Accessibility: Gantt charts are intuitive. Non-technical stakeholders, executive sponsors, and clients can immediately grasp the project timeline, phase overlaps, and current progress without specialized scheduling knowledge.
2. Effective Operational Tracking: Project teams can readily see what tasks should be underway on any given day, who is responsible, and whether active tasks are tracking ahead of or behind schedule.
3. Baseline Comparison: Dual-bar Gantt charts can plot the approved baseline bar directly beneath the live forecasting bar, instantly exposing schedule slippage and schedule variances.

Limitations of Gantt Charts

1. Visual Clutter on Complex Projects: In large projects comprising hundreds or thousands of activities, a Gantt chart becomes unwieldy, sprawling across dozens of pages or screens and obscuring critical operational insights.
2. Obscured Dependency Logic: When dozens of dependency arrows cross over each other, tracking network logic becomes nearly impossible. It is difficult to see at a glance why a specific task cannot start or which upstream delay is causing a cascade of downstream postponements.
3. Lack of Float Transparency: While modern scheduling software can shade the critical path, basic Gantt charts do not inherently display total float or free float, making it difficult to assess how much schedule flexibility exists on non-critical tasks.
4. Failure to Show Resource Capacity: A standard Gantt chart displays time and tasks, not resource availability. It can easily display a plan that looks flawless on paper but over-allocates key specialists to multiple concurrent tasks.

---

Milestones in Schedule Planning

Definition (APM BoK7 glossary): A milestone is a key event selected for its importance in the schedule, commonly associated with tangible acceptance of deliverables.

AC 6.3 asks you to "state the purpose of milestones": a milestone exists to show a significant event. The second half of the BoK7 wording is the part candidates drop — milestones are usually placed where a deliverable is tangibly accepted, which is why they make natural contractual payment points.

Core Characteristics of Milestones

Beyond the BoK7 definition, professional scheduling practice gives a milestone two non-negotiable characteristics:

1. Zero Duration: A milestone takes 0 days, 0 hours, and 0 minutes to complete ($Duration = 0$).
2. Zero Resource Consumption: A milestone consumes no labor, no materials, and no direct financial expenditure.

Because a milestone has no duration, it does not represent an activity or a piece of work. Instead, it represents an instantaneous point in time—a marker signifying the achievement of a significant state, deliverable, or decision. On Gantt charts, milestones are conventionally depicted as solid black or colored diamonds (◆).

Strategic Functions of Milestones

• Marking Phase Gates and Decision Points: Milestones serve as formal stage-gate review points where governance bodies (such as the Project Sponsor or Steering Group) assess project health and formally authorize progression into the subsequent lifecycle phase (e.g., "Concept Gate Approved" or "Detailed Design Signed Off").
• Signifying Major Deliverable Completion: Marking the delivery of critical components (e.g., "Factory Acceptance Testing Passed" or "Civil Works Substantially Complete").
• Contractual and Commercial Triggers: In commercial contracts, client payment tranches are frequently tied to the verified attainment of specific contractual milestones (e.g., "Milestone 4: Superstructure Handover – Tranche 3 Payment Released").
• High-Level Executive Reporting: Senior executives and project boards rarely have time to inspect thousands of detailed WBS tasks. A Milestone Summary Schedule—a high-level view showing only 10 to 20 key milestone dates—provides leaders with an immediate snapshot of strategic trajectory and schedule health.