Sprint Planning
A sprint goal and sprint backlog. Dependencies other teams have requested are agreed or declined here.
Why it matters
A clear sprint goal keeps a small team focused on what matters most.
- When
- Every 2 weeks
- Length
- 2 hours
- 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
- Sprint planning runbook · Runbooks
- Sprint retrospective runbook · Runbooks
- Team sprint events: overview and schedule · Runbooks
- After Pulse Cycle planning: checklist and activities · Checklists
- Cross-product dependency and risk registers, and capacity calculator · Templates
- User story template · Templates
- Team sprint report · Reporting packs
- New starter induction for product teams · Guides
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