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 16 Discussion

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

Which statements are true regarding using Scrum for large-scale product delivery?

(choose the best two answers)

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


Contribute your Thoughts:

0/2000 characters
Precious
3 months ago
Really? I doubt that a refined backlog can eliminate all dependencies.
upvoted 0 times
...
Maryann
3 months ago
D is definitely true! A good backlog makes a huge difference.
upvoted 0 times
...
Lucia
3 months ago
C seems a bit extreme, but I see the point.
upvoted 0 times
...
Brock
4 months ago
Totally disagree with B. Teams can be flexible!
upvoted 0 times
...
Dominga
4 months ago
A is spot on! Focus is key.
upvoted 0 times
...
Fernanda
4 months ago
A well-structured Product Backlog is definitely important, and I recall it can help with dependencies, so D sounds right to me.
upvoted 0 times
...
Stephaine
4 months ago
I think I read somewhere that large-scale Scrum might need some adjustments, so C could be a valid point.
upvoted 0 times
...
Detra
4 months ago
I'm not entirely sure, but I feel like Scrum doesn't strictly require full-time commitment to one team, so B seems off to me.
upvoted 0 times
...
Felicia
5 months ago
I remember discussing how splitting a team member's time can lead to inefficiencies, so I think A might be true.
upvoted 0 times
...
Dierdre
5 months ago
Splitting team members across multiple Scrum teams - that's a tough one. I know the guidance is to avoid that, but I'm curious to learn more about the exceptions and when it might actually be productive. I'll need to think this through carefully.
upvoted 0 times
...
Micheline
5 months ago
Ah, I've seen this type of question before. The key is understanding how Scrum can be adapted to work for large-scale product delivery without compromising the core principles. I've got some ideas on how to approach this.
upvoted 0 times
...
Martha
5 months ago
Hmm, this is a tricky one. I'm not entirely sure about the best approach to managing dependencies between multiple Scrum teams. I'll need to review the Scrum guide and think through some examples.
upvoted 0 times
...
Jimmie
5 months ago
This question seems straightforward, but I want to make sure I understand the nuances of using Scrum at scale. I'll need to carefully consider the tradeoffs between team focus and flexibility.
upvoted 0 times
...
Desmond
10 months ago
I agree with Temeka and Derick. A and D are the best choices here. Although I do wonder if the person who came up with option C has ever actually used Scrum at scale...
upvoted 0 times
Corrie
8 months ago
Yeah, option C seems a bit off. It's all about effective teamwork and organization.
upvoted 0 times
...
Juan
9 months ago
I agree, focusing on a single team's Sprint Backlog and having a well-structured Product Backlog are key.
upvoted 0 times
...
Sena
9 months ago
I think A and D are the most accurate choices.
upvoted 0 times
...
...
Melinda
10 months ago
Haha, I can just imagine the person who wrote option B - 'Scrum is for single-tasking robots only!' Good thing that's not how it actually works.
upvoted 0 times
Delsie
8 months ago
Haha, I agree! Scrum is definitely not just for single-tasking robots.
upvoted 0 times
...
Bo
9 months ago
Yeah, it's important to have a well-structured Product Backlog to minimize dependencies between teams.
upvoted 0 times
...
Elmer
9 months ago
Option B is definitely not true, Scrum allows for flexibility in team member allocation.
upvoted 0 times
...
...
Lea
10 months ago
I'm not sure about C though. Do we really need to change the core Scrum framework for large-scale delivery?
upvoted 0 times
...
Derick
10 months ago
B is clearly wrong - Scrum is all about cross-functional teams, not requiring full-time dedication. C is also not correct - the core Scrum framework is designed to be adaptable for different scales.
upvoted 0 times
Sabra
9 months ago
D) A well-structured and refined Product Backlog can minimize and often eliminate dependencies between multiple Scrum Teams working together on a product during a Sprint.
upvoted 0 times
...
Nadine
10 months ago
A) Splitting a team member's time between multiple Scrum Teams is often less productive than focusing that team member on a single team's Sprint Backlog.
upvoted 0 times
...
...
Temeka
11 months ago
A and D seem like the most logical answers here. Splitting team members across multiple teams can definitely reduce productivity, and a well-organized Product Backlog can help manage dependencies between teams.
upvoted 0 times
Marleen
9 months ago
Scrum doesn't require all team members to work full time on one team, so B is not correct.
upvoted 0 times
...
Nichelle
10 months ago
A well-structured Product Backlog can really help minimize dependencies between teams.
upvoted 0 times
...
Domingo
10 months ago
Having team members focus on one team's Sprint Backlog is definitely more productive.
upvoted 0 times
...
Quinn
10 months ago
I agree, A and D make the most sense for large-scale product delivery.
upvoted 0 times
...
...
Paz
11 months ago
I agree with Detra. Having a well-structured Product Backlog can definitely help with large-scale Scrum.
upvoted 0 times
...
Detra
11 months ago
I think A and D are true.
upvoted 0 times
...

Save Cancel