Retrospective
One or two improvements for the next sprint.
Why it matters
Small, regular improvements compound into a much better team.
- When
- Every 2 weeks
- Length
- 1 hour
- Led by
- Delivery Manager
- Draws on
- Scrum; Lean
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
- Sprint planning runbook · Runbooks
- Sprint retrospective runbook · Runbooks
- Sprint review runbook · Runbooks
- Team sprint events: overview and schedule · Runbooks
- Product cycle review one-pagers · Reporting packs
- Team sprint report · Reporting packs
- New starter induction for product teams · Guides
- Pulse Cycle and sprint cadence calendar · Guides
- RACI for product delivery · Guides
- Team board states and exit criteria · 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