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

Project Portal
| Scenario
### Work Item Database
Overview |
States and Transitions |
Fields |
### Process Guidance |
Activities |
Work Streams |
Scenario Fields A scenario is a type of work item, recording a single path of user interaction through the system. As the persona attempts to reach a goal, the scenario records the specific steps that they will take in attempting to reach that goal. Some scenarios will record a successful path; others will record an unsuccessful one. When writing scenarios, be specific as there are many possible paths.
Field | Description
--- | ---
Title | Required. The title describes the intent of the scenario. The title should be descriptive enough to allow a business analyst to write it several iterations after it was initially conceived.
Issue | Issue is a Yes or No value indicating if the scenario is blocked on progress. If this field is set to Yes, the scenario will show up on the project manager’s issue report.
Specified | Specified is a Yes or No value indicating if the scenario has been assigned to the development team. After the business analyst writes the scenario, this field should be set to Yes and the scenario should be assigned to a developer.
Exit Criteria | Exit Criteria is a Yes or No value indicating if the scenario is part of the exit criteria list. If this field is set to Yes, the scenario shows up on the project checklist.
Rank | Rank indicates how important the scenario is relative to all scenarios for the software product. Valid values are 1 through 3.
Integration Build | The Integration Build is the build number in which the scenario is integrated by the development team.
ID | The ID is the unique identification number assigned to the scenario.
Area | The area is used to group the scenario into an appropriate feature or team area. The area must be a valid node in the project hierarchy.
Iteration | The scheduled iteration is the iteration in which the scenario is implemented in code.
Estimate | The estimate is how many person days are required to fully implement the scenario.
Assigned To | The current person that the scenario is assigned to.
State | Required. A scenario can be in the Active, Resolved, or Closed states.
Reason | The reason a scenario is in the current state. For example, a scenario can be in the Closed state because it was Completed.
Description | The description should be a high level outline of the scenario. The full scenario should be described in a scenario work product.
History | This history is a running discussion about the scenario that accumulates additional written entries as changes are made. Each time a change is made to the scenario, an entry is made in the History field describing what change was made and why, as well as any additional pertinent information about the change.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |