change leadership Archives - Page 2 of 53 - Scrum Master Toolbox Podcast

Gemma Murray: Small Commitments for Large Organizational Change, A Practical Approach for Scrum Masters and Agile Coaches

In this episode, Gemma discussed the concept of organizational change and how to approach it in an effective and practical way. She emphasized the importance of starting with small commitments, using the example of a team struggling with capacity and carrying issues from sprint to sprint. Gemma suggested asking for a commitment from the team to try a new approach for three sprints, as the first sprint may feel clunky, the second sprint will have less cognitive load, and the third sprint will provide empirical data to assess the impact.

She also shared her approach to making changes in large organizations, by seeking a small set of volunteer teams to try out the change and give feedback. This method helps to make the change practical, removes resistance, and gives empirical data for reassessment. Overall, Gemma emphasized the importance of giving change a chance by committing to trying it for three sprints before making a final decision. This “give it 3 sprints” mantra Gemma shares with us is not only helpful when collecting data but also energizes the team and removes resistance.

As Scrum Master we work with change continuously! Do you have your own change framework that provides the guidance, and queues you need when working with change? The Lean Change Management framework is a fully defined, lean-startup inspired change framework that can be used as the backbone of any change process! You can buy Lean Change Management the book at Amazon. Also available in French, Spanish, German and Portuguese.

About Gemma Murray

Gemma works as an Agile Coach for MOO, a branding company whose vision is to provide ‘Great design for everyone’. Having worked in various change roles using both waterfall and agile approaches throughout her career, Gemma believes in the diversity of teams to unlock innovation, creativity and delivering value.

You can link with Gemma Murray on LinkedIn.

Tinatin Tabidze: Scaling Agile Teams, a Proactive Change Management approach

Tinatin highlights the importance of being proactive in change. She stresses the need to be aware of what can be changed in one’s role and in the team, and to talk to the manager and peers to assess the changes needed.

Working with her colleagues in a change team, they decided to create a framework/guide for scaling agile in that company and with the teams involved. The process involves finding the need, identifying the source of the need, minimizing dependencies when scaling, accepting and preparing for initial failures, being one’s own critic, staying focused on the change, defining a clear picture of where they want to be, and presenting data to the team to help them reflect and define the changes they want to commit to. Tinatin’s tip is to listen to the team, present data, but avoid jumping to conclusions and let the team come up with their own interpretation. A challenge that we should take on as Scrum Masters!

About Tinatin Tabidze

Tinatin Tabidze is a Scrum Master currently working in Stuttgart, Germany. Originally she started out as a project manager. She has experience with multiple scrum and kanban teams, working with scaled agile frameworks.

You can link with Tinatin Tabidze on LinkedIn.

Bram De Block: The case for Agile Evolution, Overcoming Dependencies, and Improving Team Collaboration through Product Domains

In this episode, Bram discusses the topic of agile evolution, a process of going beyond adoption, and adapting, and improving their agile methodologies. He explains that his organization used to work in Squads (based on the Spotify Model), each with their own backlog, but found that this resulted in a lot of dependencies and some teams had no “high value” items on their backlog, while others were too busy to deliver on the valuable items they had in their backlog.

He describes how that organization evolved to using Product Domains instead. The change team used MURAL to help visualize the changes, and invited people from every team to join and build a picture of the future with Product Domains. In that process, they went from 17 squads to 7 product domains.

Bram also provides tips on how to make the changes super clear, write down what the teams and organization will STOP/START/CONTINUE, and have follow-up sessions while timeboxing the whole work of defining the “future state”.

He highlights the importance of commitment and timeboxing as a trigger for action, and advises to avoid the anti-pattern of considering the “next change” as the final word. The episode aims to help organizations evolve their agile methodologies, to overcome common challenges and to improve the collaboration and communication within their teams.

About Bram De Block

Bram is not an official trainer, consultant nor freelancer. He is just himself, supporting colleagues in applying and growing their own potential and getting stuff done. Bram started as a software developer for 10 years, then grew into a half-time agile coach, and finally, full-time “Global Agile Lead” at Skyline Communications. Something “special” he learned (even if he wishes it wasn’t special): the meaning and impact of “respect”.

You can link with Bram De Block on LinkedIn, or meet Bram face-to-face at this meetup he hosts in Belgium.

BONUS: Embracing Self-Awareness and Empathy in the Agile Change Process, Insights from Dustin Thostenson

In this episode, we explore Dustin’s personal experience with change during his career and share his lessons learned, and experiences with change in teams. Dustin notes that while he has found certain practices to be successful, sometimes things do not work out and this can lead to consequences like being fired. Dustin asks us to consider if our behavior could be perceived as telling others they are doing things wrong instead of being considered helpful by the team.

The Importance of Self-Awareness and Empathy in Agile Software Development

Continue reading BONUS: Embracing Self-Awareness and Empathy in the Agile Change Process, Insights from Dustin Thostenson

Pino Decandia: How to create a self-organized maturity assessment for Agile teams, and provide Agile adoption metrics to management

Pino was working in a large Agile transformation for a large telecommunications company. In that process, it quickly became clear that the teams needed to provide transparency on the Agile adoption process so that management would be able to help the Board of Investors understand how the adoption process was progressing. This brought up the topic of metrics, and how to measure teams and their adoption of Agile. In this episode, we discuss how to adapt the way teams reflect so that it provides useful insights for the team, as well as the necessary adoption metrics for management to follow-up, and report on.

About Pino Decandia

Pino started in software development but realized he was more interested in people than code. With experience, Pino came to believe that people can change; they don’t resist change but offer their own vision, which needs to be met.

Secondly, needs drive behaviors. To provide help, we must allow them to be clearly expressed. To set the example, we need to be ready to be the first to state our needs.

And thirdly, that ideological battles are meaningless.

You can link with Pino Decandia on LinkedIn.