Change is never an easy process, and in modern organizations that is made even more difficult because of the complex links and dependencies between the different areas. In this episode, Ravi shares how by succeeding at change in one part of the organization, the problems became worse, a typical case of “local success and collective failure”.
About Ravi Jay
Ravi started his career as a Mainframes developer in 2004 and was introduced to agility in 2007. He went from hating Scrum Masters to loving Kanban very quickly but became a believer in agile methods after learning by losing money implementing SAFe in his London-based startup in 2011. Over 16 years, Ravi has specialized in driving value out of complex software, hardware, firmware, and organizational change programs using various large-scale agile and traditional methods across industries. He enjoys spending time coaching and building teams that create products, people love to use.
When it comes to software development, every Scrum Master knows about how the “incremental” approach is the way to go. That’s why it is so critical to learn from why that works and apply it to other changes, like organization or team changes. In this episode, we talk about the incremental approach to change leadership!
About Helen Garcia
Helen’s been in projects for over 10 years, everything from construction to pharma to more recently gaming. Not only does she want to bring an Agile mindset to organizations that are ready for change but she also strongly believes that Agile can be just as effective at home. Bringing value sooner, safer and happier thanks to Jon Smart it’s a quote Helen take most places!
This organization’s planning process was about commitments, not shared understanding. This led to teams planning their work, and invariably coming to the conclusion that they could not deliver “because others…”. The organization would then spend time reassessing the output of the planning process, but never addressing the root cause of the problem. In this episode, we learn about how Chris and others in that organization started to develop a completely different approach: Continuous Planning for a multi-team organization.
About Chris Foley
Chris is a Principal Systems Design Engineer at Red Hat working in the area of Engineering Improvement. He has over 20 years of experience in software and has filled PO and ScrumMaster roles. The team, to Chris, is the essence of the whole process and the Scrum Masters role is to help optimize that. He uses his experience from the sporting world to draw parallels around how successful teams function.
When Joe came into this organization, they were stuck in the never-ending discussion of how to best setup their teams to adopt SAFe. How can we help teams that are stuck in that situation? Joe shares how simple visualization techniques helped unstuck this team and get started with concrete steps in their journey to scaling Agile.
About Joe Auslander
Joe is into game/experience design and enjoys working with teams to solve unique problems. In the past this has been in areas of ship repair, crew coordination, television production and software delivery. Joe enjoys learning and sharing what he has learned and he particularly loves seeing people succeed.
Jakub was working in an organization that needed a culture change. At first, the difficulty was how to address the topic. Culture is a fuzzy enough idea that even talking about it isn’t easy. Jakub and the team at that organization decided to setup a conversation about emotions. Using a card-facilitation technique they helped the teams co-create the Vision for where they wanted the culture of that organization to go.
Jakub shares the aspects they focused on to be able to define, and later change the culture of that organization.
About Jakub Jurkiewicz
Jakub is a kaizen practice lead who participated in his first standup in 2005 and facilitated his first retrospective in 2007. Previously a software developer, team leader, Scrum Master and Agile consultant, Jakub is also, a podcaster and trainer at Agile Coaching Lab. Loves wine, bicycles and his wife (in the reverse order).
“Everything we do is about change.” This is the phrase we start the episode with. John shares his experience on how to bring and support change in organizations and teams. In particular, we hear the story of a startup, and how bringing people together to a shared goal was the task at hand.
Agile Person, for the team by the team, used to be a developer. Got into Agile via Extreme Programming (XP), then Kanban, then Scrum. Some of his key ideas are Principles over Practices, #noestimates, love working with teams and organizations, the softer side, finding what they and customers need and what works for them.
A “big bang” approach to Agile adoption isn’t easy to pull off, and it may not even be a good idea in some cases. That was also Laurens’ thinking until he saw it happen in front of his eyes. From one day to another, 900 people were trained, and moved willingly to an Agile way of working. If you are a skeptic of “big bang” agile transformations, listen in. You might be surprised!
About Laurens Bonnema
Laurens helps leaders create high-performance organizations by guiding them to embrace who they are. As Laurens puts it: “when leaders ignite their inner strength and capability—and lead from love—they soar beyond their expectations. That is how we create a world of work that we would want our kids to live in.”
Change management is primarily an exercise in managing expectations among all stakeholders. In this episode, we talk about the role that “small changes” have in that process. We also discuss how to find the motivation / needed changes by working with the teams we support. Nikoletta shares many tips on how make change thrive and overcome change resistance.
About Nikoletta Tatár
Nikoletta is an Agile Coach who is passionate about creating an environment where teams and individuals have the space to grow, deliver awesome products to customers, and have fun doing so. She is also a Collaboration Superpowers facilitator holding workshops online about remote working and collaboration.
Jeff is the author of Actionable Agile tools (available on Amazon, and direct from the author at bit.ly/aatbook).
In this episode, we discuss how the way we organize teams can impact the effectiveness of an organization. Jeff and Simone share the journey of a team, how it changed, and how that team structure change affected not only the team itself but also the organization around them.
Simone shares that, at Meltwater, they try to focus on “empowered product teams”, and how that differs from most team setups.
We refer to the book Inspired by Marty Cagan, and how that book influenced their view on how to organize and structure product development teams.
The first problem they tackled was the Product Owner being an outsider to the team.
Making the Product Owner, a first-order citizen in an Agile team
In this story, Lakshmi shares the story of an organization that was trying to move from “work as usual” to a more collaborative approach and improve their Agile practice. However, the teams were not clear on what success looked like. We discuss how we can help organizations move from focusing on the day-to-day only to linking everything they do to a higher purpose.
About Lakshmi Ramaseshan
Lakshmi considers Agile Coaching her true calling! With 20+ years in the software industry, her journey started as a developer on an agile team. After which she quickly realized good product development is all about having the right conversations, building happy teams, and being aligned with your customer.
Lakshmi is passionate about growing people, fostering trust amongst the team members, and building high-performance teams. She also believes in giving back to the community & paying it forward to help inspire others on their Journey!