Organizing requirements

The product owner or business analyst organizes requirements and supporting artifacts in the project structure, and then works with stakeholders and team leads to define, prioritize, and obtain approval on a set of requirements.

The graphic
shows four steps for organizing requirements Click this area to get information about planning a release Click this area to get information about developing a vision Click this area to get information about planning the project Click this area to get information about planning the test effort Click this area to get information about defining requirements Click this area to get information about prioritizing requirements Click this area to get information about approving requirements

Before you begin

Prior to organizing the requirements, develop a project vision. The high-level feature requirements and related artifacts in the vision document provide a starting point for elaborating and prioritizing a set of approved requirements for the release.

1. Define requirements

Perform the following tasks to create project structure and trace to supporting artifacts:
  1. Create a project structure for organizing requirements and supporting artifacts, which were gathered while developing the vision. Add folders for storing:
    • stakeholder requests, which include business goals
    • features, which include ideas for features, market analysis, and release themes
    • user stories, which are expressed in rich-text documents, possibly with embedded images of sketches and flow diagrams
    • system-wide requirements, which include non-functional requirements such as performance and translation
    • glossary, which includes terms and definitions

    Supporting tasks:

    Managing terminology and glossaries

  2. Trace requirements to supporting artifacts.

Supporting tasks:

Links between artifacts

2. Prioritize requirements

Use the Artifacts and Collections pages to view and open artifacts and collections. Set attributes and filter for high-priority requirements.
  1. Assign business value and competitive response attribute values to requirements.
  2. Filter the requirements using high-priority attributes, such as Business Value = High and Competitive Response = High.
  3. Add the results of the query to a new collection.

Supporting references and tasks:

3. Approve requirements

Group requirements in a collection and initiate a review of the requirements by development leads, test team leads, and other stakeholders, and gain approval for the release requirements.
  1. Create a formal review of the collection and identify the reviewers.
  2. Each reviewer receives notice of the review, performs the review, and approves the collection.
  3. The analyst receives notification when approvals are complete and baselines the collection.

Supporting tasks:

Creating reviews


By completing this task, you have defined, organized, prioritize, and obtained approval on a set of requirements.

What to do next

Plan the project: Create a release plan with iterations, add and prioritize stories, estimate time for work items.