Purpose:
The purpose of Requirements Management is to manage the requirements of the project's products and product components and to identify inconsistencies between those requirements and the project's
plans and work products.
Introductory Notes:
Requirements management processes manage all requirements received or generated by the project, including both technical and nontechnical requirements as well as those requirements levied on theproject by the organization. In particular, if the Requirements Development process area is implemented, its processes will generate product and product-component requirements that will also be managed by the requirements management processes. When the Requirements Management, Requirements Development, and Technical Solution process areas are all implemented, their associated processes may bec losely tied and be performed concurrently.
The project takes appropriate steps to ensure that the agreed-upon setof requirements is managed to support the planning and execution needs of the project. When a project receives requirements from anapproved requirements provider, the requirements are reviewed withthe requirements provider to resolve issues and prevent misunderstanding before the requirements are incorporated into theproject’s plans. Once the requirements provider and the requirements receiver reach an agreement, commitment to the requirements is obtained from the project participants. The project manages changes to the requirements as they evolve and identifies any inconsistencies thatoccur among the plans, work products, and requirements.
Part of the management of requirements is to document requirements changes and rationale and maintain bidirectional traceability between source requirements and all product and product-component requirements.
Specific and Generic Goals:
SG 1: Manage Requirements
Requirements are managed and inconsistencies with project plans and work
products are identified.
GG 2 : Institutionalize a Managed Process
The process is institutionalized as a managed process.
(The following goal is not required for maturity level 2, but required for maturity level 3 and
above.)
GG 3 : Institutionalize a Defined Process
The process is institutionalized as a defined process.
Practice-to-Goal Relationship Table:
SG 1 Manage Requirements
SP 1.1 Obtain an Understanding of Requirements
SP 1.2 Obtain Commitment to Requirements
SP 1.3 Manage Requirements Changes
SP 1.4 Maintain Bidirectional Traceability of Requirements
SP 1.5 Identify Inconsistencies between Project Work and Requirements
GG 2 Institutionalize a Managed Process
GP 2.1 (CO 1) Establish an Organizational Policy
GP 2.2 (AB 1) Plan the Process
GP 2.3 (AB 2) Provide Resources
GP 2.4 (AB 3) Assign Responsibility
GP 2.5 (AB 4) Train People
GP 2.6 (DI 1) Manage Configurations
GP 2.7 (DI 2) Identify and Involve Relevant Stakeholders
GP 2.8 (DI 3) Monitor and Control the Process
GP 2.9 (VE 1) Objectively Evaluate Adherence
GP 2.10 (VE 2) Review Status with Higher Level Management
(The following goal is not required and its practices are not expected for a maturity level 2 rating,
but are required and expected for a maturity level 3 rating and above.)
GG 3 Institutionalize a Defined Process
GP 3.1 Establish a Defined Process
GP 3.2 Collect Improvement Information
