Considering how and what to demo during Iteration Planning increases the effectiveness of System Demos, which are events that provide an integrated view of new features delivered by the Agile Release Train (ART) in each Iteration12. By thinking ahead of how and what to demo, the teams can:
•Align on the product vision and roadmap and ensure that the work items are aligned with the customer value and the PI objectives12.
•Define clear and testable acceptance criteria for each work item and plan how to verify them in the demo12.
•Identify and resolve any dependencies, risks, or impediments that may affect the demo12.
•Prepare the demo environment and the necessary tools and data to support the demo12.
•Practice the demo and rehearse the script and the roles of the presenters12.
Some additional information that might be helpful for you are:
•The other options (A, B, and C) are not actions that increase the effectiveness of System Demos, but rather actions that may reduce it.
•Spending a lot of time preparing for the demo may not be effective, as it may take away time and focus from the actual development and testing of the work items. Instead, the teams should aim for continuous integration and built-in quality practices that enable them to demo the work items as soon as they are done12.
•Limiting team attendance to minimize disruptions to the team may not be effective, as it may reduce the feedback and collaboration opportunities that the demo provides. Instead, the teams should invite and engage all the relevant stakeholders, such as Business Owners, executive sponsors, other Agile Teams, development management, and customers, to the demo12.
•Focusing on team-level metrics may not be effective, as it may not reflect the true value and progress of the integrated work across the ART. Instead, the teams should focus on system-level metrics, such as PI objectives, solution quality, and customer satisfaction, to evaluate the outcome and impact of the demo12.
