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

Project Portal
| See Also Define Personas |
| Activity: Refine Personas
Business Analyst
|  |  |  | Capture Project Vision |  |
|  | Participating Roles Responsible: Business Analyst
### Overview Meetings and reviews often bring out new details about usage patterns and level of knowledge. Use these meetings as an opportunity to validate the personas. Refine personas to periodically keep them up to date and continue to understand the intended system users. When updates are made, communicate these changes to the organization. # Entry Criteria Dependencies: Interaction with the users has lead to the need to change a persona. The personas are published on the project portal. # Sub-Activities
1 | Determine Type of Difference | Look for similarities and differences in the level of knowledge, usage patterns, interactions, and goals between the persona and the user. If a difference exists, determine if the user is an intended user. If the difference is significant, determine whether a new persona is needed or a change to an existing persona.
2 | Update and Communicate Changes | Add any new personas and make changes to existing personas. Publish the personas and communicate the changes to the rest of the team. Brainstorm scenarios and quality of service requirements or if the changes are major, conduct exploratory testing to see if any changes need to be made to the scenario list. Examine the priorities.
# Exit Criteria
| The updated personas are published on the project portal.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |