Team Productivity Index Calculator
Measures how many tasks each team member completes per hour worked. Use it during sprint reviews or project retrospectives to benchmark and compare team output over time.
About this calculator
The Team Productivity Index measures the average number of tasks completed per person per hour. The formula is: Productivity Index = tasksCompleted / (hoursWorked / teamSize). First, dividing total hours worked by team size gives the average hours each person contributed. Then dividing total tasks completed by that figure yields tasks per person-hour. A higher index means each team member is completing more tasks in less time. This metric is particularly useful when comparing productivity across sprints, projects, or teams of different sizes, because it normalises both headcount and time investment. Keep in mind that task complexity can vary widely, so pair this index with a quality metric for a fuller picture.
How to use
Suppose your team of 5 people completed 40 tasks after logging a combined 100 hours. Step 1 — Calculate average hours per person: 100 ÷ 5 = 20 hours per person. Step 2 — Calculate the Productivity Index: 40 ÷ 20 = 2.0 tasks per person per hour. This means each team member is completing 2 tasks every hour on average. If next sprint the same team completes 50 tasks in 100 hours, the index rises to 2.5, indicating a 25% productivity improvement.
Frequently asked questions
What is a good team productivity index score to aim for?
There is no universal benchmark because the index depends heavily on how tasks are defined and scoped. A useful approach is to establish your own baseline over two or three sprints and then track whether the number trends upward. Consistent improvement sprint-over-sprint is a stronger signal than any absolute number. Many agile teams aim for a 10–20% improvement per quarter once a baseline is set.
How does team size affect the productivity index calculation?
Team size is used to normalise the total hours worked, so the index reflects output per person rather than raw team output. A larger team naturally logs more hours in total, which could inflate the denominator unfairly without this normalisation. By dividing total hours by team size first, the formula puts teams of different sizes on equal footing. This makes cross-team comparisons meaningful rather than misleading.
Why should I track productivity index alongside quality metrics?
The productivity index only measures the quantity of tasks completed per person-hour, not whether those tasks were done correctly. A team could score a high index by rushing through work and generating numerous defects. Pairing this metric with defect density or a rework rate gives a balanced view of both speed and quality. Together they help managers identify whether a productivity gain is sustainable or is simply borrowing against future rework time.