Process Management • Process Management in software started in late 1960’s (but informally and inconsistently) • Software Engineering Institute (SEI) is the center • Watts Humphrey (retired IBMer who joined SEI) was a key proponent of: (in sequential order) – CMM (capability maturity model) • Process maturity of organization – PSP (personal software process) • Process maturity of individual – CMMI (capability maturity model integrated) • Follow-on to CMM
32
Embed
Process Management Process Management in software started in late 1960’s (but informally and inconsistently) Software Engineering Institute (SEI) is the.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Process Management
• Process Management in software started in late 1960’s (but informally and inconsistently)
• Software Engineering Institute (SEI) is the center • Watts Humphrey (retired IBMer who joined SEI)
was a key proponent of:
(in sequential order)
– CMM (capability maturity model)• Process maturity of organization
– PSP (personal software process)• Process maturity of individual
– CMMI (capability maturity model integrated)• Follow-on to CMM
A Quick Overview of CMM
(How You May Want to “Manage”
Change & Certification)
Software Engineering Institute (SEI)
Federally Funded Research & Development Center (FFRDC) at Carnegie Mellon University
Mission is to foster improvement of software processes
Developed Capability Maturity Model and Assessment Methodology
Educate “Authorized Lead Assessors” and organizations
Many Assessors have been leading process improvement efforts since 1987
Process Management Premise
• An undefined process cannot be controlled (or measured)
• An uncontrolled process cannot be improved
• Attempting to improve an unstable process yields further instability
ControlControl
ExecuteProcess
ExecuteProcess
DefineDefine
Adapted from SEI
MeasureMeasure
ImproveImprovestart
A 5 Step Approach to Software Process Improvement (SPI)
SetContext
BuildSponsorship
CharterInfrastructure
CharacterizeCurrent &Desired States
DevelopRecommendations
SetPriorities Develop
Approach
PlanActions
CreateSolution
Pilot/TestSolution
RefineSolution
ImplementSolution
AnalyzeandValidate
ProposeFutureActions
Stimulus for Change
Initiating
Diagnosing
Establishing
Acting
Learning
IDEALSM
Meeting Your Business (SPI) GoalsWith (some)Assessor’s Products and Services
-SEPG Development & Guidance
-Strategic &Tactical Planning
-Pilot Projects
-Process Templates
-Post-Assessment Consulting-Process Implementation Plan
-CMM Training
-KPA/Process Improvement Training
-CBA -IPI (CMM based- internal process improvement assessment)
-Executive Briefing
-CMM Profiles(Pre-Assessments)
-Pre-Assessment ConsultingInitiating
Diagnosing (Assessing)
Establishing
Acting
Learning-Measurement Programs
-Action Planning Workshop
-Process Definition
BehavioralCharacteristics
ManagementProcess
Engineering Process
QuantitativeUnderstanding
ContinuousImprovement
Focus
Improvement Framework
Capability Maturity ModelSM Version 1.1
Disciplined
Consistency
Quantifiable Predictability
Total Organization Involvement
Chaos
Repeatable - Level 2
Defined - Level 3
Initial - Level 1
Managed - Level 4
Optimizing - Level 5
RISK
Productivity and Quality
Improvement Framework
Organization Process Focus Organization Process DefinitionTraining Program Integrated Software ManagementSoftware Product Engineering Intergroup CoordinationPeer Reviews
Repeatable - Level 2
Defined - Level 3
Initial - Level 1: (no process!)
Quantitative Process ManagementSoftware Quality Management
Why Use The CMM?• Provides a framework for: benchmarking the process and the
organization
• CMM is not prescriptive; it does not tell an organization how to improve
– Provides good “common sense” engineering and management practices
– The key practices do not
• Limit the choice of life cycle
• Require or preclude specific software technologies or language (e.g., prototyping, design method, coding or testing practices)
• Require that documentation conform to any particular set of standards
• The key practices are the result of “national consensus”– Use of standardized language and goals
Early Reported Benefits
Results of Software Process Improvement in 13 Organizations
Category Range Median
Productivity gain per year 9% - 67% 35%Early error detection gain per year 6% - 25% 22% (defects discovered pre-test)
Yearly reduction in time to market 15% - 23% 19%Yearly reduction in post-release 10% - 94% 39% defect reportsValue returned on each dollar invested 4.0 - 8.8 5.0
Source: Software Engineering Institute, 1994 ----- 17 years ago
Process Maturity “Spanning the Years”
80%
12%7%
1%
1%
55%26%
15%
3%
1%
Level 1Level 2Level 3Level 4Level 5
Legend
Level 1
Level 1
Level 3
1987 - 1991
19981987 - 1991 1998
92%
7%
2%
81%
15%
4%
129 Organizations
951 OrganizationsThere was a 737% increase in the number of organizations assessed from 1987 through 1998
Trends in Process Maturity*
0
100
200
300
400
500
600
Initial Repeatable Defined Managed Optimizing
Organizations Assessed1987-1998
1987 - 1991 129
1992 219
1993 317
1994 414
1995 506
1996 632
1997 782
1998 951
Year Org.
Nu
mb
er
of
As
se
ss
me
nts
* Extracted from SEI’s Process Maturity Profile of the Software Community Assessments through December 1998
10 (1%)
28 (3%)
143 (15%)
247 (26%)
523 (55%)
Maturity Profile by Organization Type
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
Initial Re peatable Defined Managed Optimizing
Commercial DOD/Fede ral Contractor Mi litary/Fede ral Othe r/Unknown
* Extracted from SEI’s Process Maturity Profile of the Software Community Assessments through December 1998
Assessment Overview• CMM Profile:
– Informal quantitative evaluation
– Excellent mechanism as a interim or pre-assessment
– Non-intrusive to organization
– Guidance on recommended process improvements
– Results not forwarded to SEI
– Typically a 3-5 day activity
• CBA IPI (CMM Based Assessment Internal Process Improvements):
– Formal Assessment
– Automated approach saving your organization up to 40% time/effort
Based on 1104 organizations who reported size (employees in software development & maintenance)
1 to 10045.9 %
201 to 2000+ 30.3%
101 to 200 23.8%
Personal Software Process(championed by W. Humphrey)
• Understanding the person’s individual – Productivity
– Skills
– Methodology
• Keeping track of the person’s individual– Efforts (e.g. requirements, design, coding, testing, etc.)
– Quality (errors and fixes)
• Allows improvements in– Estimation
– Task performance
CMMI (CMM Integrated)• CMMI model is a fairly recent extension/modification of CMM
(developed around 2002 and still growing & changing)• We are interested in CMMI for Software Engineering. (there
are others such as CMMI for Systems Engineering, Supplier Sourcing, and Integrated Product and Process Development)
• There are 2 models : i) Staged and ii) Continuous– Different levels
• 5 levels for Staged• 6 levels for Continuous
– 25 major processes grouped into 4 categories:• Organizational• Project management• Engineering• Support Category
– There are Goals and Practices for Each Process – to be satisfied for both models
Levels for Continuous versus Staged Models
– A. Continuous model has 6 capability levels where each process moves through these 6 different levels of capability:
• Level (0) Incomplete – not performed or partially performed• (1) Performed - perform the basic practice• (2) Managed - institutionalized process (performed according to policy)• (3) Defined - tailored & institutionalized specifically to the organization • (4) Quantitatively Managed – process is quantitatively managed• (5) Optimizing – process is continuously improved and adapted
– B. Staged model has 5 maturity levels (like traditional CMM) each of which contains different processes that must be mastered:
Levels for Continuous versus Staged models in CMM I
Level 5
Level 4
Level 3
Level 2
Level 1
Level 0
Continuous(Capability Levels)
Staged(Maturity Levels)
Incomplete
Performed
Managed
Defined
Quantitatively Managed
Optimizing
Quantitatively Managed
Initial
Managed
Defined
Optimizing
- - - - - -
4 CMMI Process Areas• Process Management (5 processes)
– Organizational Process Focus– Organizational Process Definition– Organizational Training– Organizational Process Performance– Organizational Innovation and Deployment