In this company, Denniz supported a DevOps transformation. As time went by, it was clear that management had to start taking the coaching role that Denniz had taken until then. While working through this change, Denniz learned some important lessons about change, and how to be able to step back from the work, so that he could be a facilitator.
Denniz has both huge academic and practical experience. He studied agile teams for his PhD at Swiss Federal Institute of Technology in Zurich (ETH Zurich) before becoming a Scrum Master and freelance consultant in 2016. Denniz believes the key to becoming more agile is to establish what he calls “enabling structures.”
In this transformation, there was a moment that may have changed the course of events. In this moment, the organization allowed the teams to self-select. Samantha and Brian share that moment, what they did, and how they prepared for a high-risk, but a transformative moment: the self-selection workshop.
About Samantha Menzynski and Brian Ziebart
Samantha Menzynski has spent her entire career in software. Starting in support and account management, moving to customer support management, and with Penta’s transformation to Scrum becoming Scrum Master for the Core product team.
Brian Ziebart started his career in software as a developer but found himself wanting to move towards coaching and developing people rather than product development. When Penta’s Scrum transformation started in August 2019, he jumped at the opportunity to work more with people while still staying involved with development.
Even when we try to help the teams we serve, we often encounter problems that the team itself can’t solve. When that happens, what’s a Scrum Master to do? In this episode, we explore what Scrum Masters can do when the issues plaguing the team extend beyond the team’s boundaries.
About Jeffrey Koors
Jeff started his studies and career as a fine artist and has gone on to use his creative thinking and vision to help many organizations find ways to design systems, solve problems and embrace Agile. Jeff is also the co-founder and host of Coaching Agile Journeys.
Charles was visiting an Agile Coach Bootcamp organized for Scrum Masters and Agile Coaches to get a solution to his problem: how to make other changes. It was then he noticed that everyone in that room had the same problem. What Charles realized was that his role as a Scrum Master was not to lead change, but rather to create the conditions for change to happen on its own. In this episode, we talk about the method that Charles uses to foster change-friendly environments. We also refer to a reference book: Leading Change by Kotter.
About Charles Rodriguez
Charles has been working in software development for 16+ years with roles ranging from a database developer to manager to agile coach all in an effort to ‘try to make things better’ for future generations joining the IT industry.
Christian is an enthusiastic Release Train Engineer, Certified Professional Co-Active Coach, and Facilitator who started his agile journey as a Product Owner. Later he turned his back on technology and focused on people and relationships. He is passionate about creating space for people and teams to be the best they can be.
Raphael shares with us the largest change initiative he’s ever worked with: adopting Agile at his company, ITLogix, and in projects with his clients. We go through the deliberate steps he took, and how he built a learning organization first, and – using Scrum – helped his organization adopt Agile, and later move all projects to Agile even with clients that did not use Agile internally.
About Raphael Branger
Raphael Branger is a Certified Disciplined Agile Practitioner and a pioneer in adapting agile methods in the context of data and analytics projects. He works as a Principal Consultant Data & Analytics at IT-Logix in Switzerland with more than seventeen years of experience in business intelligence and data warehousing.
As Marianne worked through a long Agile transformation, she faced a very common pattern: the focus on velocity. A manager was constantly asking for the team’s velocity, and the Scrum Masters have to provide that information. That’s when the change started. Instead of augmenting against that behavior, the Scrum Masters explored why there was that need, and learned about why that manager was requesting that teams report their velocity. That understanding led to a deliberate change process that helped the teams, the organization, and that manager!
About Marianne Erickson
Always an enthusiastic Agilist, Marianne is proud to be a part of the Agile Transformation Team at AAA, a company that empowers its team members to learn, grow, empower, and do the right thing!
In this episode, we explore a story that many of us have faced. When someone in the organization gets interested in one of the many scaling frameworks for Agile, and their focus shifts away from the work, and into the framework itself. We discuss possible anti-patterns that emerge when adopting SAFe (Scaled Agile Framework), and what Scrum Masters in the organization can to together to help move the teams, and the leadership to a more Agile approach to their scaling efforts.
About Steve Jaccaud
Steve is an Enterprise Agile Coach, Volunteer, Speaker, and Musician in Boston, Massachusetts. When he’s not leading workshops with creative software organizations, he’s probably working on an album or deep in meditation!
This story starts with a goal. The company wanted teams to “build and run” their own applications. How could they put that change into practice? Willem-Jan started by suggesting a full, cross-functional Scrum team for a product. That got accepted, but what came next was bold, unexpected, and kick-started the cultural change needed to bring the company to the next step in their transformation.
As a Scrum Master and writer for Serious Scrum, Willem-Jan is passionate about helping people understand what it means to work in a complex Product Environment. Which is how he likes to talk about Scrum.
When this project started, there were multiple teams involved that had not yet collaborated effectively. On top of that, the project was very challenging for everyone involved. Justin worked with the teams to help them realize that their shared challenge could be resolved if they were able to change their approach to collaboration. In this episode, we share a great story of transformation at the team level that yields many insights for changes across the whole organization.
A Product and Agile Coach with product management experience ranging from payments to enterprise custom build. Justin has hosted a small series on Product Management and another series on Being a Scrum Master.
Justin has also pioneered a new form of Canvas to help bring teams together. All of this information can be found on his blog: http://www.ponolabs.com/labs/