The Dark Side of Estimates: The Impact of Inaccuracy and Work in Progress

While estimates are meant to provide insight into project timelines and resource allocation, they can have severe negative impacts — especially when inaccuracies combine with excessive Work in Progress.

What is Little's Law and WIP?

Little's Law is a fundamental concept in queuing theory: the average number of items in a system equals the average arrival rate multiplied by the average time spent in the system.

In software development this means one thing — as Work in Progress (WIP) increases, the average time to complete any single task rises with it. More balls in the air means each one takes longer to land.

How inaccurate estimates make it worse

Burnout and eroded morale. When estimates are inaccurately low, teams face constant pressure to deliver at an unsustainable pace. Quality suffers. People leave.

Broken trust with stakeholders. Overly optimistic estimates consistently miss deadlines. Each miss damages credibility and makes the next negotiation harder. Trust, once lost, takes a long time to rebuild.

Compounding complexity. Complex tasks involve unforeseen challenges by definition. Estimates that don't account for the intricacies of real-world software development don't fail occasionally — they fail systematically.

How to fix it

The negative impacts of poor estimation aren't inevitable. A few principles help:

• Embrace agile and focus on flow — measure throughput and cycle time rather than committing to point-in-time estimates
• Limit WIP deliberately — fewer concurrent items means faster completion of each one; Little's Law works in your favour when you respect it
• Foster transparent communication — surfaces problems early, when options still exist, rather than at deadline when they don't
• Shift to value-oriented delivery — ask "what's the most valuable thing we can ship next?" rather than "how long will everything take?"
• Encourage continuous learning — retrospectives that honestly examine estimation accuracy build better instincts over time

Software development is inherently uncertain. The goal isn't perfect estimates — it's building a process resilient enough to handle the uncertainty without it becoming a crisis every sprint.