Back to Forum

If multiple Scrum Teams working on the same product then all should have the same Sprint length?

Last post 08:27 pm September 9, 2019 by Timothy Baffa
5 replies
Martin Premont
07:50 pm September 5, 2019

What happens if multiple Scrum Teams work on the same product? then all should have the same Sprint length. Are all the Sprint lengths the same duration?

 

And what consist of multiple Scrum teams?   For instance the Sprint would have multiple Scrum Masters, P.Os and Dev. Teams?

Steve Matthew
08:23 pm September 5, 2019

What happens if multiple Scrum Teams work on the same product? then all should have the same Sprint length. Are all the Sprint lengths the same duration?

@Martin Premont, There is no mandate that the Sprint cadence should be the same for multiple teams working on the same product, however, from my experience its best to keep the cadences synced. There may be circumstances where non-synced cadences are applicable and that's open for teams to experiment with.

There is only 1 PO in the scenario described, there can be 1 Scrum Master for each team or Shared Scrum Masters for different teams, with the preference being to have a dedicated Scrum Master for each team.

arvind pal singh
04:14 am September 6, 2019

It would depend on may parameters like what is dependency on the increment being produced? For some time we divided our teams for front end and backend. Backend team was always a week ahead in the iteration as front end would consume what is created by backend team.

 

Ian Mitchell
05:48 am September 6, 2019

What happens if multiple Scrum Teams work on the same product? then all should have the same Sprint length. Are all the Sprint lengths the same duration?

And what consist of multiple Scrum teams?   For instance the Sprint would have multiple Scrum Masters, P.Os and Dev. Teams?

What do you think would be the best approach to integrating a product increment which can then be released?

Martin Premont
09:40 pm September 6, 2019

All the same length.

 

That's a mock question test that I got but I had to paraphrase it as it got taken down.   The answer was different Sprint durations which would be chaotic.   That means different review for the stakeholders etc...

Timothy Baffa
08:27 pm September 9, 2019

For some time we divided our teams for front end and backend. Backend team was always a week ahead in the iteration as front end would consume what is created by backend team.

Arvind, do you believe this division of work supports Scrum?   

Is there a complete, potentially-deliverable item at the end of every sprint?   Does your Definition of Done cover this imperative Scrum requirement?

 

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.