The Team Task Calculator estimates how many tasks a team can complete within a period based on available labor time, average task duration, and an allowance for rework or coordination. It shows both adjusted task capacity and the underlying usable hours.
The estimate is useful for backlog planning, service queues, content production, and other workflows where work units are reasonably repeatable. Because real tasks vary, use an average duration drawn from recent work and update it when the task mix changes.
1. Set team resources
Enter the number of contributors and productive hours available per person.
2. Enter task duration
Use the average hands-on minutes needed for one task.
3. Allow for coordination
Estimate time consumed by handoffs, planning, and internal communication.
4. Account for rework
Enter the share of output likely to need correction or repetition.
5. Use the rounded capacity
The main result counts only fully completed tasks.
The result is the number of finished task units the team can reasonably plan for under the entered average conditions.
The calculation rounds down because a partially completed task is not counted as finished.
Given: 6 members, 30 hours each, 45 minutes per task, 15% overhead, and 8% rework.
Calculation: Gross hours = 6 × 30 = 180. Usable hours = 180 × 0.85 = 153. Task time = 0.75 hour. Initial capacity = 153 ÷ 0.75 = 204 tasks. Adjusted yield = 204 × 0.92 = 187.68.
Result: Plan for 187 completed tasks.
Capacity planning should not count a fraction of a finished task. Remaining time may still contribute to work in progress.
Use a recent sample of comparable tasks and divide total hands-on time by the number completed. Avoid mixing very different task types.
This model reduces expected finished output by the rework percentage after calculating initial capacity.
Only if one point has a stable average time in your team. Story points are usually relative estimates, so task counts are more reliable for repeatable units.
Run separate calculations for groups with similar availability, or enter the team-wide average hours per member.