| Level |
Characteristics |
Key Challenges |
Result |
5
Optimizing |
- Improvement fed back into process
- Data gathering is automated and used to identify weakest process elements
- Numerical evidence used to justify application of technology to critical
tasks
- Rigorous defect - cause analysis and detect prevention
|
- Still human - intensive process
- Maintain organization at optimizing level
|
 |
4
Managed |
(Quantitative)
- Measured process
- Minimum set of quality and productivity measurements established
- Process database established with resources to analyze its data and
maintain it
|
- Changing technology
- Problem analysis
- Problem prevention
|
|
3
Defined |
(Qualitative)
- Process defined and institutionalized
- Software Engineering Process Group established to lead process improvement
|
- Process measurement
- Process analysis
- Quantitative quality plans
|
|
2
Repeatable |
(Intuitive)
- Process dependent on individuals
- Established basic project controls
- Strength in doing similar work, but forces major risk when presented
with new challenges
- Lacks orderly framework for improvement
|
- Training
- Technical practices (reviews, testing)
- Process focus (standards, process groups)
|
|
1
Initial |
(Ad hoc/chaotic process)
- No formal procedures, cost estimates, project plans
- No management mechanism to ensure procedures are followed, tools not
well integrated, and change control is lax
- Senior management does not understand key issues
|
- Project management
- Project planning
- Configuration management
- Software quality assurance
|
|
