The estimate includes coding but not testing or rework. How should we revise it?
Incomplete work estimateEstimate the complete path to accepted delivery, including review, testing, corrections, and documentation where needed. Do not use construction effort as the forecast for a finished result.
What to do now
- Define the acceptance boundary
- Break out omitted work
- Estimate with the people doing each step
- Reforecast the complete deliverable
When to escalate
The complete estimate no longer fits the authorized deadline or budget.
The project manager and relevant commitment owner
Example
A two-day feature build becomes a five-day delivery forecast after integration tests and review are included.
Mistake to avoid
Adding a generic testing percentage without checking the actual work.
Prevent a repeat
Compare forecast versus actual results for comparable tasks, separating effort, elapsed time, waiting and scope change.
Suggested ApprovedFlow setup
- Tasks
- Timesheets
- Resources
Keep planned dates and assumptions with the affected task, compare recorded actuals, and attach the revised forecast for review. See the platform
Related cases
- Our team repeatedly starts work before dependencies are ready. How do we stop rework?Premature task starts
- How do we estimate work we have never done before?High-uncertainty estimation
- Can I use an AI estimate as the project commitment?Unvalidated model-generated estimate
- How do we forecast the final project cost?Incomplete cost-to-complete forecast