O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Scrum Cheat Sheet

2.282 visualizações

Publicada em

Publicada em: Tecnologia, Esportes
  • Seja o primeiro a comentar

Scrum Cheat Sheet

  1. 1. WWW.AGILE42.COMScrum Cheat Sheet by agile42Product Owner Sprint Planning Product BacklogOwns the Product Backlog Commit the deliverable(s) to the PO Dynamic prioritized list of requirementsThe Product Owner represents the Two part meeting. First, the PO presents The requirements for the product areinterests of everyone with a stake in the the User Stories. Second, when the Team listed in the Product Backlog. It is anproject (Stakeholder) and he is thinks they have enough Stories to start always changing, dynamically prioritizedresponsible for the final product. the Sprint, they begin breaking it down in list of requirements ordered by Business Tasks to fill the Sprint Backlog (normally 3 Value. Requirements are broken down• elicit product requirements to 4 days of work, than inspect & adapt). into User Stories by the PO.• manage the Product Backlog Prioritize the requirements by Timebox: 4 hours• manage the release plan Owner: Product Owner playing the Business Value game.• manage the Return on Investment Participants: Team, Scrum Master Buy these at www.agile42.comScrum Master Daily Scrum Burndown ChartOwns the Scrum process Inspect and Adapt the progress Displays the remaining workThe Scrum Master is responsible for the In this standup meeting the Team daily The Burndown chart shows the amount ofScrum process. He ensures everybody inspects their progress in relation to the work remaining per Sprint. It is a veryplays by the rules. He also removes Planning by using the Burndown Chart, useful way of visualizing the correlationimpediments for the Team. The Scrum and makes adaptation as necessary. between work remaining at any point inMaster is not part of the Team. Timebox: 15-20 minutes time and the progress of the Team(s).• manage the Scrum process Owner: Scrum Master Use a tool such as Agilo to automatically• remove impediments Participants: Team, all interested create the Burndown Chart.• facilitate communication parties may silently attend. Learn more at www.agile42.comDevelopment Team Sprint Review Sprint BacklogOwns the software Demonstrate the achievements List of Tasks to fulfill the Sprint GoalThe team figures out how to turn the The team demonstrate the PO the result - The Sprint Backlog contains all theProduct Backlog into an increment of on the developed product - of the Sprint. committed User Stories for the currentfunctionality within a Sprint. Each team The PO can accept or reject features Sprint broken down into Tasks by themember is jointly responsible for the depending on the agreed acceptance Team. All items on the Sprint Backlogsuccess of each iteration and of the criteria. should be developed, tested, documentedproject as a whole. and integrated in order to fulfill the Sprint Goal. Timebox: 4 hours• software quality Owner: Team• technical implementation of User Stories Estimate Story complexity by playing Participants: Scrum Master, Product• delivery of a “potentially shippable” Planning Poker. Owner, optionally the PO can invite product increment at every Sprint Buy these at www.agile42.com other Stakeholders________________________ Retrospective _________________________Requirements Maintain the good, get rid of the bad Potentially Shippable ProductMake SMART Requirements: Simple,Measurable, Achievable, Realistic, At the end of a Sprint, the Team Scrum requires at the end of each SprintTraceable. evaluates the finished Sprint. They that the product is potential shippable to capture positive ways as a best practice, the customer. That means the incrementUser Stories identify challenges and develop is:INVEST in User Stores: Independent, strategies for improvements. • thoroughly tested and stableNegotiable, Valuable, Estimable, Small, • well-structuredTestable. Timebox: 3 hours • well-written code Owner: Scrum Master • user operation of the functionality isTasks documented Participants: Team, (Product Owner)Make sure a Task is TECH. Time boxed,Everybody (can pick it up), Complete andHuman-readable. agile42 - www.agile42.com - all rights reserved © 2009