Scrum SPS Exam - Topic 4 Question 18 Discussion

Actual exam question for Scrum's SPS exam

Question #: 18
Topic #: 4

[All SPS Questions]

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)

AThe Nexus Integration Team should be responsible for integrating the work of these
two Scrum Teams.

BReorganize these two Scrum Teams so that one is responsible for development and
one is responsible for integration.

CMerge the two Scrum Teams together.

DEnsure the appropriate representatives from both teams are present during Cross-
Team Refinement.

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 Remedios at Feb 07, 2025, 02:06 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Emmett

3 months ago

Option A could work too, but it might slow things down.

upvoted 0 times

...

Felix

3 months ago

Wait, are they really finding new dependencies every time? That sounds rough!

upvoted 0 times

...

Claudia

3 months ago

Merging the teams (option C) might be too drastic.

upvoted 0 times

...

Nell

4 months ago

Totally agree with D! Communication can clear up a lot of confusion.

upvoted 0 times

...

Maurine

4 months ago

I think option D is the best choice. Collaboration is key!

upvoted 0 times

...

Andree

4 months ago

I practiced a similar question, and I think having representatives from both teams present is crucial. Option D aligns with what we learned about collaboration.

upvoted 0 times

...

Virgina

4 months ago

I feel like the Nexus Integration Team should handle dependencies, but I can't recall if that's the best approach. Maybe A is worth considering?

upvoted 0 times

...

Reuben

4 months ago

I'm not entirely sure, but merging the teams could create more issues than it solves. Option C seems risky to me.

upvoted 0 times

...

Thora

5 months ago

I remember we discussed how important it is for teams to communicate during Cross-Team Refinement. I think option D might be the best choice.

upvoted 0 times

...

Devon

5 months ago

Merging the teams might be a bit drastic. I'd start by making sure the right stakeholders are involved in the planning sessions to get a better handle on the dependencies.

upvoted 0 times

...

Nobuko

5 months ago

I'm feeling pretty confident about this one. Reorganizing the teams to have one focused on development and one on integration seems like the best approach to me.

upvoted 0 times

...

Xenia

5 months ago

Okay, I think the key here is to ensure the right people are involved in the cross-team refinement process. That should help them identify and manage the dependencies more effectively.

upvoted 0 times

...

Jose

5 months ago

Hmm, I'm a bit confused by all the dependencies they're facing. I wonder if merging the teams or having a dedicated integration team might help streamline things.

upvoted 0 times

...

Kenny

5 months ago

This seems like a tricky one. I'll need to carefully consider the options and think through the implications of each.

upvoted 0 times

...

Brent

9 months ago

I'm with you all on D. Though I have to say, the idea of merging the teams or having an integration team sounds like a recipe for even more chaos. Might as well just throw in the towel and start a juggling troupe!

upvoted 0 times

Raul

8 months ago

Yeah, let's stick with D for now and see how it goes.

upvoted 0 times

...

Hannah

8 months ago

I don't think merging the teams or having an integration team is the right move.

upvoted 0 times

...

Elinore

8 months ago

Agreed, having representatives from both teams during Cross-Team Refinement is crucial.

upvoted 0 times

...

Wei

8 months ago

I think D is the best option here.

upvoted 0 times

...

Mertie

10 months ago

Definitely option D. Keeping both teams involved and communicating during refinement is key to staying on top of those dependencies.

upvoted 0 times

Elenore

9 months ago

It's important to address those dependencies early on to avoid issues later.

upvoted 0 times

...

Nakisha

9 months ago

I agree, having both teams present during Cross-Team Refinement is crucial.

upvoted 0 times

...

Meaghan

9 months ago

Option D is the way to go. Communication is key!

upvoted 0 times

...

Martin

10 months ago

I agree, D seems like the way to go. Merging the teams or having a separate integration team might just create more problems down the line.

upvoted 0 times

Merissa

8 months ago

D) That way they can address dependencies and plan together.

upvoted 0 times

...

Leota

9 months ago

A) The Nexus Integration Team should be responsible for integrating the work of these two Scrum Teams.

upvoted 0 times

...

Krissy

9 months ago

D) That's a good point. Having the right representatives present during Cross-Team Refinement can help manage dependencies.

upvoted 0 times

...

Juan

9 months ago

A) The Nexus Integration Team should be responsible for integrating the work of these two Scrum Teams.

upvoted 0 times

...

Nancey

9 months ago

D) Ensure the appropriate representatives from both teams are present during Cross-Team Refinement.

upvoted 0 times

...

Mitsue

10 months ago

D) Ensure the appropriate representatives from both teams are present during Cross-Team Refinement.

upvoted 0 times

...

Tomoko

10 months ago

Hmm, this looks tricky. I think option D is the best choice here - getting the right people from both teams involved in the Cross-Team Refinement process could really help manage those dependencies.

upvoted 0 times