What increases the effectiveness of System Demos?

To ensure a System Demo is effective, teams on the Agile Release Train (ART) must plan for it. By considering what will be demonstrated and how during Iteration Planning, teams can ensure that their work is not only completed but also integrated and ready to be shown as part of a cohesive solution increment. This proactive approach prevents last-minute integration issues and aligns the team's efforts towards a shared, demonstrable goal for the iteration. It shifts the focus from completing individual stories to delivering an integrated piece of value that can be evaluated by stakeholders, which is the primary purpose of the System Demo.

A. Spend a lot of time preparing for the demo: This is a SAFe anti-pattern. Excessive preparation can lead to a scripted presentation rather than a demo of the actual, working system, hiding real issues and reducing transparency.
B. Limit team attendance to minimize disruptions to the team: This is a SAFe anti-pattern. The System Demo is a crucial feedback event for the entire ART; limiting attendance prevents team members from hearing direct feedback and celebrating collective progress.
C. Focus on team-level Metrics: The purpose of the System Demo is to demonstrate the working, integrated solution to get feedback from stakeholders, not to review performance metrics.

1. Scaled Agile, Inc. (2023). System Demo. Scaled Agile Framework. Retrieved from https://www.scaledagileframework.com/system-demo/.

Supporting Evidence: The article lists "A lot of time is spent preparing for the demo" and "The demo is not attended by the key stakeholders or the teams" as common anti-patterns, directly invalidating options A and B. The event's focus is described as demonstrating the "fully integrated work," which supports the need for planning (Option D).

2. Scaled Agile, Inc. (2023). Iteration Planning. Scaled Agile Framework. Retrieved from https://www.scaledagileframework.com/iteration-planning/.

Supporting Evidence: The article states that during Iteration Planning, teams determine "how much of the team’s backlog they can commit to delivering." This commitment includes ensuring the work is demonstrable in the System Demo, thus linking the planning event directly to the effectiveness of the demo.

3. Scaled Agile, Inc. (2023). SAFe Product Owner/Product Manager Courseware (Version 6.0).

Supporting Evidence: The course materials emphasize that the System Demo is a "forcing function" for integration. To meet this function effectively, teams must plan the integration and demonstration work as part of their Iteration Plan. This directly supports the idea that considering the demo during planning increases its effectiveness.