Summary5 min read

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.

Loading summary

Transcript21 lines

[00:04]
A
Hey there agile adventurer, just a quick question.
[00:07]
B
What if for the price of a.
[00:09]
A
Fancy coffee or half a pizza, you could unlock over 700 hours of the best agile content on the planet? That's audio, video, E courses, books, presentations, all that you can think of. But you can also join live calls with world class practitioners and hang out in a flame war free and AI slop clean slack with the sharpest minds in the game. Oh, and yes, you get direct access to me, Vasko, your Scrum Master Toolbox podcast. No, this is not a drill. It's this Scrum Master Toolbox membership. And it's your unfair advantage in the agile world. So if you want to know more, go check out scrummastertoolbox.org membership. That's scrummastertoolbox.org Membership. And check out all the goodies we have for you. Do it now. But if you're not doing it now, let's listen to the podcast.
[01:12]
B
Hello everybody. Welcome to the Success Thursday, the big question of the week. This week with Saloom Abdul Rahman. Hey Saloon, welcome back.
[01:22]
C
Hello.
[01:23]
B
I'm here indeed you are to talk about success. And we'll talk about that in a second. But first share with us. Saloon, what's your favorite agile retrospective format and why?
[01:37]
C
Well, my favorite agile retrospective format is the five stage retrospective format and I presented in agile retrospective is making good teams. Great. I think it really captures the learning process. And this links to my university studies. I did a minor in knowledge management and there's a knowledge management like organizational learning development model called the SECI model. So there are four phases, socialization, externalization, combination and internalization. And I really think that the different that the three central phases, like after the beginning, like after beginning, like opening the retrospective and between closing the retrospective, the three phases really well mimic three of the phases in this academic organizational development model. So I think it really well, like understanding this model really well, really helps the team to actually create new knowledge, create new behavior that helps them succeed better.
[03:07]
B
And you said something that is really important, right? Like we don't often talk about it, not even here on the podcast, but the outcome of a retrospective or at least multiple retrospectives, not necessarily every retrospective, but when you put multiple together, the outcome is behavioral change. And when you look at it, I mean we talk about it in many different ways. Learning, solving problems, removing impediments, those are all things we talk about that come out of a retrospective. But in the end they are all forms of behavioral change. And that is because we need to adapt to the system as Deming used to say, a bad system will beat a good person every time. So we need to adapt, we need to be able to succeed in the system we're part of. And sometimes of course change the system that can only happen through behavioral change. So I think that's a very important aspect of this retrospective formats that we.
[04:04]
C
Choose to apply the role of retrospectives is to create more knowledge. And the way you see an organization that has more knowledge is that the behavior is different than in an organization that does not have this new knowledge.
[04:22]
B
Absolutely. So we'll put the link to the five stage retro format as well as the book of course and to the Secchi model of knowledge management so that people can go and investigate those further. But now let's focus on success and what that means for us. So saloon share with us before we.
[04:40]
C
Go to that I want to do I want to drop one more like this is one of my favorite academic tidbits is that the people who created the Secchi model, Nonaka and Takeuchi, it was published in I think the Knowledge creating companies is the name of the article they 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.
[05:15]
B
Absolutely. We'll put the link to those on the show notes and of course the new new product development game seminal paper for anyone interested in agile and we'll put the the link to the knowledge creating company as well. And now let's dive to success. Salum share with us, what does success mean for you as a Scrum Master?
[05:35]
C
I. 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 and like to develop themselves. And 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. There's a lot of work to get to that point. I'm not sure if I've ever reached it with any team, but there's a point where as a Scrum Master, if a team is functioning well and it's developing themselves, you start thinking about well what can I do to build resilience into the team? So it's not just like success but then you need to find a way to motivate the team to challenge itself in new ways in order to develop that capability. Often this is not necessary. Like I don't think there's really any team that didn't have enough external problems to overcome external or Internal that as a Scrum Master, I would be feeding them new or coming up with new challenges in order for them to develop themselves. But I think when you're reaching that point, then you need to have that discussion with management that is this team important enough that we want to start building the resilience above the operational capability. And then it becomes like a business decision whether I'm needed elsewhere. Because I think one of the sorry part about being a Scrum Master is that often you're brought in to a project that needed a Scrum Master six months ago. So you like being there from the beginning and say helping set up a team to success, helping them overcome their initial challenges, going through that storming process, it seems to be like that. That's a luxury very rare teams have that they have like that, that methodological support from Scrum Masters in the beginning. But Scrum Masters and Agile coaches are brought in like when the tire fire is already three stories high.
[08:23]
B
And that's actually a very good point because sometimes the Scrum Master role is understood as needed, but it always takes some to get somebody to come in and do that role for the team. Right. And this is why Scrum starts from the perspective that you need three key roles in a team. The Scrum Master, the product owner and the team members. Right. Because that's what makes a great team system. Now, we could all argue that Scrum does not tackle the wider systemic issues and so on. That's another point. We can discuss that in another episode. But that knowledge, that understanding that pattern that Scrum built is very important. When you put a team together that has no Scrum Master and some teams are also put together without a product owner, anti pattern of anti patterns, then we have a big problem because that's not what a software development, a successful software development ecosystem looks like. Right? And as you very well said, maybe at some point the team is working well, like there's no more need for a Scrum Master. Okay. Is this team important enough so that we need to build it to the next level? You called it resilience, adaptability, ability to cooperate outside the team boundaries and all of that are parts of it. Is this team important enough or is it time for me to move on and help another team? Right. I think that's a very important reflection for all of us to have at.
[09:48]
C
Some point or maybe step into more of an Agile coach like role that you're no longer with the team, but you're just contributing like maybe once a week a session or something like that.
[10:03]
B
I Also from my own experience now speaking in my role as a Scrum Master and also Agile Coach, I have never seen a team that has been in that stage where they are completely, fully operationally capable for a long time. Even those 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. And to illustrate this point, I very often say that when we go to work, it's a different team from the team it was yesterday because something happened when we weren't there, right? Like there could be personal issues, somebody's on vacation, there's an urgent meeting to discuss some future decision that changes the system. And that's also an insight that we need to take in as Scrum Masters when we go to work every day, we need to understand what is the system that is in front of me now, right now, right? Like, and of course it's obvious, if a team member changes, new team member comes in, whatever that is obvious. But even when the same people are there, the conditions around may change the triggers in the system and may change the behaviors and the expectations within the team members.
[11:21]
C
At Reactor, we have this practice that teams should have these sort of recalibration workshops every once in a while because they're similar to kickoffs but maybe a bit more limited in scope 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. But of course, as with retrospectives and all other things, if there is nobody reminding you of it, it's up to the discipline of the team. And I really think that 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.
[12:15]
B
Very well said, very well said. Thank you for sharing all of those insights with us today, Saloon.
[12:21]
C
No problem. Happy to be of help for anybody who might be listening.
[12:29]
A
Alright, I hope you liked this episode, but before you hit next episode, here's the deal. This podcast is powered by people like you. The members who wanted more than just inspiration. They wanted real tools and real connection to people who are practicing Agile. Every day we're talking access to over 700 hours of agile gold, CTO level strategy talks, Summit keynotes, live workshops, E courses, deep dive interviews, books, and if you're into no estimates, we got the pioneers of no estimates in those deep dive interviews as well. Agile Business intelligence, creating product visions, coaching your product owner courses, you name it. You'll get invites to monthly live Q&As with agile pioneers and practitioners, plus a private Slack community which is free of all of that AI slop you see everywhere. And of course without the flame wars. It's a community of practitioners that want to learn and thrive together. It's the best place to connect with community and learn together. So if this podcast has helped you before, imagine what you will get from this podcast membership. So head on over to scrummastertoolbox.org membership and join the community that's shaping the future of Agile. We have so much for you, so check out all the details@scrummastertoolbox.org membership because listening is great. It's important. But doing it together, that's next level. I'll see you in the community.
[14:18]
B
Slack we really hope you liked our show. And if you did, why not rate this podcast on Stitcher or itunes? Share this podcast and let other Scrum masters know about this valuable resource for their work. Remember that sharing is caring.