Project Vision

...

Document Properties Marker

override	false

Short Description	Frame the vision for a project or iteration.
Doctype	doctype	hide
Name	Project Vision

Statement


ID	`project vision`

-statement


Suite	Software Development
Set	Software Development

hide

Parent

Parent Property

parent-doctype	topic
property-name	Name

Audience

Name List

doctype	role
render-no-hits-as-blank	true
property	Audience

Documentation Type

Name List

doctype	doctype-type
render-no-hits-as-blank	true
names	Q2 - Project
property	Documentation Type

Tags

Tag List

names	Software Development

Since

9.0

Iteration

value	finished

hide

Sort Key

hide

Section

index	true
title	Description

Frame the vision for your project or iteration. Log facts relevant for everyone on your team to envision the aim of your collective work.

projectdoc-box-version
Prior to version 9.0 this doctype has been named vision statement.

projectdoc-section

title	Properties

Transclusion

document	Note Box referencing common Document Properties
ids	Box

Section

level	2
title	Head Note

Provide brief description of the vision, probably in less than three sentences.

For those who do not want to distinguish between the short description and the head note, this property per default points to the Short Description.

Section

level	2
title	Type

The type provides a couple of predefined values.

Compact Definition List

;project:The vision for the project and its main product.
;subproject:The vision for a part of the project and its product.
;iteration:The vision for an iteration. Similar to the goal for the iteration a team is working to accomplish.
;other:The vision for some other type of venture.

Tip Box
You may also remove the macro value and replace it with a Name List Macro and its own type.

...

Section

title	Sections

Section

level	2
title	Elevator Statement

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

Quote External

source-uri	http://en.wikipedia.org/wiki/Elevator_pitch
render-anonymous	false
source	Wikipedia

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-uri	http://www.mindtools.com/pages/article/elevator-pitch.htm
author	Mind Tools
source	Crafting 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

level	2
title	Description

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

title	Summary

Transclusion

document	Summary
ids	Designation

Section

level	2
title	Justification

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

level	2
title	Context

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

level	2
title	Essential 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

level	2
title	Essential 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

level	2
title	Essential 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

level	2
title	Subordinate 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-level	2
document	Document Sections
ids	standard-sections-bottom

...

Section

title	References

Section

title	Resources

...

Piwik Set Multiple Custom Variables

Name	Value
Department	projectdoc
Category	projectdoc-doctype
Type	swdev-analysis

Space shortcuts

Page tree

Docs

Support

Free Blueprints

Tooling for Blueprints

Free Extensions

Spaces

Plugins for Maven

Incubator

Libraries for Java

Incubator

Add-ons for Confluence

Tools

Support

Team

Legal

Versions Compared

Old Version 2

New Version Current

Key

About

Keep up-to-date!

Powered by