Work in Progress Purpose and Scope

Work in Progress Purpose and Scope defines what the concept of work in progress actually encompasses within agile delivery and why deliberately managing it, rather than leaving it unconstrained, is treated as a central lever for improving how effectively a team converts effort into finished, valuable outcomes. Work in progress refers to any item that has been started but not yet completed, and understanding both its purpose as a management concept and its precise scope is foundational to the broader practice of flow control that builds upon it.

Defining What Counts as Work in Progress

The Boundary of Started but Not Finished

Work in progress specifically refers to items that have passed the point of genuine activation or start, as distinguished from work still sitting in a backlog or queue, and that have not yet reached the team's definition of done.

Including All Active States, Not Just One Stage

Work in progress typically spans every intermediate state between start and completion—development, review, testing, and any other stage the team's workflow includes—rather than referring only to a single specific phase.

Excluding Both Queued and Completed Work

Items waiting to be started, however close to the front of the queue, are not work in progress, and items that have genuinely reached completion are likewise excluded, keeping the concept focused specifically on active, unfinished effort.

Why Work in Progress Is Treated as a Distinct Concept Worth Managing

It Directly Affects How Quickly Work Completes

The amount of work simultaneously in progress has a direct, often counterintuitive relationship with how quickly any individual item moves from start to finish, making it a powerful lever for improving delivery speed.

It Reflects the True State of Effort, Not Just Intention

While a backlog reflects intended future work and completed items reflect past accomplishment, work in progress represents where the team's actual current effort and attention genuinely reside.

It Is a Primary Source of Multitasking and Context Switching

Excessive work in progress is strongly associated with contributors spreading attention across too many concurrent items, a pattern known to reduce overall efficiency despite appearing to maximize activity.

The Scope of What Work in Progress Management Covers

Individual-Level Work in Progress

The number of items a single contributor is actively engaged with at any given time, affecting their personal ability to maintain focus and complete work efficiently.

Team-Level Work in Progress

The total number of items the team as a whole has active simultaneously, affecting overall system throughput and the predictability of collective delivery.

Stage-Specific Work in Progress

The amount of work concentrated within a particular stage of the workflow, such as testing or review, which can reveal localized bottlenecks even when overall team-level work in progress appears reasonable.

Cross-Team or System-Level Work in Progress

In larger organizational contexts, the aggregate work in progress across multiple interacting teams, which can affect broader organizational flow beyond any single team's boundary.

The Purpose Behind Actively Managing This Scope

Preventing Silent, Unbounded Accumulation

Without deliberate attention, work in progress tends to grow as new items are started before existing ones are finished, gradually degrading the system's overall efficiency without any single obvious cause.

Making the Cost of Overcommitment Visible

Explicitly tracking work in progress as its own concept, distinct from queued or completed work, exposes overcommitment that might otherwise remain hidden within aggregate activity metrics.

Providing a Foundation for Deliberate Limits

Understanding precisely what constitutes work in progress is the necessary prerequisite for later establishing meaningful limits on it, a core technique within broader flow control practice.

Quantifying Work in Progress

Basic Work in Progress Count

This simple count, tracked continuously, forms the basic quantitative foundation on which more sophisticated flow control practices are built.

Common Misunderstandings of Scope

Equating Work in Progress With Total Team Activity

Conflating all forms of team activity, including planning or administrative tasks, with genuine work in progress on delivery items blurs the concept and undermines its usefulness as a focused management lever.

Ignoring Stage-Level Distribution

Tracking only the aggregate team-level count while ignoring how work in progress is distributed across different workflow stages can miss significant localized imbalances.

Treating Backlog Depth as Equivalent to Work in Progress

Confusing a large, unrefined backlog with genuine work in progress overlooks the meaningful distinction between work that has been started and work that is merely queued for future consideration.

Assuming Work in Progress Concepts Apply Only to Flow-Based Systems

Believing that work in progress management is relevant only to explicitly flow-based approaches, rather than recognizing its relevance within iteration-based systems as well, misses opportunities to apply valuable insight regardless of the overarching planning model in use.