New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Scrum SPS Exam - Topic 2 Question 4 Discussion

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

The purpose of a Nexus Sprint Retrospective is to:

(choose the best two answers)

Show Suggested Answer Hide Answer
Suggested Answer: A, C

The Nexus Sprint Retrospective is an event that occurs at the end of the Sprint where the Nexus, which is a group of approximately three to nine Scrum Teams working on the same product, plans ways to increase quality and effectiveness across the whole Nexus 11. The purpose of the Nexus Sprint Retrospective is to inspect and adapt the Nexus framework, the integrated work, the processes, the tools, and the interactions among the Scrum Teams 11. Therefore, statement C is correct.

The Nexus Sprint Retrospective follows a three-step process: first, representatives from each Scrum Team identify issues that affect multiple teams; second, each Scrum Team conducts its own Sprint Retrospective; and third, representatives from each team meet again to discuss any actions needed based on the shared challenges 112233. The Nexus Sprint Retrospective enables bottom-up intelligence to improve how the Scrum Teams in a Nexus are working together, as it allows the teams to share their insights, learn from each other, and collaborate on solutions 44. Therefore, statement A is also correct.

Statement B is incorrect because the Nexus Sprint Retrospective is not a forum for management to see how the Nexus is performing, but rather a time for the Nexus to self-organize and self-improve 1144. Statement D is incorrect because the Nexus Sprint Retrospective is not a single meeting to inspect and adapt how all Scrum Teams work together, but rather a combination of three meetings that involve both individual and collective reflection and action 112233.


Contribute your Thoughts:

0/2000 characters
Dexter
3 months ago
I thought it was just for team reflection, not management stuff.
upvoted 0 times
...
Genevieve
3 months ago
Not sure if D is really the best choice.
upvoted 0 times
...
Judy
3 months ago
Wait, isn't it also for management?
upvoted 0 times
...
Celeste
4 months ago
Definitely A and C!
upvoted 0 times
...
Dortha
4 months ago
It's all about improving teamwork!
upvoted 0 times
...
Thora
4 months ago
I practiced a similar question, and I think A and C make the most sense together for how teams can improve.
upvoted 0 times
...
Edelmira
4 months ago
I feel like B is not really the focus of the retrospective, but I could see how some might think it’s about management.
upvoted 0 times
...
Quiana
4 months ago
I'm not entirely sure, but I remember something about inspection and adaptation being key, so maybe C is one of the answers?
upvoted 0 times
...
Vernice
5 months ago
I think the Nexus Sprint Retrospective is mainly about improving collaboration, so A and D might be the right choices.
upvoted 0 times
...
Lashaunda
5 months ago
Good point, Vilma. I think those two answers capture the essence of the Nexus Sprint Retrospective - enabling bottom-up improvement and allowing for inspection and adaptation at both the team and Nexus level.
upvoted 0 times
...
Mari
5 months ago
Okay, let's think this through. The Nexus is about multiple Scrum Teams working together, so the retrospective must be about improving that collaboration.
upvoted 0 times
...
Pete
5 months ago
This question seems straightforward, but I want to make sure I understand the purpose of the Nexus Sprint Retrospective before answering.
upvoted 0 times
...
Vilma
5 months ago
I'm leaning towards options A and C, as they both mention inspecting and adapting the Scrum Teams and the Nexus as a whole.
upvoted 0 times
...
Adolph
5 months ago
This seems like a straightforward question about ensuring redundancy for a SIP trunk. I think the key is to look for options that would automatically failover to another device if one fails.
upvoted 0 times
...
Kara
5 months ago
Okay, I think I've got it. The user is clicking a button to move to the next screen, so OnSelect is probably the best event to handle here.
upvoted 0 times
...

Save Cancel