Execution · Playbook
Sprint & Delivery Cadence Playbook
Planning, stand-up, review and retro agendas mapped onto PMBOK control.
The problem it solves
The team runs ceremonies because they were told to, and reporting upward is a separate manual effort.
How to run it
- 1Pick the iteration length and never change it mid-project.
- 2Use the four agendas as written for three iterations before adapting.
- 3Derive the steering report directly from the review — do not build a second reporting layer.
- 4Track one flow metric: completed items per week.
- 5Review the cadence itself every quarter.
What's inside
- Four ceremony agendas with time boxes
- Mapping table: Agile ceremony → PMBOK control activity
- Reporting derivation guide
- Facilitation anti-patterns
Related downloads
Get this template
Sent as an editable document. No account, no drip sequence.
Want this facilitated with your team rather than filled in alone? I run these as a 90-minute session — free, no obligation.
Related templates
Work with me
Sometimes the fix needs a person, not a template.
I am Tigran Zakarian, a senior project manager with 13 years of end-to-end delivery for clients such as H&M Group, TV4, SEB and Clear Channel. I work on exactly the situations described across this site: rescuing drifting deliveries, setting up governance that people actually use, and facilitating the workshops that unblock decisions.
Projects & programmes
- Interim / rescue project management
- Programme & multi-team delivery ownership
- PMO, governance and steering setup
- Product ownership & backlog clarity
Workshops
- Risk analysis workshops
- Planning and prioritisation sessions
- Decision and stakeholder alignment
- Retrospectives that change something
Talks & training
- Educational talks and keynotes
- Hybrid PMBOK + Agile training
- Kanban / flow ways of working
- Team coaching for new PMs