Work Tradeoff Calculator for Software Development Teams

A flow calculator based on queuing theory. Adjust the inputs on the left to see how cycle time, utilization, and wait time respond. Use it to find the balance that works for your team — whether you run Scrum, Kanban, or continuous delivery.

Your team today

Choose how your team plans work.

Anything started but not yet "done." Count user stories, tickets, or features — whatever your team treats as a unit. Include items in coding, code review, QA, or waiting between stages. Exclude backlog items not yet picked up.

Everything started but not yet finished.

How many new units enter the team's flow. Use the same unit as "Items in progress" (e.g., user stories). For sprints, this is what's committed at planning. For continuous flow, average over the last few weeks.

How fast new work shows up for the team.

Hands-on work time per item, from pickup to done — coding, review, testing, deployment. This is effort, not elapsed calendar time (which includes time spent waiting in queues). If items vary widely, use a typical or median value.

How long one item takes when actually being worked on.

Team members who actively do this work — developers, QA, designers, anyone in the value stream. Exclude people who only attend meetings or do unrelated work. Round part-timers (a 50% person counts as 0 or 1).

How many people are doing the work.

Whether new requests arrive on a regular schedule or in bursts. Steady = a consistent cadence (one ticket per day). Bursty = quiet stretches broken by spikes (a flood of bugs after release, or sprint planning batching all work into one moment).
Whether items take similar effort or vary widely. "Almost identical" = strict story-point limits keep items close in size. "Wildly different" = mixing tiny one-line bug fixes with multi-week feature work in the same flow.
Time to finish each item
weeks
How busy your team is
%
Time an item spends waiting
days
Items finished per week

Where you are on the curve

As your team gets busier, wait time grows nonlinearly. The dot shows where you are now.