Prioritize Requirements

The purpose of Prioritize Requirements is to rank requirements in the order of relative importance.

Guidelines/Tools and Techniques

The guidelines/tools and techniques used to prioritize requirements.

  • Prioritize Requirements – Uses Risk Analysis and Management, Workshops, Backlog Management, Decision Analysis, Business Cases, Estimation, Financial Analysis, Interviews, Item Tracking and Prioritization, techniques to prioritize requirements.

  • Requirements – Use Business Constraints, the Change Strategy, Solution Scope, Requirements Management Tools/Repository, Domain Knowledge, the Requirements Architecture and Governance Approach as guidelines and tools.

The relationships between these guidelines, tools, techniques and Requirements, are detailed in the BABOK under the Guidelines and Tools and Techniques sections of the Prioritize Requirements task.

Workers

The people involved with prioritizing requirements.

The relationships between these roles and the task, are detailed in the BABOK under the Stakeholders section of the Prioritize Requirements task.

Customer - Verifies that the requirements and designs priority delivers value from an end-user perspective.
End User - Contributes their experience to requirements and designs priority.
Implementation Subject Matte Expert - Provides input regarding technical dependencies and constraints.
Project Manager - Uses requirements and design prioritization to plan the project.
Regulator - Verifies that prioritization is consistent with legal and regulatory constraints.
Sponsor - Verifies the prioritized requirements and designs will deliver maximum value to the business.