lint formatting fixes
This commit is contained in:
@@ -1,26 +1,33 @@
|
||||
##### Project:
|
||||
::[PROJECTNAME](Home)
|
||||
##### Project
|
||||
|
||||
::[PROJECT-NAME](Home)
|
||||
|
||||
##### Internal Release Number
|
||||
|
||||
##### Internal Release Number:
|
||||
::X.Y.Z
|
||||
|
||||
##### Related Documents:
|
||||
##### Related Documents
|
||||
|
||||
- [Project proposal](Proposal) > [Target audience and benefits](Target-and-Benefits)
|
||||
- [SRS](SRS) > [Use case suite](Use-Case-Suite)
|
||||
- ::LINKS TO RELEVANT STANDARDS
|
||||
- ::LINKS TO OTHER DOCUMENTS
|
||||
|
||||
---
|
||||
|
||||
### Demo Planning
|
||||
|
||||
*TODO: Think through your goals for this demo.*
|
||||
|
||||
#### Who is the target audience for this demo?
|
||||
|
||||
- ::Investors and potential investors
|
||||
- ::Potential customers
|
||||
- ::Management, other developers, or partners
|
||||
- ::End users as part of training
|
||||
|
||||
#### What is your main goal for this demo?
|
||||
|
||||
- ::To convince the audience to make a decision and take action. E.g., a
|
||||
sales call.
|
||||
- ::To inform the audience about the product and prompt
|
||||
@@ -30,6 +37,7 @@
|
||||
are done with the UI.
|
||||
|
||||
#### What main points will you use to achieve your goal?
|
||||
|
||||
- ::This product automates much of the user's task, thus increasing
|
||||
productivity and cutting costs.
|
||||
- ::This product is very easy to use, which will encourage
|
||||
@@ -43,11 +51,13 @@
|
||||
the remaining features cannot possibly work like the others.
|
||||
|
||||
#### How much time is available to present the demo?
|
||||
|
||||
- ::10 minutes, no questions
|
||||
- ::10 minutes, plus questions
|
||||
- ::30 minutes, including questions
|
||||
|
||||
#### What equipment and setup is needed to give the demo?
|
||||
|
||||
- ::One person. Any computer with a web browser.
|
||||
- ::One person. Any computer where we can install from CD or
|
||||
the Internet.
|
||||
@@ -56,6 +66,7 @@
|
||||
with a wireless networking card.
|
||||
|
||||
### Demo Script
|
||||
|
||||
*TODO: Outline the steps of the demo. Plan out what you will do and say.
|
||||
Practice three times to make sure that all system features actually work
|
||||
as needed, and that there is enough time.*
|
||||
@@ -66,6 +77,7 @@ you interested? What are your questions or concerns? Do you strongly
|
||||
disagree with any points?*
|
||||
|
||||
#### ::Beginning
|
||||
|
||||
- ::SET EXPECTATIONS
|
||||
- ::SET THE STAGE
|
||||
- ::KEY POINT
|
||||
@@ -73,6 +85,7 @@ disagree with any points?*
|
||||
- ::DEMO STEP
|
||||
|
||||
#### ::Middle
|
||||
|
||||
- ::KEY POINT
|
||||
- ::DEMO STEP
|
||||
- ::DEMO STEP
|
||||
@@ -80,10 +93,11 @@ disagree with any points?*
|
||||
- ::DEMO STEP
|
||||
- ::DEMO STEP
|
||||
- ::KEY POINT (if there is time)
|
||||
- ::DEMO STEP
|
||||
- ::DEMO STEP
|
||||
- ::DEMO STEP
|
||||
- ::DEMO STEP
|
||||
|
||||
#### ::Ending
|
||||
|
||||
- ::FINAL POINT
|
||||
- ::DEMO STEP
|
||||
- ::DEMO STEP
|
||||
@@ -99,26 +113,32 @@ good answers.*
|
||||
use them if someone asks a question.*
|
||||
|
||||
#### ::How does this compare to OTHER-PRODUCT?
|
||||
|
||||
::ANSWER
|
||||
|
||||
#### ::What happens if you do X or Y?
|
||||
|
||||
::It would do Z.
|
||||
|
||||
#### ::When will your product be ready?
|
||||
|
||||
- ::We have announced a release date of July 17th.
|
||||
- ::We are planning a release this Winter, but no specific date has
|
||||
been set.
|
||||
- ::We have not announced a release date yet.
|
||||
|
||||
### Demo Checklist
|
||||
|
||||
*TODO: Use the following questions to help you evaluate your demo.*
|
||||
|
||||
#### Are you making the right points in the right order?
|
||||
|
||||
::Yes, we feel that we will accomplish our goals.
|
||||
|
||||
::No, we need to better prioritize our points.
|
||||
|
||||
#### Can it be presented in the available time?
|
||||
|
||||
::Yes, we could even add more or finish early.
|
||||
|
||||
::Yes, we have optional sections that can be skipped to save time
|
||||
@@ -130,6 +150,7 @@ fewer points.
|
||||
::No, we need to change the available time.
|
||||
|
||||
#### Do all system features actually work as needed?
|
||||
|
||||
::Yes, everything is finished and working.
|
||||
|
||||
::Yes, there are defects, but they will not matter for this demo.
|
||||
@@ -141,6 +162,7 @@ something fails.
|
||||
our points without exposing defects.
|
||||
|
||||
#### Does the demo end effectively?
|
||||
|
||||
::Yes, viewers will be satisfied and convinced.
|
||||
|
||||
::No, we need to make sure the demo stops at the natural end of a
|
||||
@@ -148,6 +170,7 @@ small but complete story, and that audience members understand our
|
||||
key points.
|
||||
|
||||
#### Does the demo raise questions that it does not answer?
|
||||
|
||||
::No, the demo is very complete.
|
||||
|
||||
::Yes, but we anticipate those questions and can handle them in the
|
||||
|
Reference in New Issue
Block a user