Sprint Review
The increment shown to users and stakeholders.
Why it matters
Users seeing real changes early catches problems before release.
- When
- Every 2 weeks
- 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):
- Ways of working playbook: principles, behaviours and team structure · Playbooks
- Ways of working playbook: roles, governance and operating rhythm · Playbooks
- Product-level events overview · Runbooks
- Sprint retrospective runbook · Runbooks
- Sprint review runbook · Runbooks
- Team sprint events: overview and schedule · Runbooks
- Initiative information pack · Templates
- Sprint test summary · Reporting packs
- Team cycle reporting pack · Reporting packs
- Team sprint report · Reporting packs
- Pulse Cycle and sprint cadence calendar · Guides
- RACI for product delivery · 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