Multiple Scrum Teams Working on the Same Sprint Start Date

Scrum Question

Multiple Scrum Teams working on the same project must have the same Sprint start date.
A. True
B. False

Answer

Multiple Scrum Teams working on the same project must have the same Sprint start date.
A. True  ❌
B. False

TIP: The tricky word here is MUST, and since it’s not mandatory to have the same Sprint date, the correct answer is FALSE (B)

➡️➡️ Slide to see the answer and a short explanation or continue to read below.

Reason

When working with multiple Scrum teams on the same product, Scrum.org suggests scaling scrum using Nexus. In the Nexus Framework book, it says there is nothing to stop teams from observing their own Sprint cadence, as long as it is exactly divisible into the Nexus Sprint cadence.
Therefore the answer should be “B”

The best option to understand the Scrum framework is to go through the Scrum Guide (https://scrumguides.org/index.html) several times as your primary source of information.

In this case, since the question includes multiple scrum teams you might also want to look at the Nexus Framework primary source (https://www.scrum.org/resources/scaling-scrum). 

Here are some quotes from the Scrum Guide that I found relevant when working on a single product with multiple Scrum teams:

“If Scrum Teams become too large, they should consider reorganizing into multiple cohesive Scrum Teams, each focused on the same product. Therefore, they should share the same Product Goal, Product Backlog, and Product Owner.”

Scrum.org

“Multiple Increments may be created within a Sprint. The sum of the Increments is presented at the Sprint Review thus supporting empiricism. However, an Increment may be delivered to stakeholders prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value.”

Scrum.org

“The Developers are required to conform to the Definition of Done. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done.”

Scrum.org

A Nexus works within the boundaries of a Sprint(30 days or less), as in Scrum. If absolutely necessary, teams can work on different Sprint lengths, but there must be a common denominator. Teams must deliver into the increment at least at the end of each of their Sprints.

Introduction to the Nexus Framework Whitepaper@ Scrum.org

References:

Scrum Guide, 2021

Introduction to the Nexus Framework Whitepaper@ Scrum.org by Simon Bourk & Patricia Kong, 2016

Scroll to Top