Developer Throughput

A simple flow metric. Prefer consistent item types (stories, tickets)—not a universal productivity score.

Items per developer per period = completed ÷ (devs × periods).

Tip: Keep “Completed Items” and “Developers” on the same basis (units, period, and definition) before you calculate.

Cluster: Software Development hub · DevOps hub · Percentage guide

Developer throughput averages completed work items per developer per period (sprint/week).

Enter completed items, developer count, and number of periods.

Stories/tickets completed
FTE developers in the team
Number of periods measured

Throughput per Developer

Understanding Developer Throughput

How we calculate. Items per developer per period = completed ÷ (devs × periods). See our methodology and accuracy policy .

Real-world scenario: A typical Developer Throughput case uses completed items 120 and developers 8. Enter the same figures below to reproduce the worked path.

What is Developer Throughput?

A simple flow metric. Prefer consistent item types (stories, tickets)—not a universal productivity score.

  • Same item definition across periods
  • FTE developers in the denominator
  • Not a performance weapon—context matters

The Formula

Developer Throughput
Throughput = Completed items ÷ (Developers × Periods)

Worked Example

Scenario: 120 items completed by 8 developers over 5 sprints.
Step 1: 120 ÷ (8 × 5) = 120 ÷ 40 = 3
Answer: Throughput is 3 items per developer per sprint.

Common Use Cases

  • Capacity planning: forecast load
  • Team compare: similar work types only
  • Hiring plans: rough demand

Pro Tips

  • Normalize item size when possible
  • Exclude PTO distortion
  • Pair with cycle time
ScenarioWhen to use
Percent of a numberFinding a part of a whole (tax, tip, score)
Percent changeComparing old vs new values

Limitations: Developer Throughput results are educational software estimation aids—not bids, contracts, or performance scores. Calibrate models to your organization’s history.

Common mistakes

  • Swapping part and whole: The denominator must be the full total, not a subset.
  • Rounding too early: Carry extra decimal places through multi-step work before rounding the final percent.
  • Mixing percent and decimal forms: Enter rates in the format the calculator labels expect.

The worked example for developer throughput was verified with the calculator form on this page—enter the same values to confirm the result.

When to use this calculator

  • Use this page when your wording matches developer throughput and the form labels on screen.
  • Use percent of a number for “what is X% of Y?” problems.
  • Use number is what percent when you know part and whole and need the percent.

Still unsure about developer throughput? Start with the quick answer above, then open the linked calculator that matches your wording.

Frequently Asked Questions

How do I use this developer throughput calculator?

For developer throughput, enter the values labeled on the form, then press Calculate. Compare the result to the worked example on this page.

What formula does this page use?

See the quick answer and formula box above for developer throughput—the same percentage calculator expression is applied to your inputs.

What if my result looks wrong?

When checking developer throughput, re-check part vs whole (or rate vs base), rounding, and whether percents were entered as 25 rather than 0.25 when the form expects percents.

Authoritative References

For estimation and quality models, consult: