In this episode, the focus is on the challenges faced in a delivery factory where multiple teams are required to collaborate in order to deliver a feature. However, these teams were siloed and lacked collaboration, leading to missed deadlines and integration problems. The first step was to gather facts and data to identify the causes of delays. The next challenge was to create a vision for a cross-functional team, but faced resistance from other teams. Persistence was key in convincing the organization to adopt a cross-functional approach. Although the team faced initial failures, the advice is to have a thick skin, learn from failures, and try again. To help understand and navigate this type of challenges, Takunda recommends the book is Team Topologies by Skelton and Pais, who have been previous guests on the podcast.
Want to Improve Your Change Management Results? Discover the Lean Change Management Approach Today!
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 Takunda Noha
Takunda is a seasoned change agent. He specializes in turning dysfunctional teams into high performing teams.
We start this episode, reflecting on Tim’s journey of realizing the importance of working collaboratively and embracing agile methodologies. Tim noticed early on that he drifted to teaching and providing assistance to others rather than actively developing software. After a while, he moved to consulting in Agile, and in that role, he noticed recurring patterns and struggled with unclogging processes that seemed to be missing something crucial. Over time, frustration set in. He felt like he was fighting an uphill battle and highlighted the disruptive nature of Agile, which aimed to uncover and solve problems but often revealed bigger and deeper underlying issues.
The big problem with Agile adoption, and what we can do to prepare for it
In this segment, guest Oz emphasizes that we all work in a complex environment and are change agents. Oz shares a story about a team that faced problems with its product owner, who would add stories to the sprint backlog without refinement and interrupt the team even on the last day of the iteration. As a result, the team lost trust in the PO.
To address this challenge, Oz recommends making sure the team has an agreement on how to bring new stories into an ongoing sprint and discussing the team agreement with the PO. Oz also suggests bringing up the topic in the retrospective when the PO introduces a surprise story. Oz acknowledges that these conversations can be difficult, especially when the PO is a good friend of the team’s manager, but emphasizes the importance of building trust and ensuring shared understanding.
Featured Book of the Week: Leading Change by John Kotter
Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters
Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today!The Tips from the Trenches – Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!
About Oguz Ozyurt
Oz came from a technical background, and has worked across multiple industries, applying agile practices toward the technical and non-technical areas. He is passionate about agile, he has leveraged his passion for delivery value and agile practices by coaching, teaching, mentoring many teams to transform from traditional software development life cycle to Agile principles and practices.
This week Jurgen is with us to talk about his latest project: unFIX.work.
Jurgen shares his own experience as a product developer (Mindsettlers), and the critical lessons he’s learned as a Product Owner for his own business. We discuss how hard it is to define the real problem, as seen by our customers, and the market at large.
Are you having trouble helping the team work well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it atbit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.
About Jurgen Appelo
Jurgen Appelo is an entrepreneur, an author, and keynote speaker who applies Agile to his life and his businesses. He’s also prolific writer on all topics business and agile. He wrote Management 3.0, How to Change the World, Managing for Happiness and his latest book about entrepreneurship and product development: Startup, Scale up, Screw up.
Setting up teams to work collaboratively is one of the challenges that organizations go through when adopting Agile. The functional team setup (all DBAs, all testers, all windows devs together, etc.) is not acceptable for teams that want to quickly develop and deliver products and services to the market. But neither is it possible to have all possible skills (sometimes 10’s of skills) in one team because organizations simply don’t have that many people with certain skills.
In this episode, we talk about the possible team topologies, and how each of those affects our ability to deliver in different organizations.
How we set up teams directly affects the quality of the software teams deliver