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: https://medium.com/the-liberators/how-i-used-the-spotify-squad-health-check-model-f226c6fe0fdb

Road to PSMIII

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

Definition of Scrum
https://medium.com/serious-scrum/definition-of-scrum-2d1f224256c

Empiricism: Transparency
https://medium.com/serious-scrum/empiricism-transparency-33adad8fbba2

Empiricism: Inspection, Part One
https://medium.com/serious-scrum/empiricism-inspection-part-one-cc4cd8bf98a8

Empiricism: Inspection, Part Two
https://medium.com/serious-scrum/empiricism-inspection-part-two-fafb785bd0c0

Empiricism: Adaptation
https://medium.com/serious-scrum/empiricism-adaptation-975f044a09b2

Scrum Values
https://medium.com/serious-scrum/scrum-values-1203813e0220

The Scrum Team
https://medium.com/serious-scrum/the-scrum-team-75b8004a4bc2

The Scrum Master
https://medium.com/serious-scrum/the-scrum-master-729e223f4b64

The Scrum Master’s responsibilities
https://medium.com/serious-scrum/the-scrum-masters-responsibilities-7ee05cae707e

The Product Owner
https://medium.com/serious-scrum/the-product-owner-6b7a63fef8fe

The Development Team
https://medium.com/serious-scrum/the-development-team-575d69054a9b

The Sprint
https://medium.com/serious-scrum/the-sprint-40d0ccc895f9

Sprint Cancellation
https://medium.com/serious-scrum/sprint-cancellation-c9a9c66e8c99

Scrum’s Artifacts
https://medium.com/serious-scrum/scrums-artifacts-6f07abfab11

The Product Backlog
https://medium.com/serious-scrum/the-product-backlog-7aec7daf844f

Estimation
https://medium.com/serious-scrum/estimation-103de626551e

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: https://medium.com/serious-scrum/the-dark-side-of-the-scrum-guide-835b298f8140

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: https://medium.com/the-liberators/asking-the-right-questions-how-to-help-a-scrum-team-switch-from-a-technical-to-a-functional-bee6c1598487

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: https://medium.com/@keithmccandless/liberating-strategy-6fda41f6c1

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: http://www.barryovereem.com/the-reading-list-for-agile-newbies/