SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 438 | Next

Margaret K. Kulpa, Kent A. Johnson

"Interpreting the CMMI: A Process Improvement Approach, Second Edition"

This approach is not recommended for the CMM or CMMI,
as the information contained is not comprehensive enough to effectively manage
and implement a process improvement program. Policies are addressed in the first
generic goal in the CMMI.
Table 15.4 is an example of a policy used in an organization. Notice that it summarizes
the goals for Requirements Management as listed in the CMMI.
Charters
Charters are usually generated for the Engineering Process Group (EPG) and
Process Action Teams (PATs), and are often very similar in format; their scope is
1.0 Purpose
The purpose of Requirements Management (REQM) 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.
2.0 Scope
This policy applies to software projects within the xxx Division of the xxx organization. The
term ???project???, as used in this policy, includes system and software engineering, maintenance,
conversion, enhancements, and procurement projects.


Pages:
426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450