Question 26 - SPS discussion

When a Nexus, which is a group of approximately three to nine Scrum Teams working on the same product, faces many dependencies during Nexus Sprint Planning, it can use some techniques to manage them effectively. One technique is to reorganize team members between the teams to eliminate cross-team dependencies. This can be done by forming feature teams or component teams based on the nature of the work and the skills required. By doing so, the Nexus can reduce the need for coordination and integration across teams, and increase the autonomy and ownership of each team 1122. Therefore, statement B is correct.

Another technique is to reorder Product Backlog items to better accommodate dependencies. This can be done by applying dependency management techniques such as dependency mapping, dependency inversion, dependency breaking, and dependency prioritization. By doing so, the Nexus can identify, visualize, resolve, and minimize the dependencies that affect the delivery of the Integrated Increment, which is the combined work of all the Scrum Teams in the Nexus that meets the Nexus Sprint Goal 334455. Therefore, statement D is also correct.

Statement A is incorrect because it implies that the Nexus Integration Team, which is a group of people who are accountable for ensuring the integration and delivery of the Integrated Increment, should do the dependent work ahead of the Sprint for the teams. This would create a bottleneck and a single point of failure, as well as undermine the self-organization and collaboration of the Scrum Teams 1122. Statement C is incorrect because it suggests that the Nexus should extend the Sprint so that the teams can have more time to complete the dependent work. This would violate the Scrum principle of time-boxing, which ensures that the Nexus delivers value frequently and incrementally, and inspects and adapts its process regularly 1122.