Scrum Checklist

1. FREE ONLINE EDITION
(non-printable free online version)
If you like the book, please
support the author & InfoQ by
purchasing the printed
version:
www.sprint-it.de/scrum-checklists
(only 19,90 euro)
Brought to you courtesy of Sprint-IT &
This book is distributed for free on InfoQ.com, if you
have received this book from any other source then
please support us by registering on InfoQ.com.
Visit the homepage for this book at:
http://infoq.com/books/scrum-checklists

2. Scrum CHECKLISTS
Success with Scrum
© SPRiNT iT GmbH
http://www.sprint-it.com

3. Dear Scrum Checklists User,
Scrum is a framework with a set of simple rules which empowers agile
thinking in your organization in order to increase productivity and joy.
The Scrum Checklists refine the Scrum rules with the experience of our
SPRiNT-iT coaches. This compact combination of checks and actions
will help you to facilitate all Scrum Meetings and create the Scrum
artifacts.
Strictly follow the Checklists in the beginning. This will give you the
confidence to accomplish your first Sprints. Your success will increase
the acceptance of Scrum in your organization.
Use the free space on the back of each checklist to document individu-
al conventions and specific adaptations.
As an experienced Scrum Master, use the Checklists as backup or
training material.
The Scrum Checklists do not replace a Scrum Master training or the
individual assistance of an experienced Scrum Coach.
Start now with our Scrum Checklists and quickly become an effective
Scrum user!
WUFF!
Boris Gloger
Certified Scrum Master Trainer
Director of SPRiNT-iT GmbH

4. Overview
Overview Scrum CHECKLISTS
Impediment Backlog
Impediments occur on both team and organizational levels. Identify, prioritize
and make them visible using the Impediment Backlog.
General Meeting
All meetings follow a common standard. These basic rules not only increase the
efficiency of the meetings but also make them more satisfying for all partici-
pants.
Estimation Meeting
Product Owner and team work on the estimation of the entire Product Backlog
providing the basis for Release and Sprint Plannings.
Sprint Planning 1
The team and the Product Owner define the Sprint Goal and the Selected
Product Backlog based on the effort estimation.
Sprint Planning 2
In the Sprint Planning 2 meeting the team works on the Selected Product Back-
log by adding tasks to each Backlog Item. The effort of each task should not be
bigger than one day.
Daily Scrum Meeting
The Daily Scrum Meeting helps the team to organize itself. It is a synchroniza-
tion meeting between the team members. It takes place every day at the same
time, at the same place. The meeting is time-boxed to 15 minutes.
Sprint Review Meeting
The status of the project is controlled by reviewing the working functionality. The
Product Owner decides if the delivered functionality meets the Sprint Goal.
Retrospective
Inspect and adapt is a fundamental part of Scrum. During the Retrospective the
team analyzes the previous Sprint to identify success stories and impediments.

5. Team Conventions Space for your own notes

6. Impediment Backlog
Scrum CHECKLIST
Impediment Backlog
Prepare a flip chart with 3 Columns: New, In Progress, Done
Go through to the ten typical impediments below. If you are
experiencing any of the impediments then:
write it down on a Post-it
add it to the “New” column on the Impediment Backlog
10 Typical Impediments
The meeting rules are not followed
Product Vision and Sprint Goal are unclear
The Product Owner is not available for questions
The Product Backlog is not prioritized by business value
Not everyone who contributes to the delivery is in the team
The Scrum Master has to perform other tasks and is not able to focus
on the team progress
The team is too big (> 7 members)
The team has no room where they can work together
The team has no dashboard to access the Sprint Backlog
Add all known additional impediments to the “New” column on the Im-
pediment Backlog.
Prioritize the impediments in the “New” column
Each time you start resolving an impediment move it to the “In Progress”
column
Resolve that impediment as fast as possible
Each time an impediment is resolved, move it to the “Done” column
Collect new impediments during the Daily Scrum Meeting and
Retrospective

7. Team Conventions Space for your own notes

8. Scrum CHECKLIST
General Meeting
Every meeting is time-boxed. The Scrum Master facilitates all meetings.
General Meeting
Meeting Preparation
The meeting has a goal
All participants are invited
The agenda is defined at least one day before the meeting takes place
The meeting goal and agenda has been sent to all participants
All resources are booked
Room
Data Projector
Notebook with net access
Flip chart and markers
The meeting room is fully prepared before the meeting starts
Meeting Moderation
A parking lot is a list on a flip chart to collect topics which are not part of the
meeting agenda.
Present the meeting goal
Present the agenda
If a discussion about a topic starts, which is not part of the agenda:
add the topic to the parking lot
If the meeting time is over but the goal has not been reached:
arrange a new meeting
If the participants achieve results:
write the results down on the flip chart
make sure everyone agrees about the written results
If the parking lot is not empty:
find a person responsible for each topic
add the name of the person in charge to each topic
Meeting Result
Every participant knows where to find the results

9. Team Conventions Space for your own notes

10. Scrum CHECKLIST
Estimation Meeting
The sizes of the next relevant Product Backlog items are estimated.
Meeting Preparation | General Meeting
Estimation Meeting
Participants are invited:
Product Owner
Scrum Master
All team members
Product Backlog is prioritized
Product Backlog is visible and accessible to everyone in the meeting
A set of cards for Planning Poker labeled 1, 2, 3, 5, 8, 13, 21, 34, 89
for each team member is at hand
Meeting Moderation
Present the goal of the meeting
The Product Owner presents the portion of the Product Backlog that he
wants to be estimated
If the Backlog is not estimated at all:
select a Backlog Item that you expect to be one of the smallest stories
you’ll work on, give it 2 story points
For each Backlog Item in the Product Backlog:
the Product Owner explains the story behind the Backlog Item
each team member selects one of his Planning Poker Cards to vote
for the relative size of the Backlog Item
the team members show their cards at the same time
if the estimates differ, the most contrary team members discuss their
view of the Backlog Item and the voting is repeated up to 2 times until
all team members share the same opinion
the estimate is added to the Backlog Item
End the Estimation Meeting with a wrap-up
If necessary, schedule an additional estimation meeting
Page 1/2

11. Team Conventions Space for your own notes

12. Scrum CHECKLIST
Estimation Meeting
Meeting Results | General Meeting
The estimated Product Backlog is available for everyone in the
organization
Estimation Meeting
Page 2/2

13. Team Conventions Space for your own notes

14. Scrum CHECKLIST
Sprint Planning 1
Define the Sprint Goal and the Selected Product Backlog.
Meeting Preparation | General Meeting
Participants are invited:
Product Owner
Scrum Master
All team members
Product Backlog is prioritized
Backlog Items are estimated
Product Backlog is visible and accessible to everyone in the meeting
Planned absences (e.g. holidays) of team members are known
Planning 1
The room is suitable for team discussions
The results of the Sprint Review and the Retrospective are available
Every appointment for the regular Scrum meetings is defined before the Sprint starts.
Recommended duration for regular Scrum meetings of a 30 day Sprint:
- Sprint Planning 1: 4 hours - Sprint Review Meeting: 2 hours
- Sprint Planning 2: 4 hours - Retrospective: 2 hours
- Daily Scrum Meeting: 15 minutes
The Sprint Schedule is defined
Appointment for the Sprint Planning 1
Appointment for the Sprint Planning 2
First day of the Sprint is defined
Last day of the Sprint is defined
Appointment for the Daily Scrum Meeting
Appointment for the Sprint Review Meeting
Appointment for the Retrospective
(Optional) Pinboard for the Selected Backlog:
A pinboard of the size of at least 2 x 2 meters
Cards or Post-its
Markers
(Optional) Cards for planning poker
Page 1/2

15. Team Conventions Space for your own notes

16. Scrum CHECKLIST
Sprint Planning 1
Meeting Moderation
Make the Sprint Schedule visible to everyone
Make the Sprint Review Meeting results visible to everyone
Make the Retrospective results visible to everyone
The Product Owner informs team about the product vision
The Product Owner and the team define the Sprint Goal
If there are Backlog Items missing:
the Product Owner can add the Backlog Item
A story point is one of the values in the row: 1, 2, 3, 5, 8, 13, 21, 34, 89.
Planning 1
If the Backlog is completely unestimated:
select a Backlog Item that you expect to be one of the smallest stories
you’ll work on, give it 2 story points
assign story points to the other Backlog Items in relation to the
smallest one
If there are some Backlog Items which are not estimated yet:
estimate the Backlog Items in story points relative to the other ones.
If the Product Backlog is not well prioritized:
the Product Owner prioritizes the Product Backlog
The Product Owner and the team mutually agree on the Sprint Goal and
the Selected Product Backlog
Meeting Results | General Meeting
Selected Product Backlog is well prepared for the Sprint Planning 2
Page 2/2

17. Team Conventions Space for your own notes

18. Scrum CHECKLIST
Sprint Planning 2
Define tasks to create the Sprint Backlog and commit to the Sprint Goal.
Meeting Preparation | General Meeting
Participants are invited:
Scrum Master
All Team members
Product Owner (has to be reachable for questions)
The Selected Product Backlog is accessible for the task planning
(Optional) Pinboard for the Backlog:
A pinboard of the size of at least 2 x 2 meters
Cards or Post-its for the tasks
Markers
Meeting Moderation
Team members find tasks for each Backlog Item
Planning 2
Make sure, that every piece of work is taken into account
Coding
Testing
Code review
Meetings
Learning new technologies
Writing documentation
If a task effort is bigger than one day:
try to split the task into smaller tasks
If the team believes that the Sprint Backlog is too large:
remove Backlog Items together with the Product Owner
If the team believes that the Sprint Backlog is too small:
move the most important Backlog Items from the Product Backlog to
the Sprint Backlog together with the Product Owner
The team commits to the Sprint Goal
Page 1/2

19. Team Conventions Space for your own notes

20. Scrum CHECKLIST
Sprint Planning 2
Meeting Results | General Meeting
Sprint Goal and Sprint Backlog are visible to everyone in the
organization
The tasks in the Sprint Backlog are accessible to all team members
Planning 2
Page 2/2

21. Team Conventions Space for your own notes

22. Scrum CHECKLIST
Daily Meeting
Synchronize the team.
Meeting Preparation | General Meeting
Participants are invited:
All team members
Scrum Master
(Optional) Product Owner
(Optional) Other stakeholder
Tasks on the Sprint Backlog are editable, addable, removable and
sortable
State of a task can be set to “To Do”, “In Progress” and “Done”
Meeting Moderation
- The meeting is time-boxed to 15 minutes.
- Every team member answers the following 3 questions and takes care of the
correlated actions.
What tasks have you finished since last meeting?
Set task from “In Progress” to “Done”
What tasks do you plan to finish before the next meeting?
Daily Meeting
If task is in state “To Do”: move it to “In Progress”
If task is not on the Sprint Backlog: add it
If task is not realizable within one day: divide it into smaller tasks
If task is realizable within one day: set state to “In Progress”
If task is already in state “In Progress”: ask if there is an impediment
What is in your way?
If something is in the way: add it as an impediment to the
Impediment Backlog
If a discussion starts:
remind the team members to focus on answering the questions
If a stakeholder wants to say something:
remind him politely, that this meeting is only for the team
Page 1/2

23. Team Conventions Space for your own notes

24. Scrum CHECKLIST
Daily Meeting
Meeting Results | General Meeting
Impediment Backlog is up-to-date
Sprint Backlog is up-to-date
Burndown Graph is up-to-date
Daily Meeting
Page 2/2

25. Team Conventions Space for your own notes

26. Scrum CHECKLIST
Sprint Review Meeting
Review all Backlog Items the team has delivered in this Sprint and check if the
Sprint Goal was achieved.
Meeting Preparation | General Meeting
Participants are invited:
Product Owner
Scrum Master
All team members
The Sprint Goal is visible to everyone
The Selected Product Backlog is accessible and visible to everyone
The team has prepared workstations, devices etc. to demonstrate the
new functionality
Meeting Moderation
The team presents the Sprint results and demonstrates the new
functionality, Backlog Item after Backlog Item
If the Product Owner wants to change a feature:
add a new Backlog Item to the Product Backlog
If a new idea for a feature occurs:
add a new Backlog Item to the Product Backlog
If the team reports an impediment which is not solved yet:
add the impediment to the Impediment Backlog
Meeting Results | General Meeting
Common understanding about the Sprint results and the product state
Review

27. Team Conventions Space for your own notes

28. Scrum CHECKLIST
Retrospective
Learn from past experience to improve the productivity of the team.
Meeting Preparation | General Meeting
Participants are invited:
Scrum Master
All team members
(Optional) Product Owner
Additional facilities:
Text markers for all participants
Post-its
Red and green sticky dots
Whiteboard and flip chart
Prime Directive: Regardless of what we discover, we must understand and truly believe
that everyone did the best job he or she could, given what was known at the time, his
or her skills and abilities, the resources available, and the situation at hand.
A flip chart with the Prime Directive
A time-line over at least 3 connected flip charts
A flip chart with “What Went Well”
A flip chart with “What could be Improved”
A flip chart with “Who is in Control” divided in 2 areas “Team” and
“Organization”
Meeting Moderation
Present the goal of the meeting
Present the Prime Directive
Mark the start and the end date of the Sprint on the time line
Retrospective
Page 1/2

29. Team Conventions Space for your own notes

30. Scrum CHECKLIST
Retrospective
Meeting Moderation
Working with Post-its: Write only ONE event on each Post-it.
Explain to the participants how to work with Post-its
Hand out Post-its and ask everyone to write on them all significant events
of this sprint; Timebox: 5 min.
Each participant in turn adds his Post-its to the time-line and explains in
two sentences the story behind each event
Hand out Post-its and ask everybody to write on them “What went well”;
Timebox: 5 min.
Each participant in turn adds his Post-its to the flip chart “What went well”
and explains it
Hand out Post-its and ask everybody to write on them “What could be im-
proved”; Timebox: 5 min.
Each participant in turn adds his Post-its to the flip chart “What could be
improved” and explains it
For each item on the “What could be improved” flip chart:
ask the team “Who is in control of this impediment?”
move the Post-it to the corresponding column on the flip chart “Who
is in control”
Prioritize both lists with the team
Run a wrap-up of the meeting:
Each participant gives a short reflection about the retrospective
Meeting Results | General Meeting
The “Who is in control” flip chart is visible to everyone in the
organization
The impediments related to the organization are added to the
Retrospective
Impediment Backlog
The impediments related to the team are added to the Product Backlog
Page 2/2

31. Roles Scrum CHECKLIST
Product Owner
The Product Owner is the representative of all stake-
holders. His focus is the business side of the product. He
carries the product vision to the team. He formalizes a
specific, measurable and reasonable Product Backlog and
prioritizes it by business value.
Team
The team does everything to win the game – to deliver the
product. The team is cross-functional. That means the full
know-how to realize the product is located in the team.
The team needs to understand the vision and Sprint Goals
of the Product Owner in order to deliver potentially ship-
pable product increments.
Scrum Master
The Scrum Master is the coach and facilitator of the team.
He improves the productivity. He always has a training plan
for the team – the Impediment Backlog.
The Scrum Master controls the “inspect and adapt” cycles
of Scrum. He protects the team and works with the Prod-
uct Owner to maximize the return on investment. He takes
care that the agile ideals are understood and respected by
all stakeholders.

32. Artifacts Scrum CHECKLIST
Product Backlog
The Product Backlog lists any required deliverables. Its
contents are ordered by business value. Backlog Item
priority might change, requirements can be added and
removed – thus the Product Backlog is a continuously
maintained plan towards a growing business value.
Selected Product Backlog
The Selected Product Backlog is the result of the Sprint
Planning. It defines the amount of work the team has
accepted. It remains unchanged during the whole Sprint.
Sprint Backlog
The Sprint Backlog consists of the necessary tasks to
realize the final accepted a version of the Selected
Product Backlog. The team uses it to synchronize its
activities.
Impediment Backlog
An Impediment Backlog lists any issues that have to be
solved within or concerning the team. The Scrum Master
makes sure that Impediment Backlog items are assigned
and worked on.

33. “I was pleasantly surprised when I perused this little book: these are virtually the same
checklists I myself make in my head or on index cards! The content provides “just enough”
information, without trying to teach Scrum, which is better done in-person. The form factor of
the printed book suits me well - attractive, robust and useful. I can see myself giving these to
apprentices I am training - not as a replacement for other learning, but as a reminder to apply
that learning instead of the old patterns they have from habit.”
Deborah Hartmann, Certified Scrum Practitioner, InfoQ.com Agile Community Editor
“Thanks for the Scrum Checklists. Those are fantastic. Brilliant idea and execution!”
Mike Cohn, Author of ‘Agile Estimating and Planning’
Publisher:
Scrum CHECKLISTS
SPRiNT iT Gesellschaft für Lösungen mbH
Pforzheimer Straße 160
76275 Ettlingen
Germany
sales@sprint-it.com
http: //www.sprint-it.com
Copyright © 2006 SPRiNT iT Gesellschaft für Lösungen mbH
All rights reserved. This publication is protected by copyright, and permission must be
obtained from the publisher prior to any prohibited reproduction, storage in a retrieval
system, or transmission in any form or by means, electronic, mechanical, photocopying,
recording, or likewise.
3rd Printing – October 2006 | Printed in Germany