Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Scrum Exam SPS 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:

Desmond
2 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
Yeah, option C seems a bit off. It's all about effective teamwork and organization.
upvoted 0 times
...
Juan
9 days ago
I agree, focusing on a single team's Sprint Backlog and having a well-structured Product Backlog are key.
upvoted 0 times
...
Sena
10 days ago
I think A and D are the most accurate choices.
upvoted 0 times
...
...
Melinda
2 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
6 days ago
Haha, I agree! Scrum is definitely not just for single-tasking robots.
upvoted 0 times
...
Bo
9 days ago
Yeah, it's important to have a well-structured Product Backlog to minimize dependencies between teams.
upvoted 0 times
...
Elmer
1 months ago
Option B is definitely not true, Scrum allows for flexibility in team member allocation.
upvoted 0 times
...
...
Lea
2 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
2 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
1 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
2 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
2 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
1 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
1 months ago
A well-structured Product Backlog can really help minimize dependencies between teams.
upvoted 0 times
...
Domingo
1 months ago
Having team members focus on one team's Sprint Backlog is definitely more productive.
upvoted 0 times
...
Quinn
2 months ago
I agree, A and D make the most sense for large-scale product delivery.
upvoted 0 times
...
...
Paz
2 months ago
I agree with Detra. Having a well-structured Product Backlog can definitely help with large-scale Scrum.
upvoted 0 times
...
Detra
3 months ago
I think A and D are true.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77