Episode
Three Teams, Three Backlogs, One Feature—Can You Make Them See Each Other? | Olaitan Fashanu
- Published
- Jun 24, 2026
- Duration seconds
- 1039
- Processing state
not_requested- Canonical source
- https://scrummastertoolbox.libsyn.com/three-teams-three-backlogs-one-featurecan-you-make-them-see-each-other-olaitan-fashanu
Actions
POST https://stenobird.com/v1/public/podcasts/scrum-master-toolbox-podcast-agile-storytelling-from-the-trenches-445588/episodes/three-teams-three-backlogs-one-feature-can-you-make-them-see-each-other-olaitan-fashanu/transcription-requests
Idempotently request low-priority transcript generation for this episode.GET https://stenobird.com/podcast/scrum-master-toolbox-podcast-agile-storytelling-from-the-trenches-445588/three-teams-three-backlogs-one-feature-can-you-make-them-see-each-other-olaitan-fashanu.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
Olaitan Fashanu: Three Teams, Three Backlogs, One Feature—Can You Make Them See Each Other? Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes . "How do we ensure that these teams actually work together to show the same data?" - Olaitan Fashanu Olaitan brings a problem most Scrum Masters in scaled environments will recognize. Three teams. Three separate backlogs. One product, accessed across app, web, and support channels. Leadership made a top-down team topologies decision: split the work to move faster. Predictable result—each team optimizes for their own backlog, blind to what the others are building, sometimes shipping the same feature twice with different behaviors. The product owners know there's overlap. The teams love the idea of linking tickets across backlogs. They just won't maintain the habit. Olaitan and Vasco walk through experiments together: a sync between POs, joint refinement sessions, linking tickets, putting "this is also being built by Team B" notes at the top of stories. The deeper insight: the Scrum Master's job is to keep surfacing information until a habit forms. As Vasco's old lifting coach put it— you find the imbalance, you get rid of the imbalance, one by one. That's how you get stronger. In this episode, we refer to team topologies and the practice of surfacing information across team boundaries. Self-reflection Question: Where in your organization are teams unknowingly building the same thing twice—and what's the smallest experiment you could run this week to make that visible? [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching…