GuideRolesEventsWorkflow

SAFe Events

System Demo

The System Demo occurs every iteration and demonstrates the integrated, working increment from all teams on the ART. It provides stakeholders with an objective measure of progress and generates feedback that can influence backlog priorities.

Integrated increment review · Timebox: 1–2 hours per iteration

Overview

The System Demo occurs every iteration and demonstrates the integrated, working increment from all teams on the ART. It provides stakeholders with an objective measure of progress and generates feedback that can influence backlog priorities.

Event Ownership

Owned / Facilitated By
RTE (orchestrator) / Product Management (content framing)
RTE coordinates the demo logistics, agenda, and ensures all teams contribute their integrated work
Product Management frames the demo around PI Objectives and feature progress
RTE ensures the demo environment is set up and the integrated increment actually works end-to-end
Product Management captures stakeholder feedback and translates it into backlog actions

Who Should Be Present

ART Teams (representatives)
Demo their portion of the integrated increment. Show working software, not slides
Product Management
Frames progress against PI Objectives. Gathers and synthesizes stakeholder feedback
Business Owners / Stakeholders
Provide feedback on the integrated increment. Surface new opportunities or concerns
RTE
Facilitates the session, keeps the timebox, ensures all teams are represented

Preparation Checklist

01Teams: Integrate their work into the shared demo environment before the demo
02RTE: Prepare the agenda, confirm team demo slots, test the demo environment
03Product Management: Map demo items to PI Objectives for context
04Teams: Rehearse demos briefly — keep them concise and focused on value delivered

Facilitation Techniques

Click any technique to expand details and learn when to apply it.

Show Working Software Only

No slides, no screenshots — show the actual integrated product running in a realistic environment. If it doesn’t work end-to-end, that’s critical information for the ART.

Click to expand

PI Objective Progress Framing

Open by showing progress against PI Objectives (red/yellow/green or percentage). This grounds the demo in business outcomes, not just feature lists.

Click to expand

Structured Feedback Capture

Use a feedback grid (Likes / Wishes / Questions / Concerns) to capture stakeholder input systematically. This prevents feedback from being lost in open discussion.

Click to expand

Tips & Tricks

01
Integration Focus
System Demo is about integration, not individual team demos stitched together
02
Show Failures Too
If the increment doesn’t integrate cleanly, show that too — hiding integration failures delays risk resolution
03
Respect Time
Keep it to 1–2 hours maximum. Respect stakeholder time
04
Record Demos
Record the demo for stakeholders who can’t attend live

Anti-Patterns to Avoid

Feedback-to-Backlog Pipeline: Product Management should process System Demo feedback into backlog items within 48 hours. Close the loop by telling stakeholders how their feedback was incorporated.
Integration Health Tracking: Track integration success/failure across System Demos over time. Declining integration quality is an early warning signal for architectural or process issues.

Success Takeaways by Role

What each participant should walk away with when this event is run well.

Teams

Validation that their work integrates with other teams; stakeholder feedback on what matters; pride in demonstrated progress

Product Management

Objective view of feature progress; stakeholder feedback to inform backlog reordering; data for PI predictability

Stakeholders

Confidence in ART progress; opportunity to influence direction; transparency into delivery reality

RTE

Pulse on integration health; data on ART delivery cadence; identified integration risks

Cross-Framework Definition
See System Demo in the glossary
→