Scaling Scrum across teams with Nexus: a practitioner's guide

Nexus is what you reach for when one product needs several Scrum teams and the integration work starts to dominate. Here is how it has played out on real engagements.

The integration team

A small group that owns the cross-team dependencies is the difference between Nexus working and not.

One backlog, many teams

Shared ordering keeps everyone pointed at the same outcome.

The Nexus Sprint Review

Reviewing the integrated increment, not each team’s slice, is the practice that pays off most.

(Draft — full write-up in progress.)