System Demo in SAFe: An Essential Overview

What Is System Demo in SAFe? Is It a Multi-Team Review? This article delves into this critical and essential event in SAFe.

What is System Demo?

The System Demo is a vital event within SAFe, aimed at presenting all the new features integrated into the increment achieved during the latest iteration of Agile Release Trains (ART). Its objective is to gather valuable feedback from stakeholders with the purpose of enhancing products and guiding future developments. During this event, all achievements are showcased, serving as an objective measure of progress during a program increment (PI).

These feedback sessions should lead to considerations such as:

• Are we on the right track, or do we need to change course?
• What improvements can be made to the entire proposed system?

This event requires upfront work to ensure its smooth execution. It is crucial that it unfolds efficiently, focusing on the essentials. Effective management of this event will help prevent future absences. If stakeholders feel they are losing time, they might be less inclined to attend regularly.

Who Participates in this Event?

The System Demo in SAFe involves:

• All stakeholders in the ART
• Product Owners and Product Managers of the ART
• One or more members of the System Team
• The System Architect/Engineering, operations, and a few developers

It’s important to note that in SAFe, stakeholders are considered to include:

• Business owners
• Sponsors
• Other Agile teams (potential clients)
• Management (related to the business)
• Clients and/or their representatives

When Should This Event Be Conducted?

Ideally, the System Demo should be held on the day following the closure of the sprint. A significant gap between the end of a different iteration and this event could result in delayed feedback processing. This event should be conducted at the end of each iteration.

Generally, allocate between 1 to 2 hours for this event, with the exact time frame depending on the size of your ART. However, it is recommended to aim for a one-hour duration.

Here is the agenda proposed by SAFe:

1. Review the business context and PI objectives (between 5 and 10 minutes).
2. Briefly describe each new feature before the demo (5 minutes).
3. Perform the demo of each new feature with an end-to-end scenario (between 20 and 30 minutes).
4. Identify current risks and obstacles.
5. Conduct discussions with the aim of obtaining feedback.
6. Summarize progress, feedback, and action items.

As a reminder, this event is part of the Inspect And Adapt (I&A) process, which we will cover on this blog soon.

Does the System Demo Replace Sprint Reviews?

No, the iteration review (SAFe’s term for sprint review) is conducted within each team at the end of an iteration and unfolds exactly like a standard sprint review. The System Demo is the presentation of the system as a whole, which can yield very different feedback. The sprint review within each team is quite isolated from the work accomplished by the team.

This is why the System Demo takes place after the sprint closes. Scrum teams are focused on their sprint closing ceremonies, requiring the presence of all team members.