The Nexus Sprint Review is an event that occurs at the end of the Sprint where the Nexus, which is a group of approximately three to nine Scrum Teams working on the same product, presents the Integrated Increment to the stakeholders and collects feedback 1 2 . The Integrated Increment is the combined work of all the Scrum Teams in the Nexus that meets the Definition of Done and the Nexus Sprint Goal 1 . The purpose of the Nexus Sprint Review is to inspect the Integrated Increment and adapt the Product Backlog based on new learnings 1 . Therefore, statement A is correct.

The Nexus Sprint Review replaces individual Scrum Team Sprint Reviews because the focus is on the entire Integrated Increment rather than the work of each team 1 2 . The Nexus Sprint Review is not a container for each individual Scrum Team’s Sprint Review, nor is it when individual Scrum Teams demo their work. These statements imply that the Nexus Sprint Review is a collection of separate Sprint Reviews, which is not the case. The Nexus Sprint Review is a single event that involves all the Scrum Teams and stakeholders in the Nexus 1 2 . Therefore, statement B is also correct, and statements C and D are incorrect.

The Nexus framework is a way of scaling Scrum for multiple teams working on a single product. The Nexus framework uses Scrum as its building block and extends it only where necessary to minimize and manage dependencies between teams 1 1 . The Nexus framework defines the accountabilities, events, and artifacts that bind and weave together the work of the teams in a Nexus 1 1 . One of the key events in the Nexus framework is the Nexus Sprint Planning, which is used to coordinate the activities of all teams in the Nexus for a single Sprint 1 1 .

In Scenario B, the Nexus is developing a complex product with different parts that only certain teams can work on. There are also 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 teams. Dependencies are the relationships between the work items that affect the order, timing, or outcome of the work 2 2 . Dependencies can cause delays, rework, waste, and lower quality 2 2 . Therefore, it is important to identify and resolve dependencies as early and as often as possible 2 2 .

The two strategies that would be most effective in dealing with the dependencies are:

Discover and document dependent work during Cross-Team Refinement of the Product Backlog, so teams are aware of dependencies before Nexus Sprint Planning. This will allow Nexus Sprint Planning to focus on resolving dependencies for the upcoming Sprint. This is answer A. This is a valid strategy because Cross-Team Refinement is an activity where representatives from each team in the Nexus meet to decompose and re fine the Product Backlog items into smaller pieces of work that can be delivered by a single team or multiple teams 1 1 . By doing this, the teams can discover and document the dependent work that needs to be done by other teams or external parties 1 1 . This will help the teams to be aware of the dependencies before the Nexus Sprint Planning and to prepare for them 1 1 . This will also allow the Nexus Sprint Planning to focus on resolving the dependencies for the upcoming Sprint, rather than spending time on identifying them 1 1 .

During Nexus Sprint Planning, have appropriate representatives from each team in the Nexus briefly meet to discuss dependencies for the upcoming Sprint. This conversation will help their individual team’s Sprint Planning. This is answer C. This is a valid strategy because Nexus Sprint Planning is an event where the Nexus, consisting of the Product Owner and appropriate representatives from each team, meet to plan the Sprint 1 1 . The purpose of Nexus Sprint Planning is to coordinate the activities of all teams in the Nexus for a single Sprint 1 1 . The result of Nexus Sprint Planning is a Nexus Sprint Goal that aligns with the Product Goal and a Nexus Sprint Backlog that contains the work to be done by the teams to achieve the Nexus Sprint Goal 1 1 . During Nexus Sprint Planning, the representatives from each team can briefly meet to discuss the dependencies for the upcoming Sprint and how to resolve them 1 1 . This conversation will help their individual team’s Sprint Planning, where they can create their own team Sprint Goal and team Sprint Backlog that support the Nexus Sprint Goal and the Nexus Sprint Backlog 1 1 .

The other two answers are not correct because:

Have the Nexus Integration Team order the Nexus Sprint Backlog. They should control and resolve the dependencies. This is answer B. This is not a valid strategy because the Nexus Integration Team is not the owner or the controller of the Nexus Sprint Backlog. The Nexus Integration Team is a role that consists of the Scrum Master, the Product Owner, and other members who are responsible for coordinating, coaching, and supervising the integration of the work done by the teams in the Nexus 1 [1][5] . The Nexus Integration Team facilitates the Nexus Sprint Planning, but does not order or dictate the Nexus Sprint Backlog 1 [1][5] . The Nexus Sprint Backlog is owned and managed by the Nexus, not by the Nexus Integration Team 1 [1][5] . The Nexus Integration Team helps the teams to identify and resolve the dependencies, but does not control or impose them 1 [1][5] .

Gather all people in the Nexus into a 48-hour Nexus Sprint Planning event. Discover, document, and resolve dependencies during this time. This is answer D. This is not a valid strategy because gathering all people in the Nexus into a 48-hour Nexus Sprint Planning event is not feasible, efficient, or effective. The Nexus Sprint Planning is not meant to be a long and exhaustive event that involves all people in the Nexus 1 1 . The Nexus Sprint Planning is meant to be a short and focused event that involves only the Product Owner and appropriate representatives from each team in the Nexus 1 1 . The Nexus Sprint Planning is not meant to be the only time to discover, document, and resolve dependencies 1 1 . The Nexus Sprint Planning is meant to be the time to coordinate the activities of the teams for the upcoming Sprint and to create a Nexus Sprint Goal and a Nexus Sprint Backlog 1 1 . The discovery, documentation, and resolution of dependencies should be done continuously throughout the Sprint, not only during the Nexus Sprint Planning 1 1 .