Skip to main content

Showing Off: How to Do a User Demo


Rather than repeating what has been said elsewhere, here is a nice short post on agile-for-all that covers the basics.

Here are a few things for my own future reference and teams that I'm working with...

Try to keep each demo to 5 minutes or less.  

If it's longer than that, it's possible that you should be demoing more than one story.  More likely, you're just being too wordy.


TALK LOUDLY.  

No, louder than that.  Louder.  Do you feel like you're yelling?  OK, that's about right.  You need to put your voice in public-address mode for 5 minutes.


Focus on why your audience should care about the story 

This is particularly important for back-end work.  For example: Your story generates a feed of XML that will be consumed by another application. Show the output, and point to a couple of salient features in it.  Then be done.

The important part of the above is "show the output."  Showing the end users how to interact with your service is a separate sit-down, not part of demo.

At base, you want to remember who your audience is, and why you're doing a demo. 

Your audience

Usually, people come to a demo because they have a stake in the success of your software project. They're executives and end-users who want a preview of what they're getting.  The questions that are foremost in their minds are:
  • Am I spending my software budget wisely?
  • Is what the team is working on what I need next, or do I need to change their priorities?
What it does and why it matters are most important.  They do not care if you came up with a way-cool whiz-bang solution to a technical problem.  They do not care if you just learned how to use the MEAN stack.  Show off your skills to the rest of your team in a lunch & learn session later.

Why do a demo?

You're doing this to ensure that you're building the right thing.  Hopefully you have other controls in place (tests, business validation reviews, etc) to ensure that you're building the thing right.  This isn't the time & place to prove it.  You're here to give the business-oriented people a chance to judge the value of your work, so they can help you adjust if you're not giving them what they really need right now.

On this last point, it's important to keep an open mind and accept the feedback you get.  If you aren't getting any feedback, you probably need to adjust how you're doing the demo.
Post a Comment

Popular posts from this blog

Agile Performance Management: Why Performance Reviews Suck

Many thanks to Mary Poppendieck, who wrote about this topic in 2004, and proposed a comprehensive solution.  She is the inspiration for much of my thinking on this subject.  She is also a better writer than I am a cartoonist.


Performance reviews suck.  I don't know of anyone who goes into their appraisal without some trepidation.  Your boss is guaranteed spring some surprise criticism on you that is ill-informed or misses the point as you see it.  It's a real challenge not to get defensive about that.

The only thing that makes your own performance review suck less is having to give them.  As a manager, I have dished out quite a few, and some of them went pretty badly.  (To the people at my first management job: Thanks for helping me learn how to get better at them.  Your sacrifice was not in vain.)  Since then, receiving one isn't nearly as gut-wrenching, if only because I try to make it easier for the guy on the other side of the desk.  I've been there, and I know how …

Do. Not. Optimize.

You've probably heard this quote before:
Premature optimization is the root of all evil.
 - Tony Hoare
Speculative optimization is always wasted time.  In the absence of an actual performance problem, you're just burning time that could be better spent on refactoring your code to make it clearer.  This is exacerbated because performance-optimized code is usually harder to read than code which hasn't received such treatment.

Here is what you're doing when you optimize:
Adding code that now must be maintained.Obfuscating the existing code.Spending time writing code that doesn't add value. But what's that you say?  You have the experience and know-how to decide when optimization is needed?  Maybe, but probably not.   The people at Sun and Oracle may or may not be smarter than  you or me, but they certainly know more about optimizing Java bytecode than we do.

For example, some people think that having a large number of classes is slower than the alternative.  This …

Software Craftsmanship Day at my workplace

Well, we finally pulled together a schedule and planned out all of our sessions for a Software Craftsmanship day at my workplace. 
The coolest part?  I didn't have to beg anyone to make it happen.  One of the VP's suggested that we could devote a day per month to honing our development skills.  How many organizations do that?  Very few, I think.
Since I was already leading a craftsmanship group, my boss asked me to lead the effort to put this together.  I just asked for volunteers, called a weekly meeting to work out what we wanted to do, and we did it!
I'll be sure to report what I learned once the first one is over.  I expect this to be a very useful and interesting day, but I won't know for sure until after Friday, Nov 12.
The best way to describe what we're doing is to paste the invitation I just sent to all of the agile teams here (about 120 people are invited, I expect around 100 to attend).
Craftsmanship Day (a.k.a. "Craft Day") takes place all day th…