What the distributed and hybrid module trains
Distributed Scrum is not the same framework with a video call bolted on, and this module starts by naming exactly why it is harder: the informal, hallway-level information that keeps a co-located team synchronized simply does not exist across time zones, so every Scrum event has to work harder to carry the same transparency. The opening lessons build a distributed Scrum Master playbook and immediately test it in a game, then move into the unglamorous but decisive skill of doing the timezone math properly, figuring out which hours actually overlap and designing the events around that reality instead of around whichever office happens to hold the most senior people.
A recurring theme is written by default: documenting decisions, context, and outcomes as the primary channel rather than the exception, so that team members who were asleep during a conversation are not permanently one step behind. This connects directly to a lesson on vendor mode versus team mode, the difference between treating an offshore group as an order-taking subcontractor and treating them as full accountabilities inside one Scrum Team, which the module argues is the single biggest predictor of whether a distributed team ever becomes trustworthy to itself. A checkpoint applies the distributed playbook to a batch of realistic judgment calls before the module moves further.
The middle section covers onboarding someone you will never share a whiteboard with, structuring hybrid meetings so remote participants are not reduced to a small video tile while the room runs its own separate conversation, running retrospectives that actually surface cross-timezone friction instead of politely ignoring it, and choosing tooling that supports asynchronous work rather than just replicating a synchronous meeting online. A second checkpoint raises the difficulty with harder two-timezone judgment calls.
The campaign closes on the human side of distributed work: building trust with people you may never meet in person, working productively across cultural differences in communication style and hierarchy, and naming offshore anti-patterns directly, second-class citizenship for the offshore half of the team, decisions made in a timezone-privileged meeting and only communicated afterward, work parceled out by geography rather than by skill. A final checkpoint and a lesson on the specific challenges of being a Product Owner for a distributed team close the module.
Mistakes teams make with this material
Scheduling every ceremony for the convenience of the headquarters office and treating the offshore team's attendance at 9pm as a minor inconvenience. This quietly signals which half of the team actually matters.
Handing fully specified tickets to an offshore group with no involvement in refinement or planning. This is vendor mode, not team mode, and it produces exactly the low-context execution you would expect from an outsourced arrangement.
Making real decisions in a hallway chat or an unscheduled call and never writing them down. Anyone outside that timezone finds out secondhand, late, and often wrong.
Running the same retro format regardless of location and letting the loudest, most co-located subgroup dominate it, while the distributed half of the team quietly disengages.
Questions people ask
How do you run a Daily Scrum across a 10-hour time difference?
You usually cannot run one true synchronous event that includes everyone comfortably. Most distributed teams either split into two overlapping mini-syncs with a written handoff between them, or move to an asynchronous written Daily Scrum posted in a shared channel, with a synchronous slot reserved only for the days something actually needs live discussion.
Is it possible to build real trust with a team you never meet in person?
Yes, but it takes deliberate investment: consistent 1:1 time, visible follow-through on commitments, and giving the same weight to input from remote members that you give to people in the room. Trust across distance is built the same way as trust up close, just without the shortcut of shared physical presence.
What is the biggest sign a distributed team is not actually one team?
Decisions get made in one timezone's meeting and are only communicated to the other timezone afterward, as an announcement rather than a discussion. If the offshore half of the team consistently finds out about changes to its own Sprint Goal after the fact, it is being treated as a vendor, not a peer.