We reflect on the time it takes to effect meaningful change, and how Scrum Masters can help teams learn to be patient in the process. We also discuss some critical tools that help change take hold. Specifically, how transparency and customer/stakeholder engagement can drive change in a team.
About Jassy (Jan-Simon Wurst)
Jassy moved from developer to being a Scrum Master and then a freelancer. He calls himself: the person to contact for help in On-Boardings, as well as a friend of bottom-up, power to the people! No top-down, no micro-management. No despotism in agile software development.
As we work with organizations in transition, we need to help teams and Product Owners make sense of the new ways of working. In this episode, we discuss how Scrum Masters can help Product Owners and teams find a way to collaborate when changing towards Agile. We share some tools that help large groups come together and learn to focus more on the impact they seek, rather than just the work they need to do.
About Bradley Pohl
Bradley is a young Scrum Master working for a mid-sized US bank that is currently undergoing an “Agile Transformation.” As a part of the Transformation, his training consisted of a 4 week Agile boot camp that was designed to build scrum masters from the ground-up. In his free time, he applies lean and agile principles to designing websites and providing social media advertising to local small business as Catch On, at catchontech.com.
OKR’s are a management tool that is gaining wide acceptance in the tech industry and other industries. The ideas are simple and should be simple to adopt, except they are not.
In this episode, we talk about what Jeremy learned about the roll-out of OKR’s at his company and how Scrum Masters can help adopt OKR’s the right way! Not a simple process.
About Jeremy Willets
Jeremy Willets is a Technical Writer turned Scrum Master/Agile Coach. He’s passionate about bringing Agile to all facets of his organization. He enjoys spending time with his family, making music, and drinking the finest craft beer the world has to offer!
As Agile and Scrum get adopted in more and more organizations, there’s a need to help organizations replace the old coordination mechanisms, like the Program (several projects coordinated via a centralized organization). In this episode, we talk about coordinating at Portfolio level many Scrum teams. We also share the steps to get that implemented at Elena’s company.
About Elena Popretinskaya
Elena considers herself a lifetime learner (she says, she absolutely loves having “aha!” moments). And she especially enjoys learning together with and from other people: her team and her friends. Elena is curious about everything: people, software craftsmanship and the world around. Elena is also a passionate hiker and a cross-country skier 🙂
When the organizations we work with need to adapt, sometimes that means changing the team composition. In this episode, we talk about a project that required the teams to re-organize and find a new way to collaborate. We discuss the impact of distribution on team formation and dive deep into a process of self-selection: when teams create themselves by allowing team members to find the right group to contribute to a mission.
About Catrine Björkegren
Agile coach and scrum master, Catrine has worked with agile for a decade in various areas like education, nuclear waste, government agencies, pharmaceutical and at the Royal Swedish Opera.
She believes that co-location is the key to building teams and that leadership is the key to successful agile transformation.
Teams can get carried away with the practices of Scrum and continue to follow them blindly, even when they are not getting the value they want out of those practices. In this episode, we tackle the need for the team to own the process, and take over changing it to meet their needs. Kristopher shares a technique that can help the team learn what it means, and effectively own their process.
About Kristopher Stice-Hall
Is the co-owner of Digital Maelstrom, a consultancy specializing in custom software, DevOps, managed cloud services, and information security. He has been doing Scrum Master work for over 10 years. He has worked with fortune 500 companies to companies less than 15 people. He also has been doing software development for 17 years.
Digital transformations are a dime a dozen at this time. Many organizations are going through a transformation of business model, not just adding IT to an old business model. However, digital transformations are not only about business models, but also about ways of working. In this episode, we talk about the change process inherent to digital transformations, and how Scrum Masters can help teams survive the big change we call Enterprise Agile Adoption.
About Varun Maheshwari
Varun is a Scrum Master and agile practitioner in Australia. He believes in “being agile” rather than “doing agile”. For him, Agile frameworks are not the goal, but rather “Delighting customers, Zero Defects, Quick ROI, Better team work, Excellent Quality & Shortest ‘Time to Market’” are some of the possible goals.
Sometimes, the teams and organization are excited about the change. Possibly the adoption of Scrum or some other Agile methodology. However, it is not enough to have the enthusiasm of the team. Without a clear direction for the change process, “business as usual” will catch up, the pressures of daily work will take over and the change will stall. We talk about how we can avoid, or recover from the “business as usual” pressure cooker that teams will inevitably face during the change process.
About Elena Astilleros
Elena coaches people who hate wasting their time with badly run agile ceremonies, meetings or projects. She gives them tools to get more out of their time while sprinkling in a little enthusiasm and cheerleading. You can find some of her tools in the forthcoming book Invisible Leader.
Scrum Masters can be change catalysts, and often they become an active part of Agile adoption at their organization. However, even motivated, energetic Scrum Master can burn out. Change is a long process, and it can’t keep going if only you are working on it. In this episode, we talk about the importance of creating a “guiding coalition” to ensure that change takes hold and progresses in an organization.
About Eduardo Ribeiro
Eddy is passionate about helping people, teams, and organizations foster a culture of continuous improvement where experimentation and embracing change becomes part of their DNA.
He’s also the author of the Beyond Lean Agile Blog, a Co-Founder of the Lean Coffee Portugal Community, Founder of Agile Online Community and Co-Founder & Director of Startup Grind Porto.
One rainy Monday, a developer runs a script. The whole database is wiped out, and there are no backups. What can we learn from this story? Scrum Masters must help teams prepare, and sometimes recover, from disasters. This is such a story. We also discuss how we can prepare our teams to avoid catastrophic failures.
Nedeljko is a Scrum Master and a full-stack developer who has been in the IT industry for the better part of the decade. He spent the last 5 years actively working as a Scrum Master with many diverse teams and projects who has helped him understand his role better. One of the core developers of the first VivifyScrum release, he has participated in its development product-wise ever since.