Estimated vs Executed compares the estimated effort on completed items to the actual time those items consumed. It's the most direct measure of estimation accuracy across a period.
What it measures
The ratio (or signed delta) between Estimated Hours and the actual executed time on completed items.
How Leanmote calculates it
estimated_vs_executed = estimated_hours / executed_hours
executed_hourstypically uses Done Active Time or logged work, depending on your workflow configuration.Reported as a ratio (1.0 means estimates matched reality), or as a delta percentage.
How to interpret it
Ratio above 1.0 — your team estimates more time than work consumes. Could be padding, or could mean efficient delivery.
Ratio below 1.0 — actual work is exceeding estimates. Common in teams that don't include review/QA/deploy in estimates.
Stable around 1.0 across periods — estimates are well-calibrated.
What to do about it
Don't react to single-period swings. The signal is in 4–8 week trends.
If consistently below 1.0, expand the scope of "estimate" to include review and QA.
If wildly inconsistent, the team is probably mixing estimate units or item types — split by item type and re-check.
Related metrics
Estimated Hours
Invested Hours
Sprint Efficiency