Method wall › Ceremonies
Ceremonies
Method cards filed under Ceremonies.
Ceremonies
The Daily Standup Is About Flow Not Status Reporting
CeremonyDaily standup (daily scrum) plus sprint planning, sprint review, and sprint retrospective in Scrum; in Kanban, the daily standup is joined by replenishment and delivery reviews as needed.
RolesScrum: product owner, scrum master, developers. Kanban: no mandated roles, though a service manager or flow manager may be designated.
ArtifactsScrum: product backlog, sprint backlog, increment. Kanban: visual board, work-in-progress limits, flow metrics.
CadenceScrum: fixed-length sprints, usually one to four weeks. Kanban: continuous flow with no fixed iteration.
The daily standup is often treated as a status meeting where each person reports what they did yesterday and what they will do today.
Ceremonies
Sprint Planning Sets a Goal Not a Frozen Contract
CeremonySprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, and backlog refinement.
RolesProduct Owner, Scrum Master, Developers (the team).
ArtifactsSprint Goal, Sprint Backlog, Increment, Definition of Done.
CadenceTimeboxed sprints, commonly one to four weeks, with a fixed length per team.
Sprint Planning is the ceremony that opens a sprint.
Ceremonies
The Sprint Review Shows Working Software to Real Users
CeremonySprint Review, typically a timeboxed meeting at the end of each sprint, often lasting one to four hours depending on sprint length.
RolesProduct Owner, Scrum Master, Development Team, stakeholders, and real users who provide feedback.
ArtifactsWorking software increment, updated Product Backlog, and feedback captured for future backlog refinement.
CadenceSprint length of one to four weeks, with the Sprint Review occurring at the end of each sprint.
The Sprint Review is a recurring ceremony in Scrum where the Development Team shows a working software increment to stakeholders and real users.
Ceremonies
A Retrospective Only Works When Safety Comes First
CeremonyRetrospective meeting, plus the daily coordination meeting, sprint review, and sprint planning that surround it
RolesFacilitator, product owner, development team members, and a scrum master or coach who protects the process
ArtifactsRetrospective board or notes, action items with owners, and the team working agreement
CadenceOne retrospective per iteration, typically every one to four weeks, often after a review
A retrospective is a recurring ceremony where a team pauses after a period of work to examine how it worked together, not just what it built.