Frame the vision for a project or iteration.
Frame the vision for your project or iteration. Log facts relevant for everyone on your team to envision the aim of your collective work.
The document type vision statement provides the following properties:
Please note that only information about specific properties is provided here. Common document property used by all document types are documented by Document Properties.
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.
The type provides a couple of predefined values.
- The vision for the project and its main product.
- The vision for a part of the project and its product.
- The vision for an iteration. Similar to the goal for the iteration a team is working to accomplish.
- The vision for some other type of venture.
You may also remove the macro value and replace it with a Name List Macro and its own type.
The elevator statement provides a brief, concise definition of the project's goal and value proposition.
Gerard Meszaros suggests in From Concept to Product Backlog the following template to use:
Mind Tools. 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.
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.
Describe the objectives of the projects and list what problems the to-be-created system should solve.
- formulates the problem
- addresses no solutions
- mentions no technologies or techniques
- is written in the language of the user of the system.
Provide a summary of the document's structure and key points. This is an informative abstract typically of about 100 to 200 words.
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.
Describe the context in which the system is used by its users form the user's perspective.
- 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.
List the essential (and initial) stakeholders. Stakeholders mentioned here are involved in the vision and/or the sponsoring of the project.
List the central actors of the system to be created.
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.