Slideshare.net (beta)

Slide 1: Team delivers something after each sprint Team follows PO's priorities Team usually delivers what they committed to Team acts when they are behind schedule PO = Product Owner Team alerts PO when there are problems SM = Scrum Master For each story, team knows PBL = Product Backlog where to find out more info. Glossary Problems detected & discussed SBL = Sprint Backlog when they occur, not later. DoD = Definition of Done Sprint length doesn't change Sprint after each sprint Team sits together Major unplanned items are logged Team members collaborate to bring stories all the way to Team isn't consistently working overtime Done. Max 1 day gap between sprints Team members not locked into Stakeholders/customers know specific roles about the sprint Team members collaborate to Other teams & the rest of the complete high-priority stories Team company know about the sprint first. Sometimes overcommit, Team members admit sometimes undercommit. problems and ask for help Stories that get started usually Team members help each other get finished within same sprint Team members hold each other responsible Same time, same place every day Starts and ends on time Team has a SM All team members present SM sits with the team SM focuses on removing Scrum master (SM) Everybody answers the 3 questions impediments No interruptions Daily Scrum PO owner visits daily scrum regularly Team has one PO Team members are pulling PO has the power to prioritize tasks, rather than SM pushing what his team does tasks PO understands the product Product Owner (PO) Team members address each enough to prioritize well other, not the SM PO has at least 1 dedicated team Demo is done after each sprint PO owns PBL Demo shows working code PBL is visible Only stories that are Done are demonstrated PBL is updated before sprint planning All stakeholders and other PO understands all stories Sprint demo teams are invited to the demo Product Backlog (PBL) Feedback received from "Conditions of satisfication" / "How to demo" is clear for each stakeholders during demo story Original sprint plan is Scrum checklist shown at beginning of PB contain stories (not tasks) demo Each story has a DoD (or inherits a default DoD) Retrospective takes place All team members + PO Team respects DoD participate PO + all team members know Results in concrete DoD by heart improvement suggestions Definition of Done (DoD) DoD includes testing Retrospective Some improvement suggestions actually get Team is not dependent on implemented others to achieve DoD Everybody speaks PO can get estimates from the team No uninvited guests PO is available when team is estimating Team has impediment backlog Only the team writes the estimates Everyone on the team Impediment backlog is visible participates in estimating Impediment backlog is Top priority stories are small Estimation up-to-date enough that several can fit in a Impediment backlog Impediment backlog is sprint prioritized Highest prio items on PBL are Impediments that can't be estimated before sprint solved are escalated to PO or planning meeting (at least line manager enough to cover 1 sprint) Velocity is written down after each sprint PO participates Velocity only includes stories All team members participate Velocity that are done according to DoD Results in a sprint plan Velocity is used for release planning All team members think the plan is realistic, and commit to it. Sprint planning meeting Team has a burndown chart PO is satisfied with the priorities Burndown chart highly visible All stories in the sprint plan Burndown chart Burndown chart updated every day have an estimate. Team takes action when Starts and ends on time burndown is too high/low Team has a sprint backlog SBL is highly visible SBL updated every day Task estimates updated every day Tasks and stories are clearly Sprint backlog (SBL) distinguished It is clear which task is part of which story Team members update the SBL themselves (not only SM) Team members have easy access to update the SBL Scrum checklist.mmap - 2008-01-14 - Henrik Kniberg