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

Margaret K. Kulpa, Kent A. Johnson

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

For example, you might merge a systems engineering
training program and a software engineering training program
for the same reason you merge process improvement groups to eliminate
overlap, simplify the efforts, increase communication, and focus your
resources.
Merging courses with similar content, roles, and level of detail. For example,
you might merge data management and configuration management
courses to eliminate redundancy, improve consistency, and increase knowledge
across two similar groups. Caution: Some courses, for example, a quality
assurance orientation and a quality assurance techniques course, are
similar, but with a different level of detail for different audiences. Those
would not be merged.
The other outcome of this effort is identifying courses that need to be developed
to address the expanded scope of CMMI. For example, if you have a software
project manager course but don??™t have a systems or purchasing project manager
course, you will either want to expand the scope of the software course or create
new courses for systems and purchasing.


Pages:
311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335