Programming codex

The Scrum Checklist

The Scrum Checklist


Understanding the fundamentals of scrum is a very simple thing to do. However putting it into practice in the world of deadlines, strong characters and the need for quick decisions can often make it a huge challenge to get the job done using the scrum rules. There are often situations where the rules are forgotten and put to one side, especially when they are most needed.

In my experience as a scrum master, team lead and software engineer I saw how easy it is for employees of fast-moving businesses to put the scrum rules to one side and destroy the very framework that would help make their daily lives easier. Observing how easy it is to forget the fundamental elements of the scrum, I have put together this simple checklist that anyone can use daily. It covers:

o checklists for the fundamental tasks of every scrum role

o an overview and recap of each scrum meeting (time-box)

o checklists for the preparation, carrying out, and goals of every scrum meeting

Using these checklists, you can be prepared and confident that you are carrying out the scrum practices on your daily job, boosting the productivity of your scrum team and increasing return on investment for the business. One section of the checklist is below.

The SCRUM MASTER checklist

o update list of impediments from daily scrum, emails and another contact

o follow up on impediments above

o order any team equipment

o write sprint report to stakeholders (once a sprint)

o chase up any information holding up sprint backlog (e.g. the third party supplied artifacts)

o make sure burndown and task board are visible in the team room

o arrange meetings and have chats to coach any new or needy team members, product owners or stakeholders

The PRODUCT OWNER checklist

o update backlog daily with any changes

o prioritize backlog daily based on business value

o meet stakeholders when needed to coordinate and capture requirements

o liaise with the team to clarify requirements and make trade-offs communicate release plan to stakeholders


o update task board with time remaining on tasks

o report any impediments to scrum master

o communicate with product owner before attempting and after completing a story

o achieve daily targets

o maintain team communication

o keep solutions simple

o focus on ship-ability (e.g. using practices such as pair programming, code review, continuous refactoring)


Source by Paul B. Vii

Share on facebook
Share on google
Share on twitter
Share on linkedin
Share on pinterest
Share on whatsapp

Leave a comment

Your email address will not be published. Required fields are marked *



Recent Posts