Scrum cheatsheet
8 likes3,583 views
This document provides definitions and explanations of key terms and artifacts used in Scrum project management. It describes the product backlog, sprint backlog, daily scrum, sprint planning meeting, sprint review, and sprint retrospective. It also outlines the roles of the product owner, scrum master, and scrum team, and includes a glossary of additional Scrum terms.
Scrum cheatsheet
- 1. Artifacts To-do list (also known as Backlog item) for the Sprint Created by the Scrum Team Product Owner has defined as highest priority Sprint Backlog – (SB) Chart showing how much work remaining in a Sprint Calculated in hours remaining Maintained by the Scrum Master daily Burndown Chart – (BC) Same as the Product Backlog. May involve one or more sprints dependent on determined Release date Release Backlog – (RB) Meetings Product backlog prepared prior to meeting First half – Team selects items committing to complete Additional discussion of PB occurs during actual Sprint Sprint Planning – Day 1 / First Half Team presents “done” code to PO and stakeholders Functionality not “done” is not shown Feedback generated - PB maybe reprioritized Scrum Master sets next Sprint Review Sprint Review Occurs after first half done – PO available for questions Team solely responsible for deciding how to build Tasks created / assigned – Sprint Backlog produced Sprint Planning – Day 1 / Second Half Held every day during a Sprint Lasts 15 minutes Team members report to each other not Scrum Master Asks 3 questions during meeting “What have you done since last daily scrum?” “What will you do before the next daily scrum?” “What obstacles are impeding your work?” Opportunity for team members to synchronize their work Daily Scrum Estimating “DONE”= Potentially Shippable! List of all desired product features List can contain bugs, and non-functional items Product Owner responsible for prioritizing Items can be added by anyone at anytime Each item should have a business value assigned Maintained by the Product Owner Product Backlog - (PB) SCRUM CHEAT SHEET Attendees – SM and Team. PO is optional Questions – What went well and what can be improved? SM helps team in discovery – not provide answers Sprint Retrospective Roles Accountable for product success Defines all product features Responsible for prioritizing product features Maintains the Product Backlog Insures team working on highest valued features Product Owner (PO) Holds daily 15 minute team meeting (Daily Scrum) Removes obstacles Shields the team from external interference Maintains the Sprint Burndown Chart Conducts Sprint Retrospective at the end of a Sprint Is a facilitator not a manager Scrum Master (SM) Team is cross-functional and consists of 5-9 people There are no set project roles within the team Team defines tasks and assignments Team is self-organizing and self-managing Maintains the Sprint Backlog Conducts the Sprint Review Scrum Team FAQ Who decides when a Release happens? At the end of any given Sprint the PO can initiate a Release. Who is responsible for managing the teams? The teams are responsible for managing themselves. What is the length of a task? Tasks should take no longer than 16 hours. If longer then the task should be broken down further. Who manages obstacles? Primary responsibility is on the Scrum Master. However, teams must learn to resolve their own issues. If not able then escalated to SM. What are two of the biggest challenges in Scrum? Teams not self-managing, Scrum Master managing not leading. White Board containing teams Sprint goals, backlog items, tasks, tasks in progress, “DONE” items and the daily Sprint Burndown chart. Scrum meeting best held around task board Visible to everyone Task Board Tools Process Shippable Product Sprint Review Sprint Daily Scrum Sprint BacklogProduct Backlog Sprint Planning Sprint Retrospective A very high level definition of what the customer wants the system to do. Each story is captured as a separate item on the Product Backlog User stories are NOT dependent on other stories Story Template: “As a <User> I want <function> So that <desired result> Story Example: As a user, I want to print a recipe so that I can cook it. User Stories A simple way to initially estimate level of effort expected to develop Story points are a relative measure of feature difficulty Usually scored on a scale of 1-10. 1=very easy through 10=very difficult Example: “Send to a Friend” Story Points = 2 “Shopping Cart” Story Points = 9 Story Points Capacity = # Teammates (Productive Hrs x Sprint Days) Example – Team size is 4, Productive Hrs are 5, Sprint length is 30 days. Capacity = 4 (5 x30) = 600 hours NOTE: Account for vacation time during the Sprint! Estimate Team Capacity Each User Story in the Product Backlog should have a corresponding business value assigned. Typically assign (L,M,H) Low, Medium, High PO prioritizes Backlog items by highest value Business Value Glossary of Terms Time Box - A period of time to finish a task. The end date is set and can not be changed Chickens – People that are not committed to the project and are not accountable for deliverables Pigs – People who are accountable for the project’s success Single Wringable Neck – This is the Product Owner! The rate at which team converts items to “DONE” in a single Sprint – Usually calculated in Story Points. Velocity Visibility + Flexibility = Scrum