How is a team demo defined in the described SAFe context?

• A. A meeting to discuss business goals
• B. Traditional scrum prescribed ceremony every two weeks
• C. A backlog refinement session
• D. A stakeholder review

Answer: (B)

In SAFe, a Team Demo is the regular, end-of-iteration demonstration where the team shows the latest working increment to stakeholders. This is the moment to reveal the actual, integrated software the team built during the iteration, ensure it meets the acceptance criteria, and gather feedback from product owners and other stakeholders. Because iterations are typically two weeks long, the Team Demo naturally occurs on that cadence, making it a standing, time-boxed ceremony that aligns the team’s progress with shared expectations across the ART.

This emphasis on showing functioning software at the iteration boundary distinguishes the Team Demo from backlog refinement (which is about grooming work for future sprints) and from a general stakeholder review focused on goals or roadmaps. It also differs from a standalone stakeholder review in scope, since the Team Demo is specifically about the team’s own increment and its readiness, often in a format that invites direct feedback on what was built.