agile ceremonies


Someone other than the team or product lead should facilitate. Sharing the facilitation around the team keeps retrospectives fresh, encourages greater participation, and uncovers more inconvenient truths.

Set the boundary of the discussion and be clear how far back the team is going to go:

The team does retrospectives because they provide a roll-up summary for project post mortems and we know that without them projects turn into death marches. Having a reserved period of time allows us to inspect, adapt and improve our processes and techniques. We value working smater, not harder.


standard play:

the four l's:

map out the past two months (10 min):

sprint kick-off

The purpose of this meeting is to agree upon which work will be done, at a high level agree how it will be done and incorporate learnings from the retrospective. If the refinement has been done successfully then there should be minimal definition activities during kick-off.


define the scope:

plan the execution:



The purpose of this meeting is to identify risk, define what work will be done in the future and inspect progress of the current sprint.


plan for the future:

inspect the sprint:


As a team we get together daily to share learnings, call out risk and ask for help. We do this to help us to achieve the sprint goal.