Skip to main content

Question about Nexus Integrated Increment

Last post 03:20 pm July 17, 2017 by Ian Mitchell
6 replies
07:52 pm July 13, 2017

What is the cadence of a Nexus "Integrated Increment"? Is this also 1 to 4 weeks like a 'standard' Sprint in Scrum, or can teams decide on this for their own project/program?


08:55 pm July 13, 2017

Note that the Nexus guide states: "The Nexus Integration Team is accountable for ensuring that an Integrated Increment is produced at least every Sprint".

I assume that in this context, "Sprint" is a "Nexus Sprint" (or "Nexus") which will MOST LIKELY consist of multiple (standard) team Sprints?


05:32 am July 14, 2017

Increments can be integrated and deployed on an ongoing basis in Scrum. Integration and deployment is not necessarily constrained by Sprint cadence or by any other cadence. A Nexus facilitates integration when multiple teams are involved.


05:21 pm July 14, 2017

So increment duration does not have to be decided upfront, similar to a Release Planning (or PI Planning) process in Scaled Agile Framework?


07:10 pm July 14, 2017

In Scrum an increment is an artifact, not an event, and so it cannot be said to have a duration.

There is no correlation between the Nexus Framework and SAFe.


02:35 pm July 17, 2017

Ian,

Thanks for your explanation.

What I am most confused about is whether a "Nexus Sprint" is synonymous with a SINGLE "Sprint", or does it consist of multiple sprints?

 


03:20 pm July 17, 2017

It could be either. Nexus is a framework and is deliberately as non-prescriptive as possible. There must be a common time-box which all teams observe to meet the Nexus Sprint Goal, but there's nothing to stop each team from also observing its own Sprint arrangements (e.g. a team could run 2 x 2 week Sprints in a Nexus 4 week Sprint).


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.