Coordinating Work in a Nexus
In a Nexus framework, coordination among Scrum Teams is essential to ensure the successful integration of their work into a single product. The Scrum Master plays a vital role in facilitating this coordination without directly managing the teams’ work.
Exam Question
A Nexus with five Scrum Teams has been created to build one product. A few of the Developers on one of the Scrum Teams ask the Scrum Master how to coordinate their work with the other Scrum Teams. What should the Scrum Master do?
(choose the best answer)
A. Collect the Sprint tasks from the Scrum Teams at the end of their Sprint Planning and merge that into a consolidated plan for the entire Sprint.
B. Teach them that it is their responsibility to work with the other Scrum Teams to create an Integrated Increment.
C. Teach the Product Owner to work with the lead Developers on ordering the Product Backlog in a way that avoids too much technical and development overlap during a Sprint.
D. Have the Nexus Integration Team visit all Scrum Teams daily to observe cross-team dependencies and shift the teams’ work.
Correct Answer
B. Teach them that it is their responsibility to work with the other Scrum Teams to create an Integrated Increment.
Explanation
Correct Answer
B. Teach them that it is their responsibility to work with the other Scrum Teams to create an Integrated Increment:
The Nexus framework emphasizes self-management and accountability. The Scrum Teams are responsible for coordinating their work with other teams to create an Integrated Increment. The Scrum Master should coach the teams on their responsibilities and facilitate communication and collaboration among them, rather than consolidating plans or shifting work daily.
Why the Other Options Are Less Effective
A. Collect the Sprint tasks from the Scrum Teams at the end of their Sprint Planning and merge that into a consolidated plan for the entire Sprint:
This approach contradicts the self-managing nature of Scrum Teams and places unnecessary control in the hands of the Scrum Master. Each team should be responsible for their planning and coordination.
C. Teach the Product Owner to work with the lead Developers on ordering the Product Backlog in a way that avoids too much technical and development overlap during a Sprint:
While it is essential for the Product Owner to order the Product Backlog effectively, avoiding overlap alone is not sufficient for ensuring proper coordination and integration. Teams must collaborate continuously to manage dependencies and integration issues.
D. Have the Nexus Integration Team visit all Scrum Teams daily to observe cross-team dependencies and shift the teams’ work:
This method is overly prescriptive and diminishes the teams’ autonomy. The Nexus Integration Team supports the teams in managing dependencies but should not control or shift their work on a daily basis.
Benefits of Self-Managed Coordination
- Empowerment: Teams feel empowered and take ownership of their work.
- Better Collaboration: Continuous interaction among teams fosters collaboration and mutual support.
- Adaptability: Teams can adapt to changes more effectively when they manage their coordination.
Relevance to the SPS Exam
Understanding the role of the Scrum Master in facilitating coordination without direct control is crucial for the SPS exam. It demonstrates knowledge of scaled Scrum practices and the principles of self-management and collaboration in a Nexus.
Key Takeaways
- Scrum Teams in a Nexus are responsible for coordinating their work to create an Integrated Increment.
- The Scrum Master should coach and facilitate collaboration, not control or shift the work of the teams.
- Effective coordination empowers teams, improves collaboration, and enhances adaptability.
Conclusion
In a Nexus, effective coordination among Scrum Teams is vital for creating an Integrated Increment. The Scrum Master’s role is to facilitate and coach the teams, ensuring they understand their responsibilities and collaborate effectively.

Get ready for the official SPS exam
182 SPS practice questions, each with an in-depth explanation like the one above.
- Practice Mode: study at your own pace and choose the test length.
- Mock Exam Mode: 40 random questions in 60 minutes, like the real exam.
$29 is ScrumPrep's one-time price. The official SPS exam fee ($250) is paid separately to Scrum.org.
More SPS exam questions
- How should multiple Scrum Teams deliver a a valuable and useful Increment in a Sprint?
- Who has overall responsibility for ensuring Nexus Sprint Retrospective occur?
- What is the primary purpose of the first part of the Nexus Sprint Retrospective, when representatives from across the Nexus meet?
- What is the purpose of the Nexus Sprint Retrospective?
- 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. Some individual Scrum Teams in this Nexus have said that they do not see how the work they are doing is contributing to the product’s progress. What is the best remedy for this situation?
