Refinement Meeting Checklist
Use this checklist to prepare a focused conversation, clarify user stories and leave with decisions the team can act on. Adapt it to your context rather than treating every item as a gate.
Before the meeting
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.
- Select a manageable set of upcoming items with the Product Owner and state why they matter now.
- Write down the user problem and intended outcome for each item.
- Share draft acceptance criteria, designs and relevant technical context in advance.
- Identify known dependencies and invite people who can answer critical questions.
- Choose reference stories if the team plans to estimate, and make them available.
- Agree on a facilitator and a place to capture decisions and open questions.
For each story
- Explain who benefits and what changes for that person when the story is done.
- Confirm what is included and explicitly exclude adjacent work that belongs elsewhere.
- Discuss an example of success, a relevant failure case and an important boundary condition.
- Check permissions, data needs, accessibility and operational concerns where they affect the story.
- Name dependencies, unverified assumptions and questions that require investigation.
- Consider splitting the item if it contains several outcomes or cannot be understood well enough.
Before agreeing on an estimate
- Confirm that everyone is assessing the same scope and definition of finished work.
- Ask developers to consider complexity, effort and risk separately before discussing differences.
- Compare assumptions behind differing ratings; do not simply average the numbers.
- Record the reason for the final estimate and any remaining uncertainty.
- If information is insufficient, record “not yet estimated” with the question and a responsible person.
An unanswered question does not always prevent estimation. Decide whether it could materially change the scope or solution. If it could, guessing a precise-looking value can hide more than it helps.
After the meeting
- Update backlog items with agreed acceptance examples, boundaries and decisions.
- Assign each follow-up question an owner and a date or event for revisiting it.
- Make the results available to people who did not attend.
- Identify which stories are understood well enough for upcoming planning and which need more work.
- Ask what the session clarified and what would make the next refinement more useful.
Use the checklist as a conversation aid
For the CSV export example, the most important unchecked item may be the maximum supported dataset, not the final point value. Use the checklist to expose that missing decision, assign an investigation and return to the story with evidence. Consonus can support the rating discussion once the relevant scope is clear.
This is a suggested working aid, not an additional Scrum rule or a mandatory approval process. Keep the parts that help your team make useful decisions.
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.