The Scrum Checklist

Understanding the fundamentals of scrum is a very simple thing to do. However 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 a fast moving business 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 scrum, I have put together this simple checklist that anyone can use on a daily basis. It covers:

o checklists for the fundamental tasks of every scrum role

o an overview and recap of each scrum meeting (-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 check list is below.

The SCRUM MASTER checklist

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

o follow up on impediments above

o order any team equipment

o write sprint report to stake holders (once a sprint)

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

o make sure burndown and task board are visible in 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 prioritise backlog daily based on business value

o meet stakeholders when needed to coordinate and requirements

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

The DEVELOPMENT TEAM checklist

o update task board with 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, refactoring)

About Nirbhaya 21028 Articles
Nirbhaya has been interested in doing something on his own from the days when he was in college. But, things didn’t favour him in the beginning, and he had to work for others. Later, he finally started Onhike.com as a news portal, and then never looked back. The website is gaining popularity every day. He puts all of his skills into his work and making his dream come true. He covers Tech and General news on this website.