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:

• Team Agility Coach, who is the facilitator of the demonstration
• Whole Agile Team
• Product Owner, who is the primary sponsor of the meeting

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

Inputs to this practice include:

• The stories of the current iteration.
• The Team Agility Coach has prepared to facilitate the meeting

Approach

1. Team Agility Coach works with Product Owner to prepare the introduction for the demo:
   • The goals of the iteration
   • The commitment list and the stretch objectives
2. Team Agility Coach works with the team to identify the following:
   • Stories in the iteration commitment list that were finished
   • Stories in the iteration commitment list that are not complete
   • Stories in the stretch objectives that were finished
   • Who will demo and when
3. Sequence and script the demo
   1. Prepare demo data if necessary
   2. Team Agility Coach creates final demo agenda and handouts if necessary
   3. Team Agility Coach sends out final demo agenda to stake holders (attach to the meeting invitation)

Tools and techniques

These items are used to plan the demonstration

• Demo script
• Demo agenda
• Demo participants

Outputs

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

Outcomes

Here are some of the compelling reasons for this practice:

• Ensure demonstrations that maintain good relationship with stakeholders.
• Show value added.
• Gain feedback.