Scenario B: Six Team Nexus with complex dependencies
A six team Nexus is developing a complex product, with different parts of the product that only certain Scrum Teams can work on. In fact, there are some highly specialized individuals outside the Nexus that are required for some of the work. In past Sprints the Nexus encountered challenges dealing with the many dependencies between Scrum Teams.
Which of the following practices could this Nexus try in order to conduct Nexus Sprint Planning more effectively?
(choose the best two answers)
- Ensure all Scrum Teams and outside experts are available during the Nexus Sprint Planning event and have a way of quickly communicating with each other.
They should try to be together in the same room or use technology that makes it seem as if they are in the same room. - Plan one Scrum Team's Sprint at a time before moving on to the next team. This way you can account for time zone differences and can communicate dependencies across all teams.
- Have the Nexus Integration Team select the work for each of the individual Scrum Teams. This allows the Nexus Integration Team to control the dependencies.
- Visualize the known dependencies in the Product Backlog for all to see. As Scrum Teams select work for the Sprint, they can easily check for any dependent work and communicate with other teams.
Answer(s): A,D
Explanation:
The purpose of Nexus Sprint Planning is to coordinate the activities of all Scrum Teams within a Nexus for a single Sprint. To do this effectively, the Nexus needs to have a clear understanding of the dependencies between the teams and the work items, and to communicate and collaborate with each other and any outside experts as needed. Therefore, the best practices for this Nexus are:
A) Ensure all Scrum Teams and outside experts are available during the Nexus Sprint Planning event and have a way of quickly communicating with each other. They should try to be together in the same room or use technology that makes it seem as if they are in the same room. This practice enables the Nexus to have a shared understanding of the Product Backlog, the Product Goal, and the Nexus Sprint Goal, and to resolve any issues or questions that may arise during the planning. It also allows the Nexus to leverage the expertise of the outside specialists who are required for some of the work.
D) Visualize the known dependencies in the Product Backlog for all to see. As Scrum Teams select work for the Sprint, they can easily check for any dependent work and communicate with other teams. This practice helps the Nexus to identify and manage the dependencies between the teams and the work items, and to optimize the flow of value delivery. It also supports transparency and alignment within the Nexus.
The other two practices are not effective for this Nexus because:
B) Plan one Scrum Team's Sprint at a time before moving on to the next team. This way you can account for time zone differences and can communicate dependencies across all teams. This practice is not optimal because it does not allow the Nexus to plan the Sprint as a whole, and to adjust the work allocation and sequence based on the dependencies and the Nexus Sprint Goal. It also creates delays and inefficiencies in the planning process, and reduces the collaboration and feedback opportunities among the teams.
C) Have the Nexus Integration Team select the work for each of the individual Scrum Teams. This allows the Nexus Integration Team to control the dependencies. This practice is not consistent with the Nexus framework, which states that the Nexus Integration Team does not select the work for the Scrum Teams, but rather facilitates the integration and delivery of the work done by the Scrum Teams. It also undermines the self-organization and empowerment of the Scrum Teams, and reduces their ownership and accountability for the work.