This task describes the decisions involved in organizing the project requirements. A large requirement set will quickly
become unmanageable if it is not organized so that the analysts and other project team members can easily find them. The
organizational structure must be captured in the requirements management plan.
Steps
Categorize requirements
Assign each requirement to a requirement type from among those requirement types identified for use in the project. In
projects with more formality, the requirement types are specified in the Requirements Management Process Description. See Guideline: Categorizing Requirements for information on how to assign requirements
to the proper category.
Help the stakeholders understand the requirements better by organizing them into packages or collections. Create a
project structure for organizing requirements and supporting artifacts. Trace requirements to the supporting artifacts.
The definition of the packages or collections is usually organization-specific, and can sometimes be
project-specific. See Guideline: Packaging Requirements for more information.
Assign attributes
Analyze and understand each individual requirement. As part of the initial analysis of each requirement, assign
requirement attribute values to each requirement. For example, assign business value (such as high, medium, or low) to
requirements. This improves your ability to prioritize, track and manage the requirements. Review existing attribute
values and update as necessary.
Work with project manager and stakeholders to prioritize and approve requirements for the release, updating
the project plan or release backlog to reflect requirements prioritization as needed. Establish traceability between items
in the project plan or backlog and the approved requirements for the release.