How do multiple teams that work on one product stay aligned once the Sprint starts? In this episode we follow Teams Mosaic and Nova through the rhythm of a LeSS Sprint: continuous integration, code-first communication, and lightweight, human coordination.
See how a simple commit ping sparks collaboration between Mark (Mosaic) and Max (Nova), why automated acceptance tests come before coding, and how a 90-minute Overall Retrospective , Scout visits between Daily Scrums, and a weekly Open Space keep learning and problem-solving flowing across teams.
What you’ll learn:
* How CI across all teams surfaces dependencies early (and invites collaboration)
* Using version control + chat for real-time code cues (“bleep bleep → let’s sync!”)
* Writing automated acceptance tests before code to uphold a solid DoD
* What an Overall Retrospective looks like in LeSS (system-wide improvements)
* Scout pattern for Daily Scrums and when to use Open Space for cross-team topics
* Cross-team pairing as the default, not the exception
