You are invited to help an Agile Release Train that has struggled through multiple PIs. They just finished the second Iteration in the current PI and have nothing to demonstrate at the System Demo…

Question

Options

• AHave every team demonstrate their team increment to the stakeholders separately in the team
• BFind a vendor that specializes in integrating system increments form multiple teams.
• CStop working on any new functionality and fully integrate and test the system; adjust scope based
• DRe-plan the current PI: De-scope to leave enough time to integrate what you've built during the IP
• ERe-architect the system so that there are no dependencies between the teams and integration is

• A
  5% (1)
• B
  5% (1)
• C
  48% (10)
• D
  14% (3)
• E
  29% (6)

Explanation

Stopping new feature work to fully integrate and test reflects SAFe's core "stop the line" principle - when an ART cannot demonstrate a working integrated system increment, it must treat integration as the highest-priority work item before adding more unintegrated functionality. A is wrong because separate team demos bypass the System Demo's entire purpose: showing a collectively integrated system increment to stakeholders. B is impractical mid-PI and outsources a fundamental team capability the ART must own internally. D is premature - re-planning the full PI at Iteration 2 is a drastic overreaction when the immediate fix is to halt new work and integrate now; re-planning is reserved for when the PI's objectives become unachievable. E is a valid long-term architectural goal but cannot be executed in the middle of a struggling PI and does nothing to resolve the current demo crisis.

Memory tip: Think "C = Cease and Converge" - when the ART can't show a working system, cease new features and converge all teams on integration before stakeholder confidence collapses entirely.

No community discussion yet for this question.