Permalink
Browse files

Checklist for holding a demo

Some helpful bullet points.
  • Loading branch information...
tskogberg committed Sep 15, 2014
1 parent 8f1a3ff commit d8802aea1023ccb94ce0f5341d4d60fc40a30d2d
Showing with 14 additions and 0 deletions.
  1. +1 −0 README.md
  2. +13 −0 holding_a_demo/README.md
View
@@ -19,3 +19,4 @@ For reference and discussion.
## Checklists
* [Arranging a meetup](/arranging_a_meetup)
* [Holding a demo](/holding_a_demo

This comment has been minimized.

Show comment
Hide comment
@henrik

henrik Sep 15, 2014

Member

Borked markup, missing a “)"

@henrik

henrik Sep 15, 2014

Member

Borked markup, missing a “)"

View
@@ -0,0 +1,13 @@
![Barsoom](http://barsoom.se/barsoom.png)
# Holding a demo
We like to do demos to evaluate our products as we work on them. This is a checklist for those.
* Appoint someone in charge of making this demo session happen
* Announce a time, place and duration and respect it (so we don't waste anyone's time)
* Plan the specific scenarios we want to run through
* A pre-demo with only devs can be good to catch obvious bugs
* Invite stakeholders and make it clear that we want their input
* Try to get stakeholders involved in realistic scenarios to discover real issues
* Take notes, make tickets

0 comments on commit d8802ae

Please sign in to comment.