The ys behind the ceremonies

1. May 29, 2015

2. AGENDA
Kickoff Activity
Backlog Refinement
Daily Scrum/Standup
Retrospective/Kaizen
Sprint Planning
Sprint Review
Final Thoughts and Close

3. Form groups and collaborate on the Purpose and Desired
Outcomes of each ceremony.
We will give you 3 minutes for each ceremony to discuss in your
group.

4. Refinement or Grooming
Purpose:
 To gain a relative understanding of the requirements
 Identify technical uncertainties and/or dependencies
 Acceptance Criteria is negotiated and the DevTeam is able to estimate
the work
Outcome
 Prioritized and estimated PBIs for the next 1-3 sprints
 Fewer surprises at Sprint Planning
 Decomposed and/or elaborated stories/PBIs that enables consistent
estimation

5. Daily Scrum or Standup
Purpose
 Synchronization and daily planning activity
 Identify any impediments and hold each other accountable
 A key inspect and adapt meeting
Outcome
 DevTeam has a clear understanding of the day’s work and where there
are any impediments
 DevTeam members work collaboratively helping each other complete
stories and/or remove impediments
 Ownership of this meeting belongs to…

6. The Retrospective or Kaizen
Note: Retrospective is Scrum, Kaizen is Kanban
Purpose
 Reflect on how the team is working
 Inspect the team’s processes and team dynamics in order to adapt and
improve
Outcome
 A ranked list of improvements that the team agrees is important to adjust
 Agreement to address the top 1 or 2 items
 A hypothesis, recommend an ‘experiment’, validate results

7. Sprint Planning
Note – Specific to Scrum
Purpose
 To task out the work necessary to achieve a the team’s DoD for the
specified Sprint Goal
Outcome
 A sprint plan that the DevTeam understands and commits to deliver in
the specified sprint duration

8. Sprint Review
Note – Specific to Scrum
Purpose
 To demonstrate each product increment to our product owner and
stakeholders
 To build confidence in the customer and to gain valuable feedback from
them on the direction of the product and any necessary changes
Outcome
 Acceptance that each story and/or PBIs have met our UACs and gain the
approval of our PO
 Potentially new stories for the backlog based on the valuable feedback
provided

9. How can I keep this all straight?
 We have coaching cards available to you
 Agile Sharepoint site under Training->Coaching Cards
Need help?
How can you help?