Backlog Refinement
Stories ready for the next sprint, each with acceptance criteria written as scenarios (Given, When, Then), tests written before the build, and story points: 1 (XS), 3 (S), 5 (M) or 8 (L). Anything bigger is XXL and is broken down first. Service requests and small changes are assessed and pointed here too. Story points add up within the feature’s size: S up to 15, M up to 30, L up to 40.
Why it matters
Well-prepared stories make planning quick and delivery predictable.
- When
- Every sprint
- Length
- 1 hour
- Led by
- Product Owner
- Draws on
- Scrum
Draws on
Led or owned by
In the resource library
Ready-to-use resources in the DelPulse workspace (sign in to open them):
- Planning readiness by week and role · Playbooks
- Ways of working playbook: roles, governance and operating rhythm · Playbooks
- Backlog refinement runbook · Runbooks
- Estimation · Runbooks
- Product-level events overview · Runbooks
- Sprint planning runbook · Runbooks
- Team sprint events: overview and schedule · Runbooks
- Test case review · Checklists
- Data requirements template · Templates
- Initiative information pack · Templates
- Test case · Templates
- User story template · Templates
The rest of this page is for subscribers
Subscribe to read the other 4 sections of this page:
- How to run it
- Rules
- In the DelPulse workspace
- If you use Jira or Azure DevOps