Scenario C: Dependencies and Product Backlog items
During 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 would you recommend to the two teams that are continually dependent on each other to
help them manage their work?
(choose the best answer)
The other options are not advisable for the following reasons:
What is the purpose of Nexus Sprint Retrospective?
(choose the best answer)
The purpose of Nexus Sprint Retrospective is all of the above, meaning that it aims to:
Which statements are true when multiple Scrum Teams work on a product at the same time?
(choose the best two answers)
When multiple Scrum Teams work on a product at the same time, the statements that are true are:
The other three answers are not correct because:
How might the Nexus evolve its Definition of Done over time?
(choose the best answer)
Four teams in a Nexus typically integrate their work only once, late in the Sprint. The teams
report that it takes many hours or days to integrate their work, which delays the Sprint's end. To
address this issue, which of the following would help?
(choose the best answer)
The other answers are not correct for the following reasons:
D . Using Behavior-Driven Development. This answer is not relevant because using Behavior-Driven Development does not directly affect the integration of the work. Behavior-Driven Development is a technique that can help to define and communicate the expected behavior and outcomes of the product increment, but it does not ensure that the integration is done frequently and effectively. Additionally, using Behavior-Driven Development may require more collaboration and coordination, and complicate the delivery of the product increment [6].
E . Investing in more Requirements Traceability. This answer is not useful because investing in more Requirements Traceability does not improve the integration of the work. Requirements Traceability is a practice that can help to track and document the origin and evolution of the product requirements, but it does not ensure that the integration is done timely and efficiently. Also, investing in more Requirements Traceability may increase the overhead and bureaucracy, and slow down the delivery of the product increment [7].
F . All of the above. This answer is not correct because none of the above answers are effective for addressing the issue of the late integration of the work. As explained above, each of the above answers has its own limitations and drawbacks, and does not directly or sufficiently help the Scrum Teams in a Nexus to integrate their work more frequently and successfully. Therefore, the best answer is A. Integrating more frequently.