True or False: Multiple scrum Teams working on the same product must have the same Sprint start date.

The Scrum Guide, which is the definitive body of knowledge for Scrum, does not contain a rule stating that multiple Scrum Teams working on the same product must have the same Sprint start date. While synchronizing the Sprint cadence (start dates, end dates, and length) is a widely accepted best practice and a formal rule in scaling frameworks like Nexus, it is not a mandatory rule within the Scrum framework itself. The Scrum Guide defines the framework for a single team, and while it allows for multiple teams to work on a single product, it does not prescribe this specific coordination mechanism. Therefore, the use of the word "must" makes the statement false.

The statement is presented as an absolute requirement ("must") of the Scrum framework. Since this rule is not codified in the official Scrum Guide, it cannot be considered a mandatory element of Scrum. It is an emergent practice or a rule from a specific scaling framework (like Nexus), not a core rule of Scrum itself.

1. Schwaber

K.

& Sutherland

J. (2020). The Scrum Guide. Scrum.org.

Reference Location: The entire guide. The guide defines the roles

events

artifacts

and rules of Scrum. A thorough review of the guide reveals the absence of any rule mandating that multiple teams share a Sprint start date. The guide states that when multiple teams work on a product

they "share the same Product Goal

Product Backlog

and Product Owner

" but it does not prescribe their Sprint cadence. The omission of this rule from the definitive guide is the primary evidence.

2. Scrum.org. (2021). The Nexus Guide.

Reference Location: Page 5

"The Nexus Framework" section.

Quote: "A Nexus Sprint begins and ends at the same time for all Scrum Teams in the Nexus."

Justification: This reference explicitly shows that synchronized Sprints are a rule within the Nexus framework

which is designed for scaling Scrum. This highlights that it is an additional rule for scaling

not a rule of the base Scrum framework itself

thereby supporting the conclusion that the original statement about Scrum is false.