A. Find a vendor that specializes in integrating system increments from multiple teams
B. Stop working on any new functionality and fully integrate and test the system; adjust scope based on what is learned
C. Have every team demonstrate their team increment to the stakeholders separately in the team branch
D. Re-architect the system so that there are no dependencies between the teams; integration is not required at this time
The correct answer is
B. stop working on any new functionality and fully integrate and test the system; adjust scope based on what is learned.
The most effective action in this scenario is to stop working on any new functionality and fully integrate and test the system; adjust scope based on what is learned.
Why this is correct
- Focus on Integration and Testing: When an Agile Release Train (ART) has struggled through multiple Program Increments (PIs) and has nothing to show at the System Demo, it indicates a significant integration and testing challenge. Pausing new functionality development to concentrate on integrating and testing the current work can help identify and resolve underlying issues. This approach allows the ART to focus on delivering a working increment, which is a core principle of Agile methodologies.
- Scope Adjustment: Based on the outcomes of the integration and testing effort, the ART can better understand what is realistically achievable within the current PI. This understanding enables informed decisions about scope adjustments, ensuring that the ART focuses on delivering the most valuable and feasible outcomes.
Why the others are not as correct
- Find a vendor that specializes in integrating system increments from multiple teams: While outsourcing integration work can bring in expertise, it does not address the underlying issues within the ART that led to the current situation. Moreover, it could introduce delays and dependencies on external parties, further complicating the process.
- Have every team demonstrate their team increment to the stakeholders separately in the team branch: Demonstrating team increments separately does not address the integration challenge and might give stakeholders an incomplete or misleading picture of the overall system’s progress. The System Demo is intended to show integrated, potentially shippable increments, emphasizing the importance of end-to-end functionality.
- Re-architect the system so that there are no dependencies between the teams; integration is not required at this time: While reducing dependencies can be a long-term goal, re-architecting the system during a PI is impractical and could lead to significant disruption. Furthermore, complete elimination of dependencies is often unrealistic in complex systems, and integration will still be necessary to deliver a cohesive product.
Other SAFe Scrum Master Question – What is one way a Scrum Master can gain the confidence of a stakeholder?