• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content


Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this document? Why not share!

Scrum checklist



Checklist to validate implementation of Scrum in your agile project (based on Henrik Kniberg's scrum checklist)

Checklist to validate implementation of Scrum in your agile project (based on Henrik Kniberg's scrum checklist)



Total Views
Views on SlideShare
Embed Views



3 Embeds 224

http://dusankocurek.wordpress.com 117
http://www.scrumdesk.com 101
http://www.slideshare.net 6


Upload Details

Uploaded via

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.


11 of 1 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • ScrumDesk, scrum project management tool, now allows to check sprint planning and execution by unique Coach feature that validates data according this checklist and other best practices as well.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Scrum checklist Scrum checklist Document Transcript

    • # Area Category 1 Core Scrum Product Ownership 2 Core Scrum Product Ownership 3 Core Scrum Product Ownership 4 Core Scrum Product Ownership 5 Core Scrum Product Ownership 6 Core Scrum Team 7 Core Scrum Team 8 Core Scrum Team 9 Core Scrum Team 10 Core Scrum Team 50 Core Scrum Team 51 Core Scrum Team 52 Recommended Team 53 Recommended Team 11 Core Scrum Daily Scrum 12 Core Scrum Daily Scrum 13 Core Scrum Daily Scrum 14 Core Scrum Daily Scrum 15 Core Scrum Daily Scrum 16 Core Scrum Daily Scrum 17 Core Scrum Daily Scrum Core Scrum Daily Scrum 18 Core Scrum Daily Scrum 19 Core Scrum Demo 20 Core Scrum Demo 21 Core Scrum Demo 22 Core Scrum Demo 23 Core Scrum Demo 24 Core Scrum Demo 25 Core Scrum Demo 26 Core Scrum Definition of Done 27 Core Scrum Definition of Done 28 Core Scrum Definition of Done 29 Core Scrum Retrospective 30 Core Scrum Retrospective 31 Core Scrum Retrospective 32 Core Scrum Retrospective 33 Core Scrum Product Backlog 34 Core Scrum Product Backlog 35 Core Scrum Product Backlog 36 Core Scrum Product Backlog 37 Core Scrum Product Backlog 38 Core Scrum Product Backlog 55 Recommended Product Backlog 56 Recommended Product Backlog 57 Recommended Product Backlog 58 Recommended Product Backlog 59 Recommended Product Backlog
    • 69 Recommended Velocity 70 Recommended Velocity 71 Recommended Velocity 72 Recommended Velocity 39 Core Scrum Sprint Planning 40 Core Scrum Sprint Planning 41 Core Scrum Sprint Planning 42 Core Scrum Sprint Planning 43 Core Scrum Sprint Planning 44 Core Scrum Sprint Planning 45 Core Scrum Sprint Planning 46 Core Scrum Timeboxed iterations 47 Core Scrum Timeboxed iterations 48 Core Scrum Timeboxed iterations 49 Core Scrum Timeboxed iterations 54 Recommended Timeboxed iterations 60 Recommended Impediments 61 Recommended Impediments 62 Recommended Impediments 63 Recommended Impediments 64 Recommended Scrum Masterships 65 Recommended Scrum Masterships 66 Recommended Scrum Masterships 67 Recommended Scrum Masterships 68 Recommended Scrum Masterships 73 Positive indicators General 74 Positive indicators General 75 Positive indicators General
    • Question Product Owner is defined Product Owner prioritize backlog Product Owner has direct contact with team. Product Owner has direct contact with stakeholders One voice from PO teams Team has Sprint Backlog Sprint Backlog is highly visible Product Backlog is highly visible Sprint Backlog is updated daily by team members Only team can change the sprint backlog Team members sit together Max 9 people per team Team has all skills needed to bring backlog items to Done Team members not locked into specific roles Daily Scrum happends Daily Scrum are at the same time every day All team members are active in daily scrum Tasks are updated before daily scrum Remaining time is known for every task after daily scrum Daily scrum is short (no sidetalks) Daily Scrum is moderated by Scrum Master Product Owner knows about Unplanned tasks and he plans them Impediments are surfaced Demo happends after every sprints Working & tested software is presented Feedback is received from PO & stakeholders World is invited (other teams, etc.) Length of demo is limited All comments are logged Status of work presented (completed/not completed stories, burn down chart) Definition of Done is known by all team members Testers are included in DoD DoD is achievable in one iteration Retrospective happened every sprint Results in concrete improvement proposals Some proposal are implemented Whole team participates PO has Product Backlog Top items are prioritized based on business value Top items are estimated Estimates written by the team Top items in PBL small enough to fit in a sprint PO understands purpose of all backlog items PO has product vision that is in sync with PBL PBL and product vision is highly visible Everyone on the team participates in estimating PO available when team is estimating Estimate relative size (story points) rather than time
    • Velocity is measured All items in sprint plan have an estimate PO uses velocity for release planning Velocity only includes items that are Done Have sprint planning meetings PO participates PO brings up-to-date PBL Whole team participates Results in a sprint plan Whole team believes plan is achievable PO satisfied with priorities Iteration length 4 weeks or less Always end on time Team not disrupted or controlled by outsiders Team usually delivers what they committed to Iterations that are doomed to fail are terminated early Whole team knows top 1-3 impediments SM has strategy for how to fix top impediment SM focusing on removing impediments Escalated to management when team can’t solve Team has a Scrum Master (SM) SM sits with the team PBL items are broken into tasks within a sprint Sprint tasks are estimated Estimates for ongoing tasks are updated daily Having fun! High energy level. Overtime work is rare and happens voluntarily Discussing, criticizing, and experimenting with the process
    • Team Member Team Team A Member B Member C (0-No/1-Yes) 1 1 1 0 0 0
    • 0.0% 0.0% 0.0%
    • Areas Created by Dusan Kocurek, ScrumDesk company based on http://www.crisp.se/scrum/checklist/scrum-checklist.pdf made by Henrik Kniberg