Podcast Summary

Podcast: Scrum Master Toolbox Podcast: Agile Storytelling from the Trenches
Host: Vasco Duarte
Guest: Salum Abdul-Rahman
Episode Title: The SECI Model of Knowledge Management Applied to Team Retrospectives
Date: August 28, 2025

Episode Overview

This episode delves into the intersection of knowledge management theory and effective agile retrospectives. Vasco Duarte welcomes Salum Abdul-Rahman to explore how the SECI model, a cornerstone of knowledge management, dovetails with the five-stage retrospective format. The conversation covers how retrospectives drive behavioral change, what true success looks like for Scrum Masters, and how discipline and adaptability underpin sustainable agile practices.

Key Discussion Points & Insights

1. Favorite Retrospective Format and Academic Foundations

[01:23–04:21]

• Salum’s Preferred Retrospective Approach:
  Salum favors the five-stage retrospective format, as presented in Agile Retrospectives: Making Good Teams Great. He links this approach to the SECI model of knowledge management, which involves four phases: Socialization, Externalization, Combination, and Internalization.

  "The different...central phases, like after the beginning, like after opening the retrospective and between closing the retrospective, the three phases really well mimic three of the phases in this academic organizational development model."
  — Salum Abdul-Rahman [01:55]

• The Role of Retrospectives:
  Retrospectives aren’t just for identifying problems or solutions; their cumulative intent is to shape behavioral change by fostering new knowledge and practices within teams.

  "When you put multiple [retrospectives] together, the outcome is behavioral change...Those are all forms of behavioral change."
  — Vasco Duarte [03:07]

  "The role of retrospectives is to create more knowledge...the behavior is different than in an organization that does not have this new knowledge."
  — Salum Abdul-Rahman [04:04]

2. The SECI Model’s Agile Roots

[04:39–05:14]

• Academic Backbone of Agile:
  Salum highlights that the creators of the SECI model, Nonaka and Takeuchi, also contributed to Scrum’s foundation through their influential work, “The New New Product Development Game”.

  "The people who created the Secchi model...also wrote earlier the new product development game article which is a major contributor for the creation of Scrum. So this is from the same academic heritage."
  — Salum Abdul-Rahman [04:39]

3. Defining Success as a Scrum Master

[05:35–08:23]

• Ultimate Success: Becoming Unneeded
  For Salum, the highest achievement is when the team evolves to sustain high performance and continuous improvement without relying on the Scrum Master’s support.

  "I want to make myself not needed anymore. So the biggest, like the most important role of a Scrum Master is to help the team to develop...when you are at the point that the team is learning then the team can develop themselves without your help. Then my job is done."
  — Salum Abdul-Rahman [05:35]

• Building Team Resilience:
  Once teams are self-sufficient, the next step is structuring for resilience—preparing them for challenges beyond daily operations.

  • Salum notes that Scrum Masters are often only brought in after significant problems arise, making early proactive intervention a rare luxury:

    "...often you're brought in to a project that needed a Scrum Master six months ago...Scrum Masters and Agile coaches are brought in when the tire fire is already three stories high."
    — Salum Abdul-Rahman [07:00]

4. The Dynamic Nature of Teams and Organizational Systems

[09:47–11:21]

• Teams Are Never Static:
  Vasco discusses how team dynamics shift daily, due to both internal and system-wide changes, stressing that Scrum Masters must constantly reassess context, not rely on previous stability.

  "Even those [teams] that get to that point, there are other conditions within the system but outside the team that start to affect team behavior and start to create deterioration...when we go to work, it's a different team from the team it was yesterday because something happened when we weren't there."
  — Vasco Duarte [10:02]

• Systemic Reflection and Team Roles:
  Both host and guest agree on the necessity of the three Scrum roles (Scrum Master, Product Owner, Team) for functioning agile teams, noting especially the systemic risks when these are absent:

  "...when you put a team together that has no Scrum Master and some teams are also put together without a product owner...that's not what a software development, a successful software development ecosystem looks like."
  — Vasco Duarte [08:23]

5. Maintaining Team Cohesion: Recalibration Workshops

[11:21–12:14]

• Recalibration Over Time:
  Salum shares a practice from Reactor: periodic recalibration workshops for teams, akin to mini-kickoffs, to restore shared understanding and adapt to evolving team contexts.

  "Teams should have these sort of recalibration workshops every once in a while...just to create the shared understanding about like, what's going on, how have we changed? I think that's a really useful tool for that."
  — Salum Abdul-Rahman [11:21]

• Discipline in Agile:
  Agile's freedom demands high discipline—self-organization doesn’t work without the team's conscious commitment to maintaining practices.

  "People under appreciate how much discipline working in agile ways requires from the developers because you get a lot of freedom, but that freedom comes with the cost that you need to be really disciplined in how you work as a team."
  — Salum Abdul-Rahman [11:58]

Notable Quotes & Memorable Moments

• "The role of retrospectives is to create more knowledge...the behavior is different than in an organization that does not have this new knowledge."
  — Salum Abdul-Rahman [04:04]

• "I want to make myself not needed anymore."
  — Salum Abdul-Rahman [05:35]

• "Scrum Masters and Agile coaches are brought in when the tire fire is already three stories high."
  — Salum Abdul-Rahman [07:00]

• "When we go to work, it's a different team from the team it was yesterday...conditions around may change the triggers in the system and may change the behaviors and the expectations within the team members."
  — Vasco Duarte [10:02]

• "People under appreciate how much discipline working in agile ways requires...that freedom comes with the cost that you need to be really disciplined in how you work as a team."
  — Salum Abdul-Rahman [11:58]

Timestamps for Important Segments

| Timestamp | Segment Description | |-----------|--------------------------------------------------| | 01:23 | Salum introduces his favorite retrospective format and SECI model connection | | 03:07 | Host and guest discuss behavioral change as a retrospective goal | | 04:39 | SECI model’s authors and link to Scrum’s academic foundation | | 05:35 | Salum’s definition of success as a Scrum Master | | 07:00 | Challenges faced when Scrum Masters are brought in late | | 09:47 | Teams’ dynamics and the importance of daily reassessment | | 11:21 | Practice of recalibration workshops and the necessity of discipline in agile teams |

Conclusion

This episode provides a rich, conceptual yet practical discussion for Scrum Masters and agile practitioners, connecting theory (SECI model & academic origins) with actionable practices (retrospectives, recalibration workshops). It reinforces the idea that retrospectives are not just for finding fixes—they are instrumental in shaping team behaviors and capabilities. Success as a Scrum Master is defined by fostering a team's self-sufficiency and adaptability, with discipline as a foundational requirement for any agile journey.