InfoQ

Minibook

Scrum Checklists

Posted by Sprint-IT on Nov 02, 2006 08:04 PM

Community
Agile
Topics
Methodologies,
Training / Certification
Tags
Scrum,
Self-organizing Team


The SPRiNT-iT coaches, including Scrum Trainer Boris Gloger, have abstracted the basics from the major Scrum books and added their collective experience to produce the Scrum Checklists mini-book.  This compact collection of checks and actions will enable team members to facilitate all Scrum Meetings and create the Scrum artifacts. 

Free download, buy the print version for 19,90 euro

The Checklists are printed on cover stock and spiral bound, which creates a book that is attractive and easy to handle.  The Overview with coloured index matches the coloured tabs on the right, to give fast access to the different Checklist pages.  Use the blank space on the back of each checklist to document individual conventions and specific adaptations.  Support the author as well as future InfoQ books by purchasing the print copy for only 19,90 euro. 

You can also Login to download this book FREE (PDF)

About the book

The book is not intended to teach the details of Scrum, and no book will replace intelligent team self-organization.  Instead, this book was created to give trained teams confidence in accomplishing their first Sprints. The full list of topics is explained in an Overview page and tabs down the right edge give fast access to the colour-coded topics:

  • Checklist: Impediment Backlog (an innovation springing up in teams on both sides of the Atlantic)
  • Checklist: General Meeting (basic etiquette for teams moving out of adhoc or chaos processes)
  • Checklist: Estimation Meeting (creating the Product Backlog)
  • Checklist: Sprint Planning Part 1
  • Checklist: Sprint Planning Part 2
  • Checklist: Daily Meeting
  • Checklist: Sprint Review
  • Checklist: Sprint Retrospective
  • Scrum Roles
  • Scrum Artifacts
The authors indicate that the Scrum beginner should strictly follow the Checklists. This will give them confidence to accomplish their first Sprints. Those first success will increase the acceptance of Scrum in their organization.  Experienced Scrum Masters may want to use the Checklists as an adjunct to their own training material. 

Related Sponsor

Expanding Agile Horizons: techniques and technologies, attitudes and policies and the management and dev sides of Agile development. Register early!

Exclusive Content

Business Natural Languages Development in Ruby

Jay Fields presents his concept of Business Natural Languages - a type of Domain Specific Languages geared towards being readable by domain experts.

Distributed Version Control Systems: A Not-So-Quick Guide Through

Adoption and interest for Distributed Version Control Systems is constantly rising. We will introduce the concept of DVCS and have a look at 3 actors in the area: git, Mercurial and Bazaar.

Segundo Velasquez and Agile as Seen Through the Customer's Eyes

Deborah Hartmann interviewed Segundo Velasquez about his experience as customer with an Agile team during the initial phase of software design of a product.

Fine Grained Versioning with ClickOnce

David Cooksey shows how to fine grained versioning to a ClickOnce deployment using an HttpHandler written with ASP.NET, making partial rollouts to a test audience much easier.

Implementing Manual Activities in Windows Workflow

Windows workflow (WF) is an excellent framework for implementing business processes, but lacks support for human activities. This article describes a completely generic approach for changing this.

Markus Voelter about Software Architecture Documentation

In this interview taken during OOPSLA 2007, Markus Voelter talks about the importance of documenting the software architecture, and gives some good and also bad examples on how it could be done.

Voca, UK's largest payment processing engine running Spring

William Soo and Meeraj Kunnumpurath discuss the Voca transaction processing system, architectural challenges and requirements, Voca's Spring/J2EE architecture, and the future SEPA architecture.

Patterns for securing architectures

Security is about trade-offs. Only a few have the expertise to design good security. This talk focuses on Security Patterns, such as Role-based Access Control, Single Access Point, and Front Door.