Lynn is the Scrum Master for her organization and she's working with seven Development Teams on a single Scrum project. What statement best describes…

When multiple Scrum Teams work on a single project, it is a best practice to synchronize their Sprints. Having all teams start and end their Sprints on the same day simplifies the integration of their work into a single, cohesive product increment. This alignment facilitates a common cadence for planning, review, and retrospective activities across the entire project, making it easier to manage dependencies and assess overall progress. A synchronized approach ensures that a potentially shippable increment, representing the combined effort of all teams, is available at the end of each Sprint.

B. Staggering Sprint start dates creates significant complexity in integrating the work of different teams and makes it difficult to have a unified Sprint Review for the entire product increment.

C. The Sprint duration is a consistent time-box for the Sprint itself; it is not determined by the project's start date. This option confuses Sprint duration with Sprint scheduling.

D. Sprint Planning is an event for a team to plan the work for the upcoming Sprint, not to determine the start dates or sequence for different teams across the project.

1. A Guide to the Scrum Body of Knowledge (SBOK® Guide) – 2017 Edition. SCRUMstudy

VMEdu

Inc.

Section 14.4

Conducting and Coordinating Sprints

Page 338: "In large projects

various Scrum Teams work in parallel. The Sprints of the various teams should be synchronized to end on the same day. This synchronization of Sprints facilitates the integration of the deliverables from the various teams and allows for a common Sprint Review meeting with relevant Stakeholder(s)." This directly supports the principle of synchronized Sprints.