Episode Summary: When Scrum Practices Aren't Enough – Learning to Sense the System | Terry Haayema

Podcast: Scrum Master Toolbox Podcast
Host: Vasco Duarte
Guest: Terry Haayema, International Author, Speaker, Agile Trainer, & Coach
Air Date: September 22, 2025

Main Theme

This episode dives into why just following Scrum practices is not enough for team success. Terry Haayema shares a pivotal story about moving beyond surface-level Scrum and learning to "sense the system"—understanding how organizational structure and metrics can drive behavior in ways that hinder true agility. The conversation centers on the importance of recognizing system-wide influences, the pitfalls of misaligned KPIs, and the evolving role of the Scrum Master as an organizational catalyst rather than just a process facilitator.

Key Discussion Points & Insights

1. Terry’s Accidental Scrum Journey

• [02:02] Terry recounts how he became a Scrum Master by chance, coming from a lead developer background in New Zealand.
  • Given a book as his only training, he and his team learned through experimentation:

  "We floundered about not really knowing what to do. But we were blessed to be in a space where experimenting and trying things out and getting them a bit wrong and adjusting them was okay." — Terry Haayema [02:37]

• The experience shifted his perspective from loving technical problems to finding people problems "more interesting and much more rewarding." [03:18]

2. Fail Monday: When Practices Alone Don’t Work

• [05:05] Terry shares a failure from his second Scrum Master role:
  • He focused on enforcing practices (standups, retros, planning), assuming these would suffice.
  • The turning point came when he realized the team was not responding, and systemic issues were blocking progress.
• The need to explore what was holding the team back led to the realization that broader organizational structures were undermining the Scrum framework.

3. The Power of Sensing the System

• [06:58] The organizational design separated developers, testers, and analysts under different managers and individual KPIs.
  • Example of dysfunctional KPIs:

  "We literally had KPIs for developers about less defects and KPIs for testers about finding more defects. Right. I kid you not." — Terry Haayema [09:13]

• This incentivized conflicting behaviors: developers hoarded work, testers felt pressured to find any error, and mistrust grew within the team.
• The environment bred conflict, undermining collaboration and eroding the team structure essential to Scrum.

4. Changing the System: Conversations with Leadership

• [09:02] Terry describes how they had to engage management to modify KPIs:
  • Shifted from individual to more collaborative, though still imperfect, metrics (e.g., defect leakage measured for developer and tester together).
  • Small changes fostered slightly better collaboration but highlighted the limits of change without addressing deeper systemic issues.

  "The learning for me from that was you do need to understand the system that you're in. The Scrum Master is not just the coach for the team, they're the coach for the organization as well." — Terry Haayema [10:54]

5. Scrum Masters as System Catalysts

• [11:00] Vasco emphasizes the broader responsibility of Scrum Masters:

  "We need to be looking at the end to end performance of the system. And that starts with first defining what the system is... Not the people and not individual teams either." — Vasco Duarte [11:19]

• Both highlight the need to measure and optimize the system holistically, not at the individual or even single-team level.

Memorable Quotes

• "People problems were more interesting and much more rewarding. Even though it's more complex, a lot harder, but it's a lot more rewarding and I love it even more than I used to love solving technical problems." — Terry Haayema [03:20]
• "I was there trying to drive processes and practices and the team were not actually responding ... the broader system was the thing that was actually driving the behaviors in the team." — Haayema [05:35]
• "You imagine in a team, people disliking each other. They don't want to talk to each other. They don't want to actually share anything meaningful when we're coming together for our various events." — Haayema [09:33]
• "Scrum Master is not just the coach for the team, they're the coach for the organization as well." — Haayema [10:54]
• "First start by defining what the system is and then start measuring that system. Not the people and not individual teams either." — Vasco Duarte [11:30]

Timestamps for Key Segments

• [02:02] Terry’s origin story – becoming a Scrum Master by accident
• [05:05] Main failure story: why enforcing practices failed
• [06:58] Realization: org structure & conflicting KPIs as root cause
• [09:02] Attempting system change—modifying KPIs, engaging management
• [10:54] Big learning: Scrum Master as organizational coach
• [11:19] How to define and improve the system, not just individuals or teams

Tone & Takeaways

The episode is candid and practical, focusing on blind spots that even experienced Scrum Masters can fall into when they limit themselves to rituals and practices rather than addressing systemic organizational blockers. Both Terry and Vasco maintain an approachable, honest, and slightly humorous tone. The central message is clear: Success in Scrum is less about following ceremonies and more about understanding and influencing the organizational system as a whole.

For Scrum Masters and Agile practitioners:
This episode is a prompt to look beyond daily routines, to have courageous conversations with organizational leaders, and to continuously develop your ability to sense and influence the entire system for sustainable, team-wide agility.