Episode

Two Teams, One Sprint Cadence — The Hidden Cost of Synchronization | Mirco Gerling

Podcast
Scrum Master Toolbox Podcast: Agile storytelling from the trenches
Published
Jul 15, 2026
Duration seconds
1231
Processing state
not_requested
Canonical source
https://scrummastertoolbox.libsyn.com/two-teams-one-sprint-cadence-the-hidden-cost-of-synchronization-mirco-gerling
Audio
https://traffic.libsyn.com/secure/scrummastertoolbox/20260715_Mirco_Gerling_W.mp3?dest-id=246429
JSON
/v1/public/podcasts/scrum-master-toolbox-podcast-agile-storytelling-from-the-trenches-445588/episodes/two-teams-one-sprint-cadence-the-hidden-cost-of-synchronization-mirco-gerling
Markdown
/podcast/scrum-master-toolbox-podcast-agile-storytelling-from-the-trenches-445588/two-teams-one-sprint-cadence-the-hidden-cost-of-synchronization-mirco-gerling.md

Actions

  • POST https://stenobird.com/v1/public/podcasts/scrum-master-toolbox-podcast-agile-storytelling-from-the-trenches-445588/episodes/two-teams-one-sprint-cadence-the-hidden-cost-of-synchronization-mirco-gerling/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/two-teams-one-sprint-cadence-the-hidden-cost-of-synchronization-mirco-gerling.md
    Read the agent-friendly Markdown representation of this episode resource.

Summary

Mirco Gerling: Two Teams, One Sprint Cadence — The Hidden Cost of Synchronization 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 . "The teams need to understand the advantage of the synchronization — but will they?" - Mirco Gerling Two of Mirco's teams just got merged into one — and the brand-new, fused team is now part of a 10+ team organization trying to move from loose-coupled chaos to a standard process. Different sprint lengths. Different estimation methods. Different ticketing tools. The plan: align everyone to 4-week sprints, hold a global planning week every three months, and synchronize start and end dates across all teams. Mirco voted for 2-week sprints. The majority went with 4. And then the side effects started. Sprint reviews stack up on the same days, making it impossible for Scrum Masters to facilitate them all. Teams synchronize on paper , but interact organically across the four weeks anyway, so the cadence advantage doesn't materialize. And the merged team itself? Pushed back through Tuckman's stages by the merge — the Tuckman model reminded Mirco that "adjourning" is real, and a high-performing team starts over when its membership changes. Mirco's experiment: let faster-moving teams run two 2-week sprints inside the 4-week window, keeping organizational sync while restoring their own learning rhythm. Self-reflection Question: Where in your organization is process standardization being mistaken for actual alignment — and what would it cost you to separate the two? [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she w…