How to use the Project Effort Estimate Generator.
Effort estimates should expose uncertainty and use relevant reference tasks. Split unknown work from work the team has performed before.
Make the workflow fit your task.
Break the work into known components and uncertain investigations, using relevant past tasks as references. Give ranges or assumptions where appropriate and explain what evidence would narrow the estimate.
- What you provide
- Work packages, historical reference tasks and stated assumptions.
- What you get
- Bottom-up effort ranges with uncertainty and missing inputs.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
A familiar page takes six hours; a new integration has unknown authentication requirements.
Completed example
Estimate the known page work separately and propose an authentication investigation before committing to integration effort.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should unfamiliar integration work receive the same estimate as a familiar page?
No. Identify the unknown authentication, data or operational requirements before treating the tasks as comparable.
Why does the estimate change sharply after work starts?
Check whether unresolved dependencies were hidden inside a single number. Record uncertainty and use discovery to reduce it.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑