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

- Free Preparation Discussions

Scaled Agile Exam SAFe-SASM Topic 6 Question 23 Discussion

Actual exam question for Scaled Agile's SAFe-SASM exam
Question #: 23
Topic #: 6
[All SAFe-SASM Questions]

A Scrum Master is asked to help an Agile Release Train that has struggled through multiple Pls. They just finished the second Iteration in the current PI and have nothing to show at the System Demo. The ART stakeholders are concerned. What should be done?

Show Suggested Answer Hide Answer
Suggested Answer: A

Problem Statement: The ART has nothing to show at the System Demo, indicating potential issues with integration, quality, or coordination among teams.

Recommended Action: Stopping new development work to focus on integrating and testing the system allows the team to identify and resolve integration issues, ensuring that the system is in a stable state.

Scope Adjustment: Based on what is learned during integration and testing, the scope can be adjusted to focus on delivering a coherent and functional system increment.

SAFe Scrum Master Reference:

SAFe emphasizes the importance of a stable, integrated system increment to demonstrate progress and ensure quality. Addressing integration issues promptly is crucial for maintaining stakeholder confidence and delivering value.


Contribute your Thoughts:

Sharika
4 days ago
A) This is the only sensible option. Stop the bleeding, then figure out how to stitch it all back together. Though I wonder if the Scrum Master has a magic wand to make this all go away.
upvoted 0 times
...
Naomi
8 days ago
Having each team demonstrate their increment separately might help identify issues quicker.
upvoted 0 times
...
Carlee
8 days ago
D) Re-architect the system to avoid dependencies? That's like trying to build a house without any walls - it's not going to work. Integration is kind of important, you know?
upvoted 0 times
Stanford
3 days ago
A) Stop working on any new functionality and fully integrate and test the system; adjust scope based on what is learned
upvoted 0 times
...
...
Richelle
14 days ago
I believe re-architecting the system to remove dependencies between teams could also be a good solution.
upvoted 0 times
...
Sarina
19 days ago
C) Ah, the old 'hire a vendor to fix our problems' approach. Sounds like a quick way to burn through some cash without actually solving the underlying issues.
upvoted 0 times
...
Tish
25 days ago
B) Showing the team increments separately? That's like trying to hide the fact that the whole system is a mess. Stakeholders want to see the big picture, not a bunch of disconnected pieces.
upvoted 0 times
Linwood
2 days ago
A) Find a vendor that specializes in integrating system increments from multiple teams
upvoted 0 times
...
Ruthann
16 days ago
B) Showing the team increments separately? That's like trying to hide the fact that the whole system is a mess. Stakeholders want to see the big picture, not a bunch of disconnected pieces.
upvoted 0 times
...
Youlanda
17 days ago
A) Stop working on any new functionality and fully integrate and test the system; adjust scope based on what is learned
upvoted 0 times
...
...
Johnetta
1 months ago
A) Definitely the way to go. Focusing on integration and testing is crucial when the system is struggling. Scope can be adjusted later, but a stable and functional system is the priority.
upvoted 0 times
Clay
4 days ago
A) Definitely the way to go. Focusing on integration and testing is crucial when the system is struggling. Scope can be adjusted later, but a stable and functional system is the priority.
upvoted 0 times
...
...
Raul
1 months ago
I agree with Rosendo, adjusting scope based on what we learn is crucial at this point.
upvoted 0 times
...
Rosendo
2 months ago
I think we should stop working on new functionality and fully integrate and test the system.
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