System Demo

Base milestones on objective evaluation of working systems.

—Lean-Agile Principle #5

Definition: The System Demo provides stakeholders an integrated view of new features for the most recent iteration delivered by all the teams on the ART. Each demo provides an objective measure of progress and the opportunity to give feedback.

Summary

The System Demo is a key event for Agile Release Trains (ART), that showcases the integration of new features developed by the Agile Teams. The System Demo provides an objective measure of progress toward PI Objectives and fosters actionable feedback. It contrasts with team-specific Iteration Reviews by involving all ART members and stakeholders. The System Demo is led by the RTE.

What is the System Demo?

The System Demo provides stakeholders with an integrated view of new features delivered by teams on the Agile Release Train (ART) in the most recent iteration. Each System Demo provides an objective measure of progress toward the goals of the PI with the opportunity to give feedback.

The System Demo plays a crucial role in the way an Agile Release Train operates and is attended by everyone on the ART. This contrasts with the specific Iteration Reviews for each team, which focus on the specific deliverables of a single Agile Team within an iteration. Generally, only the Agile Team and any stakeholders involved in that team’s work attend Iteration Reviews.

During the System Demo, the Agile Teams on the ART showcase the features they've been working on, demonstrating them from a production-like environment. This provides an objective measure of progress in place of checking off tasks or generating status reports. Regularly demonstrating a working system also helps identify defects or design flaws early on, making them cheaper and easier to fix. It also generates new ideas to improve over time.

In addition to the teams on the ART, the System Demo is attended by business owners, key stakeholders, and often customers. In this way, it creates an opportunity to gain a shared understanding of the current state of the products and solutions on a regular cadence. System Demos create a safe space for early identification of issues and opportunities. It is a dedicated time for stakeholders to clearly articulate the potential benefits of features as they are developed. The feedback provided during the System Demo informs future iteration work of the Agile Teams.

System Demos also benefit the Agile Teams on an ART. Demonstrating the integrated system helps teams understand and optimize how their work contributes to the overall solution. Each Agile Team gets visibility into the work of the other teams, fostering collaboration and knowledge sharing. Agile Teams get immediate feedback from stakeholders during the demo, enabling quick changes and focusing on what is important. This reduces wasted effort.

Figure 1. System Demos occur on a cadence at the end of each Iteration

For larger Solutions involving multiple ARTs, this System Demo becomes a part of the broader Solution Demo. Solution Demos have participation from all involved ARTs.

Read more about how multiple ARTs demo their connected solution:

Solution Demo

What is the purpose of the System Demo?

In this article

What is the System Demo?
What is the purpose, intent, and outcome of the System Demo?
What are the inputs and outputs of the System Demo?
How often does the System Demo take place?
Who attends the System Demo?
How to facilitate the System Demo?
How do we apply what we learned from the System Demo?

Key Takeaways

  • The System Demo is an event where the Agile Teams on an ART showcase new features from the most recent iteration to stakeholders.
  • The System Demo includes the active involvement of all ART members and stakeholders of the ART.
  • The System Demo enables the attendees to provide fast feedback, allowing teams to make necessary adjustments to the solutions they deliver.

Last Update: 18 March 2026