What does a team demo show?

• A. System architecture and design decisions
• B. Work done in iteration
• C. Release plan for the next increment
• D. Inter-team integration status

Answer: (B)

The team demo shows the actual work completed during the iteration—the working product increment the team built and tested, demonstrated to stakeholders. It focuses on finished user stories, acceptance criteria met, and the value delivered in that sprint, allowing feedback to guide the next steps. It isn’t about architectural decisions, which happen in separate design activities; it isn’t about planning the release for the next increment, which comes from PI planning; and it isn’t the cross-team integration status, which is covered in system-level demos. So the best fit is the work done in the iteration.