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 312 | Next

Margaret K. Kulpa, Kent A. Johnson

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


Table 9.1 contains an example of what you might find existing across an organization.
This example is based on documentation we have reviewed from organizations
in the past. The three right columns indicate the disciplines of systems
engineering, software engineering, and acquisition (or purchasing). Key characteristics
for each discipline are identified in the policies, processes, and procedures in
the left-hand columns.
Measurement Programs
If the organization has not developed an integrated measurement program, it is
likely that measures* and measurement will be unbalanced across multiple process
improvement initiatives. Different improvement models place different levels of
* Measures in this section refer to both base measures and derived measures. Base measures are
simple values of some attribute, for example, size of a document in pages or effort to produce
a document in hours. Derived measures are defined to be a function of two or more base measures,
for example, productivity in hours per page to produce a document.


Pages:
300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324