Work Charts: Flow-Based Visual Tools for Limiting WIP

PMBOK v8 Definition

Work charts are visual management tools used in flow-based projects, such as those employing Kanban boards, to limit the amount of work in progress (WIP). When a column approaches its WIP limit, project team members can "swarm" around current work to help those working on tasks that are slowing the flow. Burn charts (burnup and burndown) are a related category that shows project team velocity—the productivity rate at which deliverables are produced, validated, and accepted within a predefined interval.

Why It Matters for the Exam

The PMI exam frequently tests work charts in questions about adaptive/agile project management, specifically regarding flow optimization and WIP limits. Questions appear in the Executing and Monitoring & Controlling process groups, often asking candidates to identify which chart to use in a given scenario or to distinguish between cycle time, lead time, and velocity concepts.

Key Points to Remember (for the exam)

Primary Purpose: Work charts limit work in progress (WIP) in flow-based projects using Kanban boards
Swarming Technique: When a column approaches WIP limit, team members "swarm" to help those on tasks slowing the flow
Burnup Chart: Tracks work completed (starts at zero, increases upward) versus expected work (straight line across top of graph)
Burndown Chart: Graphical representation of work remaining versus time left in a timebox
Velocity: Measures productivity rate of deliverables produced, validated, and accepted within a predefined interval
Cycle Time: Time from when a task starts until it is completed
Lead Time: Time from when a task is put on the board until it is delivered (includes waiting time)

Typical PMI Exam Example

A software development team using a Kanban board notices that the "In Progress" column has reached its WIP limit of five tasks. The project manager observes that one complex task is blocking completion of other work. According to PMBOK v8, what should the team do? → The team should "swarm" around the current work to help those working on tasks that are slowing the flow.

PMI Exam Traps

Trap: Confusing burnup chart with burndown chart
- Reality: Burnup shows work completed (increasing line); burndown shows work remaining (decreasing line)
Trap: Thinking velocity measures only speed of work
- Reality: Velocity measures deliverables produced, validated, AND accepted—not just output speed
Trap: Confusing cycle time with lead time
- Reality: Cycle time starts when work begins; lead time starts when work is added to the board (includes waiting)
Trap: Believing WIP limits are optional in flow-based projects
- Reality: WIP limits are a fundamental constraint in Kanban method to optimize flow and prevent overburdening

Important PMI Connections

Related Concept	Relationship Type	Exam Attention Point
Kanban Method	Foundation approach	Work charts are primary tools for implementing Kanban's WIP limits
Theory of Constraints	Complementary philosophy	Both focus on identifying and addressing limiting factors in flow
Adaptive Development	Primary application domain	Burnup charts are used mostly within adaptive development approaches
Visual Controls	Broader category	Work charts are a type of visual control for monitoring project progress

Quick Review Questions

What is the primary purpose of using work-in-progress limits on a Kanban board?
A burnup chart shows work completed at 60% against expected work at 80%. What does this indicate about project progress?
If a team's cycle time is 3 days and lead time is 7 days, what does the 4-day difference represent?
What action should a project team take when a column on a Kanban board approaches its WIP limit?
Which chart would best show whether a team is on track to complete all work within a timebox?

PMBOK v8 Reference

Section 5.7 - "Work Charts" (Kanban Board, Burn Charts, Velocity concepts) Section 5.7.1 - "Flow-Based Projects and Work-in-Progress Limits"