Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
SlideShare a Scribd company logo

The ys behind the ceremonies

•Download as PPTX, PDF•
•
T
TheAgileDen

This document provides an overview of the agenda and purpose of various agile ceremonies, including backlog refinement, daily standup, retrospective, sprint planning, and sprint review. It discusses forming groups to discuss the purpose and desired outcomes of each ceremony. For each ceremony, it lists the purpose as gaining a shared understanding of requirements, identifying uncertainties, negotiating acceptance criteria, prioritizing backlog items, synchronizing work and identifying impediments, reflecting on and improving processes, tasking out sprint work, and demonstrating product increments for feedback. The desired outcomes include estimated backlog items, fewer surprises, elaborated stories, understanding of daily work and impediments, agreed-upon process improvements, a committed sprint plan, and accepted stories and new

1 of 10
May 29, 2015
AGENDA Kickoff Activity Backlog Refinement Daily Scrum/Standup Retrospective/Kaizen Sprint Planning Sprint Review Final Thoughts and Close
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.
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
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…
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
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
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
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?
The ys behind the ceremonies

More Related Content

The ys behind the ceremonies

  • 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?

Editor's Notes

  1. Explain the 3C’s (Card, Conversation, Confirmation) DEEP Backlog mnemonic (Detailed appropriately, Estimated, Emergent, Prioritized) Tools – Planning poker, Affinity Estimation, Consider for sizing LOE, Complexity, Uncertainty) DoR
  2. Not a status meeting Team norms? Defined DoD is visible Approaches to this Smells like a STATUS meeting Principle #4 – work together daily
  3. Don’t change for the sake of change Have a clear understanding of what success should look like What problem are you trying to solve? Hits principle #12
  4. Capacity and average velocity needs to be understood Stories completed (developed, tested and documented) as quickly as possible during sprint Key is consistent backlog grooming
  5. Hit principle #1 – highest priority is to satisfy the customer through early and continuous delivery of valuable software Hits principle #2 – welcome changing requirements, even late in the development. Agile processes harness change for the customer’s competitive advantage
  6. You have a responsibility to ensure that the purpose and outcomes are being met