Discuss Scrum SPS Exam Topic 3 Question 13

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 should the Scrum Teams do to effectively deal with their dependencies?

(choose the best answer)

AIncrease the frequency of Cross-Team Refinement to reduce dependencies.

BMerge the two Scrum Teams together that have the most dependencies with each
other.

CInstitute quarterly meetings for planning out all dependencies between teams.

DAll of the above.

Suggested Answer: A, C

The Nexus framework is a way of scaling Scrum for multiple teams working on a single product. The Nexus framework uses Scrum as its building block and extends it only where necessary to minimize and manage dependencies between teams 12. The Nexus framework defines the accountabilities, events, and artifacts that bind and weave together the work of the teams in a Nexus 12. One of the key roles in the Nexus framework is the Nexus Integration Team, which is a team of people who are responsible for coordinating, coaching, and supervising the integration of the work done by the Scrum Teams in the Nexus 21.

The purpose of the Nexus Integration Team is to:

Raise transparency. This is answer A. This is a valid answer because the Nexus Integration Team is responsible for raising transparency across the Nexus 213. Transparency is one of the pillars of empiricism, which is the principle of making decisions based on observation, inspection, and adaptation 12. The Nexus Integration Team helps to raise transparency by facilitating the Nexus events, such as the Nexus Sprint Planning, the Nexus Daily Scrum, the Nexus Sprint Review, and the Nexus Sprint Retrospective 213. The Nexus Integration Team also helps to raise transparency by visualizing the Nexus Sprint Backlog, which is a representation of the work across the Nexus that has dependencies 213. The Nexus Integration Team also helps to raise transparency by communicating and collaborating with the stakeholders, the Product Owner, and the Scrum Teams 213.

Be accountable that an Integrated Increment is produced. This is answer C. This is a valid answer because the Nexus Integration Team is accountable that an Integrated Increment is produced 214. The Integrated Increment is the integrated aggregation of all work completed by all the Scrum Teams in a Nexus 124. The Integrated Increment is the potentially releasable outcome of the Sprint, which means it meets the quality standards and expectations of the stakeholders 124. The Nexus Integration Team is accountable that an Integrated Increment is produced by ensuring that the work done by the Scrum Teams meets the Definition of Done, which is a formal description of the state of the Increment when it meets the quality measures required for the product 214. The Nexus Integration Team is also accountable that an Integrated Increment is produced by helping the Scrum Teams to identify and resolve any integration issues or dependencies that may affect the quality and delivery of the product 214.

The other two answers are not correct because:

Manage the Nexus. This is answer B. This is not a valid answer because the Nexus Integration Team is not the manager of the Nexus. The Nexus Integration Team is a role that consists of the Scrum Master, the Product Owner, and other members who are responsible for coordinating, coaching, and supervising the integration of the work done by the Scrum Teams in the Nexus 211. The Nexus Integration Team does not manage or control the Nexus, but rather supports and enables the Nexus 211. The Nexus is self-organizing and autonomous, which means it decides how to do its work and what work to do 124.

Integrate the work of the Scrum Teams. This is answer D. This is not a valid answer because the Nexus Integration Team is not the one who integrates the work of the Scrum Teams. The Nexus Integration Team is a role that consists of the Scrum Master, the Product Owner, and other members who are responsible for coordinating, coaching, and supervising the integration of the work done by the Scrum Teams in the Nexus 211. The Nexus Integration Team facilitates the integration of the work, but does not do it for the teams 211. The teams are responsible for integrating their own work and delivering a potentially releasable Increment of product value in each Sprint 124.

Get Premium SPS Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

37 comments · newest first

Wilda 10 months ago

Really? Are we sure that will actually solve anything?

Rikki 11 months ago

I think all of the above could help!

Gianna 11 months ago

Quarterly meetings? Seems like a lot of time wasted.

Dyan 11 months ago

Merging teams? That could create more chaos.

Gracia 11 months ago

Increasing Cross-Team Refinement sounds smart!

Krystina 12 months ago

I think "All of the above" could be a valid approach, but it seems like a lot to manage. I need to think about which option would be the most effective in practice.

Geoffrey 12 months ago

I feel like quarterly meetings might be too infrequent to address ongoing dependencies. We practiced a question similar to this, and I think more frequent touchpoints are better.

Carline 12 months ago

Merging teams sounds drastic, but I think it could work if the dependencies are really high. I just wonder if it would create more issues down the line.

Veronika 1 year ago

I remember we discussed how increasing Cross-Team Refinement could help clarify dependencies, but I'm not sure if that's the only solution.

Johnetta 1 year ago

This is a tough one, but I feel pretty confident that the best approach is to increase the frequency of cross-team refinement. That should help the teams identify and address dependencies more effectively.

Kenny 1 year ago

Okay, I think I've got a strategy for this. Increasing the frequency of cross-team refinement is probably a good start, but I also like the idea of instituting quarterly meetings to plan out dependencies. I'll make sure to weigh all the options carefully.

Luann 1 year ago

Hmm, I'm a bit confused by this question. Increasing the frequency of cross-team refinement seems like it could help, but I'm not sure if that's the best approach. I'll need to think this through.

Tandra 1 year ago

This seems like a tricky one. I'll need to carefully consider the different options and how they might address the dependencies between the teams.

Eladia 1 year ago

This seems like a straightforward question, I'll just read through the statements carefully and select the appropriate answer.

Fletcher 1 year ago

I remember studying the categories of adopters, and I think Trevor fits the early majority since he bought the phone after the software issues were resolved.

Tegan 1 year ago

I feel like the exam might be tricky, like the one we practiced where all options were valid. Could all be possible here too?

James 1 year ago

Dependencies? More like 'defriend-encies'. Maybe we should just send the backlog items to each other on Snapchat - those disappear fast enough, right?

Irving 1 year ago

↳ replying to James

User 3: D) All of the above.

Abel 1 year ago

↳ replying to James

User 2: B) Merge the two Scrum Teams together that have the most dependencies with each other.

Stanford 1 year ago

↳ replying to James

User 1: A) Increase the frequency of Cross-Team Refinement to reduce dependencies.

Alfred 1 year ago

All of the above? Might as well throw in a dance party and some trust falls while we're at it. Dependencies are tough, but we've got this!

Virgie 1 year ago

↳ replying to Alfred

D) All of the above.

Antonio 1 year ago

↳ replying to Alfred

C) Institute quarterly meetings for planning out all dependencies between teams.

Lili 1 year ago

↳ replying to Alfred

B) Merge the two Scrum Teams together that have the most dependencies with each other.

Marge 1 year ago

↳ replying to Alfred

A) Increase the frequency of Cross-Team Refinement to reduce dependencies.

Karrie 1 year ago

Quarterly meetings for planning dependencies? Sounds like a recipe for endless meetings and bureaucracy. Let's keep things agile!

Lazaro 1 year ago

But what about merging teams with the most dependencies?

Callie 1 year ago

I agree with Lasandra, that could help us reduce dependencies.

Casie 1 year ago

Merging teams might work, but it could create other issues. Better to focus on improving communication and collaboration between teams.

Jerry 1 year ago

↳ replying to Casie

Merging teams might work, but it could create other issues. Better to focus on improving communication and collaboration between teams.

Jolanda 1 year ago

↳ replying to Casie

A) Increase the frequency of Cross-Team Refinement to reduce dependencies.

Lasandra 1 year ago

I think we should increase Cross-Team Refinement.

Georgiann 2 years ago

Increasing the frequency of Cross-Team Refinement seems like the most logical approach. Sharing information and aligning backlog items across teams can help reduce dependencies.

Bette 1 year ago

↳ replying to Georgiann

D) All of the above.

Glory 1 year ago

↳ replying to Georgiann

C) Institute quarterly meetings for planning out all dependencies between teams.

Gracie 1 year ago

↳ replying to Georgiann

B) Merge the two Scrum Teams together that have the most dependencies with each other.

Lemuel 1 year ago

↳ replying to Georgiann

A) Increase the frequency of Cross-Team Refinement to reduce dependencies.

Scrum SPS Exam - Topic 3 Question 13 Discussion