Scrum Agile Project Management

ScrumMaster Checklists

Even if for some Agile and Scrum practitioners, checklists can have the bad reputations as being on the wrong side of the “Individuals and interactions over processes and tool ” Agile Manifesto preferred values, it doesn’t always mean that it contains “items you should always check”. They can be also considered as a good practice that allows to capitalize and share experience when they are used as guidelines to assess the different aspects of a situation.

This article presents various websites, articles and blog posts that suggest checklists for ScrumMasters. The main reference is and many web sites just reference this content. We tried to uncover different perspectives on this topic. I hope their content might help beginning or experienced Scrum Masters consider their work with a different perspective. Feel free to suggest any content that I missed and that should be featured in this article.

* Michael James’ Example Scrum Master Checklist

This site is dedicated to Michael James’ Example Scrum Master Checklist, an example list of things a Scrum Master should pay attention to in a typical organization. This list is translated in multiple languages (Chinese, Japanese, German, French, Spanish, etc.) Some of the items mentioned in this list are “Is the backlog an information radiator immediately visible to all stakeholders?” or “Are there issues/opportunities the team isn’t discussing because they’re too uncomfortable?”.

Michael James' Example Scrum Master Checklist

Web address:

* Crisp Scrum Checklist

The Scrum checklist is a simple tool created by Henrik Kniberg that provides guidelines to help you get started with Scrum or assess your current implementation of Scrum. Some of the items mentioned in this list are “Team has a sprint backlog that is updated daily” or “Velocity only includes items that are Done”.

Crisp Scrum Checklist

Web address: (PDF)

* SolutionsIQ ScrumMaster Thoughtlist

This blog post reminds the danger of checklists when they are used by Agile teams to “do things because the checklist says they should, not because it brings any value”. It then provides an Agile “thoughtlist” to help ScrumMasters, agile teams, and product owners. Some of the items mentioned in this list are “Is the Sprint planning meeting length proportionate to the length of the Sprint?” or “Do the improvements selected in the Sprint retrospective regularly result in actions and changes that are carried out in the next Sprint?”

Web address:

* Pascal Dufour Scrum Master Checklist

This document use a mindmap to present a list of positive (relax) and negative (take action) situations that a ScrumMaster should monitor. Some of the items mentioned in this list are “There is a shared understanding of the Definition of Done” and “The development team expect that the Product Owner checks the delivered items complies to the Definition of Done”

Web address:

1 Comment on ScrumMaster Checklists

  1. These ScrumMaster checklists are interestng resources, but I encourage any ScrumMaster or Scrum Team to build its own version. This is like the Definition of Done (Dod), they must be the result of your own considerations about your specific context.

Comments are closed.