large_highway-traffic-m.webp

medium_highway-traffic-m.webp

small_highway-traffic-m.webp

thumbnail_highway-traffic-m.webp

highway-traffic-m.webp

Are you struggling with unpredictable delivery times and inefficient workflows? Discover why trying to tackle too much work at once is hurting your Agile team’s efficiency. Learn how limiting Work in Progress (WIP) and tracking key metrics can transform your software development process.

## What Software Development and Busy Highway during rush hour have in common?

Think of a highway you regularly travel. When traffic is light, cars move smoothly and predictably, allowing you to estimate how long your trip will take with confidence. As the number of cars on the road increases, throughput (the number of cars passing a point per unit of time) also increases—up to a certain point. However, beyond that optimal point, adding more traffic leads to congestion. When the road becomes overcrowded, travel times become highly unpredictable and significantly longer.

Queueing theory explains this phenomenon. When more traffic is added to a road already operating at maximum throughput, throughput quickly slows down. If the problem isn’t addressed and more cars continue to enter the highway than leave it, congestion occurs. This phenomenon follows a parabolic curve, where throughput is maximized at an optimal density and speed of traffic. Beyond this point, throughput deteriorates rapidly as capacity becomes overloaded, causing significant delays and unpredictability.



highway-throuput.png

As Donald Reinertsen explains in his work, this same pattern occurs when software development teams take on new work when they are already operating at their optimal throughput. When teams start new work while already having enough on their hands, they extend the list of work in progress instead of focusing on completing existing tasks. This creates congestion that severely limits throughput.

Just like traffic on a congested highway, when one task encounters an issue or delay, it can trigger a cascade of delays across other tasks. This ripple effect increases the variability of cycle times and makes accurate forecasting nearly impossible. As Reinersten describes in The Principles of Product Development Flow, operating at high levels of capacity utilization doesn’t just slow down progress—it also increases cycle times and drastically reduces the efficiency of the entire workflow.

## The Solution is simple - but challenging to implement
Just like traffic on a congested highway, the only way to restore maximum throughput and achieve predictable flow is to reduce the number of cars on the road. This happens when the number of cars entering the highway drops below the number of cars exiting—reducing congestion and allowing traffic to flow smoothly again.

The same principle applies to software development. When your development process is overloaded with too much work in progress (WIP), the only way to combat this issue is by actively limiting your WIP. By doing so, you create enough breathing room to absorb variability and maintain a smooth flow.

### What To Do When You’re Stuck in Congestion
If your development pipeline is overloaded with too much WIP, here’s how to start solving the problem:

- **Stop Starting New Work:** Instead of constantly adding new tasks to your workflow, focus your team’s effort on completing existing work in progress.
- **Define WIP Limits:** Establish clear WIP limits that allow your team to run at optimal throughput. Only start new work when you are within those limits.
- **Continuously Monitor Key Metrics:** This allows you to maintain optimal flow by providing clear visibility into state of your process. Monitoring the following metrics gives you objective data to push back against the constant pressure to start more work.

#### Metrics to monitor
1. **Work in progress** (the number of items your teams are working on at any given time)
2. **Cycle-time** (how long it takes each of those team to get through your dev-process)
3. **Throughput** (how many work items complete per unit of time)
-- Only start new work in line with your WIP limts

The key is to  **only start new work in line with your WIP limits**. By respecting these limits, you create a stable environment where tasks can flow smoothly and predictably—just like traffic moving efficiently on a highway operating at optimal throughput.

Unlike traffic, where the number of cars entering a highway is not controlled, in software development, you have the ability to decide when new work starts. However, implementing this control is challenging because there are many forces pushing in the opposite direction—stakeholder pressure, conflicting priorities, and the belief that having more work in progress means more progress is being made.

## Why Limiting Work in Progress Is So Hard to Implement
Implementing a process that actively limits Work in Process (WIP) and focuses on optimizing throughput sounds simple in theory, but it’s incredibly challenging in practice due to several reasons:

### 1. Cultural and Organizational Resistance
These challenges relate to deeply ingrained beliefs and leadership resistance that prevent effective WIP management.

- **Lack of Leadership Buy-In:** Change needs to be embraced from the top down. If leadership does not understand or support limiting WIP and monitoring flow metrics, it will be very difficult for teams to adopt these practices effectively.

- **Cultural Resistance:** Many organizations equate productivity with having a lot of work in progress (WIP). This deeply ingrained mindset makes it hard for managers and stakeholders to accept that working on fewer items at once will actually improve overall throughput and predictability. The idea that having more work in progress means more progress is being made is difficult to shake.

- **Fear of Idle Time:** Managers frequently worry that if team members aren’t fully loaded with work, time is being wasted. This fear drives a tendency to push capacity utilization to unsustainable levels, which paradoxically reduces throughput and predictability.

### 2. Misaligned Incentives & Lack of Understanding
These issues arise from how success is measured and incentivized within the organization.

- **Misaligned Incentives:** Performance metrics and incentives are often focused on individual productivity rather than team flow. When developers are rewarded for “keeping busy” rather than completing work, high WIP becomes a structural problem.

- **Lack of Understanding of Flow Metrics:** Teams and organizations may lack the knowledge or tools to track critical metrics like WIP, cycle time, and throughput. Without accurate metrics, it’s nearly impossible to determine whether changes to the process are genuinely improving flow and predictability or simply adding more complexity.

### 3. Stakeholder Pressure & Conflicting Priorities 
Challenges that result from pressure to meet external demands and conflicting expectations.

- **Pressure from Stakeholders:** Different stakeholders often push teams to start new work before they have completed existing work. This pressure usually comes from a fear of missing deadlines that have been previously communitated, even if it means sacrificing flow efficiency.

- **Perceived Urgency:** When people are waiting for your work, the pressure to “just get started” is enormous. Without clear alignment and communication, it’s easy for WIP limits to be ignored or overridden.

- **Dependency Conflicts:** When teams are asked to limit WIP, it often means delaying work that stakeholders are waiting on. This can lead to difficult discussions where you have to explain why prioritizing flow efficiency over starting new work is ultimately better for everyone.

- **Difficulty Enforcing WIP Limits:** Even when teams agree on WIP limits, enforcing them can be difficult. Teams may feel tempted to bend the rules to accommodate urgent requests or new priorities, which undermines the benefits of limiting WIP.

Effectively managing work in progress requires transparency, prioritization, and a clear commitment to maintaining WIP limits—even when it feels uncomfortable. But having the right data and insights makes it much easier to stay on track.

## Introducing a Better Way to Track and Improve Your Flow Metrics
Knowing where you stand is essential. Having clear data about how fast you’re moving today, how fast you could be moving, and what actions are needed to improve is crucial for gaining buy-in from management and stakeholders.

**Want To Be The First To Know When the solution is ready?**
Sign up now to receive updates and be the first to try this powerful new solution [Get notified here.](/solutions/forecast-backlog-completion/)



Why Trying To Do Everything At Once Is Destroying Your Agile Team’s Efficiency and Predictability

Try One-Click Planning Poker you run from the Jira Backlog and you will never look back.



"After trying many tools in Jira, we landed on Smart Guess. It's the best app ❤️ we've ever used!"

Now available for free — no budget approval needed! 🚀

Transform your Planning Poker


https://marketplace.atlassian.com/apps/1225496/

Free app

nav-try-button

SG-full-color-black.svg

SG-full-color-blue.svg

SG-logo-black-07.svg

SG-logo-color-05-MarketPlace.svg

SG-logo-white-06.svg

SG-full-color-white.svg

Forever Free. No setup. One Click—Planning Poker you run directly from the Jira backlog. Including
- **Fully featured Planning-** & [Async -Poker](/solutions/async-planning-poker/)
- **Fully configurable** [Card decks](/blog/configurable-card-decks/)
- **Role-based controls**, [Team lead, Observer, etc.](/blog/smartguess-role-based-controls-observing-leading-sharing/)

Perfect for two teams - up to 31 story estimates/week.

Everything in Free included, plus:
- **Unlimited Estimates:** No limits, no boundaries.
- **Silent Estimation:** Estimate large backlogs fast.
- **Atlassian Fortified:** Enhanced security and reliability.
- **Free Demo and Trial:** Experience the Pro Plan before committing.


Smart Guess can be used from within the Jira Backlog

large_PlanningPoker-from-Backlog-E.png

medium_PlanningPoker-from-Backlog-E.png

small_PlanningPoker-from-Backlog-E.png

thumbnail_PlanningPoker-from-Backlog-E.png

PlanningPoker-from-Backlog-E.png

Silent Estimation by Smart Guess allows teams to estimate large number of stories faster

Why Overloading Your Agile Process With Too Much Work Destroys Efficiency and Predictability

Flow Metrics

Topics covered in the series

Popular posts

Transform your Planning Poker

Transform your Planning Poker

Smart Guess Free

Smart Guess Pro