Beruflich Dokumente
Kultur Dokumente
Geir Amsjø
What do a customer want?
Customers wants:
Predictable performance
• On time deliveries
• Costs according to budget
• All functionality
• Reliable promises
Visibility of progress and quality
SW-CMM 2
Crisis-Driven Organizations
Processes:
• ad hoc - improvised and reinvented each time
• abandoned under stress
• reactionary
Schedules and budgets:
• unpredictable
• usually exceeded
Success factors:
• heroes
• overtime
• fire fighting
Blaming others: bad subcontractors, hardware problems...
SW-CMM 3
Executive Problems in Software
SW-CMM 4
Project Manager Problems
SW-CMM 5
What Frustrates Developers
SW-CMM 6
Sources of Crisis
SW-CMM 7
Cost (i.e Effort) to Remove Defects
Cost/Effort
Cost to repair
Time/phase
SW-CMM 8
Improvement Areas
Technology
Product
People Process
SW-CMM 9
The Role of the Process
Management
Process
Staff
Technical assets
Reference: Bill Curtis, TeraQuest Metrics
SW-CMM 10
Definition of Software Process
Definition from SEI technical report SEI-93-TR-24, ”Capability Maturity Model for
Software, Version 1.1”
SW-CMM 11
Potentials in Process-Based Development
SW-CMM 12
Misconceptions About Process
SW-CMM 13
What is an Effective Process?
Defined
Documented
Used
Trained
Tailored
Improved/maintained
SW-CMM 14
The Process is a Part of the Competition
Process is a competitive weapon in almost every industry except software
development
Our software process decides quality, cost and cycle-time
Software Development
• Historically not considered to be engineering
“The quality of a software system is governed by the quality of the process used to
develop and evolve it.”
Watts Humphrey (Father of the CMM)
SW-CMM 15
Internal Delivery Precision
% 105 5
100
95 4
90
CMM Level
3
85
80
2
75
70 1
65
60 0
92/01
92/05
92/09
93/01
93/05
93/09
94/01
94/05
94/09
95/01
95/05
95/09
96/01
96/05
96/09
97/01
97/05
97/09
TG2 Rolling Average TG2 Min Roll Ave
TG2 Max Roll Ave CMM Level
SW-CMM 16
Fault Density, First 6 Months
Fault Density, First 6 Months of Operations
(Plotted against PR-A Date)
Fault/KPlex
5
1.50
4
CMM Level
1.00 3
2
0.50
1
0.00 0
91-01
91-06
91-11
92-04
92-09
93-02
93-07
93-12
94-05
94-10
95-03
95-08
96-01
96-06
96-11
97-04
97-09
ETM/R Failure 12 mth Rolling CMM Level
Goal Density avarage
SW-CMM 17
The Start of CMM
Millions of dollars wasted for DoD, Ada etc didn’t solve all problems.
Management problem, not technical!
Watts Humphrey, then at IBM, had an idea!
SEI and MITRE Corporation began the development late 1986
Brief description - September 1987
Managing the Software Process by W. Humphrey- 1989
CMM Version 1.0 - 1991
Version 1.1 - 1993
Integrated CMM (CMMI) released in 2001
SW-CMM 18
Software-CMM by SEI:
SW-CMM 19
Capability Maturity Model Objectives
SW-CMM 20
Improvement Challenges
The CMM
• Overcomes these hurdles one by one
SW-CMM 21
CMM Design Rationale
SW-CMM 22
Maturity Framework
Continuous Level 5:
process
improvement Optimizing
Level 4: Change
Process Managed management
control
Process
Level 3:
Quantitative
definition Defined management
Process Level 2:
Engineering
discipline Repeatable management
Level 1:
Project
Initial management
SW-CMM 23
CMM Architecture
SW-CMM 24
Key Process Area (KPA)
SW-CMM 25
Key Process Area Goals
SW-CMM 26
Key Practices
Practices
Goals Practices
Key Process Area
Goals
Practices
Practices
SW-CMM 27
Key Practices
SW-CMM 28
Common Features
Goals
Key Practices:
Institutionalization Implementation
SW-CMM 29
Common Features
Common features:
Organize the key practices
Supports institutionalization of process performance
SW-CMM 30
Implementation vs. Institutionalization
Note that:
SW-CMM 31
Commitment to Perform
Actions to ensure that the organization is committed to the activities in the KPA:
SW-CMM 32
Ability to Perform
Providing resources
Providing training
Establishing the necessary organizations (i.e. new roles and
responsibilities)
SW-CMM 33
Activities
Planning of activities
Performing activities
Tracking activities
Taking corrective actions
Informing about activities and results
SW-CMM 34
Measurement and Analysis
SW-CMM 35
Verifying Implementation
Commitments
Policies
Processes
Documented procedures
SW-CMM 36
The Structure of CMM - Summary
Commitment
Ability
Verification
SW-CMM 37
The Repeatable Process
SW-CMM 38
Responsibilities at Level 2
SW-CMM 39
Moving to Level 2
Manage Commitments
SW-CMM 40
The Commitment Process
A commitment process is
Participation increases commitment the core of level 2
SW-CMM 41
The Repeatable Level
5. Optimizing
4. Managed
3. Defined
SW-CMM 42
Requirement Management
customer software
project
SW-CMM 43
Why Requirements Management?
The agreement
covers both technical and non-technical requirements
is the basis for estimating, planning, performing and tracking
xxxxx
xxx
xxxxx
SW-CMM 44
Requirements Management Goals
2. Software plans, products, and activities are kept consistent with the system
requirements allocated to software.
SW-CMM 45
Typical Problems
SW-CMM 46
What is Requirements Management
Software development
gather analyze/
specify
manage change
verify xxxx
xxx
xxxx.
SW-CMM 47
Maturity framework
Level 4:
Control process variation Managed
Level 3:
Install a common process Defined
Level 1:
Initial
SW-CMM 48
Level 3 - the Defined Process
SW-CMM 49
Moving to Level 3
Level 2:
Engineering
Repeatable management
SW-CMM 50
Problems to avoid on Level 3
SW-CMM 51
What is Defined?
SW-CMM 53
Moving to Level 4
Level 4:
Process Managed
control
Level 3:
Quantitative
Defined management
SW-CMM 54
What is Managed?
Control Chart
Upper performance boundary
SW-CMM 55
Level 5 - the Optimizing Process
SW-CMM 56
Moving to Level 5
Continuous Level 5:
process
improvement Optimizing
Level 4: Change
Managed management
SW-CMM 57
What is Optimizing
Initial
capability Upper performance boundary
Improved
capability
Lower performance boundary
SW-CMM 58
Management Visibility by Level
In Out
Level 5
Level 4 In Out
Level 3 In Out
Level 2 In Out
Level 1 In Out
SW-CMM 59
Process Capability by Level
Probability
target
Probability
target
4
Probability
target
3
Probability
target
2
target
Probability
1
SW-CMM 60
Changing the Organization
Organization
establishes
Organization
process
framework
y
Tr
lit
us
i
ab
t
St
Management Project
establishes reduces
Project
process process
discipline variation
Ad hoc, Individual
Inconsistent improves
Individual
undisciplined personal
process process
SW-CMM 61
Cultural Changes by CMM Level
SW-CMM 62
Experiences - Raytheon’s
Equipment Division
Raytheon’s Equipment Division, USA;
• 400 software engineers
• real-time embedded radar and air traffic control
Started with process improvements 1988
Level 2 1990
Level 3 1992
Level 4 1995
SW-CMM 63
Raytheon’s Cost Analysis Method
SW-CMM 64
Cost of Quality
SW-CMM 65
Return on Investment
Received a $9.600.000 bonus for early delivery on one system (not included in ROI
numbers!)
SW-CMM 66
Better quality
SW-CMM 67
Higher productivity
SW-CMM 68
Predictability
SW-CMM 69
SEI data and experiences
CBA IPIs and SPAs conducted since 1987 through June 2002 and
reported to the SEI by July 2002:
2325 assessments
• 1840 CBA IPI
• 485 SPA
1756 organisations
512 different companies
451 reassessed organisations
9632 projects
Kilde: http://www.sei.cmu.edu/sema/pdf/2002aug.pdf
SW-CMM 70
SEI Industry Analysis results
Herbsleb et al 1994
SW-CMM 71
Characteristics of successful organizations
SW-CMM 72
Characteristics of less successful organizations
Turf guarding
Organizational politics
Cynicism from previously unsuccessful improvement experiences
Beliefs that SPI gets in the way of real work
Need more guidance on how to improve, not just what
SW-CMM 73
More info
http://www.sei.cmu.edu/activities/cmm/cmm.articles.html
SW-CMM 74