Obtain commitment to the requirements from the project participants.
Refer to the Project Monitoring and Control process area for more information about monitoring the commitments made.
IPPD Addition
When integrated teams are formed, the project participants are the integrated teams and their members. Commitment to the requirement for interacting with other integrated teams is as important for each integrated team as its
commitments to product and other project requirements.
Whereas the previous specific practice dealt with reaching an understanding with the requirements providers, this specific practice deals with agreements and commitments among those who have to carry out the activities necessary to
implement the requirements. Requirements evolve throughout the project, especially as described by the specific practices of the Requirements Development process area and the Technical Solution process area. As the requirements evolve, this specific
practice ensures that project participants commit to the current, approved requirements and the resulting changes in project plans, activities, and work products.
Typical Work Products
1. Requirements impact assessments
2. Documented commitments to requirements and requirements changes
Subpractices
1. Assess the impact of requirements on existing commitments.
The impact on the project participants should be evaluated when the requirements change or at the start of a new requirement.
2. Negotiate and record commitments.
Changes to existing commitments should be negotiated before project participants commit to the requirement or requirement change.
676/1102 - 0 sub articles
CMMI-DEV 1.2
4. 
SP 1.2 Obtain Commitment to Requirements