And the procedures you write must be specific enough to be
followed. That means they must be detailed. You cannot write detailed procedures
for Web site customer service that can be used by the rest of the automobile insurance
departments. Another example: If you are building weapons systems using
nuclear missiles, don??™t think you can use the procedures written for tracking financial
accounts payable.
So, get the PATs working. After they get some experience with the CMMI, get
all the PATs together. Discuss who is doing what. Draw a chart on how the work is
fitting together. Draw a chart on what needs to be done and where the connections
are. Don??™t get too detailed, and don??™t get too excited when you find duplication of
effort or work deferred to other PATs.
Whatever you choose will be wrong and you will have to backtrack. The PATs
love deferring work to other PATs. It??™s not always fair or workable to have one PAT
write documentation for all of the PATs to implement. Remember, you should just
choose an approach, start out doing it one way or another, and then stop and see
what you have and whether it is working.
Pages:
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397