Overview of the Capability Maturity Model (CMM) Flashcards

(40 cards)

1
Q

It is a structured framework designed to help organizations improve their software processes.

A

Capability Maturity Model (CMM)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

In CMM, this refers to how explicitly defined, managed, and controlled a software process is.

A

Maturity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Processes are improvised, highly dependent on individual heroics, and lack consistency.

A

Immature Organizations

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What level is Immature Organization?

A

Level 1

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

There is a clear, organization-wide process that is documented, repeatable, measured, and improved over time.

A

Mature Organizations

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What level is Mature Organization?

A

Level 2 - 5

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

This level’s characteristic in the TMM is that processes are ad hoc and chaotic.

A

Initial

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

This level’s characteristic is that success depends on the individual effort rather than an established methodology.

A

Initial

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

This TMM level is also described as Chaotic and Unpredictable

A

Initial

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

The implications of this level is that there is little to no stability or predictability in project outcomes.

A

Initial

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

This level’s characteristic is that basic project management processes are in place.

A

Repeatable

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

This level’s characteristic is that Past experiences are used to guide current projects, making it possible to repeat successes.

A

Repeatable

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

The key focus for this level is establishing and tracking cost, schedule and functionality using elementary project management controls.

A

Repeatable

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

This TMM level is also described as Basic Project Management

A

Repeatable

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

This level’s characteristic is that the organization develops a standard, documented software process that is tailored for each project

A

Defined

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

The key focus for this level is integrating both management and engineering practices across the organization; ensuring that every project follows a coherent process.

A

Defined

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

This level is also described as Standardized and Documented

18
Q

This level’s characteristic is that Quantitative management practices are introduced

19
Q

This level’s characteristic us that detailed measures of the process and product quality are collected, enabling better control and predictability.

20
Q

The key focus for this level is reducing variability by using statistical process control; establishing performance baselines through rigorous measurement

21
Q

This level is also described as Quantitative Control

22
Q

This level’s characteristic is that the focus is on continuous process improvement through proactive defect prevention and technology innovation

23
Q

The key focus for this level is using data-driven insights to drive incremental improvements and to incorporate innovative practices that push the boundaries of process capability

24
Q

This level is also described as (Continuous Improvement)

25
Explain the transition from Level 1 to Level 2
Organizations must establish basic project management before trying to implement engineering improvements
26
Explain the transition from Level 2 to Level 3
Standardizing processes is crucial before applying advanced engineering techniques
27
Explain the transition from Level 3 to Level 4
Without well-defined processes, collecting and interpreting quantitative data becomes meaningless.
28
Explain the transition from Level 4 to Level 5
Continuous improvement efforts must be based on solid quantitative analysis
29
These are clusters of related practices that, when implemented, collectively achieve the goals required for that level
Key Process Areas
30
Example by Maturity Level: Requirements Management
Level 2
31
Example by Maturity Level: Software Project Planning
Level 2
32
Example by Maturity Level: Software Project Tracking
Level 2
33
Example by Maturity Level: Software Quality Assurance
Level 2
34
Example by Maturity Level: Organization Process Focus
Level 3
35
Example by Maturity Level: Training Program
Level 3
36
Example by Maturity Level: Organization Process Definition
Level 3
37
Example by Maturity Level: Quantitative Process Management
Level 4
38
Example by Maturity Level: Software Quality Management
Level 4
39
Example by Maturity Level: Defect Prevention
Level 5
40
Example by Maturity Level: Technology Change Management
Level 5