Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Scrum SPS Exam - Topic 2 Question 17 Discussion

Actual exam question for Scrum's SPS exam
Question #: 17
Topic #: 2
[All SPS Questions]

Scenario A: Nexus Sprint Review with Five Scrum Teams

There are five Scrum Teams working on a product. During the Nexus Sprint Review, the teams

present the results of the Sprint. After introductions, each team takes time to present their work

for inspection by individually showing the new features they have built. They are not using a

shared environment. The stakeholders do not provide much feedback. The event ends and

people filter out of the room.

What could help this Nexus create a single Integrated Increment for inspection at the Nexus

Sprint Review?

(choose the best answer)

Show Suggested Answer Hide Answer
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.


by Naomi at Jan 25, 2025, 01:57 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Dong
6 months ago
D sounds like a waste of a whole Sprint, honestly.
upvoted 0 times
...
Heike
6 months ago
Surprised they didn't integrate earlier in the Sprint!
upvoted 0 times
...
Alex
6 months ago
C could work, but it might slow down the teams too much.
upvoted 0 times
...
Lorriane
7 months ago
Totally agree, a shared Definition of Done is key!
upvoted 0 times
...
Hyman
7 months ago
B seems like the best option for consistent quality.
upvoted 0 times
...
Sylvie
7 months ago
I recall a similar question where dedicating a Sprint to integration was mentioned. It seems like a risky move, though, since it could delay other work.
upvoted 0 times
...
Lettie
7 months ago
I'm not entirely sure, but I feel like having the Integration Team work early on the integration might be the best approach. It could prevent last-minute issues.
upvoted 0 times
...
Albina
7 months ago
I think enforcing a Definition of Done that includes integration could really help. It’s something we practiced in our last mock review.
upvoted 0 times
...
Effie
8 months ago
I remember we talked about the importance of having a shared environment for integration. It seems like none of the options directly address that.
upvoted 0 times
...
Helaine
8 months ago
This is a good question. I think the Nexus Integration Team idea could be really helpful here. Getting them involved early on to integrate the work could make the Nexus Sprint Review much more effective.
upvoted 0 times
...
Lynette
8 months ago
Okay, I've got an idea. Reserving time for testing and integration at the end of the Sprint could help pull everything together. And enforcing a common Definition of Done across the Nexus seems like a smart move.
upvoted 0 times
...
Jacquelyne
8 months ago
Hmm, I'm a bit confused by this scenario. It sounds like the teams are working in silos, which is not ideal for creating a single Integrated Increment. I'll need to think this through carefully.
upvoted 0 times
...
Albert
8 months ago
This seems like a tricky one. I'm not entirely sure how to approach it, but I think focusing on integration and a shared Definition of Done could be key.
upvoted 0 times
...
Cristina
1 year ago
Wow, five Scrum Teams working on the same product? That's a lot of cooks in the kitchen. I hope they have a good recipe for success, or else it's going to be a hot mess. *winks*
upvoted 0 times
...
Minna
1 year ago
I don't know, this whole Nexus thing sounds like a recipe for chaos. Can't we just have one team build the whole thing and call it a day? *chuckles*
upvoted 0 times
...
Millie
1 year ago
A Sprint dedicated to integration? That's like trying to put out a fire by setting the building on fire. How about we just build integration into the regular process?
upvoted 0 times
Lashawnda
11 months ago
Enforcing a Definition of Done that includes integration across the Nexus seems like a better approach.
upvoted 0 times
...
Loren
11 months ago
I agree, we should integrate as we go along to avoid any last-minute chaos.
upvoted 0 times
...
Donte
11 months ago
It might slow things down initially, but in the long run, it will ensure a smoother integration process.
upvoted 0 times
...
Carissa
11 months ago
A Sprint dedicated to integration? That sounds counterproductive.
upvoted 0 times
...
Veronika
11 months ago
But wouldn't that slow down the process?
upvoted 0 times
...
Lawrence
12 months ago
Enforce a Definition of Done across the entire Nexus that includes integration.
upvoted 0 times
...
Beckie
12 months ago
A Sprint dedicated to integration? That's like trying to put out a fire by setting the building on fire.
upvoted 0 times
...
...
Gail
1 year ago
Option C seems like a good idea, but I'm not sure how the Nexus Integration Team would coordinate with the individual teams. Seems like it could create some bottlenecks.
upvoted 0 times
...
Edelmira
1 year ago
I think Option B makes the most sense. Having a shared Definition of Done that includes integration will ensure the teams are working towards a single Integrated Increment.
upvoted 0 times
Joye
11 months ago
Definitely, having a shared Definition of Done would help streamline the integration process.
upvoted 0 times
...
Olive
12 months ago
Option B sounds like a good idea. It would keep everyone on the same page.
upvoted 0 times
...
Rikki
1 year ago
Option B) Enforce a Definition of Done across the entire Nexus that includes integration.
upvoted 0 times
...
...
Flo
1 year ago
That's a good point, Laurel. Option C does sound like a good solution to ensure integration is done early in the process.
upvoted 0 times
...
Laurel
1 year ago
I disagree, I believe option C is more effective. Having the Nexus Integration Team integrate all the work as early as possible will help create a single Integrated Increment for inspection.
upvoted 0 times
...
Flo
1 year ago
I think option B is the best choice. Enforcing a Definition of Done across the entire Nexus that includes integration will ensure that all work is integrated properly.
upvoted 0 times
...

Save Cancel