Select two ways in which technical debt impacts transparency.
(choose the best two answers)
A. It leads to false assumptions about the current state of the system, specifically of an Increment being releasable at the end of a Sprint.
B. As development progresses and code is added, the system becomes more difficult to stabilize, which results in future work being slowed down in unpredictable ways.
C. When calculated and estimated, the total amount of technical debt shows exactly how long until the Product Owner can release the Increment.
D. It enhances transparency for the Product Owner as the Developers are not allowed to do additional feature development in a Sprint as long as there is technical debt.

The purpose of the Nexus Sprint Backlog is:
(choose the best two answers)
A. To visualize all Product Backlog items.
B. To make the work of the Nexus Integration Team transparent.
C. To provide a view of dependent Product Backlog items in a Sprint.
D. To make dependencies transparent to the Scrum Teams.

True or False: A Nexus Integration Team is accountable for there being an Integrated Increment at the end of each Sprint.
A. True
B. False

Which statements are true when multiple Scrum Teams work on a product at the same time?
(choose the best two answers)
A. The Developers must integrate their work before the end of the Sprint.
B. They are all on the same Scrum Team.
C. Each Scrum Team develops one or more product components which the Nexus Integration Team uses to assemble the Integrated Increment.
D. The different Scrum Teams coordinate their work to deliver a single Increment.
E. The Scrum of Scrums assembles the components into an Integrated Increment.

[color=#6495ed]Scenario B: Six Team Nexus with complex dependencies[/color]
A six team Nexus is developing a full-featured e-commerce application. There are different parts of the application 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)
A. 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.
B. Visualize the known dependencies in the Product Backlog for all to see. As teams select work for the Sprint, they can easily check for any dependent work and communicate with other teams.
C. 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 communicate dependencies across all teams.
D. 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 seems as they are in the same room.

[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.
You overhear a few stakeholders talking about their concerns about the product after the Nexus Sprint Review. They didn’t find the review valuable. Why?
(choose the best answer)
A. The Nexus Sprint Review was not a review of the Integrated Increment and Nexus Sprint Goal, but rather a review of each team’s individual work.
B. The Nexus Sprint Review should have been longer. It failed to cover all completed work in detail.
C. The Stakeholders lack understanding of Scrum and coaching.
D. All of the above.