One of the major tenets of Agile is the Product Demo. As we all know, agile encourages us to demo at the end of our sprints. This is done for several reasons. Not only does this keep us accountable to our customers, but it helps us to focus on forward thinking. At many companies, it is highly likely that actual external customers will attend these demos, so it is of the utmost importance that we always put forth our very best.
In our pursuit of excellence, here are a few things to keep in mind when prepping for a demo. I compiled this list with a few of my collegues, so I can’t take all the credit. Here goes.
What to include in every demo deck
Frame the demo with PowerPoint and then broadcast it via a webinar. Just about everyone has access to a phone and the internet, so use them. You can bring in your external customers this way, while still catering to your internal customers. That being said, always be cognizant of WHEN you have customers attending your demos. Make sure you inform everyone just who is on the phone so that you’re on your best behavior.
That’s great, you say. But what should I include?
This is basically the goal of the project, our elevator pitch, our reason for being. This needs to be repeated at every demo because our audience fluctuates.
This is the reason the world needs our project. Again, the overall customer value of the project needs to be repeated every demo. However, sprint specific value can be spelled out in the goals we set for ourselves. We should be able to answer questions like “What have we given to customers thus far”, “What are we delivering next”, and “What are our plans for future customer value?” Additionally, customer value should be integral to every part of our demo. When we show something live, we need introduce it in such a way that spells out WHY it is valuable to our internal and/or external customers.
I think this is optional for demos that include external customers. You don’t want to get TOO in the weeds because you want to keep your external customers engaged.
These goals ultimately align with the overall project goal, but think of them as bite-sized pieces that we can deliver iteratively. Sprint goals usually change every two weeks and are specific to the work to which we’ve committed. These goals should manifest with customer value in mind. Remember: customers are both internal and external.
This lets everyone attending the demo know the health of our project. It should answer questions describing how we’re tracking to our road map deadline, how much work is left, and whether or not we are meeting our commitments. We also need to comment on major milestones or epics: are they done, and if not, are they accounted for? Finally, do our customers KNOW what we’re giving them? Have we communicated TO THEM the way we’re going to change their world for the better?
Show everyone how awesome we are! Get to it with live demos of transitions, versioning, provisioning, wireframes, slick UI, YOU NAME IT. DO NOT merely insert slides stating what we did. SHOW IT OFF! If we have very little or nothing live to demo, then we need to show reports, matrices, RACIs, Visio diagrams, etc. This is all in addition to anything live we can show. Also, we shouldn’t demo any stories that are incomplete. That’s just plain silliness.
What to Expect Next
“What To Expect Next” is usually the Product Owner’s vision of things to come, tempered by the realism of the team as a whole. While we haven’t had planning for the next sprint yet, we need to let our audience know what’s on the horizon for our project. This gives them the opportunity to plan whether or not they need to attend or whether or not they can move forward with their own agenda (project dependencies, sales pipelines, roadmap planning, etc). This also keeps us always looking forward. Keep in mind that “what to expect next” can change based on feedback and market trends, and this is the very reason why we demo! We need that feedback to make sure our customers are getting the value they’re asking for.
Things you need to do as a teammate
This means physically as well as mentally, even if you haven’t contributed much during the sprint. Try to avoid being out of the office on demo days. Being together lends credence to what we’re doing, and it also serves to bolster team morale.
While not everyone can participate at every demo, make it a point to participate as much as possible.
Make sure the demo is recorded
This is more for moderators/facilitators, but if you can, help remind them to push the “record” button. Recorded demos help keep our executives and sales folks in the loop when they can’t make it to demos.
Tips and Tricks
If we’ve done something great, then we need to shout it from the rooftops! Find creative and exciting ways to weave these wins into the demo deck.
This is a dress rehearsal, so to speak. In prep we can iron out technology wrinkles, get a feel for presentation flow, and actually calm our nerves. I like to do demo prep an hour or so before the demo.
If we promise something in a previous demo, we need to deliver it in a subsequent demo. If we don’t, then we need to explain why.
This is self-explanatory.
Have fun with images!
Image searches on Google bring up loads of crazy things. Create interest! Incorporate some of these into our demos! Of course, all things should be done in moderation and good taste. Remember: external customers can and will see these demos!
So that’s it in a nutshell. Be prepared and have fun! What are some ways you give great demos? Chime in!