Overview |  | Roles |  | Work Items |  | Views |  | Index |  | Glossary |

Project Portal
| ### Next Steps Define Personas Define Test Approach |
| Activity: Write Vision Statement
Business Analyst
|  |  |  | Capture Project Vision |  |
|  | Participating Roles Responsible: Business Analyst
### Overview A vision statement is a short, coherent statement that concisely describes the purpose for building the new or improved system. It provides to the team a brief summary of the project background, the driving factors, and the justification for building the system. The vision statement should provide a high level understanding of the application’s users. It also should include what the users need and how this application is going to meet that need. Finally, it should specify whether the delivery of the system is date-driven or functionality-driven. The language of the end user domain should be used to write the vision statement. Writing a concise, effective vision statement can be a challenge. # Entry Criteria The problems the product intends to solve have been identified # Sub-Activities
1 | Summarize Project Background | Provide a one or two paragraph context for the project. The paragraphs should describe the events that determine the need for a new or improved system.
2 | Explain Driving Factors | Describe the major requirements or timeframe driving the release of the product. Be brief. Make it clear whether this project is driven by date (such as a major tradeshow) or functionality (such as the desire to outdo a competitor).
3 | Identify Users | Determine the set of users who get primary value from the system.
4 | Determine Key Value | Write the value proposition of the new or enhanced system. Distill the key concepts down to approximately a twenty-five word statement that provides a single value proposition for the users identified.
# Exit Criteria
| The reviewed vision statement is uploaded to the project portal.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |