At the end of each iteration, the team comes together and shows off their work. They demonstrate what they’ve completed and show it to other teams, their ProductOwner, and sometimes end users. This is a chance to talk about what they’ve done and get real feedback on their work.
The iteration demo can be a real morale booster. It’s a chance to come together not to work, but to celebrate! Look at what we’ve done. See how it works. What did you do?
Without a meeting to review the work, the reviews either don’t happen, or they become messy ad hoc events where some work is seen and appreciated and other work is missed. Work slips under the radar and either isn’t used (as others don’t realize it’s be done) or isn’t appreciated.
All people need their work to be meaningful and appreciated. The demo provides an opportunity to show others your work and see it appreciated.
✓ Critical ❑ Helpful ❑ Experimental
The ScrumMaster schedules 30 minutes to show off the last iteration’s work. They walk around and talk to a few of the sales team, several members of customer support, and a few executives. They tell them a bit about what will be in the demo and encourage them to attend. Hint at food bribes that might be provided.
On the day of demo, everyone gathers around the projector in the middle of the work area. The TeamLead kicks off the meeting with an overview of what the team accomplished. Perhaps they highlight what percentage of the accepted work was completed. Then they hand the meeting over to the first team member. They bring up the story on the big screen, showing both the story, the completion criteria, and any notes. Then they switch over to the live software, walking the team through the code for the first time. A few questions about work flow and perhaps usability come from customer service. Sales wants to know which release this will be in.
This continues until each story has been reviewed and the work shown. The meeting is wrapped up with a round of applause and everyone grabs one more cookie before returning to their work. A few people linger to discuss how this or that new feature might used by a certain customer persona.
Try attending other teams demos and see how they’re presenting their work. Try to make the demo a fun event… provide donuts or other treats.
If another team is consuming your work (or you theirs), make a point of attending each other’s demos and see what’s coming down the pipeline.
Use key demos as a communication tool. Reach out to users and invite them to attend, in person or virtually, for sneak peak into what might be in the next version of the product