Scrum Checklist

Team delivers something after each sprint

Team follows PO's priorities

Team usually delivers whatthey committed to

Team acts when they arebehind schedule

Team alerts PO when there are problems

For each story, team knowswhere to find out more info.

Stories that get started usuallyget finished within same sprint

Problems detected & discussedwhen they occur, not later.

Sprint length doesn't changeafter each sprint

Major unplanned items are logged

Team isn't consistently working overtime

Max 1 day gap between sprints

Stakeholders/customers knowabout the sprint

Other teams & the rest of thecompany know about the sprint

Sometimes overcommit,sometimes undercommit.

Same time, same place every day

Starts and ends on time

All team members present

Everybody answers the 3 questions

No interruptions

PO owner visits daily scrum regularly

Team members are pullingtasks, rather than SM pushingtasks

Team members address eachother, not the SM

Team site together

Team members collaborate to bring stories all the way to Done.

Team members not locked into specific roles

Team members collaborate to complete high-priority stories first

Team members help each other

Team members admit problems and ask for help

Team members hold each other responsible

Team has a SM

SM sits with the team

SM focuses on removing imprediments

Demo is done after each sprint

Demo shows working code

Only stories that are Done aredemonstrated

All stakeholders and otherteams are invited to the demo

Feedback received fromstakeholders during demo

Original sprint plan isshown at beginning ofdemo

PO has he power to prioritize what his team does

PO understands the product enough to prioritize

PO has at least one dedicated team

Retrospective takes place

All team members + PO participate

Results in concrete improvement suggestions

Some improvement suggestions actually get implemented

Everybody Speaks

No uninvited guests

PO owns PBL

PBL is visible

PBL is updated before sprint planning

Conditions of satisfaction / How to Demo is clear for each story

PB contains stories not tasks

Team has impediment backlog

Impediment backlog is visible

Impediment backlog isup-to-date

Impediment backlog isprioritized

Impediments that can't besolved are escalated to PO orline manager

Each story has a DoD

Team respects the DoD

PO +all team members understand the DoD

DoD includes tests

Team in not dependent on others to achieve DoD

Velocity is written down after each sprint

Velocity only includes storiesthat are done according to DoD

Velocity is used for release planning

PO can get estimates from the team

POis available when team is estimating

Only the team writes the estimates

Everyone on the team participates in point estimating

Top Priority stories are small enough that several can fit in one sprint

Highest priority PBL are estimated before sprint planning

Team has a burndown chart

Burndown chart highly visible

Burndown chart updated every day

Team takes action whenburndown is too high/low

PO Participates

All team members participate

Results in Iteration Plan

All team members think plan is realistic and commit to it (Fist of 5)

All stories in the sprint plan have an estimate

Starts and ends on time

Same time and place

Team has a sprint backlog

SBL is highly visible

SBL updated every day

Task estimates updated every day

Tasks and stories are clearlydistinguished

It is clear which task is part of which story

Team members update theSBL themselves (not only SM)

Team members have easyaccess to update the SBL