Scrum SPS Exam - Topic 3 Question 20 Discussion

Actual exam question for Scrum's SPS exam

Question #: 20
Topic #: 3

[All SPS Questions]

Scenario B: Six Team Nexus with complex dependencies

A six team Nexus is developing a complex product, with different parts of the product 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?

(choose the best answer)

ADuring Nexus Sprint Planning, have all the teams plan the Sprint together in one
room, so they can see what other teams are working on.

BDuring Nexus Sprint Planning, ensure that all Scrum Teams understand the Nexus
Sprint Goal.

CAsk the Scrum Master to explain to the teams that the Product Owner can choose
which features to work on, as she has the final say.

DDuring Nexus Sprint Planning, ask each Scrum Team to create a Sprint Goal that
describes the purpose of the Sprint.

Show Suggested Answer

Suggested Answer: B

Creating a communication plan is not enough to fully address the coordination challenges that arise when many Scrum Teams work on the same product. A communication plan is a document that outlines the objectives, methods, channels, and frequency of communication among the stakeholders of a project or product 1. While a communication plan is useful for ensuring clarity, transparency, and alignment among the Scrum Teams and other parties involved, it does not address other aspects of coordination, such as integration, dependency management, alignment of goals and vision, and cross-team collaboration 2.

To effectively coordinate multiple Scrum Teams working on the same product, a communication plan should be complemented by other practices and frameworks, such as:

Nexus: Nexus is a framework for scaling Scrum that consists of three to nine Scrum Teams working together to deliver an Integrated Increment every Sprint 3. Nexus provides roles, events, artifacts, and rules that help the Scrum Teams coordinate, integrate, and align their work, while maintaining the Scrum values and principles 4.

Scrum of Scrums: Scrum of Scrums is a technique for scaling Scrum that involves a regular meeting of representatives from each Scrum Team to share progress, identify dependencies, resolve issues, and align on the product vision and goal . Scrum of Scrums helps the Scrum Teams communicate and collaborate effectively, while minimizing the overhead and complexity of coordination .

Communities of Practice: Communities of Practice are groups of people who share a common interest, skill, or domain, and who meet regularly to exchange knowledge, ideas, and best practices . Communities of Practice help the Scrum Teams learn from each other, improve their skills, and foster a culture of continuous improvement .

by Larue at Mar 19, 2025, 02:29 AM

Limited Time Offer

25%

Off

Get Premium SPS Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Keneth

5 months ago

Wait, can the Product Owner really just choose whatever features they want?

upvoted 0 times

...

Scarlet

5 months ago

Option D could help teams feel more connected to the overall goal.

upvoted 0 times

...

Caprice

6 months ago

Totally agree, understanding the Nexus Sprint Goal is crucial!

upvoted 0 times

...

Denise

6 months ago

Not sure if just planning together will solve the dependency issues.

upvoted 0 times

...

Mona

6 months ago

I think option B is key for alignment.

upvoted 0 times

...

Kati

6 months ago

I recall a practice question where we emphasized the role of the Product Owner. Option C seems a bit dismissive of team input, though.

upvoted 0 times

...

Ona

7 months ago

I feel like option D could lead to confusion since each team might focus too much on their own goals instead of the overall product.

upvoted 0 times

...

Rima

7 months ago

I'm not entirely sure, but I think having all teams plan together could help with visibility on dependencies. Option A sounds like it could work too.

upvoted 0 times

...

Robt

7 months ago

I remember we discussed the importance of having a shared understanding of the Sprint Goal in our study group. It seems like option B might be the best choice here.

upvoted 0 times

...

Lindsay

7 months ago

The key here seems to be helping the individual teams understand how their work contributes to the overall product progress. Focusing on the Nexus Sprint Goal could be a good way to do that. I feel pretty confident that's the best approach.

upvoted 0 times

...

Lanie

7 months ago

Hmm, getting all the teams together during Sprint Planning sounds like a good way to improve visibility and alignment. That way they can see how their work connects to the bigger picture. I'd probably go with that option.

upvoted 0 times

...

Sherell

8 months ago

I'm a bit confused by this question. It seems like there are a lot of different factors at play, and I'm not sure which one is the "best" remedy. I think I'd want to gather more information before deciding on an approach.

upvoted 0 times

...

Minna

8 months ago

This seems like a tricky situation with a lot of moving parts. I'd probably start by trying to get a better understanding of the dependencies between the teams and how their work fits into the overall product. Focusing on the Nexus Sprint Goal could help provide that clarity.

upvoted 0 times

...

Zena

1 year ago

I'm leaning towards option D. Having each team create their own Sprint Goal could help them understand their role and how it fits into the bigger picture. Plus, it sounds more fun than just listening to the Scrum Master lecture them.

upvoted 0 times

...

Janine

1 year ago

Haha, the Scrum Master telling the teams that the Product Owner has the final say? That's like the teacher telling the students that the principal is the boss. Not very helpful, is it?

upvoted 0 times

Elizabeth

11 months ago

A) During Nexus Sprint Planning, have all the teams plan the Sprint together in one room, so they can see what other teams are working on.

upvoted 0 times

...

Janessa

11 months ago

B) During Nexus Sprint Planning, ensure that all Scrum Teams understand the Nexus Sprint Goal.

upvoted 0 times

...

Phuong

11 months ago

A) During Nexus Sprint Planning, have all the teams plan the Sprint together in one room, so they can see what other teams are working on.

upvoted 0 times

...

Vernell

1 year ago

I agree with Fabiola. Ensuring that the Nexus Sprint Goal is understood is crucial in a complex multi-team setup. That way, everyone can align their efforts towards a common objective.

upvoted 0 times

Felton

12 months ago

A) During Nexus Sprint Planning, have all the teams plan the Sprint together in one room, so they can see what other teams are working on.

upvoted 0 times

...

Matthew

1 year ago

B) During Nexus Sprint Planning, ensure that all Scrum Teams understand the Nexus Sprint Goal.

upvoted 0 times

...

Monroe

1 year ago

A) During Nexus Sprint Planning, have all the teams plan the Sprint together in one room, so they can see what other teams are working on.

upvoted 0 times

...

Fabiola

1 year ago

I think option B is the best answer. If the Nexus Sprint Goal is clearly understood by all the Scrum Teams, they'll be able to see how their work contributes to the overall product progress.

upvoted 0 times