Interpreting the CMMI (R): A Process Improvement Approach, Second Edition
The following table can be used to plan and track completion of artifacts and implementation associated with CMM process area practices and goals. See Chapter 15 for more information.
| No. | Process Area | CMM Reference | Document | Assigned To | Date Due/Reviewed | Status |
|---|---|---|---|---|---|---|
| 1 | Infrastructure | SPI Plan | ||||
| 2 | Infrastructure | Implementation Plan | ||||
| 3 | Infrastructure | Organization's Standard Software Process (OSSP) | ||||
| 4 | Infrastructure | SEPG Charter | ||||
| 5 | Infrastructure | SEPG Presentation Template | ||||
| 6 | Infrastructure | Procedure Template | ||||
| 7 | Infrastructure | Training Packet Guidelines for Pilots | ||||
| 8 | Requirements Management | RM Charter | ||||
| 9 | Requirements Management | RM Action Plan | ||||
| 10 | Requirements Management | RM WBS | ||||
| 11 | Requirements Management | RM Schedule | ||||
| 12 | Requirements Management | CO1, AB1, AB3, AB4 | Policy for managing system requirements allocated to software: includes establishing responsibility, providing adequate resources and required RM training | |||
| 13 | Requirements Management | AB2, AC1 | Procedure for Requirements Specification and Review | |||
| 14 | Requirements Management | AB2, AC2 | Procedure for completing Requirements Traceability Matrix (RTM): includes use as basis for SDP and work products | |||
| 15 | Requirements Management | AC3 | Procedure for SRS and RTM changes | |||
| 16 | Requirements Management | ME1 | Procedure for RM metrics | |||
| 17 | Requirements Management | VE1, VE2 | Procedure for Project and Senior Management reviews | |||
| 18 | Software Project Planning | SPP Charter | ||||
| 19 | Software Project Planning | SPP Action Plan | ||||
| 20 | Software Project Planning | SPP WBS | ||||
| 21 | Software Project Planning | SPP Schedule | ||||
| 22 | Software Project Planning | SPP Process Overview Document | ||||
| 23 | Software Project Planning | Com-1 | Software PM designated in Policy for SDP and commitments | |||
| 24 | Software Project Planning | Com-2 | Policy for planning a software project | |||
| 25 | Software Project Planning | Abil-1 | Statement of Work for each software project | |||
| 26 | Software Project Planning | Act-6 | Procedure for developing a Software Development Plan | |||
| 27 | Software Project Planning | Act-7 | Software Development Plan for each software project ( Note: may be contained in several "documents" of different names ) | |||
| 28 | Software Project Planning | Act-9 | Procedure for estimating size of software work products | |||
| 29 | Software Project Planning | Act-10 | Procedure for estimating effort and cost for the software project | |||
| 30 | Software Project Planning | Act-11 | Procedure for estimating critical computer resources | |||
| 31 | Software Project Planning | Act-12 | Procedure for deriving software project schedule | |||
| 32 | Software Project Planning | Act-13 | Risk identification and assessment document for each software project | |||
| 33 | Software Project Planning | Act-14 | Plans for software facilities and tools for each software project | |||
| 34 | Software Project Planning | Act-15 | Estimates and basis for estimates data is recorded for each software project | |||
| 35 | Software Project Planning | ME1 | Measurements are made to determine status of software planning activities (rationale for measurements and how to collect and analyze them) | |||
| 36 | Software Project Planning | VE1 VE2 | The activities of SW project planning are reviewed with Senior Management and Project Management ” procedures for both | |||
| 37 | Software Project Planning | VE3 | SQA audit of PP Activities ” procedures for quality reviews ” may be found in SQA KPA |
Категории