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

Project Portal
| ### Next Steps Create a Scenario Create a Quality of Service Requirement |
| ### Patterns & Practices Personas: Practice and Theory |
| Capture Project Vision Business Analyst
|  | Participating Roles Responsible: Business Analyst
### Overview Getting a project started requires the clear establishment of the project vision. Capturing and communicating this central vision is the most important element to keeping a project focused. During the project, this vision may change as a result of the business or project climate. If change occurs, it is necessary to realign the project to the new vision. From the vision, we begin to understand who the users will be. Usage patterns and goals of these users will be captured using personas. We will also understand if the project is driven by date or by content. The vision and its related activities create the solid foundation on which a project can be built. # Entry Criteria There are no entry criteria for this work stream # Activities
1 | Write Vision Statement | Summarize the project background. Explain driving factors for the project. Determine the application's key value. Identify the application's users.
2 | Define Personas | Define the user groups. Create personas for each user group.
3 | Refine Personas | Determine the type of difference between the written persona and the user. Update and communicate persona changes.
# Exit Criteria
| The vision statement is completed and published to the project portal.
| The personas are written and published to the project portal.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |