Scope and assumptions
Completion % = completed items ÷ total items × 100. For weighted work, see weighted percentage. Illustrative.
Three of ten tasks done reads as 30% complete, and that number is behind almost every progress bar you've watched. It's honest arithmetic — and it can be badly misleading, because it counts items rather than effort.
A project where the remaining seven tasks include the two biggest pieces of work is not 70% outstanding. It's usually much more.
Done over total
Completion % = (completed ÷ total) × 100 Remaining % = 100 − completion %
| Total tasks | Done | Complete | Remaining |
|---|---|---|---|
| 10 | 3 | 30% | 70% |
| 20 | 5 | 25% | 75% |
| 4 | 4 | 100% | 0% |
When one task outweighs the rest
Item counting assumes tasks are interchangeable. They rarely are. Three finished small tasks against one enormous one shows 75% complete by count and perhaps 15% by effort.
The fix is to weight each task by the work it represents — hours, story points, or cost — and divide completed weight by total weight:
| Task | Weight | Done | Weight completed |
|---|---|---|---|
| A | 10 | yes | 10 |
| B | 5 | yes | 5 |
| C | 30 | no | 0 |
| D | 5 | no | 0 |
| Total | 50 | 15 / 50 = 30% |
Two of four items are done, but the weighted figure is still 30% — because the dominant task C hasn't started. That's a far more useful picture than "50% complete."
The tail that never ends
Projects routinely sit at "90% done" for weeks. The cause is structural: the last stretch is made of many small tasks — bug fixes, reviews, edge cases — each counting as one item and each taking far longer than its size suggests. Item-based percentages flatten this; weighted percentages expose it.
Where progress percentages go wrong
Counting items when effort varies wildly; forgetting the ×100; reporting remaining as complete; letting scope creep without recomputing the denominator, so the number drifts upward while the project grows; treating a blocked task as done; and averaging task-level percentages instead of weighting them by size.
FAQ
How do I handle tasks added mid-project? Recompute the denominator. Adding scope without updating the total makes the percentage look like progress when it's actually regression.
What's the difference between percent complete and earned value? Percent complete counts what's done; earned value converts that into budget terms by multiplying by the planned cost of the completed work.
Why does the last 10% of a project take so long? Short tasks dominate the tail — fixes, reviews, and edge cases each count as one item but consume disproportionate effort. Counting items hides this.
Should blocked tasks count as complete? No. A blocked task is open work. Counting it as done is the most common way a progress bar lies.
Sources: Khan Academy, Ratios; project-management guides.
Disclaimer: Illustrative. Informational only.
Sources and references
- Khan Academy — Ratioshttps://www.khanacademy.org/math