The Solution Demo is a key event in the Scaled Agile Framework (SAFe) at the Large Solution Level. It showcases the integrated outcomes of multiple Agile Release Trains (ARTs) and external suppliers working together on a solution. Its purpose is to provide an end-to-end view of progress, gather stakeholder feedback, and guide further development based on real results.
Origin and Purpose
The Solution Demo builds on the concept of the System Demo, but scales it to a higher level. While the System Demo shows the integrated outcomes of a single ART per iteration, the Solution Demo integrates the contributions of multiple ARTs and partners. It serves to:
- make the business and customer value of a complete solution transparent,
- keep dependencies and interfaces visible,
- identify risks early and enable corrective action,
- build trust between business, customers, and suppliers.
Core Elements
- Participants: Solution Train Engineers (STEs), Solution Management, Solution Architects, RTEs of contributing ARTs, Business Owners, customers, and stakeholders.
- Content: Integration and demonstration of capabilities, solution epics, and architectural outcomes.
- Frequency: At the end of every iteration, plus a comprehensive PI Solution Demo at the end of each Program Increment (typically during the IP Iteration).
- Focus: Demonstrating the integrated Solution Increment – a tested, usable end-to-end system.
Application and Best Practices
- Preparation: Continuous integration at the solution level is essential.
- Stakeholder involvement: Customers, Business Owners, and suppliers should be actively engaged.
- Storytelling: Solution Management ensures the demo is presented in terms of business value and solution vision.
- Alignment with Solution Intent: Results are checked against the documented Solution Intent and non-functional requirements.
- Integration with ARTs: System Demos provide input; the Solution Demo consolidates them into a holistic view.
Practice Examples (patterns from practice)
Automotive: Several ARTs collaborate on driver assistance features; the Solution Demo demonstrates hardware-software integration in real scenarios.
Telecommunications: A Solution Train integrates network upgrades, hardware modules, and external vendors.
Aerospace/Defense: Solution Demos validate integration of avionics, communication systems, and ground stations for end-to-end operability.
Distinction and Complement to System Demo
- System Demo: ART-level, per iteration, showing incremental ART progress.
- Solution Demo: Solution-level, per iteration, integrating outcomes of multiple ARTs and suppliers.
- Complement: System Demos are the building blocks; the Solution Demo provides the end-to-end picture.
Criticism and Limitations
- Complexity: Execution is demanding; quality depends on strong integration practices.
- Superficiality risk: If only partial elements are shown, end-to-end value is lost.
- Stakeholder absence: Lack of business or customer involvement undermines the event.
- Technical challenges: Diverse systems, suppliers, and compliance add complexity.
- Business Value: Final evaluation of PI Objectives happens in the Inspect & Adapt Workshop, not during the Solution Demo.
Embedding and Combination
The Solution Demo is linked with:
- System Demos at ART level
- PI Planning (delivery against PI Objectives)
- Solution Intent and Solution Backlog
- Inspect & Adapt Workshop
CALADE Perspective
In practice, Solution Demos are often mistaken for reporting events. CALADE helps organizations turn them into true feedback and alignment opportunities. Our experts support Solution Train setup, coach roles like STE and Solution Architect, and ensure demos reflect both business value and technical feasibility.
Cross References Glossar items
- System Demo
- Solution Train
- Solution Intent
- Agile Release Train (ART)
- Inspect & Adapt Workshop
← back to list