How I Used the Spotify Squad Health Check Model

The ‘Squad Health Check Model’ is an approach that visualises the ‘health’ of a team. It covers areas like teamwork, fun, easy to release, learning, the health of codebase. While discussing the different health indicators, the team builds up self-awareness about what’s working and what’s not. The broad selection of questions helps expand their perspective. Perhaps they were well aware of the code quality issues but hadn’t really thought about the customer value perspective, or how fast they learn. It also provides a balanced perspective, showing the good stuff as well as the pain points.

Read how Barry Overeem usde the Spotify Squad Health Check Model in this article:

Road to PSMIII

Sjoerd Nijland has written a nice series of blogposts about his road to PSMIII:

Definition of Scrum

Empiricism: Transparency

Empiricism: Inspection, Part One

Empiricism: Inspection, Part Two

Empiricism: Adaptation

Scrum Values

The Scrum Team

The Scrum Master

The Scrum Master’s responsibilities

The Product Owner

The Development Team

The Sprint

Sprint Cancellation

Scrum’s Artifacts

The Product Backlog


The Dark Side of the Scrum Guide

Sjoerd Nijland has written a great blogpost about his journey to PSMIII and the nuances in words from the Scrum Guide. Such as:

  • Framework, Methodology, Process, Techniques
  • Event, Meeting
  • Development
  • Done, “Done”, Ready, Shippable, Releasable
  • Self-organising
  • Facilitate, Serve
  • Visible, Open, Transparent, Accessible
  • Titles vs Roles and Multi-disciplinary vs Cross-functional.
  • When is a Sprint Backlog created? And is it considered output of a Sprint Backlog?
  • When does the Sprint Planning take place?

Read the complete post here:

Asking the right questions; how to help a Scrum Team switch from a technical to a functional Backlog

One of the biggest challenges for a Scrum Team is to switch from a technical to a functional perspective on their work. Christiaan Verwijs has developed a set of helpful questions that often trigger teams into a functional frame of mind.

  • Why is it important that we implement this?
  • What problem of stakeholders and/or end-users do we solve by doing this?
  • What personas benefit from this, and why? (given that you have personas)
  • How would sales explain the benefits of this to customers and/or users
  • What reasons would an end-user have to want this?
  • How would you explain this to a colleague who is not part of this project?
  • How would you explain this to your spouse, at home, after a hard of work?
  • What would you show during the review to demonstrate that this is working?
  • If you are a user, how would you test if this works?
  • What changes would a user notice after implementing this?
  • What stakeholders benefit from this, and why?
  • If we wouldn’t do this, what would end-users and or customers miss or be unable to do?
  • What compliment would a happy user of customer give after delivering this?
  • How would you explain this to a potential end-user?
  • What steps would you go through in the application to test if this works?
  • If we’d put this in release notes that will be read by end-users, how would we announce it?

Read the original article here:

Liberating Strategy

Liberating Strategy begins and ends with Liberating Structures (LS). They are simple rules that make it possible to include and engage every voice in shaping the future and strategy. LS can be used to not only create a different kind of strategy but also to transform the whole process of strategy-making.

Read the complete article by Keith McCandless and Johannes Schartau here:

The Reading List for Agile Newbies

Barry Overeem created a list of must-reads for agile newbies:

  • The Agile Manifesto
  • The Scrum Guide – Jeff Sutherland, Ken Schwaber
  • The Power of Scrum – Rini van Solingen
  • Scrum: A Pocket Guide – Gunther Verheyen
  • Succeeding with Agile – Mike Cohn
  • The Agile Samurai – Jonathan Rasmusson
  • The Five Dysfunctions of a Team – Patrick Lencioni
  • The Scrum Field Guide – Mitch Lacey
  • The Phoenix Project – Gene Kim, Kevin Behr, George Spafford
  • Kanban – David J. Anderson
  • Clean Code – Robert C. Martin

Read his complete blogpost here: