Managing a Scrum Board: Workflow, WIP and Blocked Work

A Scrum Board provides a visual representation of work during a Sprint. It helps the Scrum Team see where work is and where problems may be occurring.

The board should support transparency and conversation, not become a tool for controlling individual Developers.

What Is a Workflow?

A workflow describes the steps that work goes through from start to completion.

A simple workflow might be:

To Do → In Progress → Review → Done

The exact workflow should reflect how the team actually creates a usable Increment.

What Is WIP?

WIP means Work In Progress.

It refers to work that has started but has not yet been completed.

Too much WIP can cause multitasking, delays and reduced focus.

Simple example:

If five items are simultaneously being developed but none are reaching Done, the team may have too much WIP.

WIP Limits

A team may choose to set a limit on how many items can be in a particular workflow stage at one time.

For example:

In Progress: Maximum 2 items

When the limit is reached, the team focuses on completing existing work instead of starting more work.

WIP limits are a flow practice and are not prescribed by the Scrum Guide.

What Is a Bottleneck?

A bottleneck occurs when work accumulates at a particular stage because that stage cannot process work quickly enough.

Example:

1 item is being developed, but 6 items are waiting for testing.

The testing stage may be a bottleneck.

What Is Blocked Work?

Work is blocked when an impediment prevents meaningful progress.

Examples include:

  • External dependency
  • Technical problem
  • Missing information
  • Environment unavailable
  • Required decision is delayed

How Should a Scrum Master Respond?

The Scrum Master should not automatically solve every problem personally.

Instead, the Scrum Master helps the Scrum Team understand the impediment and supports its removal or resolution.

Think beyond the card:

A blocked item is a symptom. The Scrum Master should also look for the underlying cause.

Example: Repeated Blockage

Imagine a team repeatedly waits for another department to approve access before development can continue.

Simply marking the card as "Blocked" does not solve the problem.

The Scrum Master can facilitate discussion about why the dependency occurs and help the organization address the underlying barrier.

What Should a Scrum Master Look For?

Too Much WIP Many items started but few completed.
Growing Queue Work continuously accumulating at one stage.
Aging Work An item remaining in progress unusually long.
Repeated Blockers The same type of impediment occurring repeatedly.

Common Mistakes

Optimizing for Movement Moving cards simply to make the board look active.
Starting More Work Beginning new items while existing work remains unfinished.
Ignoring Blockers Leaving blocked items untouched for several days.
Blaming Individuals Treating workflow problems as individual performance issues.

Scrum Board and Daily Scrum

The board can provide useful information during the Daily Scrum.

Instead of simply asking every person for a status report, Developers can inspect the work and coordinate their plan toward the Sprint Goal.

Key Takeaway

A good Scrum Board makes workflow visible and helps the team identify problems early.

The Scrum Master's job is not to keep cards moving. It is to help the team improve its ability to create value.