Costs and benefits of the proposed
versus actual improvements are also studied.
Some people have interpreted this PA as including both process and product
improvements. This opens up a can of worms for appraisal teams. What was
expected in the CMM for Software was process improvements and improvements
in technology to support the processes. Technologies, such as a new requirements
traceability tool or a new unit test tool, were included. Technologies that were to be
part of a product, such as a new database management system or a new algorithm,
were not included. With CMMI, these concepts become an even bigger issue. The
systems that we may be building can include a lot of technologies. The question
becomes how far should an appraisal team go? Is the organization expected to have
a defined process to select technologies? When selecting the type of phones for its
staff, is that covered by OID? When selecting which type of interface to put on
their new phone system, is that covered by OID? Or is that covered in Technical
Solution at Level 3?
The steps in this PA include:
Submitting improvement proposals
Reviewing and analyzing the proposals (including a cost-benefit review)
Piloting the proposed improvement
Measuring the improvement to see whether it has been effective in the
pilot
Planning the deployment of the improvement
Deploying the improvement
Measuring the effectiveness of the improvement across the organization or
project
For example, a Level 1 organization will simply mandate that a certain change
control tool is now to be used.
Pages:
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307