Working code is the best measure of progress, and the demonstration of working code maintains the buy-in and support of stakeholders. It also provides a means of feedback on whether or not the development is shaping up the way the stakeholders expected. Demos can generate new features and alter the actions of existing features. By planning well for the demo, it is possible to make sure the most valuable work is shown to be completed and acceptable, and can present other work that may need clarification or is important in ways the stakeholders may not immediately see (e.g. infrastructure).
Who does this practice
Here are the roles involved in this practice:
Usually, the TAM is the one to arrange the logistics of the meeting. The Team Agility Coach works with the Product Owner to send out communications and invitations. The TAM is probably the one to document the guidance and insights gained in the meeting on behalf of the team.
What to do
Inputs to this practice include:
Tools and techniques
These items are used to plan the demonstration
The primary output is a defined demonstration plan.
When to do this practice
Iteration demonstration planning is done as needed prior to demonstration
Where to do this practice
Iteration demonstration planning is always done in the team’s work area
Here are some of the compelling reasons for this practice: