[color=#6495ed]Scenario A: Nexus Sprint Review with Five Scrum Teams[/color]
There are five Scrum Teams working on a Product. During the Nexus Sprint Review, the teams present the results of the Sprint. After introductions, each team takes time to present their work for inspection by individually showing the new features they have built. They are not using a shared environment. The stakeholders do not provide much feedback. The event ends and people filter out of the room.
If this pattern of Nexus Sprint Reviews continues for many Sprints, what may be the effects?
(choose the best two answers)
A. Quality will degrade as the teams delay creating a single Integrated Increment.
B. There will be more and more work to inspect so teams will need their own individual Sprint Reviews.
C. Empiricism will suffer as the teams cannot produce a shared velocity.
D. Ability to adapt will suffer as the stakeholders continue to disengage and not give feedback.

[color=#6495ed]Scenario C: Dependencies and Product Backlog Items[/color]
During the Nexus Sprint Planning, representatives from each of the 9-member Scrum Teams identify many dependencies. This makes it hard for them to choose the work they could pull into their individual teams for the next Sprint. No matter how they reorganize the Product Backlog items, they continually find more or new dependencies.
What should the Scrum Teams do to effectively deal with their dependencies?
(choose the best answer)
A. Increase the frequency of Cross-Team Refinement to reduce dependencies.
B. Merge the two Scrum Teams together that have the most dependencies with each other.
C. Institute quarterly meetings for planning out all dependencies between teams.
D. All of the above.

What is the purpose of Nexus Sprint Retrospective?
(choose the best answer)
A. Plan ways to increase quality and effectiveness across the whole Nexus.
B. To inspect how the last Sprint went with regards to individuals, teams, interactions, processes, tools, and its Definition of Done.
C. To complement the Scrum Teams’ Sprint Retrospectives by using bottom-up intelligence to focus on issues that affect the Nexus as a whole.
D. All of the above.

Which statements best describe a Nexus Sprint Review?
(choose the best two answers)
A. It is when individual teams demo their work.
B. It provides feedback on the Integrated Increment.
C. It is a container for each individual Scrum Team’s Sprint Review.
D. It replaces individual Scrum Team Sprint Reviews.

From the list below, what is the most important concern for multiple Scrum Teams when they are working from the same Product Backlog?
(choose the best answer)
A. Meeting original scope projections.
B. Clear definition of requirements.
C. Minimizing dependencies between teams.
D. Making sure there is enough work for everyone on every team.

The Scrum Teams in a Nexus find they have simply too much work each Sprint to do to deliver a valuable and useful Increment. What could they try to improve their ability to produce an Increment in the next Sprint?
(choose the best answer)
A. Reduce the amount of work that the teams pull into the Sprint.
B. Add another Scrum Team to the Nexus to increase capacity.
C. Reduce the number of Scrum Teams to reduce complexity.
D. Ask the Nexus Integration Team to extend the Sprint to allow more time for integration.