ExamGecko
Home Home / Scrum / SPS
Question list
Search
Search

List of questions

Search

Related questions











Question 16 - SPS discussion

Report
Export

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)

A.
The Nexus Integration Team should be responsible for integrating the work of these two Scrum Teams.
Answers
A.
The Nexus Integration Team should be responsible for integrating the work of these two Scrum Teams.
B.
Reorganize these two Scrum Teams so that one is responsible for development and one is responsible for integration.
Answers
B.
Reorganize these two Scrum Teams so that one is responsible for development and one is responsible for integration.
C.
Merge the two Scrum Teams together.
Answers
C.
Merge the two Scrum Teams together.
D.
Ensure the appropriate representatives from both teams are present during Cross- Team Refinement.
Answers
D.
Ensure the appropriate representatives from both teams are present during Cross- Team Refinement.
Suggested answer: D

Explanation:

The best way to help the two teams that are continually dependent on each other to manage their work is to ensure the appropriate representatives from both teams are present during Cross-Team Refinement. Cross-Team Refinement is an optional event in Nexus that allows the Scrum Teams to collaborate and coordinate on the Product Backlog items that have dependencies or require integration 11. By having the representatives from both teams present during this event, they can identify and resolve the dependencies, clarify the requirements, align the expectations, and plan the work for the next Sprint. This will improve the transparency, the quality, and the value of the Integrated Increment.

The other options are not advisable for the following reasons:

The Nexus Integration Team should not be responsible for integrating the work of these two Scrum Teams, as this would create a bottleneck and a hand-off. The Nexus Integration Team is a specialized Scrum Team that provides services and guidance to the Scrum Teams in the Nexus to ensure that the Integrated Increment is produced every Sprint 11. However, the Nexus Integration Team is not accountable for the integration of the work of the individual Scrum Teams, as this is the responsibility of the Scrum Teams themselves 22.

Reorganizing these two Scrum Teams so that one is responsible for development and one is responsible for integration is not a good idea, as this would create a silo and a separation of concerns. The Scrum Teams in a Nexus should be cross-functional and self-organizing, meaning that they have all the skills and abilities to deliver a potentially releasable product Increment every Sprint 11. Separating the development and the integration tasks would compromise the collaboration, the feedback, and the agility of the Scrum Teams.

Merging the two Scrum Teams together is not a viable solution, as this would create a large and unwieldy team. The Scrum Guide states that the optimal size of a Scrum Team is between three and nine members 33. Merging two Scrum Teams together would exceed this limit and create challenges in communication, coordination, and decision-making. Moreover, merging the two teams would not necessarily eliminate the dependencies, as they may still exist within the larger team or with other teams in the Nexus.

asked 23/09/2024
SAI CHARAN TANGELLA
35 questions
User
Your answer:
0 comments
Sorted by

Leave a comment first