Transcript
Vasko (0:04)
Hey there, agile adventurer, just a quick question. What if for the price of 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.
Host (1:11)
Hello everybody. Welcome to our Wednesday the Change Leadership episode this week with Somia Mehra. Hey Somia, welcome back.
Soumya Mehra (1:20)
Thank you for having me again Vasco.
Host (1:22)
Absolutely. So Wednesday is the change episode. And when we talk about change, of course we talk about a change process, right? Like certain things that happen that lead to the certain outcome that we are trying to reach. So we want you to tell us such a story as a story of a change process and walk us through the steps, like what were the key things that happened during that change process? And as you go through those steps, highlight for us the tools, the tips, the tricks and the techniques you learned back then that you still apply today.
Soumya Mehra (1:56)
Okay. Change process that was part of it recently happened like one month. Just, it has been only one month I've been part of a change process. So my current organization was doing the business unit split like having two business units. So then at that time we thought, okay, few of the people from the current organized like the current unit will go to the newer unit. And we've hired few new people also in the team. So the current, the previous setup of our teams were like we were having huge teams with having multiple products under each team. So then the focus was more scattered. So we already knew that this is something which is impacting our efficiency. So when this business unit split happened, the upper organization thought like this is the correct time to do the reorganization making team smaller and better. So most of the time you see like these are the, this, these are the decisions made at the top level. They decide what portfolio, which team will have and how, where, who will go and they just inform them. But this time something different happened. The top management ask us, we are the team of five to six Scrum Masters in our organization that, hey guys, we are inviting you to create a process and have this new reorganization and you brainstorm it and come up with a process and give us the new structure. We as a star master, we were always having this, we were always getting this feedback in our town hall, in our normal teams meeting or the business unit meetings, that people are complaining that, okay, the change, change happens in the company, but we are never part of it. We are, we are just told like, okay, these are the changes and that's how we are going to operate. And they were not liking this kind of approach. So when we got this opportunity, we thought of including the team, whoever is impacted by the whole process, into it so that they feel they are part of it and they have control over making these changes. And that's how we made this whole change in the organization. The next thing that you asked me was the step by step how we did it. So the first thing that we did was we went to the upper management, asked them for the constraints, like, what are the things that you just don't want to get changed or what are the things you want to happen when the teams are getting, you know, decided, like how they will form? The reason behind it was not to go back and forward. Like we do a whole formation with team, we go to management and the management is saying, oh, but we had this constraint, you did it wrong and then doing it. So we first followed the constraint. Once we got the constraint, the Scrum master decided like, before going in front of team and doing this workshop with them, let's do it by ourselves. Each Scrum master, based on the constraint, tried to create the teams to see what kind of different approaches each one is taking. Then we collaborated and share our feedback and we saw, okay, you can have a location based team, you can have a skill based team, you can have a team where, where there is a constraint. Like, okay, these two people don't like to work together, so let's split them and have them in a different team so that they feel happy about it. So these are the kind of feedback we got. So once we were done with this, then we had a first workshop with the product owners, which was the bumpier one. Because now we have to decide what.
