Nexus is a framework, based on Scrum, that helps companies to scale software and product development. In fact, thanks to this framework organizations can plan, launch, scale and manage large product and software development projects. In addition, they are able to develop products in a faster way by reducing costs. Let’s analyze the Sprint Planning event in Nexus.
Nexus Sprint Planning
During this event the Nexus creates a plan for the next Sprint. This is the moment when the Nexus Sprint Goal is developed. In particular, the Sprint Goal in Nexus is a goal shared by all the Scrum Teams. These teams have to work together to achieve the goal during the Sprint.
Who attends Nexus Sprint Planning?
The Nexus Sprint Planning event starts when the right representatives meet each other to identify, minimize and resolve dependencies that can exist in the Sprint. In fact, each Scrum team needs to have its representatives at this event. Then, they will work to reorder the items as required. After this event all people involved in the joint meeting come back to their individual Scrum Teams. At this point they need to perform the individual Sprint Planning with their Scrum Team.
The result of Nexus Sprint Planning
The result of the Nexus Sprint Planning is an artifact named Nexus Sprint Backlog. The Nexus Integration Team (NIT) creates and manages the backlog. Basically, the backlog shows all dependencies that will exist during the Sprint. In addition, it represents a way to manage the work in a Nexus. The backlog should be reviewed at least daily.
Keep in mind
Thanks to Nexus, organizations are able to develop products in a faster way by reducing costs. During the Nexus Sprint Planning the Nexus Sprint Goal is developed. Afterwards, as a result the Nexus Sprint Backlog is produced. The backlog will show all dependencies that will exist during the Sprint.