Synerzip Agile Cheat Sheet


of 1

  • date post

  • Category

  • view

  • download


Embed Size (px)




  • 1. Roles Artifacts Meetings AGILE CHEAT SHEET * Scrum Team Product Backlog - (PB) Sprint Planning - Day 1 / First Half Estimating Scrum teams are self organizing. Maintained by the Product Owner Product backlog prepared prior to meeting User Stories Team is cross-functional and consists of 5-9 List can contain bugs, and non-functional items First half - Team selects items committing to complete people Product Owner responsible for prioritizing Additional discussion of PB occurs during actual High level definition of user requirements There are no set project roles within the team Items can be added by anyone at anytime Sprint that serves as a starting point for discussion. Team defines tasks and assignments Each item should have a business value assigned Building blocks that can be assigned priorities, Usually Dev : QA ratio is 3:1. Team develops the List of all desired product features Sprint Planning - Day 1 / Second Half estimates, completion status. product as per sprint backlog Product backlog can be organized as a prioritized list Large user stories (Epics) that take longer than a Occurs after half done - PO available for questions sprint to build are broken into smaller user stories. Ensures team works on highest valued features of user stories in order of high-risk, high-value, low- Team solely responsible for deciding how to build risk, high-value, low-risk, low-value User stories are NOT dependent on other stories Tasks created / assigned - Sprint Backlog produced Story Template: As a I want Product Owner - (PO) Daily Scrum So that Sprint Backlog - (SB) Story Example: As a user, I want to print a recipe Accountable for product success Held every day during a Sprint so that I can cook it. Defines all product features To-do list (also known as Backlog item) for the Sprint Lasts 15 minutes Responsible for prioritizing product features Created by the Scrum Team Team members report to each other not to Scrum Story Points Maintains the Product Backlog Product Owner has defined as highest priority Master Story points indicate relative degree of difficulty Ensures team works on highest valued features Answers 3 questions during meeting One full time product owner for every scrum team Burndown Chart - (BC) and they follow the Fibonacci series because it What have you done since last daily scrum? represents a set of numbers that we can intuitively Chart showing how much work remaining in a Sprint What will you do before the next daily scrum? distinguish between them as different magnitudes What obstacles are impeding your work? Scrum Master - (SM) Calculated in hours remaining Example: Send to a Friend Story Points = 2 Maintained by the Scrum Master daily Opportunity for team members to synchronize their Shopping Cart Story Points = 8 Holds daily 15 minutes team meeting (Daily Scrum) Maintain seperate account of work remaining out of the work Advanced Search Story Points = 13 Removes road blocks Original RB and New Features added during the Having daily scrum over a conference call in Facilitates planning and estimation release distributed teams is not advisable. Business Value Maintains the Sprint Burndown Chart Distributed teams are advised to break in multiple Each User Story in the Product Backlog should have Conducts Sprint Retrospective at the end of every Release Backlog - (RB) colocated teams. a corresponding business value assigned. Sprint Typically assign (L, M, H) Low, Medium, High Maintains team spirit Same as the Product Backlog. May involve one or Sprint Review PO prioritizes Backlog items by the highest value Typically one scrum master can handle two scrum more sprints dependent on determined Release date User Stories can be classified as Must have, teams Team presents done code to PO and stackeholders Should have, Could Have, Good to have DONE= Potentially Shippable! Functinality not done is not shownTDD = Refactoring + TFD Feedback generated - RB may be reprioritized. Planning Poker FAQ Scrum Master sets next Sprint ReviewRefactor code 3a Testing via xUnit Framework Cards bearing Fibonacci numbers[tests unbroken] are distributed to all team menbers. Story is Who decides when a Release happens? At the end Sprint Retrospective of any given Sprint the PO can initiate a Release. discussed and team members put down the card 3b Refactor code Refactor code [Test(s) broken]