Agile Estimation Template
Capture more than a number. This reusable template records scope, assumptions and the reasons behind complexity, effort and risk ratings.
How to use the template
Select and copy the text, or use your browser’s Print command for a clean paper copy. No account is needed to use this resource.
Copy the blank version into your issue, team document or meeting notes. Complete the story and scope before collecting ratings. Let participants form their own assessment, then use differences to uncover missing information. Record the final reasoning rather than preserving every intermediate vote.
Agree on a team scale before using it. Consonus uses five rating levels, numbered 1–5, with descriptions for each dimension. Define what those levels mean using reference stories. Keep the dimension ratings distinct from the final estimate and agree on any mapping to story points as a team.
Blank estimation template
- Story and user outcome
- [Who needs what, and why?]
- Scope and boundaries
- [Included work; excluded work; definition of finished]
- Acceptance examples
- [Successful case; failure case; relevant boundary]
- Assumptions and references
- [Known facts; unverified assumptions; comparable completed story]
- Complexity and reasoning
- [Rating on the team scale; rules or interactions behind it]
- Effort / scope and reasoning
- [Rating; implementation, testing, review and documentation]
- Risk and evidence needed
- [Rating; unknowns, dependencies and how to investigate them]
- Differences discussed
- [Different assumptions; what changed after discussion]
- Open questions, owner and next step
- [Question — owner — action — revisit date]
- Final estimate or decision to defer
- [Final ratings; team-configured output and unit, or reason for deferral]
Worked example: CSV export
Illustrative example — not a customer report
- Story and user outcome
- As an account manager, I want to export filtered customer records so I can analyze the selected records outside the application.
- Scope and boundaries
- Export the currently filtered records and permitted fields. Include file generation, error handling, tests and review. Scheduled exports and new data fields are excluded.
- Acceptance examples
- The file contains only filtered records and authorized fields. An empty result is explained. The agreed maximum export size must be verified before the estimate is finalized.
- Assumptions and references
- The existing export mechanism is reusable. The team references a previous internal report export, but customer data volumes may be larger.
- Complexity and reasoning
- Medium: field-level permissions must remain consistent with the filtered view. The team understands the rules but needs integration tests.
- Effort / scope and reasoning
- Large: the implementation pattern is familiar, but several permission combinations and failure paths need tests.
- Risk and evidence needed
- High: behavior at the maximum agreed data volume is unverified. Check execution time and failure handling with representative data.
- Differences discussed
- The lower initial rating assumed only small exports. The team now shares the same data-volume question and includes permission testing in scope.
- Open questions, owner and next step
- Can the existing mechanism handle the agreed maximum dataset? A designated developer checks this before the next refinement and shares the findings.
- Final estimate or decision to defer
- Not yet estimated. Revisit risk after the data-volume check, then agree on final ratings and use the team’s configured mapping.
The example deliberately ends with a decision to investigate. A completed template does not have to contain a numerical estimate when a consequential assumption remains unresolved. Once evidence is available, update the same record instead of starting a disconnected discussion.
Use it with your existing workflow
Use the template alongside Planning Poker or a Consonus session. Keep the full notes in your issue or team document. In Consonus, add a brief summary to the story description and link to the detailed notes. Then collect the ratings, discuss their distributions and update the notes with the team’s decisions.
Keep only the detail needed for a useful decision. For familiar, small work, short notes may be sufficient. For uncertain work, spend the effort on clarifying the unknowns rather than filling every line with confident-sounding guesses.
Ready for clearer estimates?
Bring one story to Consonus. Compare your team’s complexity, effort and risk ratings, discuss the different assumptions and agree on your next step.
Free during public preview. No payment details required.