projectdoc Toolbox

Space shortcuts

Page tree

Versions Compared

Old Version 2

changes.mady.by.user Robert Reiner

Saved on

compared with

New Version 3

changes.mady.by.user Robert Reiner

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section
titleSections
Section
level2
titleElevator Statement

The elevator statement provides a brief, concise definition of the project's goal and value proposition.

Quote External
source-urihttp://en.wikipedia.org/wiki/Elevator_pitch
render-anonymousfalse
sourceWikipedia

An elevator pitch, elevator speech, or elevator statement is a short summary used to quickly and simply define a person, profession, product, service, organization or event and its value proposition. 

Gerard Meszaros suggests in From Concept to Product Backlog the following template to use:

Panel

For (target customers)
who are dissatisfied with (the current market alternatives),
our product is a (new product category)
that provides (key problem-solving capability).
Unlike (the product alternative)
we have assembled (key "whole product" features for our specific application).

On mindtools.com provides tips on Crafting an Elevator Pitch:

Quote External
source-urihttp://www.mindtools.com/pages/article/elevator-pitch.htm
authorMind Tools
sourceCrafting an Elevator Pitch

An elevator pitch is a brief, persuasive speech that you can use to spark interest in what your organization does. You can also use one to create interest in a project, idea, or product.

It needs to be succinct, while conveying important information.

To craft a great pitch, follow these steps.

  • Identify your goal.
  • Explain what you do.
  • Communicate your USP.
  • Engage with a question.
  • Put it all together.
  • Practice.

Try to keep a business card or other take-away item with you, which helps the other person remember you and your message. And cut out any information that doesn't absolutely need to be there.

Section
level2
titleDescription

Describe the objectives of the projects and list what problems the to-be-created system should solve.

The description

  • formulates the problem
  • addresses no solutions
  • mentions no technologies or techniques
  • is written in the language of the user of the system. 
Section
titleSummary
Transclusion
documentSummary
idsDesignation

Section
level2
titleJustification

Describe why this project has been initiated and why the objectives of this project are important for the enterprise.

Possibly this project substitutes a running system. In this case the deficiencies will be mentioned that need to be addressed by the new system. Also the well solved issues of the old system should be mentioned to prevent the new system fall behind the old system in particular aspects.

Section
level2
titleContext

Describe the context in which the system is used by its users form the user's perspective.

This includes:

  • who is using the system (see actors section)
  • how the system is used
  • which kind of interface does the system provide.

It may also mention other systems the new system is communicating with. 

You may want to provide a context diagram and reference or transclude it here.

Section
level2
titleEssential Stakeholders

List the essential (and initial) stakeholders. Stakeholders mentioned here are involved in the vision and/or the sponsoring of the project.

Tip Box

Use the Stakeholder Doctype to document the stakeholders of your project. Then either select on them using the Display List Macro or use the Tour Macro and enumerate the essential stakeholders.

Section
level2
titleEssential Actors

List the central actors of the system to be created.

Tip Box

Use the Role Doctype to document the roles of your project. Then either select on them using the Display List Macro or use the Tour Macro and enumerate the essential roles.

Section
level2
titleEssential Features

List the top (usually up to seven) features that are the building blocks and key features of the new system. Describe the features in present tense, since they already exist in the vision.

Tip Box

Use the Feature Doctype to document the features of your product. Then either select on them using the Display List Macro or use the Tour Macro and enumerate the most important features.

Section
level2
titleSubordinate Visions
In case you want to subdivide the vision in a number of visions. This will rarely be the case, but since most templates allow this form of partitioning, this doctype is no exception.
Transclusion
taget-heading-level2
documentDocument Sections
idsstandard-sections-bottom

...

Section
titleReferences

Section
titleResources

 

...

About

This site is maintained by smartics.

Imprint / Impressum

Data Privacy / Datenschutz 

End User License Agreement (EULA)


To get in touch please send us an e-mail!

smartics email

Keep up-to-date!

Read our

smartics Blog

Follow us on

Twitter YouTube Prezi

Find us on

Bitbucket GitHub Atlassian Marketplace

Powered by




© 2001-2023 smartics - Kronseder & Reiner GmbH