As Scrum Masters we are constantly facing a changing environment. Every Scrum Master needs to learn about change, change methods and tools that work in practice. In this episode we dive deep into the change approach that Mike Burrows developed based on his experience as a coach and leader in the software industry.
In the past few years a few new trends have emerged in the Agile community that have challenged some of the basic assumptions of how software should be delivered. The first one, #NoProjects is challenging the idea that software work is best managed as a project. As Allan puts it in this episode: “Successful software does not end. It continues. And projects are for temporary endeavours, that have a known start and fixed end. That’s now how software is developed today.”
With that start to the episode you can expect that many unconventional (and inconvenient?) ideas will be shared in this podcast focused on the latest trends in how to manage software development.
Distributed teams are a fact of the multinational organizations we work with. Hiding from it is not going to remove that. And crying “distributed agile = bad agile” is only going to alienate people who genuinely need to learn to cope with the fact that distributed teams are the new normal.
There are good and bad ways to adapt to the reality of distributed software, and copying the methods and practices from co-located teams into the digital world is not enough. Molood shares some of the common anti-patterns that arise when we plainly try to copy the co-located team methods into the new distributed reality.
One such example is the communication channels: trying to copy daily meetings from the co-located team into a digital world will eventually bump against the frustratingly low quality sound of some conference room setups. Molood suggests a different route and shows how a team she helped took full advantage of Slack (or any other asynchronous communication channel) to make their daily meetings for effective, and efficient for everyone involved.
Marcus is the author of Salvation: The Bungsu Story, a book we here at the Scrum Master Toolbox Podcast are helping to publish. This book is inspiring, and will definitely move you to action.
In this episode, we discuss some of the many techniques Marcus used in Indonesia while he was helping the team at The Bungsu Hospital literally save the hospital from bankruptcy. And that’s not an over-statement!
Click to liste to the interview and read more about the topics of this episode.
Karin has a long experience helping teams and businesses to use self-organization as a way to drive business success. She’s worked as an interim-CEO in several companies where she helped drive major changes and positive business results using the principles and ideas behind self-organization.
Self-organization is not only for small teams. Karin shares with us the stories of the businesses where she worked, and how some fundamental changes enabled not only self-organization but also major business changes.
Read on for the detailed insights from this episode.
Psychological safety has been claimed to impact greatly the productivity and well being of teams. Building trust is how we reach psychological safety, but trust is a touchy topic for teams. Scrum Masters try to build trust between team members, with stakeholders, with other teams, with the Product Owner. Trust maybe one of the critical ingredients that allows collaboration to emerge. But how do we build trust? How do we learn what works, and what doesn’t when building trust?
Tim Ottinger shares his learning in this BONUS episode on trust, with a very practical approach, just like we like it here on the podcast.
Does your company need estimation? Listen to Erwin’s take. He’s a CEO. He should know.
Erwin has his own company and invests his own money in that company. For him, #NoEstimates solves a clear problem: too much time wasted estimating, instead of producing.
He challenges us to investigate how much money and time we already invest in that process, and then to measure the benefits. Are we getting enough return on the time and money we invest on estimation?
We learn about Erwin’s story of adoption. How he started with gradually larger projects, even at larger clients, and what he learned about the dynamics that push companies to make larger and larger decisions. Those larger decisions look like they require estimates, but why aren’t we questioning the need to make large decisions (large batch)?
Can we apply Agile ideas to the definition and execution of Strategy for our businesses? Trent Hone, award winning Naval historian, Karl Scotland, Agile Strategy pioneer, and Henri Mårtensson, long time author on the topic of business strategy got together to discuss just that.
Al Shalloway is a veteran of the software industry, and one of the early adopters of Agile. His company NetObjectives has even been podcasting on the Agile space way before Agile was popular. NetObjectives started their Lean And Agile Straight Talk Podcast way back in 2006, and you can still find many of their episodes on iTunes.
Business Value, the forgotten goal
In this episode we start by talking about the concept of “Business Value”, which is often forgotten in favor of some process goal like “adopt agile”. One can ask: what is the value of adopting Agile if we end up going bust?
But it is not so easy to define business value. In this episode we explore what might be the meaning or definition of business value in our organizations. We also discuss how we can help our teams focus on impact, not just more features delivered. And we end up talking about the need to have a process that adapts to many different organizations. Al talks about FLEX, a model NetObjectives developed after working with many organizations and understanding what is not working today when we try to scale Agile.
Developing an Agile model for organizations of many sizes
Al and his team have been around for a while. They have used XP, Scrum, Kanban, SAFe, Lean and more recently FLEX. From that varied experience, Al has learned a lot that he applies today in his company. From the insight that Scrum can only succeed if we take care of the people, to how SAFe is more appropriate to certain organizations, to the idea that management has to be an integral part of any transformation or Agile adoption. We talk about the Art of Action by Bungay, the orientation of management (hint: not top-down or bottom-up!), and double-loop learning. Double-loop learning is an essential part of transformation and actionable learning. We also refer to the New New Product Development Game, and other work by Nonaka, which informed the creation of Scrum.