Planning Multiple Sprints in Nexus
One of the big differentiators I see between Nexus and SAFe is the number of advanced sprints planned. In SAFe, the work for the Next 2 Program increments is always being refined. When a PI is planned, there are 5 two week iterations for everyone to review and agree on. This helps a lot with knowing where you are going and resolving known dependencies.
How does Nexus track and resolve dependencies if you are only planning sprint by sprint?
Regards,
Thom
Hi Thomas,
Nexus essentially does the equivalent of PI planning at each Sprint, but since the # sprints being planned is less, it can be done in far less time than a PI planning meeting(even with the same # of teams involved). Dependency mgmt. is handled in two ways: during Refinement (through multi level refinement events), and during the Sprint via the Nexus Integration Team and the Nexus Daily Scrum.
Nexus takes the view that dependencies need to be constantly tracked and optimized on, while SAFe tends to take a "we worry mostly about dependences once a quarter and then occasionally at a SoS". This leads SAFe toward a bias of not being as nimble... or say.. Agile. :-) This is not to say one could not overcome said bias with better practices of course. (even with SAFe)
(Btw, I'm certified in all 3 major scaling approaches). For a preso on the major similarities and differences between them, see here:
http://ScrumCrazy.com/presentations
sorry, link here:
(also note that Refinement in Nexus typically covers the horizon of 3-4 sprints beyond the current sprint, so dependencies are still known and optimized 3-4 sprints ahead)
When a PI is planned, there are 5 two week iterations for everyone to review and agree on. This helps a lot with knowing where you are going and resolving known dependencies.
Planning an increment for release is one thing, resolving dependencies in a product backlog is another. Increments should be delivered as early and as often as possible in order to realize value and establish empirical control, while dependencies ought to be identified and resolved in the timeliest manner to minimize waste. Might the SAFe prescription you refer to be a rather blunt instrument?
How does Nexus track and resolve dependencies if you are only planning sprint by sprint?
Because the two concerns are not the same. Plan to release as early and as often as possible...perhaps even multiple times per Sprint. Resolve dependencies as far ahead as you need to without attracting excessive rework and other inefficiencies. Also, on a day-to-day basis, learn to use continuous integration as a means of ensuring transparency.