NOTE: We want to thank the folks at Tuple.app for being so generous with their stories, and supporting the podcast. Visit tuple.app/scrum and share them if you find the app useful! Remember, sharing is caring!
In this BONUS episode, Antony, co-founder of RiverGlide and Head of Engineering at Ford Digital, joins us to share his experiences and insights from 30 years in software development, including 25 years in Agile practices. As a technical practitioner, leader, and consultant, Antony reflects on navigating remote work, overcoming challenges, and setting up successful remote software teams, while exploring future trends in the industry.
Antony reflects on his first fully remote software project, which took place during the pandemic when everyone was forced to work from home. While his team had been working together for 12 months, they struggled with traditional video conferencing tools that lacked the ability to support pair programming or mob programming effectively. This is when Antony and his team discovered Tuple, a tool that allows for seamless control sharing and a co-located pairing experience.
"Switching to Tuple was a game-changer for us in making remote pairing feel as interactive as in-person collaboration."
The biggest challenge Antony identifies in remote work is the loss of serendipitous moments—those random watercooler conversations that often lead to innovation. To address this, Antony encourages teams to create opportunities for these moments by structuring time for informal interactions and fostering a safe and open communication culture.
"You can’t recreate the watercooler, but you can create opportunities for innovation by encouraging open-door policies and setting up shared virtual spaces."
For Antony, real collaboration is critical to the success of remote teams. He grew up on XP (Extreme Programming) and believes in the power of pairing and mob programming. Antony emphasizes the importance of maintaining good practices from in-person work, such as prioritizing mental well-being, while adapting to the unique needs of remote teams.
"Collaboration is not just about tools—it’s about mental well-being, trust, and giving the team what they need to succeed."
Antony shares his approach to ensuring that teams remain aligned with clear goals and progress tracking. His teams focus on delivering small, incremental slices of work and using techniques like limiting Work In Progress (WIP). Rather than viewing user stories as a list of tasks, Antony encourages teams to focus on the user benefit and desired outcomes.
"It’s about the ‘why,’ not just the ‘what.’ User stories should focus on the goal, not just be a list of tasks."
Looking ahead, Antony predicts that tools will continue to evolve, with AI playing a more significant role in software development. He discusses the possibility of having AI participants in pairing sessions and shares his concerns about the convergence of tools that may lose focus over time. Antony encourages developers to experiment with new technologies and remain open to change.
"AI is the next frontier in software development, and we need to embrace how it can enhance our remote work experiences."
Antony notes that while many resources on remote work are often too generic, there are valuable tools and practices software teams can adopt. He recommends regularly rotating hosts during remote pairing sessions and setting aside time for retrospectives and discussions about the bigger 'why' behind the work.
"When pairing, rotate roles, reflect regularly, and always focus on the bigger ‘why’ to keep your team aligned and motivated."
About Antony Marcano
Antony is the co-founder of RiverGlide and Head of Engineering at Ford Digital. With 30 years of software development experience, including 25 years in Agile practices, he is a respected leader, coach, and consultant. Antony has contributed to books and journals and is a keynote speaker at global conferences and universities such as Oxford and McGill. He is also the co-creator of 'PairWith.Us,' and remains a hands-on technical practitioner, specializing in Agile development and leading teams to excel in agility.
You can link with Antony on LinkedIn visit RiverGlide.com, or check out RiverGlide TV on YouTube.
NOTE: We want to thank the folks at Tuple.app for being so generous with their stories, and supporting the podcast. Visit tuple.app/scrum and share them if you find the app useful! Remember, sharing is caring!
In this episode, Eli Goodman, Head of Product at Tuple, shares an inspiring example of a Product Owner who truly embraced collaboration, ensuring the entire team was aligned with the product vision. Eli highlights the positive impact of this behavior on both team morale and product outcomes.
Eli explores a classic Product Owner anti-pattern—working in isolation from the team. In this episode, he discusses the negative effects of this behavior on team collaboration and product success. Listen in to find out how Product Owners can avoid becoming isolated and instead foster collaboration within Agile teams.
About Eli Goodman
Eli Goodman has been working on software teams for 17 years. He’s been a full-stack developer and engineering manager at both large and small companies, including Etsy and Headspace. A few years ago, Eli transitioned to product management and is now the Head of Product at Tuple, a remote pair programming service used by companies such as Figma, Shopify, and many others in the software industry.
You can link with Eli Goodman on LinkedIn, or email Eli at Eli@Tuple.app.
NOTE: We want to thank the folks at Tuple.app for being so generous with their stories, and supporting the podcast. Visit tuple.app/scrum and share them if you find the app useful! Remember, sharing is caring!
Eli reflects on the unique challenges of being a product manager for a distributed team. He emphasizes the importance of staying in touch with reality, testing assumptions, and journaling as key habits for success. He also shares tips on how to pair effectively with colleagues to maintain accountability and stay aligned with the team’s goals. Listen in to find out what are some of the key habits that can help product managers thrive in remote environments.
In this episode, Eli Goodman, Head of Product at Tuple, shares his favorite retrospective format: the Sailboat Retrospective. Eli explains why this format helps teams visualize their progress and challenges while promoting open communication. He highlights the importance of retrospectives in creating alignment and continuous improvement within distributed teams.
About Eli Goodman
Eli Goodman has been working on software teams for 17 years. He’s been a full-stack developer and engineering manager at both large and small companies, including Etsy and Headspace. A few years ago, Eli transitioned to product management and is now the Head of Product at Tuple, a remote pair programming service used by companies such as Figma, Shopify, and many others in the software industry.
You can link with Eli Goodman on LinkedIn, or email Eli at Eli@Tuple.app.
NOTE: We want to thank the folks at Tuple.app for being so generous with their stories, and supporting the podcast. Visit tuple.app/scrum and share them if you find the app useful! Remember, sharing is caring!
In this special BONUS episode, Giovanni Asproni, CTO and co-founder of Launch Ventures, takes us behind the scenes of his work on the UK government's COVID-19 app project. Giovanni shares insights into the rapid development process, the adoption of remote pairing and ensemble programming, and valuable lessons on leadership in large-scale, high-stakes projects. Giovanni also offers practical advice for teams embracing remote collaboration and agile methodologies.
"When we got the call from the UK government, we knew this was a mission to help stop the spread of the virus." Giovanni kicks off the episode by recounting how his team at Zühlke Engineering got involved in the development of the UK’s COVID-19 app. Tasked with the challenge of building a solution that could help prevent the spread of the virus, they were under immense pressure to deliver quickly. Giovanni explains how they tackled technical hurdles, such as using Bluetooth technology to assess contagion risks, despite the lack of existing APIs on iOS and Android at the time.
"Speed was essential, but we also needed a robust design—Bluetooth was key to evaluating contagion risks, even though we didn’t have the APIs we needed."
"We had to move fast, but accessibility and coordination were non-negotiable." Giovanni discusses how the team, which consisted of around 60-70 members spread across the globe, used agile methodologies to stay organized and on schedule. By fostering open communication and using a clear team structure, they were able to streamline development. Agile planning and strong leadership, including cross-team coordination, were crucial to staying on track.
"Agile was our backbone—every team knew their responsibility, and clear communication meant we could deploy with confidence."
"Pairing allowed us to maintain quality under immense pressure." Giovanni dives deep into the practices of remote pairing and ensemble programming (or mobbing), which were introduced to enhance code quality and resilience during the project. With team members working remotely and under heavy scrutiny, mobbing provided a social outlet and improved problem-solving, while tools like Tuple made remote collaboration seamless. He reflects on the success of these practices, highlighting their impact on efficiency and team morale.
"We embraced mobbing not just for resilience, but to stay connected in a time when social contact was scarce."
"Don’t overthink it—just start and take breaks!" For teams new to remote pairing or ensemble programming, Giovanni offers simple but effective advice: give it a serious try, take breaks to avoid burnout, and don't overcomplicate the process. He emphasizes that these practices can dramatically improve productivity and team cohesion if executed well.
"Take the plunge—remote pairing can feel awkward at first, but the benefits are worth it."
"Don’t try to recreate the office—remote work offers unique advantages." Reflecting on the lessons from the COVID-19 app project, Giovanni explains how remote work is not just a substitute for office work but an entirely different mode of collaboration. He warns against trying to replicate office dynamics remotely, and instead, encourages teams to embrace the benefits of remote settings, such as easier scheduling and fewer distractions from management oversight.
"Remote work isn’t about replicating the office—when done right, it’s a whole new way to collaborate."
"Explore the power of mob programming with these great resources." To wrap up, Giovanni shares a few key resources for listeners who want to dive deeper into remote pairing, ensemble programming, or leadership in software engineering. He recommends "Software Teaming" by Woody Zuill and the Remote Mob Programming website, which offers comprehensive guides and tools.
You can also find out more about Giovanni’s work at his company website: https://www.asprotunity.com.
During the episode, Giovanni mentions a network of consultants, which you can access at: https://www.clockwork.ing.
And the podcast Giovanni hosts is the Software Engineering Radio podcast.
About Giovanni Asproni
Giovanni Asproni is a consultant, CTO, and co-founder of Launch Ventures. He is an expert in agile development, software design, and modern software engineering practices. Giovanni is a host for the Software Engineering Radio podcast and a frequent speaker at international conferences.
You can link with Giovanni Asproni on LinkedIn.
NOTE: We want to thank the folks at Tuple.app for being so generous with their stories, and supporting the podcast. Visit tuple.app/scrum and share them if you find the app useful! Remember, sharing is caring!
Eli Goodman, Head of Product at Tuple, discusses a recurring anti-pattern in product development: the over-reliance on A/B testing. Reflecting on his experiences at two different companies, Eli illustrates how A/B testing, when misused, can slow down product progress and lead to a bloated team structure. He also shares strategies on how to avoid this trap and take responsibility for product decisions. How can product teams avoid hiding behind A/B testing and instead move forward with confidence? Listen in to find out!
In this episode, Eli Goodman, Head of Product at Tuple, shares the profound influence of The Idea Factory, a book about Bell Labs, on his career as a product manager. Eli delves into how the book’s lessons on creativity, innovation, and the long-term impact of foundational ideas have shaped his thinking. What can today’s product leaders learn from the story of Bell Labs? How does creativity fuel product success, even in today’s fast-paced tech world? Listen in to find out.
About Eli Goodman
Eli Goodman has been working on software teams for 17 years. He’s been a full-stack developer and engineering manager at both large and small companies, including Etsy and Headspace. A few years ago, Eli transitioned to product management and is now the Head of Product at Tuple, a remote pair programming service used by companies such as Figma, Shopify, and many others in the software industry.
You can link with Eli Goodman on LinkedIn, or email Eli at Eli@Tuple.app.
NOTE: We want to thank the folks at Tuple.app for being so generous with their stories, and supporting the podcast. Visit tuple.app/scrum and share them if you find the app useful! Remember, sharing is caring!
In this episode, Eli Goodman, Head of Product at Tuple, shares a compelling failure story that transformed his approach to product development. Eli reflects on a time when he ambitiously pursued building a community feature that seemed like a perfect addition to the product. However, the project didn't take off, leading to a realization about investing in features that aren't critical to the core user path. How do you identify which features truly belong in your product? And when is it time to pull the plug on an idea?
About Eli Goodman
Eli Goodman has been working on software teams for 17 years. He’s been a full-stack developer and engineering manager at both large and small companies, including Etsy and Headspace. A few years ago, Eli transitioned to product management and is now the Head of Product at Tuple, a remote pair programming service used by companies such as Figma, Shopify, and many others in the software industry.
You can link with Eli Goodman on LinkedIn, or email Eli at Eli@Tuple.app.
NOTE: We want to thank the folks at Tuple.app for being so generous with their stories, and supporting the podcast. Visit tuple.app/scrum and share them if you find the app useful! Remember, sharing is caring!
In this episode, Eli Goodman, Head of Product at Tuple, shares insights from his extensive experience in software development and product management. Having transitioned from engineering management to product leadership, Eli reveals the key strategies Tuple uses to develop its remote pair programming service, which is trusted by companies like Figma and Shopify. Tune in to discover how Tuple handles remote team dynamics, customer-driven development, and balances tech debt with client needs, all while maintaining a customer-centric focus.
Tuple, a remote pair programming service designed by engineers, solves a pain point that its founders, all pairing enthusiasts, experienced firsthand. They were unsatisfied with generic screen-sharing tools that disrupted the flow of coding collaboration. Tuple’s product philosophy is about staying "one inch wide, one mile deep" to ensure the tool stays focused on enhancing the pairing experience without getting in the way.
"The details matter. Generic screen-sharing tools just don't cut it for productive pairing."
Managing a distributed team across the U.S. and Europe comes with its challenges. Eli highlights the importance of alignment and ensuring everyone is on the same page, despite working remotely. He emphasizes the role of Product Owners as "connective tissue" and the power of connecting team members with key initiatives. Through personal conversations, Eli uncovers what motivates his team, allowing him to support them without micromanaging.
"What makes you proud? What brings you shame? Understanding these emotions helps uncover what drives our team."
Effective communication is the backbone of remote work, and Eli shares some of the practices that have helped Tuple’s team stay aligned and collaborative. From using spontaneous pairing sessions to fostering a culture of checking in, Tuple has created a remote work environment where conversations are naturally sparked, and collaboration is effortless.
"We have more space in our schedules for spontaneous pairing, which keeps collaboration flowing."
One of the key insights Eli shares is how Tuple has evolved its remote pairing process. In the past, pairing might have felt like a formal meeting, but now it happens more spontaneously. Tuple's app facilitates this by offering the metaphor of a phone call—engineers can call each other at any time, making collaboration easy, especially when someone is deep into a task and needs quick support.
"At Tuple, engineers only have three meetings a week, leaving the rest of the time open for pairing and creative work."
While pairing is typically associated with programming, Eli explains how Tuple uses pairing for other activities, like design or planning sessions. This practice has extended beyond coding, fostering a culture where team members collaborate on various tasks that benefit from shared perspectives and live problem-solving.
"We’ve expanded pairing beyond coding, using it for activities like design reviews and project planning."
Responding to customer feedback is vital, but it can also lead to losing focus. Eli explains how Tuple balances this by capturing as much feedback as possible, using tools like Product Board to keep track of customer requests. However, instead of building every requested feature, Eli focuses on synthesizing broader patterns and emotional triggers that align with Tuple’s long-term vision.
"Focus on discovery as a product person. Understand the emotional context behind customer feedback—that’s what drives great products."
Tuple’s ideal customers are teams that value deep collaboration through pair programming. The platform’s most important offering is the ability to make remote pairing seamless and intuitive, something traditional tools fail to deliver.
"Tuple is built for teams that believe in the power of collaboration and want a tool that enhances their pairing experience, not disrupts it."
Looking ahead, Eli shares Tuple’s plans to continue investing in quality and lowering the barriers to remote pairing. One exciting potential direction includes creating a "social layer" within the app to help users feel more connected with their teammates. Another idea is incorporating non-human pairing agents that could assist with specific tasks.
"We want to see if we can make it feel like you're right there with your teammates, lowering the barriers to start pairing."
Eli recommends The Mom Test by Rob Fitzpatrick, a must-read for anyone working in product management. The book teaches how to talk to customers in a way that gets honest, useful feedback rather than polite responses that don't help improve the product.
"I thought caring about people was enough to talk to customers, but The Mom Test taught me what not to do during customer interviews."
About Eli Goodman
Eli Goodman has been working on software teams for 17 years. He’s been a full-stack developer and engineering manager at both large and small companies, including Etsy and Headspace. A few years ago, Eli transitioned to product management and is now the Head of Product at Tuple, a remote pair programming service used by companies such as Figma, Shopify, and many others in the software industry.
You can link with Eli Goodman on LinkedIn, or email Eli at Eli@Tuple.app.
In this BONUS episode, we dive deep into the unique intersection of agile coaching and fantasy writing with Jaques Smit, an Agile Coach in the gaming industry, and master transformational coach with his passion for crafting fantasy stories infused with Positive Psychology. Join us as we explore how his dual passions inform and enhance each other, providing practical insights for both aspiring writers and agile professionals.
"I explore ideas in agile coaching in my writing through characters and context, making complex concepts relatable and actionable to the reader."
Jaques shares how his background in fantasy writing enriches his approach to agile coaching. By creating vivid characters and immersive contexts, he brings agile principles to life, allowing teams to better understand and implement them. This storytelling technique not only engages team members but also facilitates deeper comprehension and retention of agile methodologies.
"Fiction allows you to push ideas to the nth degree, exploring possibilities that can inspire real-world solutions."
Drawing from his agile experience, Jaques discusses his method for selecting which ideas to develop further in his writing. He emphasizes the importance of iterative planning and feedback, much like agile sprints, to refine and enhance his stories. By focusing on one key idea per book and continuously improving based on reader feedback, he ensures that each narrative remains compelling and impactful.
"Understanding your target audience is crucial – you need to know your reader better than they know themselves."
Jaques outlines his strategies for collecting and utilizing feedback to shape his writing projects. From selecting alpha readers to conducting in-depth conversations, he highlights the importance of targeted feedback in refining his stories. By defining the "value" of his books and aligning them with his readers' needs, Jaques ensures that his work resonates deeply and meets the expectations of his audience.
"Character sketches and story outlines are invaluable tools for testing different ideas before committing to a full project."
Reflecting on his early writing experiences, Jaques shares how experimenting with various story and topic ideas has been pivotal in his development as an author. He discusses the use of character and story sketches to explore different directions and gather feedback, enabling him to pivot and adapt his narratives based on what resonates most with his readers. From these stories shared by Jaques, we learn how the same principles can be applied in Product Development.
"Incorporating a coach into the book creates real coaching conversations that mirror transformative leadership practices."
Jaques explains how he integrates his coaching expertise into his storytelling to illustrate effective leadership and transformational change. By embedding coaching dialogues within his narratives, he provides readers with practical examples of how to navigate challenges and foster growth, both in fictional settings and real-life scenarios.
"Reading fantasy and sci-fi allows you to explore problems from a safe distance, offering a stress holiday while fostering creative solutions."
Highlighting the benefits of fiction, Jaques discusses how genres like fantasy and science fiction can serve as powerful tools for learning and problem-solving. By presenting challenges and solutions in imaginative contexts, these stories encourage readers to think outside the box and apply creative thinking to their own professional and personal lives.
"Focusing on early adopters and serving their needs provides the motivation and evidence needed to complete a book."
Jaques shares his strategies for staying motivated and ensuring the completion of his writing projects. By engaging with his early adopters and continuously seeking their input, he maintains a clear direction and purpose, which helps him overcome distractions and challenges along the way. In Product Development, we can learn from Jaques’ story and apply some of the same ideas when developing products.
"The principles of iterative improvement and feedback loops in writing are directly transferable to agile software development."
Drawing parallels between writing and software development, Jaques emphasizes how practices like iterative drafting and continuous feedback can enhance both creative and technical projects. His insights reveal how the disciplined approach of writing can inform more effective and responsive software development processes.
"Embracing challenges as opportunities to grow strengthens both your writing and your agile practices."
Jaques discusses common obstacles writers face and how adopting an agile mindset can help overcome them. By viewing challenges as chances to iterate and improve, he maintains momentum and ensures consistent progress toward his writing goals.
"Integrating coaching techniques into storytelling not only enriches the narrative but also empowers readers to implement positive changes in their lives."
In his closing remarks, Jaques reflects on the powerful synergy between his coaching and writing endeavors. He underscores the importance of blending practical coaching strategies with engaging storytelling to create meaningful and transformative experiences for his audience.
About Jaques Smit
Jaques Smit was born in Rundu, Namibia, and lives with his family in Wellington, New Zealand. As a games Agile Coach and master transformational coach, he writes about fantasy laced with Positive Psychology, aspiring to create compelling stories that touch the reader.
You can link with Jaques Smit on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
Richard highlights a positive example of a PO at a pharma company who excelled by focusing on the holistic system and maintaining strong user relationships. This PO inspired both the team and the business by bringing a clear product vision to every planning session.
Richard discusses the pitfalls of a Product Owner who treats their role as a side job, leading to disengagement from both the users and the development team. This PO was more concerned with their personal to-do list than listening to user feedback, creating a disconnect between the system’s true needs and what was being prioritized.
[IMAGE HERE] 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 at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.
About Richard Coplan
Richard joins us from the UK. He has been a software developer for many years and later became data-centric, eventually transitioning into the role of Scrum Master. Over the past decade, Richard has specialized as a Scrum Master and Agile Coach, with a focus on collaboration tools like Miro and helping firms streamline their team structures.
You can link with Richard Coplan on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
Richard offers insights into how Scrum Masters can measure success, focusing more on soft metrics like collaboration and initiative, rather than just numerical measures. While managers often push for hard metrics, Richard argues that soft indicators—like team self-organization and PO engagement—are much more revealing.
Richard discusses his favorite retrospective format, the Sailboat retrospective. He explains how it uses metaphors to engage teams and bring future risks and opportunities into the conversation. While Richard values simplicity in retrospectives, he believes the Sailboat format strikes the perfect balance between simplicity and meaningful engagement.
[IMAGE HERE] Retrospectives, planning sessions, vision workshops, we are continuously helping teams learn about how to collaborate in practice! In this Actionable Agile Tools book, Jeff Campbell shares some of the tools he’s learned over a decade of coaching Agile Teams. The pragmatic coaching book you need, right now! Buy Actionable Agile Tools on Amazon, or directly from the author, and supercharge your facilitation toolbox!
About Richard Coplan
Richard joins us from the UK. He has been a software developer for many years and later became data-centric, eventually transitioning into the role of Scrum Master. Over the past decade, Richard has specialized as a Scrum Master and Agile Coach, with a focus on collaboration tools like Miro and helping firms streamline their team structures.
You can link with Richard Coplan on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
Richard recounts his experience with a Pharma company implementing SAFe. Initially skeptical of the framework, he learned its value, particularly in the context of PI Planning, which became a key driver for collaboration between Product Owners and Scrum teams. Richard offers practical tips for using Miro and emphasizes the importance of pre-planning activities, such as the value-effort game, to prioritize work effectively.
[IMAGE HERE] 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 Richard Coplan
Richard joins us from the UK. He has been a software developer for many years and later became data-centric, eventually transitioning into the role of Scrum Master. Over the past decade, Richard has specialized as a Scrum Master and Agile Coach, with a focus on collaboration tools like Miro and helping firms streamline their team structures.
You can link with Richard Coplan on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Richard shares his experience working in a toxic team environment at an insurance company. Brought in to replace a beloved Scrum Master, he found himself navigating a strained relationship between the Product Owner (PO) and the team. The PO's aggressive push for deliverables demotivated the team, and management sided with the PO, creating a vicious cycle of disengagement. How can a PO's leadership style make or break a team's performance? Richard explores this anti-pattern of PO-driven disengagement.
Richard reflects on how the book "Lean Enterprise" helped shape his approach as an Agile Coach, offering a holistic view of organizations. He also discusses "Team Topologies" and the importance of stream-aligned teams with CI/CD pipelines. What role does organizational agility play in the success of Scrum teams? Richard suggests that while many teams practice Scrum, organizations themselves are often not truly Agile.
[IMAGE HERE] 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 Richard Coplan
Richard joins us from the UK. He has been a software developer for many years and later became data-centric, eventually transitioning into the role of Scrum Master. Over the past decade, Richard has specialized as a Scrum Master and Agile Coach, with a focus on collaboration tools like Miro and helping firms streamline their team structures.
You can link with Richard Coplan on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
Richard shares a story about his time working as a Scrum Master for two teams at a bank. While one team excelled at developing APIs and took ownership of architectural decisions, the other struggled to build a relationship with the architecture team. Richard discusses the friction that arose from a top-down imposition of architecture and highlights the key anti-pattern of architecture governance. How can teams take more ownership of their architecture, and what role should architects play in facilitating collaboration? Listen in to find out!
[IMAGE HERE] Recovering from failure, or difficult moments is a critical skill for Scrum Masters. Not only because of us, but also because the teams, and stakeholders we work with will also face these moments! We need inspiring stories to help them, and ourselves! The Bungsu Story, is an inspiring story by Marcus Hammarberg which shows how a Coach can help organizations recover even from the most disastrous situations! Learn how Marcus helped The Bungsu, a hospital in Indonesia, recover from near-bankruptcy, twice! Using Lean and Agile methods to rebuild an organization and a team! An inspiring story you need to know about! Buy the book on Amazon: The Bungsu Story - How Lean and Kanban Saved a Small Hospital in Indonesia. Twice. and Can Help You Reshape Work in Your Company.
About Richard Coplan
Richard joins us from the UK. He has been a software developer for many years and later became data-centric, eventually transitioning into the role of Scrum Master. Over the past decade, Richard has specialized as a Scrum Master and Agile Coach, with a focus on collaboration tools like Miro and helping firms streamline their team structures.
You can link with Richard Coplan on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
Anita highlights a Product Owner who actively sought feedback and applied it to improve their work. This PO demonstrated humility and a commitment to growth, earning respect and trust from the team. Anita reflects on the importance of openness to feedback, regardless of experience level.
When we talk about PO anti-patterns, Anita describes a Product Owner who failed to communicate with customers or colleagues, making decisions based on assumptions. This anti-pattern led to a disconnect between the product and customer needs. Anita advises to work with the PO and find ways to better understand and incorporate customer feedback.
[IMAGE HERE] 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 at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.
About Anita Kalmane-Boot
Anita is a neurodiversity advocate and considers herself European, not bound to one single country. Anita is passionate about Agile but is losing hope in corporate organizations and their adaptation of Scrum.
You can link with Anita Kalmane-Boot on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Anita discusses her views on what defines success for a Scrum Master. Rather than focusing on metrics, she emphasizes the importance of communication within the team and the ability to give and receive feedback. Anita believes that true success is reflected in the team’s willingness to learn from each other and approach the Scrum Master when needed.
Anita shares her perspective on empowering team members to lead their own retrospectives. She believes that Scrum Masters should focus on building the team’s independence, offering support and guidance when needed. Anita has seen engineers thrive when given the opportunity to facilitate, despite initial hesitation. How can you encourage your team to take ownership of their retrospectives? Listen in to find out!
[IMAGE HERE] Retrospectives, planning sessions, vision workshops, we are continuously helping teams learn about how to collaborate in practice! In this Actionable Agile Tools book, Jeff Campbell shares some of the tools he’s learned over a decade of coaching Agile Teams. The pragmatic coaching book you need, right now! Buy Actionable Agile Tools on Amazon, or directly from the author, and supercharge your facilitation toolbox!
About Anita Kalmane-Boot
Anita is a neurodiversity advocate and considers herself European, not bound to one single country. Anita is passionate about Agile but is losing hope in corporate organizations and their adaptation of Scrum.
You can link with Anita Kalmane-Boot on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
Anita talks about her experience at a company where Scrum wasn’t working, and the need for change was clear. She facilitated a brainstorming session, but soon realized that Scrum wasn’t the right fit for the company’s culture. Instead, they transitioned to Kanban, learning and adapting together. Anita stresses the importance of questioning assumptions and understanding why certain frameworks are in place.
[IMAGE HERE] 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 Anita Kalmane-Boot
Anita is a neurodiversity advocate and considers herself European, not bound to one single country. Anita is passionate about Agile but is losing hope in corporate organizations and their adaptation of Scrum.
You can link with Anita Kalmane-Boot on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
Anita shares a story about a team that was paralyzed by fear of their own manager. Despite the manager's care for the team, communication had broken down entirely. Anita focused on mediating and rebuilding trust between the team and the manager. She reflects on the importance of understanding team dynamics and continuously defining the role of a Scrum Master.
In this episode, Anita introduces "NeuroTribes" by Steve Silberman, a book that explores the history of autism. Anita highlights the importance of understanding neurodiversity, especially in Scrum teams, where the percentage of neurodiverse individuals can be significant. She discusses how this book is a valuable resource for Scrum Masters to better understand and support their team members.
[IMAGE HERE] 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 Anita Kalmane-Boot
Anita is a neurodiversity advocate and considers herself European, not bound to one single country. Anita is passionate about Agile but is losing hope in corporate organizations and their adaptation of Scrum.
You can link with Anita Kalmane-Boot on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Anita shares her experience with a team that had already gone through two Scrum Masters before her arrival. Despite her best efforts, she realized that the team didn’t want to work with a Scrum Master. The situation was compounded by the challenges of remote work during the pandemic. Eventually, Anita made the difficult decision to step away from the team. She emphasizes the importance of seeking external perspectives and approaching situations without judgement. How do you handle a team that resists change, and when is it time to walk away? Listen in to find out!
[IMAGE HERE] Recovering from failure, or difficult moments is a critical skill for Scrum Masters. Not only because of us, but also because the teams, and stakeholders we work with will also face these moments! We need inspiring stories to help them, and ourselves! The Bungsu Story, is an inspiring story by Marcus Hammarberg which shows how a Coach can help organizations recover even from the most disastrous situations! Learn how Marcus helped The Bungsu, a hospital in Indonesia, recover from near-bankruptcy, twice! Using Lean and Agile methods to rebuild an organization and a team! An inspiring story you need to know about! Buy the book on Amazon: The Bungsu Story - How Lean and Kanban Saved a Small Hospital in Indonesia. Twice. and Can Help You Reshape Work in Your Company.
About Anita Kalmane-Boot
Anita is a neurodiversity advocate and considers herself European, not bound to one single country. Anita is passionate about Agile but is losing hope in corporate organizations and their adaptation of Scrum.
You can link with Anita Kalmane-Boot on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
Great Product Owners understand both the business and the team’s needs. Johann shares an inspiring example of a PO who not only managed the product but also guided the team with a deep understanding of business and technology. What qualities set great Product Owners apart, and how can they drive both product and team success? Johann highlights the importance of accountability and collaboration in effective Product Ownership.
A bad Product Owner (PO) can derail even the best Agile efforts. Johann discusses common PO anti-patterns and the importance of getting PO responsibilities right. Why do organizations struggle with effective Product Ownership, and how can they avoid common pitfalls? Johann emphasizes the critical role of the PO in maximizing value and maintaining team morale.
[IMAGE HERE] 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 at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.
About Johann Botha
Johann joins us from South Africa, helping build digital-age capabilities by developing practical skills to solve problems, grow people, and facilitate difficult change. A long-time proponent of Lean and Agile, Johann consults, coaches, speaks, and writes on the topic. He is also the chief examiner for the EXIN Agile Scrum product.
You can link with Johann Botha on LinkedIn and connect with Johann Botha on Twitter.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
Success for a Scrum Master goes beyond just following Scrum rules; it’s about nurturing a team’s belief in itself. Johann explores the delicate balance Scrum Masters must maintain between authority and influence, and why transparency and accountability are key. How can Scrum Masters help teams embrace self-management and foster a sense of belonging? Johann shares insights on how to be a coach, a counselor, and a champion for team autonomy.
Johann prefers retrospectives that go beyond surface-level discussions. His favorite format, "The Good, the Bad, the Ugly," focuses on identifying real issues and experimenting with solutions. Why is it crucial to dig deeper in retrospectives, and how can techniques like the double diamond design thinking process aid in root cause analysis? Johann explains how teams can drive continuous improvement through thoughtful reflection and experimentation.
[IMAGE HERE] Retrospectives, planning sessions, vision workshops, we are continuously helping teams learn about how to collaborate in practice! In this Actionable Agile Tools book, Jeff Campbell shares some of the tools he’s learned over a decade of coaching Agile Teams. The pragmatic coaching book you need, right now! Buy Actionable Agile Tools on Amazon, or directly from the author, and supercharge your facilitation toolbox!
About Johann Botha
Johann joins us from South Africa, helping build digital-age capabilities by developing practical skills to solve problems, grow people, and facilitate difficult change. A long-time proponent of Lean and Agile, Johann consults, coaches, speaks, and writes on the topic. He is also the chief examiner for the EXIN Agile Scrum product.
You can link with Johann Botha on LinkedIn and connect with Johann Botha on Twitter.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In large organizations, even the best Agile efforts can fail if external dependencies are not managed. Johann discusses his experience with a financial services IT department where traditional project governance stifled Agile initiatives. How can Agile leaders identify and navigate these roadblocks? Johann shares practical tips on engaging leadership, redefining governance, and using techniques like the double diamond for root cause analysis to foster an environment where Agile can thrive.
[IMAGE HERE] 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 Johann Botha
Johann joins us from South Africa, helping build digital-age capabilities by developing practical skills to solve problems, grow people, and facilitate difficult change. A long-time proponent of Lean and Agile, Johann consults, coaches, speaks, and writes on the topic. He is also the chief examiner for the EXIN Agile Scrum product.
You can link with Johann Botha on LinkedIn and connect with Johann Botha on Twitter.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
When Agile teams push too hard for transformation, they risk becoming the enemy. Johann explains how corporate "immune systems" react against new ideas, even when they’re beneficial. What strategies can Agile teams use to navigate organizational resistance and avoid self-sabotage? Johann emphasizes the importance of listening, finding safe spaces to experiment, and avoiding the trap of making Agile seem like an invasive force.
Johann shares his journey through influential books that shaped his approach to management, from Tom Peters’ Liberation Management to Netflix's story in No Rules Rules. How do these books provide a roadmap for progressive management practices in today’s fast-paced world? Johann also highlights key texts like Accelerate by Nicole Forsgren et al., and his own work, Competing in a Digital Future, offering listeners a rich library to explore.
[IMAGE HERE] 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 Johann Botha
Johann joins us from South Africa, helping build digital-age capabilities by developing practical skills to solve problems, grow people, and facilitate difficult change. A long-time proponent of Lean and Agile, Johann consults, coaches, speaks, and writes on the topic. He is also the chief examiner for the EXIN Agile Scrum product.
You can link with Johann on LinkedIn and connect with Johann on Twitter.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
Project management struggles to deliver successful software projects because customers often don’t know what they want upfront, and the world around us changes too quickly. Johann reflects on the outdated thinking rooted in the Industrial Age that hampers modern software development. How can an iterative approach help teams deliver projects on time and within budget? Johann shares insights on why traditional project management often fails in dynamic environments and discusses how concepts from books like Reinventing Organizations and The Machine That Changed the World can transform management practices.
[IMAGE HERE] Recovering from failure, or difficult moments is a critical skill for Scrum Masters. Not only because of us, but also because the teams, and stakeholders we work with will also face these moments! We need inspiring stories to help them, and ourselves! The Bungsu Story, is an inspiring story by Marcus Hammarberg which shows how a Coach can help organizations recover even from the most disastrous situations! Learn how Marcus helped The Bungsu, a hospital in Indonesia, recover from near-bankruptcy, twice! Using Lean and Agile methods to rebuild an organization and a team! An inspiring story you need to know about! Buy the book on Amazon: The Bungsu Story - How Lean and Kanban Saved a Small Hospital in Indonesia. Twice. and Can Help You Reshape Work in Your Company.
About Johann Botha
Johann joins us from South Africa, helping build digital-age capabilities by developing practical skills to solve problems, grow people, and facilitate difficult change. A long-time proponent of Lean and Agile, Johann consults, coaches, speaks, and writes on the topic. He is also the chief examiner for the EXIN Agile Scrum product.
You can link with Johann on LinkedIn and connect with Johann on Twitter.
In this BONUS episode, we hear from Alex Schladebeck, CEO and Quality Advocate at BREDEX GmbH. Alex shares her journey from testing and consultancy to becoming a CEO, offering valuable insights into agile leadership, the importance of communication, and the evolving landscape of technology and quality in software development.
"Communication isn't just part of the work; it is the work."
Alex reflects on her career, emphasizing that her approach to leadership isn't defined by a single moment but by recurring patterns where communication played a crucial role. She shares how continuous conversation is vital for navigating changes and resolving conflicts, underscoring the importance of keeping communication channels open to manage the evolving demands of the tech industry.
"Effective leadership hinges on continuous conversations. Make communication the core of your leadership practice."
"We need to balance the excitement of new technology with what the customer truly needs."
Alex discusses the importance of aligning tech strategies with broader business objectives while maintaining agility. She shares her experience with implementing OKRs (Objective-Key Results) to bridge the gap between engineering teams and business leaders. By using short cycles for experimentation and decision-making, her team remains flexible and responsive to change without becoming reactive.
"Use OKRs and short cycles to keep your tech strategy aligned with business goals, ensuring adaptability without sacrificing focus."
"Stepping outside your own perspective is key to understanding what’s critical for both the business and the customer."
Collaboration between tech and business units is essential, and Alex highlights strategies that have helped her foster this collaboration. By encouraging teams to consider different perspectives, especially when making decisions that affect customers, Alex ensures that her team remains aligned with the business’s critical needs.
"Take different perspectives into account during decision-making to ensure alignment between tech and business objectives."
"Little experiments can lead to big innovations if we collaborate with customers early on."
Alex shares her approach to roadmapping by incorporating small experiments to explore new ideas. These experiments often involve pilot projects with customers, allowing her team to test and iterate on new technologies before full-scale implementation. This method helps maintain a balance between stability in ongoing projects and innovation.
"Incorporate small experiments into your roadmap to innovate while maintaining stability in ongoing projects."
"Stepping up from a team lead to CEO is about learning to take responsibility and adapt."
One of the biggest challenges Alex faced was transitioning from a team lead to a CEO. With the guidance of her co-CEO and mentor, she learned to navigate this complex role without a clear guidebook, focusing on transparency, reflection, and adaptability as key leadership traits.
"Reflect on your decisions and be transparent with your team to navigate the challenges of leadership transitions."
"Leaders are people too, and sharing our decision-making processes helps build trust."
Alex stresses the importance of creating empathy between leaders and their teams by being transparent about decision-making processes. She believes that while transparency doesn’t eliminate conflict or disappointment, it fosters a better understanding of the context behind decisions, helping teams to navigate challenges together.
"Build empathy by sharing your decision-making process, but be prepared for conflict—it’s part of leadership."
Alex shares her perspective on the rise of AI and its potential to transform software and product development. While she recognizes the opportunities AI presents, she emphasizes the need to remain focused on human-centric development, ensuring that technology serves to enhance, rather than replace, the human element in quality and product development.
"As AI evolves, keep your focus on human-centric development to ensure technology enhances, rather than replaces, human contributions."
"Numbers are useful, but context is crucial."
Alex discusses her cautious approach to KPIs, emphasizing that while metrics like the DORA metrics are valuable, they must be interpreted within the right context. She shares an example of how a clear KPI—reducing escalation meetings—helped turn around a troubled project by focusing on the underlying issues rather than just the numbers.
"Use KPIs to guide your decisions, but always consider the context behind the numbers to drive meaningful change."
"I delegate much of the learning to my team, but I remain curious and engaged."
To stay current with industry trends and best practices, Alex relies on a flat organizational structure where team leads are empowered to stay updated. She also participates in conference watch parties, engages in Slack groups, and pairs with colleagues to learn new technologies firsthand, fostering a culture of continuous learning.
"Empower your team to stay informed, but stay curious and engaged in the learning process."
"We work with humans in socio-technical systems, and it's important to understand both the technical and human aspects."
Alex shares some of the books that have influenced her leadership approach, including "How to Talk So Kids Will Listen & Listen So Kids Will Talk," "Radical Candor," and "Never Split the Difference." These books have helped her navigate the complex, human-centric aspects of leadership in technical environments.
"Combine technical know-how with human understanding—books like 'Radical Candor' offer valuable insights for leaders."
[IMAGE HERE] 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 at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.
About Alex Schladebeck Alex Schladebeck is the CEO and Quality Advocate at BREDEX GmbH. She is an agile leader with a passion for quality and human-centric development. With a rich background in testing, product ownership, and consultancy, Alex now focuses on strategy, team coaching, and customer communication. A frequent speaker at Agile events, she was named the Most Influential Agile Testing Professional Person in 2018. Outside of work, she enjoys sports, music, and exploring new cultures.
To learn more about Alex Schladebeck and follow her work, visit BREDEX GmbH and Schladebeck.de.
You can link with Alex Schladebeck on LinkedIn.
In this BONUS episode, we sit down with Tricia Broderick, a seasoned tech leader and co-author of Lead Without Blame. With over 25 years in software development leadership, Tricia shares her journey from an individual contributor to a transformative leader. The conversation touches on the challenges of giving up control, the importance of psychological safety, and how to foster resilient and empowered teams.
"Leadership isn't about doing everything yourself; it's about empowering others to excel."
Tricia reflects on a pivotal moment early in her career when she realized that her meticulous attention to detail was sending the wrong message to her team. She shares how this realization led to her "red-pen apology," where she acknowledged her need to step up as a leader rather than continuing to act as an individual contributor. This was the beginning of her journey toward understanding the importance of giving up control to create a healthier, more scalable work environment.
"If you want to lead effectively, you must be willing to let go of control and trust your team."
One of the biggest challenges Tricia faced was learning to give up control—a common struggle for leaders who transition from individual contributor roles. She discusses the lack of leadership role models and patterns available during her early career and how this shaped her understanding of effective leadership. Tricia emphasizes the importance of creating the right environment for collective decision-making and shares her insights on how to help other leaders learn these critical skills.
"Psychological safety isn't a luxury; it's a necessity for team success."
Tricia highlights the importance of psychological safety in leadership, particularly in environments where power dynamics are at play. She shares practical tips for helping leaders recognize when their current methods aren't working and how to guide them toward learning new, sometimes uncomfortable skills. Tricia also discusses the need for transparency in leadership, recounting a moment when she realized the mixed messages she was sending about failure within her team.
"To avoid blame and shame, we must focus on resilience factors that empower teams to handle conflict healthily."
Tricia introduces the concept of resilience factors—patterns and motivators that help teams avoid blame and shame while working together effectively. She discusses the importance of fostering healthy conversations about conflict and enabling teams to manage these situations independently. By paying attention to these resilience factors, leaders can create environments where teams are empowered and equipped to thrive.
"Metrics should guide us, not define us. Focus on trends and the bigger picture."
When it comes to KPIs, Tricia is cautious about relying too heavily on metrics, as they can sometimes negatively impact team morale. She emphasizes the importance of using a set of metrics to understand trends rather than focusing on individual numbers. Tricia also shares her approach to evaluating organizational health, customer impact, and individual contributions, stressing that metrics should align with key initiatives but not become the sole focus.
"To lead in tech, you must be committed to continuous learning and staying connected with industry trends."
Tricia shares how she stays up-to-date with industry trends, emerging technologies, and best practices in software engineering. She relies on a combination of conferences, networking, and books to inform her decision-making. Tricia also discusses how certain books, like The Five Dysfunctions of a Team by Patrick Lencioni, have influenced her leadership approach, particularly in creating environments that foster trust and collaboration.
[IMAGE HERE] Retrospectives, planning sessions, vision workshops, we are continuously helping teams learn about how to collaborate in practice! In this Actionable Agile Tools book, Jeff Campbell shares some of the tools he’s learned over a decade of coaching Agile Teams. The pragmatic coaching book you need, right now! Buy Actionable Agile Tools on Amazon, or directly from the author, and supercharge your facilitation toolbox!
About Tricia Broderick
Tricia Broderick, co-author of Lead without Blame, is a seasoned leadership and organizational advisor with over twenty-five years of experience in software development leadership. She specializes in transforming leaders and teams to achieve quality outcomes through authentic, inclusive, and engaging collaboration.
You can link with Tricia Broderick on LinkedIn and connect with Tricia Broderick on Twitter.