Task Completion Estimator
Borrowing Agile's Burn-Rate Math for Any Kind of Work
Agile teams have used velocity — how much work gets done per sprint, week, or day — to forecast finish dates for decades, and the same idea scales down to a single freelancer or a personal project list. Instead of guessing "it'll probably be done sometime next week," dividing remaining work by a measured rate of progress gives an actual number of periods left, grounded in how fast you've actually been moving, not how fast you hope to move.
The Formula
Velocity is whatever unit you're measuring — tasks per day, story points per sprint, pages per hour — as long as remaining work is expressed in the same unit. The result is the number of periods left at the current pace.
Where This Estimate Is Useful
- Sprint forecasting — teams use exactly this division to answer "will the backlog be done by the release date?" using the last few sprints' measured velocity.
- Freelance and project deadlines — if you've completed 40 of 200 pages of a document in 4 days, your velocity (10 pages/day) projects a real finish date for the rest.
- Spotting a slipping timeline early — recalculating velocity partway through a project flags a slower-than-planned pace long before the deadline arrives.
| Remaining work (units) | Velocity (units/period) | Estimated periods left |
|---|---|---|
| 40 | 10 | 4.0 |
| 80 | 8 | 10.0 |
| 120 | 15 | 8.0 |
| 200 | 25 | 8.0 |
Computed as remaining work ÷ velocity, rounded to two decimals.
How to Use This Calculator
- Enter the Remaining Work in whatever units you're tracking (tasks, points, pages, units).
- Enter the Current Velocity — units completed per period, based on recent actual progress.
- Select Calculate to see the estimated number of periods left to finish.
Related Calculations
Track whether you're hitting planned targets along the way with the Productivity Tracker.