MENU
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?
Suggested Answer: A
Get Premium SAFe-SASM Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
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.
30 comments · newest first
DO
Dortha
10 months ago
Re-architecting (D) sounds risky, dependencies are part of Agile.
EL
Elin
10 months ago
I disagree, separate demos (B) could show progress better.
AN
Anjelica
10 months ago
Option A makes the most sense. Integration is key!
LA
Lashaunda
11 months ago
Vendor help (C) could be a good idea if teams are really stuck.
BE
Bette
11 months ago
Surprised they haven't integrated yet! How did it get this far?
YE
Yen
11 months ago
Re-architecting the system sounds drastic. I feel like we learned that dependencies are common, and just ignoring them might lead to bigger issues later on.
JE
Jerry
11 months ago
I vaguely recall a case study where they brought in a vendor for integration. It seemed to work, but I wonder if that’s a sustainable solution for this ART.
DO
Dorethea
11 months ago
I think having each team demonstrate their increments separately could help identify issues, but it might not address the bigger integration problem we talked about in class.
AU
Augustine
12 months ago
I remember we discussed the importance of integration during our Agile training. Stopping new functionality to focus on integration seems like a solid approach, but I'm not sure if it's the best option right now.
LE
Letha
12 months ago
Finding a vendor to help with integration, as in option C, could be a good short-term solution. But I'd want to make sure we're also building up our own integration capabilities.
QU
Quiana
12 months ago
I like the idea of having the teams demo their increments separately in option B. That could help identify where the integration problems are.
RI
Rikki
1 year ago
I'm a bit confused by the question. Wouldn't option D just be kicking the can down the road? Seems like we need to address the integration challenges head-on.
BA
Barrett
1 year ago
Option A sounds like the safest bet to me. Focusing on integration and testing is key when you have nothing to show at the demo.
BE
Belen
1 year ago
This seems like a tricky situation. I'd want to really understand the root causes of the integration issues before deciding on a course of action.
TE
Tess
1 year ago
A vendor to handle integration? What is this, a tech support hotline? C'mon, we're Agilists, we can do this ourselves. Option A all the way!
LO
Lorita
9 months ago
Yeah, let's show what we've got and improve from there!
PA
Paulene
9 months ago
Relying on a vendor? No thanks! We can handle this ourselves.
LA
Lashandra
9 months ago
Totally agree! Let's get everything tested and adjust as needed.
DY
Dyan
10 months ago
Option A is the way to go! We need to focus on integration.
RO
Rozella
1 year ago
D? Rearch the system? Sounds like a lot of work. I'd rather go with the tried and true 'stop and integrate' approach. Keeps it simple, you know?
EL
Elke
1 year ago
B) Have every team demonstrate their team increment to the stakeholders separately in the team branch
GR
Grover
1 year ago
D? Rearch the system? Sounds like a lot of work. I'd rather go with the tried and true 'stop and integrate' approach. Keeps it simple, you know?
MI
Mira
1 year ago
A) Stop working on any new functionality and fully integrate and test the system; adjust scope based on what is learned
MI
Michel
1 year ago
I think we should stop working on new functionality and fully integrate and test the system.
DE
Derick
1 year ago
Option B? Really? Showing off individual team increments? That's like a chef presenting individual ingredients instead of the whole meal. Nah, not gonna fly.
LI
Lili
1 year ago
A) Stop working on any new functionality and fully integrate and test the system; adjust scope based on what is learned
KA
Kasandra
1 year ago
Option A is the way to go. No more new features, just focus on integration and testing. Gotta get that system working, baby!
CH
Chauncey
1 year ago
Yes, stopping new functionality and focusing on integration is crucial for the success of the Agile Release Train.
AL
Alyce
1 year ago
I agree, we need to make sure everything is integrated properly before moving forward.
LE
Leanora
1 year ago
Option A is the way to go. No more new features, just focus on integration and testing. Gotta get that system working, baby!