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 as I like to call it this week with Anamaria Unguriano. Hey Anna Maria, welcome back.
Anamaria Unguriano (1:23)
Hello. Hello.
Host (1:25)
So change, of course is the big topic of our Wednesday episode. We want you to tell us the story of a change process, something that was important in that organization or team or even for the person. And we want to explore how that change process happened because we want to understand the tools, the tips, the tricks, the techniques you used back then that you still apply today. So tell us that story. Anna Maria.
Anamaria Unguriano (1:56)
Is that I spartan organization where alignment requests with the business strategy Companies should change to using tool as JIRA for backlog all types of backlog management, requirements management. So they needed to move from their actual ALMA to this new tool jira. Okay, so it was part for impacting different teams because we spoke for a large organization here which they use their Agile framework scale Agile framework say. So the change process have been a journey in the sense that at the beginning requires some discussion with the key stakeholders. It's important to have the buy in from the key stakeholders, for example the managers, the business owners for those teams. So we require a plan to present why we are doing this and what's the value. Highlighting the importance that this tool provides like transparency and alignment helps support the dependencies, for example, for sure we had a lot of push back every change we are human at the base. So every change comes with a phase of pushback and it's involved like reasoning the cost of changing the impact of the release is. So it's important to have a plan or to do this change to not impact our delivers iteratively, incrementally and to support this first we continue with the strategy of value. But on my role as coaching and supporting this change transformation. Okay, I think I constructed some change agents if I could say so I looked between teams and I had some assessment with the teams to say what involves and I spotted which are those members who believed in this change and I worked with those police. I think you cannot go alone in a change in a transformational change.
