Free electronic library

Specific Goals and Practices for This Process Area:
SG1 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
64 n Interpreting the CMMI
Why is Requirements Management at Level 2? Why is there another process
area called Requirements Development at Level 3? What??™s the difference? Requirements
Management for Level 2 is all about managing already existing requirements;
that is, those requirements that have been elicited from the customer, are
documented, and are ready to be worked or are in the process of being worked.
This PA refers to capturing and managing the requirements that set the scope of
the project. It is at this level because if you don??™t set the scope you cannot control
how much work will need to be done by the project. So, at this level, requirements
already exist, and we are basically just managing the changes to them.


Pages:
149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173