Question about Nexus Integrated Increment
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?
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?
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.
So increment duration does not have to be decided upfront, similar to a Release Planning (or PI Planning) process in Scaled Agile Framework?
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.
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?
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).