5.2 Project Planning: WBS, Gantt Charts & Communication Plans

Project Planning: WBS, Gantt Charts & Communication Plans

Quick Answer: Project planning translates Six Sigma charter goals into executable operational schedules through the Work Breakdown Structure (WBS), Gantt charts, and Critical Path Method (CPM). The WBS breaks down deliverables following the 100% Rule, ensuring complete scope capture without extraneous additions. Gantt charts map work packages across calendar timelines, while CPM identifies zero-float tasks that dictate minimum project duration. Complementary communication plans and risk registers sustain stakeholder alignment and mitigate operational hurdles. Independent CSSYB study guide by OpenExamPrep.

The Work Breakdown Structure (WBS)

While the project charter establishes what the team must accomplish, it does not specify daily operational execution. To bridge this gap, teams construct a Work Breakdown Structure (WBS)—a hierarchical, deliverable-oriented visual decomposition of the total scope of work required to complete the project.

A standard WBS organizes project outputs into progressive levels of detail:

• Level 1: The overarching project deliverable or goal (e.g., Reduce Electronic Billing Errors).
• Level 2: The primary project phases, typically mapped to the DMAIC lifecycle (Define, Measure, Analyze, Improve, Control Deliverables).
• Level 3: Sub-deliverables supporting each phase (e.g., under Define: Approved Charter, Process Map, Stakeholder Plan).
• Lowest Level (Work Package): The fundamental unit of the WBS. A work package represents a discrete, manageable unit of work assigned to a single owner, with clear completion criteria, measurable output, and predictable cost and duration.

The 100% Rule

The governing standard of WBS construction is the 100% Rule. This rule requires that the WBS encompass 100% of the project scope defined in the charter—including internal project management activities such as tollgate presentations, team workshops, and baseline audits—with zero omissions and zero extraneous additions. At each downward tier of decomposition, child deliverables must sum to exactly 100% of the parent deliverable. Adhering to the 100% rule prevents scope omissions while barring non-chartered tasks from siphoning team capacity.

---

Project Scheduling with Gantt Charts

Once the WBS establishes all work packages, the project leader arranges them across an operational calendar using a Gantt Chart. Developed by Henry Gantt in the 1910s, the Gantt chart is a horizontal bar chart displaying project activities against a calendar timeline.

Key components of a Gantt chart include:

• Task Identification: Individual work packages and summary rows listed along the vertical axis.
• Calendar Timeline: Units of time (days, weeks, or months) displayed along the horizontal axis.
• Duration Bars: Horizontal bars whose lengths correspond to planned task durations from start to finish.
• Predecessor Dependencies: Visual links establishing task relationships. The most common is Finish-to-Start (FS), where Task B cannot begin until Task A completes (e.g., data collection must finish before statistical capability calculations can start).
• Milestones: Zero-duration checkpoints (often represented by diamonds) denoting major achievements or gate reviews (e.g., Define Tollgate Sign-off).

Yellow Belts reference Gantt charts during weekly huddles to monitor assignments, track dependencies, and catch schedule slippage early.

---

Critical Path Method (CPM) and Float Concepts

Complex Six Sigma projects involve multiple parallel activity paths. To determine project duration and prioritize resources, leaders utilize the Critical Path Method (CPM). The critical path represents the longest continuous sequence of dependent activities from project start to finish.

Strategic Importance of the Critical Path

The critical path determines the absolute minimum time required to complete the entire project. Even if parallel non-critical tasks finish early, the overall project cannot complete any faster than the cumulative duration of tasks along the critical path.

Understanding Float (Slack)

Activities in a project network possess varying degrees of schedule flexibility, termed Float or Slack:

• Total Float: The total duration an activity can be delayed from its early start date without delaying the overall project completion deadline ($Total\ Float = Late\ Start - Early\ Start = Late\ Finish - Early\ Finish$).
• Free Float: The duration an activity can be delayed without delaying the early start of any immediate successor activity.

The Zero Float Rule: Activities residing on the critical path possess zero total float ($Float = 0$). Consequently, any delay to a critical path activity causes an identical, day-for-day delay to the final project completion date, unless leadership applies schedule compression.

To recover lost time on the critical path, project leaders evaluate two compression techniques:

• Crashing: Adding resources (e.g., assigning additional Yellow Belts to data logging or paying overtime) to shorten critical task durations, which increases project cost.
• Fast-Tracking: Executing sequential critical tasks in parallel rather than waiting for preceding tasks to finish, which elevates operational risk and rework potential.

---

Project Communication Planning & Risk Management

Technical rigor alone does not guarantee project success; stakeholder alignment is equally vital. Process changes frequently trigger operational anxiety among frontline personnel. To maintain transparency, teams develop a formal Project Communication Plan defining audience, objectives, delivery channels, update frequency, and assigned owners.

In parallel, teams maintain a Risk Register throughout DMAIC execution. For each identified hurdle, the team calculates a priority score ($\text{Risk Score} = \text{Probability} \times \text{Impact}$) and formulates targeted response plans: Avoidance, Mitigation, Transfer, or Acceptance. Yellow Belts assist by monitoring operational triggers during daily tasks.