Nexus Sprint Planning

The purpose of Nexus Sprint Planning is to coordinate the activities of all Scrum Teams in a Nexus for a single Sprint. The Product Owner provides domain knowledge and guides selection and priority decisions. The Product Backlog should be adequately refined with dependencies identified and removed or minimized prior to Nexus Sprint Planning.

During Nexus Sprint Planning, appropriate representatives from each Scrum Team validate and make adjustments to the ordering of the work as created during Refinement events. All members of the Scrum Teams should participate to minimize communication issues.

The Product Owner discusses the Nexus Sprint Goal during Nexus Sprint Planning. The Nexus Sprint Goal describes the purpose that will be achieved by the Scrum Teams during the Sprint. Once the overall work for the Nexus is understood, Nexus Sprint Planning continues with each Scrum Team performing their own separate Sprint Planning. The Scrum Teams should continue to share newly found dependencies with other Scrum Teams in the Nexus. Nexus Sprint Planning is complete when each Scrum Team has finished their individual Sprint Planning events.

New dependencies may emerge during Nexus Sprint Planning. They should be made transparent and minimized. The sequence of work across teams may also be adjusted. An adequately refined Product Backlog will minimize the emergence of new dependencies during Nexus Sprint Planning. All Product Backlog items selected for the Sprint and their dependencies should be made transparent on the Nexus Sprint Backlog.

The Nexus Events in detail

Read on