Back to Forum

Nexus - TimeBox/Duration of Nexus Sprint?

Last post 02:03 am July 11, 2016 by Alan Larimer
4 replies
Pankaj Ahuja
12:45 pm July 3, 2016

Should the duration of Nexus sprint be same as that of all the sprints which are part of the Nexus?

Or should it be slightly longer in order to carry out the Integration related tasks/activities (Integration, Issue Resolution, Testing (Integrated functional and non-functional specifically Performance and Load aspects, Defect Resolution and regression)?

Olivier Ledru
06:50 pm July 3, 2016

Nexus is "just" Scrum at scale.
Instead of a team of 3 / 9 people, you have a meta-team of 3 / 9 dev team.

How do you deal with integration ; testing ; NFR in "regular" Scrum ?

Ian Mitchell
09:36 am July 4, 2016

> should it be slightly longer in order to carry out the Integration
> related tasks/activities

How would each team ensure they delivered a release quality increment by the end of their respective Sprints, if that were the case?

Michael Kogan
01:20 pm July 10, 2016

Hi Pankaj,

naturally, a Nexus sprint should take longer than one team's sprint due to integration and coordination activities, which cannot all be done in parallel. For instance, Sprint Planning meeting must happen before each team's planning meeting.

Hope this helps,
Michael

Alan Larimer
02:03 am July 11, 2016

"A new Sprint starts immediately after the conclusion of the previous Sprint." The length is the same; if it were longer then it would continually become further out of sync. Any perceived "extra" time for the Nexus events is time the Scrum Teams and their members can use to engage in individual or team improvement, meeting business needs such as HR training, one-on-one meetings with managers, etc.

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.