introduction to the software engineering institute’s (sei) capability maturity model (cmm) global...

Introduction to the Software Engineering Institute’s (SEI) Capability Maturity Model (CMM) Introduction to the Software Engineering Institute’s (SEI) Capability Maturity Model (CMM)

Global Systems Technology, Inc. © 1997, 1998Global Systems Technology, Inc. © 1997, 199811

GST

Understanding the Understanding the

Defined LevelDefined Level

of Process Maturityof Process Maturity

(Cont’) Day 3(Cont’) Day 3

Global Systems Technology, Inc.Global Systems Technology, Inc.IN

TE

RG

RO

UP

CO

OR

DIN

AT

ION

ORGANIZATION

PROCESS

DEFINITION

SOFTWARE

PROCESS

ENGINEERING

TRAINING PROGRAM

INTE

GR

ATE

D

SOFT

WA

RE

MA

NA

GEM

ENT

PEER

REVIEW

ORGANIZATION

PROCESSFOCUS



GST

Global Systems Technology, Inc.Global Systems Technology, Inc.

REQUIREMENTSMANAGEMENT

SOFTWAREPROJECTPLANNING

SOFTWAREPROJECT

TRACKINGAND OVERSIGHT

SOFTWARESUBCONTRACTMANAGEMENT

SOFTWAREQUALITY

ASSURANCE

SOFTWARECONFIGURATION

MANAGEMENT

Defined Level of Process MaturityDefined Level of Process Maturity

ORGANIZATIONPROCESS

FOCUS

ORGANIZATIONPROCESS

DEFINITION

TRAININGPROGRAM

INTEGRATEDSOFTWARE

MANAGEMENT

SOFTWAREPRODUCT

ENGINEERING

INTERGROUPCOORDINATION

PEERREVIEW



GST

Integrated Software Management (ISM)Integrated Software Management (ISM)

Purpose is to integrate the project’s software engineering Purpose is to integrate the project’s software engineering and management activities into a coherent, defined and management activities into a coherent, defined software process documented by tailoring the software process documented by tailoring the organization’s software process assetsorganization’s software process assets

InvolvesInvolves• developing the project’s defined software process by developing the project’s defined software process by

tailoring the organization’s standard software processtailoring the organization’s standard software process• managing the software project according to this defined managing the software project according to this defined

software processsoftware process




GST

Integrated Software Management (ISM)Integrated Software Management (ISM)


Policy

OrganizationProcedures

&Work aids

Vol. 12

OrganizationAnd ProjectManagement

PracticesProcedures

Vol. 2

OrganizationEngineering

PracticesProcedures

Vol. 3

Adaptation of theengineering

practicesto the specificneeds of the

project

IntegratedProjectManagementPractices

Project Plan

By Reference, as appropriate



GST

Integrated Software Management (ISM) Integrated Software Management (ISM) GoalsGoals

Goal 1: The project’s defined software process is a Goal 1: The project’s defined software process is a tailored version of the organization’s standard tailored version of the organization’s standard software processsoftware process

Goal 2: The project is planned and managed Goal 2: The project is planned and managed according to the project’s defined software process.according to the project’s defined software process.




GST

Tailoring Organization ProcessesTailoring Organization Processes At Level 3, each project tailors the organization’s At Level 3, each project tailors the organization’s

standard software process for their particular needsstandard software process for their particular needs• includes software life cycles, standards, procedures, etc.includes software life cycles, standards, procedures, etc.• uses the lessons learned and data from previous projectsuses the lessons learned and data from previous projects• feeds back appropriate measurement data and documents to feeds back appropriate measurement data and documents to

the organization for use by other projectsthe organization for use by other projects• assesses project needs and customer requirements to select assesses project needs and customer requirements to select

and modify the appropriate subset of organization processesand modify the appropriate subset of organization processes

Tailoring can be accomplished with appropriate Tailoring can be accomplished with appropriate allocation of funds to project’s tasks allocation of funds to project’s tasks




GST

Project Management Process Project Management Process EvolvesEvolves

Software development plan is now based on the Software development plan is now based on the organization’s defined software process as tailored organization’s defined software process as tailored by the projectby the project

Projects can use and share process data and lessons Projects can use and share process data and lessons learned across the organization as the process base learned across the organization as the process base is common across all projectsis common across all projects

Integrated Software Management is the evolution of Integrated Software Management is the evolution of Software Project Planning and Software Project Software Project Planning and Software Project Tracking and Oversight key process areasTracking and Oversight key process areas




GST

Integrated Software Management (ISM) ActivitiesIntegrated Software Management (ISM) Activities

Activity 1:Activity 1: The project’s defined software process is developed The project’s defined software process is developed by tailoring the organization’s standard software process by tailoring the organization’s standard software process according to a documented procedure. according to a documented procedure.

Activity 2:Activity 2: Each project’s defined software process is revised Each project’s defined software process is revised according to a documented procedure. according to a documented procedure.

Activity 3:Activity 3: The project’s software development plan, which The project’s software development plan, which describes the use of the project’s defined software process, is describes the use of the project’s defined software process, is developed and revised according to a documented procedure. developed and revised according to a documented procedure.

Activity 4:Activity 4: The software project is managed in accordance with The software project is managed in accordance with the projects defined software process. the projects defined software process.

Activity 5:Activity 5: The organization’s software process database is The organization’s software process database is used for software planning and estimating. used for software planning and estimating.




GST

Integrated Software Management (ISM) ActivitiesIntegrated Software Management (ISM) Activities Activity 6:Activity 6: The size of the software work products (or size of The size of the software work products (or size of

changes to the software work products) is managed according to changes to the software work products) is managed according to a documented procedure. a documented procedure.

Activity 7:Activity 7: The project’s software effort and cost are managed The project’s software effort and cost are managed according to a documented procedure. according to a documented procedure.

Activity 8:Activity 8: The project’s software critical computer resources are The project’s software critical computer resources are managed according to a documented procedure. managed according to a documented procedure.

Activity 9:Activity 9: The critical dependencies and critical paths of the The critical dependencies and critical paths of the project’s software schedule are managed to a documented project’s software schedule are managed to a documented procedure. procedure.

Activity 10:Activity 10: The project’s software are identified, assessed, The project’s software are identified, assessed, documented, and managed according to a documented procedure. documented, and managed according to a documented procedure.




GST

Integrated Software Management (ISM) ActivitiesIntegrated Software Management (ISM) Activities Activity 11:Activity 11: Reviews of the software project are periodically Reviews of the software project are periodically

performed to determine the actions needed to bring the software performed to determine the actions needed to bring the software project’s performance and results in line with the current and project’s performance and results in line with the current and projected needs of the business, customer, and end users, as projected needs of the business, customer, and end users, as appropriate.appropriate.




GST

Barriers to ISMBarriers to ISM

An organization standard software process does not An organization standard software process does not existexist

Organizational assets are hard to retrieve and useOrganizational assets are hard to retrieve and use

Key individuals do not understand tailoring issuesKey individuals do not understand tailoring issues

Organization personnel have not been adequately Organization personnel have not been adequately trained in the organization’s processestrained in the organization’s processes

Underlying processes are too “generic” so that Underlying processes are too “generic” so that interpretation can be universally appliedinterpretation can be universally applied




GST

Software Product Engineering (PE, SPE)Software Product Engineering (PE, SPE)

Purpose is to consistently perform a well-defined Purpose is to consistently perform a well-defined engineering process that integrates all the software engineering process that integrates all the software engineering activities to produce correct, consistent engineering activities to produce correct, consistent software products effectively and efficientlysoftware products effectively and efficiently

InvolvesInvolves• performing the engineering to build and maintain the performing the engineering to build and maintain the

software using appropriate tools and methodssoftware using appropriate tools and methods• All appropriate tasks from the analysis of the system All appropriate tasks from the analysis of the system

requirements allocated to software to requirements allocated to software to




GST

Software Product Engineering (PE, SPE)Software Product Engineering (PE, SPE)


Not included:•User Needs Analysis•Requirements Definition•System Requirements•System Design•Risk Management

Not included:•Systems Testing•Implementation Support•Customer Support•User Training

QualityReviews

PeerReviews

TechnicalReviews

ManagementReviews

Software Engineering•Analyze system requirements allocated to software•Develop software requirements•Develop high-level software design•Develop detailed software design•Develop code •Unit testing•Integration of software elements•Integration testing•Test of software product (software system)•Demonstration testing for customer acceptance

FBL

ABL

PBL



GST

Software Product Engineering (PE, SPE) GoalsSoftware Product Engineering (PE, SPE) Goals

Goal 1: The software engineering tasks are defined, Goal 1: The software engineering tasks are defined, integrated, and consistently performed to produce integrated, and consistently performed to produce the software.the software.

Goal 2: Software work products are kept consistent Goal 2: Software work products are kept consistent with each other.with each other.




GST

•Planning•Establish Project

Plans

•Project Management•Risk Management

Reviews•Business Functions

Project Life Cycle and the CMMProject Life Cycle and the CMM


•Analyze Client Needs•Define System Requirements

•Develop System Design•Allocate System Requirements

To Software•Review Allocated Requirements•Define Software Requirements •Agree to System Requirements

Allocated to Software (FBL)

•Develop Software High-Level Design•Develop Software Low-Level Design

•Agree to High Level Design (ABL)•Develop Code

•Perform Unit Testing•Integrate Software Elements

•Test Integrated Elements•Test Software System•Software Acceptance

Testing•Customer Software

Acceptance (PBL)

•Integrate Software Into System•Test System

•Systems Acceptance Testing• Customer Acceptance of System

•Implementation Support•User Training

•Customer Life-cycle Support

•Quality Assurance•Configuration Management•Subcontract Management

•Peer Reviews

•Quantitative Process Management

•Software QualityManagement

OrganizationManagement

•Process Definition•Process Focus

•Training

•Defect Prevention•Technology Change

Management•Process Change

Management

Development of Project Processes

Coordination Between Groups

Organization Oversight



GST

Work Product DocumentationWork Product Documentation Addresses needs which span the life cycleAddresses needs which span the life cycle

Customer and end user documentation includes:Customer and end user documentation includes:• user manualsuser manuals• training materialstraining materials• operator manualsoperator manuals

Developer/maintainer documentation includes:Developer/maintainer documentation includes:• software requirements documentssoftware requirements documents• specification documentsspecification documents• design documentsdesign documents• test documentstest documents• Software maintenance manualsSoftware maintenance manuals




GST

Consistency and Traceability of Project Work Consistency and Traceability of Project Work ProductsProducts

Consistency and traceability among documents are Consistency and traceability among documents are critical to their usefulnesscritical to their usefulness

If specifications are not consistent, they are not If specifications are not consistent, they are not usableusable

If the relationship between documents is not clearly If the relationship between documents is not clearly traceable, their usefulness is minimizedtraceable, their usefulness is minimized




GST

Software Product Engineering (PE, SPE) ActivitiesSoftware Product Engineering (PE, SPE) Activities

Activity 1:Activity 1: Appropriate software engineering methods and tools Appropriate software engineering methods and tools are integrated into the project’s defined software process. are integrated into the project’s defined software process.

Activity 2:Activity 2: The software requirements are developed, The software requirements are developed, maintained, documented, and verified by systematically maintained, documented, and verified by systematically analyzing the allocated requirements according to the project’s analyzing the allocated requirements according to the project’s defined software process. defined software process.

Activity 3:Activity 3: The software design is developed, maintained, The software design is developed, maintained, documented, and verified according to the project’s defined documented, and verified according to the project’s defined software process, to accommodate the software requirements software process, to accommodate the software requirements and to form the framework for coding. and to form the framework for coding.




GST

Software Product Engineering Software Product Engineering (PE, SPE)(PE, SPE) ActivitiesActivities

Activity 4:Activity 4: The software code is developed, maintained, The software code is developed, maintained, documented, and verified, according to the project’s defined documented, and verified, according to the project’s defined software process to implement the software requirements and software process to implement the software requirements and software design. software design.

Activity 5:Activity 5: Software testing is performed according to the Software testing is performed according to the project’s defined software process. project’s defined software process.

Activity 6:Activity 6: Integration testing of the software is planned and Integration testing of the software is planned and performed according to the projects defined software process. performed according to the projects defined software process.

Activity 7:Activity 7: System and acceptance testing of the software are System and acceptance testing of the software are planned and performed to demonstrate that the software planned and performed to demonstrate that the software satisfies its requirements. satisfies its requirements.




GST

Software Product Engineering (PE, SPE) ActivitiesSoftware Product Engineering (PE, SPE) Activities

Activity 8:Activity 8: The documentation that will be used to operate and The documentation that will be used to operate and maintain the software is developed and maintained according to maintain the software is developed and maintained according to the project’s defined software process. the project’s defined software process.

Activity 9:Activity 9: Data on defects identified in peer reviews and testing Data on defects identified in peer reviews and testing are collected and analyzed according to the project’s defined are collected and analyzed according to the project’s defined software process. software process.

Activity 10:Activity 10: Consistency is maintained across software work Consistency is maintained across software work products, including the software plans, process descriptions, products, including the software plans, process descriptions, allocated requirements, software requirements, software design allocated requirements, software requirements, software design code, test plans, and test procedures. code, test plans, and test procedures.




GST

Barriers to Software Product Engineering Barriers to Software Product Engineering (PE, SPE)(PE, SPE)

Incompatible, ineffective, and inefficient tools and Incompatible, ineffective, and inefficient tools and methodsmethods

Schedule pressureSchedule pressure

““Not invented here” philosophyNot invented here” philosophy

Unrealistic expectationsUnrealistic expectations

Client intervention (dynamic requirements)Client intervention (dynamic requirements)

Experience of the development teamExperience of the development team




GST

Intergroup Coordination (ICIntergroup Coordination (IC))

Purpose is to establish a means for the software Purpose is to establish a means for the software engineering group to participate actively with the engineering group to participate actively with the other engineering groups so the project is better able other engineering groups so the project is better able to satisfy the customer’s needs effectively and to satisfy the customer’s needs effectively and efficientlyefficiently

InvolvesInvolves• disciplined interaction and coordination of the project disciplined interaction and coordination of the project

engineering groups with each other to address system-engineering groups with each other to address system-level requirements, objectives, and planslevel requirements, objectives, and plans




GST

Intergroup Coordination (IC)Intergroup Coordination (IC)


Systems and Hardware Engineering

Quality Assurance

Facilities

Marketing

ProjectTeam



GST

Intergroup Coordination (IC) GoalsIntergroup Coordination (IC) Goals

Goal 1: The customer’s requirements are agreed to Goal 1: The customer’s requirements are agreed to by all affected groups.by all affected groups.

Goal 2: The commitments between the engineering Goal 2: The commitments between the engineering groups are agreed to by the affected groups.groups are agreed to by the affected groups.

Goal 3: The engineering groups identify, track, and Goal 3: The engineering groups identify, track, and resolve intergroup issues.resolve intergroup issues.




GST

Inputs:

Human,Financial,Technological,Material,Resources

Organization GroupsOrganization Groups

The World of a Project

Outputs:

ProductsServices

StrategicSubsystem

Human/Cultural Subsystem Structural

Subsystem

Technology Subsystem

ManagerialSubsystem

Organizational System




GST

Ongoing Working RelationshipsOngoing Working Relationships ““Commitments” between groups are Commitments” between groups are

documented and agreed to by all groupsdocumented and agreed to by all groups

Intergroup Coordination can be:Intergroup Coordination can be:• as minimal as one or two meetings between as minimal as one or two meetings between

interproject (development and test) groupsinterproject (development and test) groups• as extensive as “integrated product teams”or as extensive as “integrated product teams”or

Joint Application Development (JAD) teams Joint Application Development (JAD) teams (where hardware, systems, software and product (where hardware, systems, software and product assurance, coordinate product development)assurance, coordinate product development)




GST

Interdisciplinary GroupsInterdisciplinary Groups The software engineering groups actively interface with The software engineering groups actively interface with

a variety of groupsa variety of groups

Examples of these groups, to whom the interface must Examples of these groups, to whom the interface must be managed include:be managed include:• systems engineeringsystems engineering

• marketingmarketing

• trainingtraining

• subcontract managementsubcontract management

Intergroup Coordination is a first step on the road to Intergroup Coordination is a first step on the road to concurrent engineering concurrent engineering




GST

Intergroup Coordination (IC) Goals ActivitiesIntergroup Coordination (IC) Goals Activities

Activity 1:Activity 1: The software engineering group and the other The software engineering group and the other engineering groups participate with the customer and end users, engineering groups participate with the customer and end users, as appropriate, to establish the system requirements. as appropriate, to establish the system requirements.

Activity 2:Activity 2: Representatives of the project’s software engineering Representatives of the project’s software engineering group work with representatives of the other engineering groups group work with representatives of the other engineering groups to monitor and coordinate technical activities and resolve to monitor and coordinate technical activities and resolve technical issues. technical issues.

Activity 3:Activity 3: A documented plan is used to communicate intergroup A documented plan is used to communicate intergroup commitments and to coordinate and track the work performed. commitments and to coordinate and track the work performed.

Activity 4:Activity 4: Critical dependencies between engineering groups are Critical dependencies between engineering groups are identified, negotiated and tracked according to a documented identified, negotiated and tracked according to a documented procedure. procedure.




GST

Intergroup Coordination (IC) Goals ActivitiesIntergroup Coordination (IC) Goals Activities

Activity 5: Activity 5: Work products produced as input to other Work products produced as input to other engineering groups are reviewed by representatives of the engineering groups are reviewed by representatives of the receiving groups to ensure that the work products meet their receiving groups to ensure that the work products meet their needs. needs.

Activity 6: Activity 6: Intergroup issues not resolvable by the individual Intergroup issues not resolvable by the individual representatives of the project engineering groups are handled representatives of the project engineering groups are handled according to a documented procedure. according to a documented procedure.

Activity 7:Activity 7: Representatives of the project engineering groups Representatives of the project engineering groups conduct periodic technical reviews and interchanges. conduct periodic technical reviews and interchanges.




GST

Barriers to Intergroup CoordinationBarriers to Intergroup Coordination

Rigid organizational structure with communication Rigid organizational structure with communication barriersbarriers

Lack of mutual respect between the different groupsLack of mutual respect between the different groups

Battles over responsibility, authority, and Battles over responsibility, authority, and accountabilityaccountability




GST

Peer Reviews Peer Reviews (PR)(PR)

Purpose is to remove defects from the software Purpose is to remove defects from the software work products early and efficiently. An important work products early and efficiently. An important corollary effect is to develop a better corollary effect is to develop a better understanding of the work products and of understanding of the work products and of defects that might be preventeddefects that might be prevented

InvolvesInvolves• methodical examination of work products by the methodical examination of work products by the

producer’s peers to identify defects and areas where producer’s peers to identify defects and areas where changes are neededchanges are needed




GST

Peer Reviews Peer Reviews (PR)(PR)


As simple as anInformal one-on-one

Moderator Notes,Minutes,

&ActionItems

Reviewer(Develop)

Reviewer(QA)

Reviewer(Test)

Presenter, Software Developer

Module 15.3 Add A to Z Z Minus (B+C) Z=TotalModule 15.4

As complex as aformal Inspection

OR



GST

Peer Reviews Peer Reviews (PR)(PR) Goals Goals

Goal 1: Peer review activities are planned.Goal 1: Peer review activities are planned.

Goal 2: Defects in the software work products are Goal 2: Defects in the software work products are identified and removed.identified and removed.




GST

Return on InvestmentReturn on Investment Finding and fixing defects early in the life Finding and fixing defects early in the life

cycle is cost effective.cycle is cost effective.• approximately 100 times less expensive to find approximately 100 times less expensive to find

and fix a defect in development rather than and fix a defect in development rather than delivered system maintenancedelivered system maintenance

• peer reviews can find anywhere from 50 to 90% of peer reviews can find anywhere from 50 to 90% of product defects prior to testingproduct defects prior to testing

• Formality of peer review should be scaled to the Formality of peer review should be scaled to the needs of the project needs of the project (What should be considered?)(What should be considered?)




GST

Performing Peer ReviewsPerforming Peer Reviews Plan, budget and schedule peer reviews in the Project PlanPlan, budget and schedule peer reviews in the Project Plan Train leaders and participantsTrain leaders and participants Give material to reviewers in advance or reviewGive material to reviewers in advance or review Assign each reviewer a specified roleAssign each reviewer a specified role Specify criteria to begin and end reviewsSpecify criteria to begin and end reviews Use pre-planned checklistsUse pre-planned checklists Identify action items and track to closureIdentify action items and track to closure Collect and analyze data for product quality trends and Collect and analyze data for product quality trends and

effectiveness of peer review processeffectiveness of peer review process




GST

Alternative Peer Review MethodsAlternative Peer Review Methods

Possible alternative ways of implementing Possible alternative ways of implementing peer reviews include:peer reviews include:• Fagan style inspectionsFagan style inspections• structured walkthroughsstructured walkthroughs• active reviewsactive reviews• phased inspectionsphased inspections




GST

Peer Reviews Peer Reviews (PR)(PR) Activities Activities

Activity 1:Activity 1: Peer reviews are planned, and the plans are Peer reviews are planned, and the plans are documented. documented.

Activity 2:Activity 2: Peer reviews are performed according to a Peer reviews are performed according to a documented procedure. documented procedure.

Activity 3:Activity 3: Data on the conduct and results of the peer Data on the conduct and results of the peer reviews are recorded. reviews are recorded.




GST

Barriers to Peer ReviewsBarriers to Peer Reviews

Belief that peer reviews are too expensiveBelief that peer reviews are too expensive

Schedule pressureSchedule pressure

Hostile reviewsHostile reviews

Untrained participantsUntrained participants




GST


Emphasis shifts to organizationEmphasis shifts to organization

Organization Process FocusOrganization Process Focus• coordinate software process improvement coordinate software process improvement

activitiesactivities• identify strengths and weaknesses of processesidentify strengths and weaknesses of processes• plan organization’s software process improvement plan organization’s software process improvement

effortsefforts




GST


Organization Process DefinitionOrganization Process Definition• develop and maintain an organization’s standard software develop and maintain an organization’s standard software

processprocess• collect, review and distribute data and documents related to collect, review and distribute data and documents related to

the organization's standard software processthe organization's standard software process

Training ProgramTraining Program• plan organizational training activitiesplan organizational training activities• provide training for developing skills and knowledge for the provide training for developing skills and knowledge for the

organizationorganization• ensure that individuals are trainedensure that individuals are trained




GST


Integrated Software ManagementIntegrated Software Management• develop the project’s defined software processdevelop the project’s defined software process• manage the project according to a plan which manage the project according to a plan which

includes the project’s defined software processincludes the project’s defined software process

Software Product EngineeringSoftware Product Engineering• perform software activities in a defined, integrated perform software activities in a defined, integrated

and consistent mannerand consistent manner• ensure consistency among productsensure consistency among products




GST


Intergroup CoordinationIntergroup Coordination• involve all affected groupsinvolve all affected groups• ensure commitments are agreed to by all affected ensure commitments are agreed to by all affected

partiesparties• identify, track and resolve intergroup issuesidentify, track and resolve intergroup issues

Peer ReviewsPeer Reviews• plan and fund peer review activitiesplan and fund peer review activities• identify and remove defects as early as possibleidentify and remove defects as early as possible




GST


Managed LevelManaged Level



QUANTITATIVE PROCESS

MANAGEMENT

SOFTWARE QUALITY MANAGEMENT



GST




SOFTWAREPROJECT



SOFTWAREQUALITY

ASSURANCE


MANAGEMENT

Managed Level of Process MaturityManaged Level of Process Maturity

ORGANIZATIONPROCESS

FOCUS

ORGANIZATIONPROCESS

DEFINITION

TRAININGPROGRAM

INTEGRATEDSOFTWARE

MANAGEMENT

SOFTWAREPRODUCT

ENGINEERING


PEERREVIEW

QUANTITATIVE PROCESSMANAGEMENT

SOFTWARE QUALITYMANAGEMENT



GST

Moving from Level 3 to Level 4Moving from Level 3 to Level 4

At Level 3, measurements have been defined At Level 3, measurements have been defined and collected systematicallyand collected systematically

At Level 4 At Level 4 decisionsdecisions are made based on are made based on data data collectedcollected• common measurementcommon measurement• data analysisdata analysis




GST

Understanding the Understanding the Managed Maturity LevelManaged Maturity Level

Control Chart with Special Causes

Applies the principles of statistical process controland addresses special causes of process variation

Fix the processproblem


Range of Normal Process Variation



GST

Product and Process Are Quantitatively Product and Process Are Quantitatively ManagedManaged

In Out

Management has an objective basis for making decisionsManagement is able to predict performance withinquantified bounds




GST

Quantitative Process Management (QP, QPM)Quantitative Process Management (QP, QPM)

Purpose is to control the process performance of the Purpose is to control the process performance of the software project quantitativelysoftware project quantitatively

InvolvesInvolves• establishing goals for process performanceestablishing goals for process performance• measuring the performance of the projectmeasuring the performance of the project• analyzing these measurementsanalyzing these measurements• making adjustments to maintain process performance within making adjustments to maintain process performance within

acceptable limits.acceptable limits.




GST



1stQtr

2ndQtr

3rdQtr

4thQtr

Task A

Task B

Task C

TodayOverrun

Status of Project

Independent ReviewsOf Project

Quantitative UnderstandingOf Process

Understand Status:• Determine causes of not making goals• Review possible courses of action• Determine how to get back on path to goals

PlannedActualEstimate

Decisive Course of Action



GST


Goal 1: The quantitative process management Goal 1: The quantitative process management activities are planned.activities are planned.

Goal 2: The process performance of the project’s Goal 2: The process performance of the project’s defined software process is controlled quantitatively.defined software process is controlled quantitatively.

Goal 3: The process capability of the organization’s Goal 3: The process capability of the organization’s standard software process is known in quantitative standard software process is known in quantitative terms.terms.




GST

Controlling Special Causes of VariationControlling Special Causes of Variation

An important concern is identifying variations in An important concern is identifying variations in performance that are not within the normal range of performance that are not within the normal range of process performanceprocess performance• ““extraordinary” events outside the bounds of normal extraordinary” events outside the bounds of normal

process capabilityprocess capability

Control Chart with Special Causes




GST

Taking Corrective Action at Level 4Taking Corrective Action at Level 4

Quantitative Process Management focuses Quantitative Process Management focuses on the processon the process

Process capability is quantitatively knownProcess capability is quantitatively known

When performance falls outside the limits:When performance falls outside the limits:• the reason is identifiedthe reason is identified• corrective action is taken, when appropriatecorrective action is taken, when appropriate




GST

The Meaning of Quantitative The Meaning of Quantitative ControlControl

Quantitative control in the CMM implies any Quantitative control in the CMM implies any quantitative or statistically-based techniquequantitative or statistically-based technique

The words “statistical and “quantitative” The words “statistical and “quantitative” imply dataimply data

Objective data reflect factsObjective data reflect facts

Fact-based management results in objective Fact-based management results in objective decisionsdecisions




GST

Basic StatisticsBasic Statistics

Quantitative, or statistical, techniques need Quantitative, or statistical, techniques need not be sophisticated to be useful.not be sophisticated to be useful.• Pareto analysis, for example, is fairly simplePareto analysis, for example, is fairly simple

Quantitative techniques do require:Quantitative techniques do require:• measurable datameasurable data• consistent data collectionconsistent data collection• defined, comparable measurementsdefined, comparable measurements




GST

The Basic Tool Set of Statistical Process ControlThe Basic Tool Set of Statistical Process Control

Deming identified seven quantitative tools Deming identified seven quantitative tools considered basic to statistical process or quality considered basic to statistical process or quality controlcontrol• histogramshistograms

• cause-and-effect (fishbone) diagramscause-and-effect (fishbone) diagrams

• check sheetscheck sheets

• Pareto diagramsPareto diagrams

• run charts (graphs)run charts (graphs)

• control chartscontrol charts

• scatter diagramsscatter diagrams




GST

Quantitative Process Management (QP, QPM) Quantitative Process Management (QP, QPM) ActivitiesActivities

Activity 1:Activity 1: The software project’s plan for quantitative process The software project’s plan for quantitative process management is developed according to a documented management is developed according to a documented procedure. procedure.

Activity 2:Activity 2: The software project’s quantitative process The software project’s quantitative process management activities are performed in accordance with the management activities are performed in accordance with the project’s quantitative process management plan. project’s quantitative process management plan.

Activity 3:Activity 3: The strategy for the data collection and the The strategy for the data collection and the quantitative analyses to be performed are determined based on quantitative analyses to be performed are determined based on the project’s defined software process. the project’s defined software process.

Activity 4:Activity 4: The measurement data used to control the project’s The measurement data used to control the project’s defined software process quantitatively are collected according defined software process quantitatively are collected according to a documented procedureto a documented procedure




GST

Quantitative Process Management (QP, QPM) Quantitative Process Management (QP, QPM) ActivitiesActivities

Activity 5:Activity 5: The project’s defined software process is analyzed The project’s defined software process is analyzed and brought under quantitative control according to a and brought under quantitative control according to a documented procedure. documented procedure.

Activity 6:Activity 6: Reports documenting the results of the software Reports documenting the results of the software project’s quantitative process management activities are project’s quantitative process management activities are prepared and distributed. prepared and distributed.

Activity 7:Activity 7: The process capability baseline for the The process capability baseline for the organization’s standard software process is established and organization’s standard software process is established and maintained according to a documented procedure.maintained according to a documented procedure.




GST

Barriers Quantitative Process ManagementBarriers Quantitative Process Management

Lack of supporting analysis trainingLack of supporting analysis training

Linear nature of software as opposed to Linear nature of software as opposed to cyclical nature of manufacturing cyclical nature of manufacturing

Too busy reacting to problems; no time to Too busy reacting to problems; no time to analyze themanalyze them

Client focus is on schedule, product; not on Client focus is on schedule, product; not on the underlying processthe underlying process




GST

Software Quality Management (QM, SQM)Software Quality Management (QM, SQM)

Purpose is to develop a quantitative understanding Purpose is to develop a quantitative understanding of the quality of the project’s software products and of the quality of the project’s software products and achieve specific quality goalsachieve specific quality goals

Involves:Involves:• defining quality goals for the software productsdefining quality goals for the software products• establishing plans to achieve these goalsestablishing plans to achieve these goals• monitoring and adjusting software plans, software work monitoring and adjusting software plans, software work

products, activities, and quality goals to satisfy the needs products, activities, and quality goals to satisfy the needs and desires of the customer and end-userand desires of the customer and end-user




GST

Software Quality Management (QM, SQM)Software Quality Management (QM, SQM)


Status of Product

Independent ReviewsOf Products

Quantitative UnderstandingOf Product Quality

Understand Product in Terms of Quality:• Review product problems (by type/impact)• Determine causes of common problems• Decide on what actions are appropriate

Decisive Courses of Action

1stQtr

2ndQtr

3rdQtr

4thQtr

0

5

10

15

20

25

1stQtr

2ndQtr

3rdQtr

4thQtr

Errors by Type/Time



GST

Software Quality Management (QM, SQM) Software Quality Management (QM, SQM) GoalsGoals

Goal 1: The project’s software quality management Goal 1: The project’s software quality management activities are planned.activities are planned.

Goal 2: Measurable goals for software product Goal 2: Measurable goals for software product quality and their priorities are defined.quality and their priorities are defined.

Goal 3: Actual progress toward achieving the quality Goal 3: Actual progress toward achieving the quality goals for the software products is quantified and goals for the software products is quantified and managed.managed.




GST

Building High Quality ProductsBuilding High Quality Products

Software Quality Management focuses on the Software Quality Management focuses on the productproduct

Measurable quality goals for the product are Measurable quality goals for the product are defineddefined

The product is “ready” when the goals are The product is “ready” when the goals are achievedachieved




GST

Quality EvolvesQuality Evolves At Level 2, the focus of quality is “conformance to At Level 2, the focus of quality is “conformance to

requirements”requirements” By Level 4, there is an emphasis on By Level 4, there is an emphasis on

understanding the needs of:understanding the needs of:• the customerthe customer• the end usersthe end users• the organizationthe organization

Ultimately the customer determines what quality Ultimately the customer determines what quality is or is notis or is not

Total Quality Management revolves around Total Quality Management revolves around customer satisfactioncustomer satisfaction




GST

Satisfactory KnowledgeSatisfactory Knowledge

““When you can measure what you are speaking When you can measure what you are speaking about, and express it in numbers, you know about, and express it in numbers, you know something about it; but when you cannot measure it, something about it; but when you cannot measure it, when you cannot express it in numbers, your when you cannot express it in numbers, your knowledge is of a meager and unsatisfactory kind.”knowledge is of a meager and unsatisfactory kind.”

Lord Kelvin




GST

Software Quality Management (QM, SQM) Software Quality Management (QM, SQM) ActivitiesActivities

Activity 1:Activity 1: The project’s software quality plan is developed and The project’s software quality plan is developed and maintained according to a documented procedure. maintained according to a documented procedure.

Activity 2:Activity 2: The project’s software quality plan is the basis for The project’s software quality plan is the basis for the project’s activities for software quality management. the project’s activities for software quality management.

Activity 3:Activity 3: The project’s quantitative quality goals for the The project’s quantitative quality goals for the software products are defined, monitored, and revised software products are defined, monitored, and revised throughout the software life cycle. throughout the software life cycle.




GST

Software Quality Management (QM, SQM) Software Quality Management (QM, SQM) ActivitiesActivities

Activity 4:Activity 4: The quality of the project’s software products is The quality of the project’s software products is measured, analyzed, and compared to the products’ measured, analyzed, and compared to the products’ quantitative quality goals on an event-driven basis. quantitative quality goals on an event-driven basis.

Activity 5:Activity 5: The software project’s quantitative quality goals for The software project’s quantitative quality goals for the products are allocated appropriately to the subcontractors the products are allocated appropriately to the subcontractors delivering software products to the project. delivering software products to the project.




GST

Barriers Software Quality ManagementBarriers Software Quality Management

Lack of supporting analysis trainingLack of supporting analysis training

Inability to distinguish between change and Inability to distinguish between change and improvement improvement

Testing, analysis identifies errors, does not Testing, analysis identifies errors, does not prove the the absence of errorsprove the the absence of errors

Client focus is on schedule; product use, Client focus is on schedule; product use, assumes product is error freeassumes product is error free




GST

At the Managed LevelAt the Managed Level Data is collected and analyzed throughout the Data is collected and analyzed throughout the

projects in the organizationprojects in the organization

Measurable product quality goals are defined Measurable product quality goals are defined and usedand used

When performance falls outside expected When performance falls outside expected limits, something is donelimits, something is done

The quality focus is on customer satisfactionThe quality focus is on customer satisfaction




GST


Optimized LevelOptimized Level



PROCESS CHANGE

MANAGEMENT

TECHNOLOGY CHANGE

MANAGEMENT

DEFECT

PREVENTION



GST




SOFTWAREPROJECT



SOFTWAREQUALITY

ASSURANCE


MANAGEMENT

Managed Level of Process MaturityManaged Level of Process Maturity

ORGANIZATIONPROCESS

FOCUS

ORGANIZATIONPROCESS

DEFINITION

TRAININGPROGRAM

INTEGRATEDSOFTWARE

MANAGEMENT

SOFTWAREPRODUCT

ENGINEERING


PEERREVIEW

QUANTITATIVE PROCESSMANAGEMENT

SOFTWARE QUALITYMANAGEMENT

DEFECTPREVENTION

TECHNOLOGY CHANGEMANAGEMENT

PROCESS CHANGEMANAGEMENT



GST

Moving from Level 4 to Level 5Moving from Level 4 to Level 5

At Level 4 the process is quantitatively understoodAt Level 4 the process is quantitatively understood

At Level 5 continuous process improvement is a way At Level 5 continuous process improvement is a way of lifeof life

At the lower maturity levels, worker participation on At the lower maturity levels, worker participation on continuous improvement may be on the order of 20 continuous improvement may be on the order of 20 to 30%to 30%

World-class companies have 70 to 80% participation World-class companies have 70 to 80% participation in improvement activities at any given point in time.in improvement activities at any given point in time.




GST

Understanding the Optimizing Maturity LevelUnderstanding the Optimizing Maturity LevelIdentify and eliminate chronic causes of poor performance

Control Chart with Common Causes

Original zone of quality control

Chronic WasteQuality

ImprovementNew zone of quality control

Continually improve the software process


Chronic Waste



GST

In

Focus on Continuous Process Improvement

Out

Disciplined change is away of life




GST

Addressing Common Causes of VariationAddressing Common Causes of Variation

Continuous process improvement means Continuous process improvement means controlled change, and measuring improving controlled change, and measuring improving process capabilityprocess capability

Systemic, not isolated, change that maintains Systemic, not isolated, change that maintains continuity of organization processcontinuity of organization process




GST

Defect Prevention (DP)Defect Prevention (DP)

Purpose is to identify the cause of defects Purpose is to identify the cause of defects and prevent them from recurringand prevent them from recurring

Involves:Involves:• analyzing defects that were encountered in the analyzing defects that were encountered in the

past past (frequency, distribution, relative impact)(frequency, distribution, relative impact)• taking specific actions to prevent the occurrence taking specific actions to prevent the occurrence

of these types of defects in the futureof these types of defects in the future




GST

Defect Prevention (DP)Defect Prevention (DP)


DefectAnalysisCausal

Analysis

Identify

Think

Act

ThinkSomeMore

IdentifyCommonCause(s)

Act to Prevent Cause(s)Avoid!



GST

Defect Prevention (DP) GoalsDefect Prevention (DP) Goals

Goal 1: Defect prevention activities are planned.Goal 1: Defect prevention activities are planned.

Goal 2: Common causes of defects are sought out Goal 2: Common causes of defects are sought out and identified.and identified.

Goal 3: Common causes of defects are prioritized Goal 3: Common causes of defects are prioritized and systematically eliminated.and systematically eliminated.




GST

Fixing Problems Before They OccurFixing Problems Before They Occur Focus is on causal analysis:Focus is on causal analysis:

• what in the process permitted the defect to occurwhat in the process permitted the defect to occur• what in the process needs to be corrected to prevent the what in the process needs to be corrected to prevent the

defect from occurring in the futuredefect from occurring in the future

Defects IdentifiedRoot Caused determinedCommon causes identifiedActions proposedSelect Actions

CausalAnalysisMeeting

ImplementActions

ReviewResults

ChangeProject’sDefinedprocess

Changeorganization’s

standard softwareprocess




GST

Defect Prevention (DP) ActivitiesDefect Prevention (DP) Activities Activity 1:Activity 1: The software project develops and maintains a plan The software project develops and maintains a plan

for its defect prevention activities. for its defect prevention activities. Activity 2:Activity 2: At the beginning of a software task, the members of At the beginning of a software task, the members of

the team performing the task meet to prepare for the activities the team performing the task meet to prepare for the activities of that task and the related defect prevention activities. of that task and the related defect prevention activities.

Activity 3:Activity 3: Causal analysis meetings are conducted according Causal analysis meetings are conducted according to a documented procedure. to a documented procedure.

Activity 4:Activity 4: Each of the teams assigned to coordinate defect Each of the teams assigned to coordinate defect prevention activities meets on a periodic basis to review and prevention activities meets on a periodic basis to review and coordinate implementation of action proposals from the causal coordinate implementation of action proposals from the causal analysis meetings. analysis meetings.

Activity 5:Activity 5: Defect prevention data are documented and tracked Defect prevention data are documented and tracked across the teams coordinating defect prevention activities. across the teams coordinating defect prevention activities.




GST

Defect Prevention (DP) ActivitiesDefect Prevention (DP) Activities

Activity 6:Activity 6: Revisions to the organization’s standard software Revisions to the organization’s standard software process resulting from defect prevention actions are process resulting from defect prevention actions are incorporated according to a documented procedure. incorporated according to a documented procedure.

Activity 7:Activity 7: Revisions to the project’s defined software process Revisions to the project’s defined software process resulting from defect prevention actions are incorporated resulting from defect prevention actions are incorporated according to a documented procedure. according to a documented procedure.

Activity 8:Activity 8: Members of the software engineering group and Members of the software engineering group and software-related groups receive feedback on the status and software-related groups receive feedback on the status and results of the organization’s and project’s defect prevention results of the organization’s and project’s defect prevention activities on a periodic basis.activities on a periodic basis.




GST

Barriers to Defect Prevention (DP)Barriers to Defect Prevention (DP)

Lack of personnel trained in Causal analysisLack of personnel trained in Causal analysis

Activity not budgeted, supported by Activity not budgeted, supported by organization organization

Lack of explicit delegation of responsibility Lack of explicit delegation of responsibility and assignment of authorityand assignment of authority

Lack of follow up process change and Lack of follow up process change and notification to work forcenotification to work force




GST

Technology Change Management (TM, TCM)Technology Change Management (TM, TCM) Purpose is to identify new technologies (i.e., tools, Purpose is to identify new technologies (i.e., tools,

methods, and processes) and transfer them into the methods, and processes) and transfer them into the organization in an orderly mannerorganization in an orderly manner

InvolvesInvolves• identifying, selecting and evaluating new identifying, selecting and evaluating new

technologiestechnologies• incorporating effective technologies into the incorporating effective technologies into the

organizationorganization




GST

Technology Change Management (TM, TCM)Technology Change Management (TM, TCM)


New, and Unused Technologies

Measured, AnalyzedCurrent Results are not

Satisfactory

Identify

SelectLikely Candidate(s)

ThinkAbout it

Adopt it! AnalyzeResults Try it!

Is it Better?



GST

Technology Change Management (TM, TCM) Technology Change Management (TM, TCM) GoalsGoals

Goal 1: Incorporation of technology changes are Goal 1: Incorporation of technology changes are planned.planned.

Goal 2: New technologies are evaluated to determine Goal 2: New technologies are evaluated to determine their effect on quality and productivity.their effect on quality and productivity.

Goal 3: Appropriate new technologies are transferred Goal 3: Appropriate new technologies are transferred into normal practice across the organization.into normal practice across the organization.




GST

Technology Transfer CurveTechnology Transfer Curve

TechnologyTransition

Pilot Test

InformationTransition Contact

AwarenessUnderstanding

Commitment

Installation

Adoption

Institutionalization




GST

Reacting to InnovationReacting to Innovation

Technology changes occur at all maturity Technology changes occur at all maturity levelslevels

At Level 5 innovation:At Level 5 innovation:• introduced into the process in a disciplined wayintroduced into the process in a disciplined way• institutionalizedinstitutionalized




GST

Technology Change Management (TM, TCM) Technology Change Management (TM, TCM) ActivitiesActivities

Activity 1:Activity 1: The organization develops and maintains a plan for The organization develops and maintains a plan for technology change management. technology change management.

Activity 2:Activity 2: The group responsible for the organization’s The group responsible for the organization’s technology change management activities works with the technology change management activities works with the software projects in identifying areas of technology change. software projects in identifying areas of technology change.

Activity 3:Activity 3: Software managers and technical staff are kept Software managers and technical staff are kept informed of new technologiesinformed of new technologies

Activity 4:Activity 4: The group responsible for the organization’s The group responsible for the organization’s technology change management systematically analyzes the technology change management systematically analyzes the organization’s standard software process to identify areas that organization’s standard software process to identify areas that need or could benefit from new technology. need or could benefit from new technology.




GST

Technology Change Management (TM, TCM) Technology Change Management (TM, TCM) ActivitiesActivities

Activity 5:Activity 5: Technologies are selected and acquired for the Technologies are selected and acquired for the organization and software projects according to a documented organization and software projects according to a documented procedure. procedure.

Activity 6:Activity 6: Pilot efforts for improving technology are Pilot efforts for improving technology are conducted, where appropriate, before a new technology is conducted, where appropriate, before a new technology is introduced into normal practice. introduced into normal practice.

Activity 7:Activity 7: Appropriate new technologies are incorporated into Appropriate new technologies are incorporated into the organization’s standard software process according to a the organization’s standard software process according to a documented procedure. documented procedure.

Activity 8:Activity 8: Appropriate new technologies are incorporated into Appropriate new technologies are incorporated into the projects defined software processes according to a the projects defined software processes according to a documented procedure. documented procedure.




GST

Barriers to Technology Change Management(TCM)

Delegation of responsibility to too low a levelDelegation of responsibility to too low a level

Activities are not funded or supportedActivities are not funded or supported

The idea of “New Technology” sounds expensiveThe idea of “New Technology” sounds expensive

Lack of serious planningLack of serious planning

No defined process for changeNo defined process for change




GST

Process Change Management (PC, PCM)Process Change Management (PC, PCM)

Purpose is to continually improve the software processes Purpose is to continually improve the software processes used in the organization with the intent of improving used in the organization with the intent of improving software quality, increasing productivity, and decreasing software quality, increasing productivity, and decreasing the cycle time for product developmentthe cycle time for product development

InvolvesInvolves• defining process improvement goalsdefining process improvement goals• systematically identifying, evaluating and implementing systematically identifying, evaluating and implementing

improvements to the organization’s standard software improvements to the organization’s standard software process and the projects’ defined software processesprocess and the projects’ defined software processes




GST

Change is a ProcessChange is a Process Disciplined change is the key to successDisciplined change is the key to success

Improvement includes planningImprovement includes planning• evaluating improvement proposals and planning evaluating improvement proposals and planning

actionsactions• establishing process improvement teamsestablishing process improvement teams• conducting pilot programs for process conducting pilot programs for process

improvementimprovement• updating procedures, training, etc.updating procedures, training, etc.

Improvements are transferred into everyday practice Improvements are transferred into everyday practice across the organizationacross the organization




GST

Process Change Management (PC, PCM)Process Change Management (PC, PCM)


Identify CurrentOpportunities forImprovement

1. Measured, AnalyzedCurrent Results are not

Satisfactory

2. Process Changes due To Defect Prevention or

Technology Change

Identify

Select ProcessChange Options

ThinkAbout it

Adopt it! AnalyzeResults Try it!

Is it Better?

GOALS



GST

Process Change Management (PC, PCM) Process Change Management (PC, PCM) GoalsGoals

Goal 1: Continuous process improvement is planned.Goal 1: Continuous process improvement is planned.

Goal 2: Participation in the organization’s software Goal 2: Participation in the organization’s software process improvement activities is organization wide.process improvement activities is organization wide.

Goal 3: The organization’s standard software process Goal 3: The organization’s standard software process and the projects’ defined software processes are and the projects’ defined software processes are improved continuously.improved continuously.




GST

95% of all dieters regain the weight they have 95% of all dieters regain the weight they have lost . . . and more. . . within one year of a dietlost . . . and more. . . within one year of a diet

60% of those who change their lifestyle to eat 60% of those who change their lifestyle to eat less and exercise more maintain their weight less and exercise more maintain their weight lossloss

Process Improvement = Lifestyle Change

Process Improvement is a Lifestyle ChangeProcess Improvement is a Lifestyle Change

Silver Bullet ≠ Diet




GST

Process Change Management (PC, PCM) Process Change Management (PC, PCM) ActivitiesActivities

Activity 1:Activity 1: A software process improvement program is A software process improvement program is established which empowers the members of the organization established which empowers the members of the organization to improve the processes of the organization. to improve the processes of the organization.

Activity 2:Activity 2: The group responsible for the organization’s The group responsible for the organization’s software process activities (e.g., software engineering process software process activities (e.g., software engineering process group) coordinates the software process improvement group) coordinates the software process improvement activities. activities.

Activity 3:Activity 3: The organization develops and maintains a plan for The organization develops and maintains a plan for software process improvement according to a documented software process improvement according to a documented procedure. procedure.




GST


Activity 4:Activity 4: The software process improvement activities are The software process improvement activities are performed in accordance with the software process performed in accordance with the software process improvement plan. improvement plan.

Activity 5:Activity 5: Software process improvement proposals are Software process improvement proposals are handled according to a documented procedure. handled according to a documented procedure.

Activity 6:Activity 6: Members of the organization actively participate in Members of the organization actively participate in teams to develop software process improvements for assigned teams to develop software process improvements for assigned process areas. process areas.

Activity 7:Activity 7: Where appropriate, the software process Where appropriate, the software process improvements are installed on a pilot basis to determine their improvements are installed on a pilot basis to determine their benefits and effectiveness before they are introduced into benefits and effectiveness before they are introduced into normal practice. normal practice.




GST


Activity 8:Activity 8: When the decision is made to transfer a software When the decision is made to transfer a software process improvement into normal practice, the improvement is process improvement into normal practice, the improvement is implemented according to a documented procedure. implemented according to a documented procedure.

Activity 9:Activity 9: Records of software process improvement activities Records of software process improvement activities are maintained.are maintained.

Activity 10:Activity 10: Software managers and technical staff receive Software managers and technical staff receive feedback on the status and results of the software process feedback on the status and results of the software process improvement activities on an event-driven basis. improvement activities on an event-driven basis.




GST

Barriers to Process Change Management(PCM)

Delegation of responsibility to too low a levelDelegation of responsibility to too low a level

Activities are not funded or supportedActivities are not funded or supported

Lack of serious planningLack of serious planning

No defined process for changeNo defined process for change




GST

Level 5 is not the DestinationLevel 5 is not the Destination

Level 5 is a foundation for building an ever-improving Level 5 is a foundation for building an ever-improving capabilitycapability

Level 5 organizations continuous improvements are:Level 5 organizations continuous improvements are:• incremental (Kaizen)incremental (Kaizen)• revolutionary (innovation)revolutionary (innovation)

Everyone in a Level 5 organization is involved in Everyone in a Level 5 organization is involved in improvementimprovement




GST

The Great Productivity DipThe Great Productivity Dip

Present

State

Desired

StateTransition

State

Pro

duct

ivit

y




GST

Optimizing LevelOptimizing Level

Some improvement is incremental (Kaizen) Some improvement is incremental (Kaizen) orientedoriented

Some improvement is revolutionary Some improvement is revolutionary (innovative) in nature(innovative) in nature

All change needs to be managed in a All change needs to be managed in a disciplined manner.disciplined manner.




GST

Tying It All Together - ObjectivesTying It All Together - Objectives

By the end of this module you will have the By the end of this module you will have the ability to:ability to:• explain some of the common themes that run explain some of the common themes that run

throughout the CMMthroughout the CMM• describe how these themes are embedded in the describe how these themes are embedded in the

common features and the wording of the practicescommon features and the wording of the practices




GST TEST TIMETEST TIME

1. Please identify the three areas you think are 1. Please identify the three areas you think are the best opportunities for improvement in the best opportunities for improvement in CMM level 2 KPAs. CMM level 2 KPAs.

2. List the three areas you think are the 2. List the three areas you think are the organizations most significant opportunities organizations most significant opportunities for CMM level 3 KPAs.for CMM level 3 KPAs.

3. What one change would your group make to 3. What one change would your group make to the organization to improve software the organization to improve software development effectiveness.development effectiveness.

4. What is preventing you from being level 4.4. What is preventing you from being level 4.



GST

Themes in the CMMThemes in the CMM

Continuous improvementContinuous improvement Defined, documented and used processesDefined, documented and used processes Commitment by senior managementCommitment by senior management Stable processesStable processes Measured processesMeasured processes Controlled processesControlled processes Processes evolveProcesses evolve




GST

Continuous ImprovementContinuous Improvement

Processes must be able to improve if we are Processes must be able to improve if we are to achieve continuous process improvementto achieve continuous process improvement

In mature organizations, processes are In mature organizations, processes are “living” entities, which are supported and “living” entities, which are supported and maintainedmaintained

Everyone is involved in continuous process Everyone is involved in continuous process improvementimprovement




GST

Defined, Documented, and UsedDefined, Documented, and Used

Processes are documentedProcesses are documented Processes are practiced as documentedProcesses are practiced as documented Only procedures that will be used are writtenOnly procedures that will be used are written ““Say what you do; do what you say.”Say what you do; do what you say.”




GST

Commitment By Senior Commitment By Senior ManagementManagement

Policies provide a way of establishing Policies provide a way of establishing expectations for the behavior of everyone in expectations for the behavior of everyone in the organizationthe organization

Written organizational policies are in Written organizational policies are in Commitment to PerformCommitment to Perform




GST

Stable ProcessesStable Processes

Training is a way to establishing normal, Training is a way to establishing normal, consistent ways for performing an activityconsistent ways for performing an activity

Training helps to ensure that everyone Training helps to ensure that everyone understands the processunderstands the process

Training and orientation practices are in Training and orientation practices are in Ability to PerformAbility to Perform

Organizational training needs are addressed Organizational training needs are addressed by the Training Program key process area.by the Training Program key process area.




GST

Measured ProcessesMeasured Processes Measurement of both product and process is an Measurement of both product and process is an

integral part of every key process areaintegral part of every key process area

Measures of the processes defined in each key process Measures of the processes defined in each key process area are in Measurement and Analysisarea are in Measurement and Analysis

Typically measures are of status and effectiveness of Typically measures are of status and effectiveness of processesprocesses

Measurements necessary to implement the process Measurements necessary to implement the process (such as size estimates in Software Project Planning) (such as size estimates in Software Project Planning) are in Activities Performedare in Activities Performed




GST

Measurement Effort Across Maturity Levels Measurement Effort Across Maturity Levels Level 1 & 2Level 1 & 2

Level 1Level 1 Measurement haphazard, but with effort Measurement haphazard, but with effort

can find cost and work-year datacan find cost and work-year data

Level 2Level 2 Projects collect management dataProjects collect management data

about cost, effort, size, schedule, about cost, effort, size, schedule,

defects, etc.defects, etc.

Different projects may use different Different projects may use different

definitionsdefinitions




GST

Measurement Effort Across Maturity Levels Measurement Effort Across Maturity Levels Level 3Level 3

Level 3Level 3 There are now consistent definitionsThere are now consistent definitions

from one project to the nextfrom one project to the next

Data are collected across the Data are collected across the


Both management and quality dataBoth management and quality data

are collectedare collected




GST

Measurement Effort Across Maturity Levels Measurement Effort Across Maturity Levels Levels 4 & 5Levels 4 & 5

Level 4Level 4 Data analysis is based on the principlesData analysis is based on the principles

of statistical process controlof statistical process control

Actual measurements are compared to Actual measurements are compared to expected values of mean and varianceexpected values of mean and variance

Level 5Level 5 Continuing improvement is based onContinuing improvement is based on

business objectives and cost/benefitbusiness objectives and cost/benefit

analysesanalyses




GST

Controlled ProcessesControlled Processes The process must be verified and validated to The process must be verified and validated to

ensure that it is really practicedensure that it is really practiced

The CMM emphasizes SQAThe CMM emphasizes SQA• Software Quality Assurance key process areaSoftware Quality Assurance key process area• Verifying Implementation common featureVerifying Implementation common feature• The feasibility of alternative ways of verifying and The feasibility of alternative ways of verifying and

validating the process depends on organizational validating the process depends on organizational cultureculture




GST

Processes EvolveProcesses Evolve

Implies that the way people do a job will Implies that the way people do a job will change (improve) over timechange (improve) over time

Frequently includes the use of more powerful Frequently includes the use of more powerful tools and methodstools and methods

Means that a “cultural shift” is under way Means that a “cultural shift” is under way because people are changing the way they do because people are changing the way they do thingsthings




GST

The Evolution of Software Project ManagementThe Evolution of Software Project Management

Optimizing

Managed

Defined

Repeatable

Initial

Software ProjectPlanning

Software ProjectTracking and Oversight

Software Project Management is Done

Integrated SoftwareManagement

Quantitative ProcessManagement

Process ChangeManagement




GST

Tying It All TogetherTying It All Together

•Defined•Documented•Trained•Practiced•Measured

•Improving•Maintained•Supported•Controlled•Verified and Validated

Common features provide common themes Common features provide common themes

throughout the CMMthroughout the CMM

Processes in mature organization share a numbered Processes in mature organization share a numbered of attributes:of attributes:




GST

Applying the CMMApplying the CMM

Assessments (CMM Based Appraisal - Internal Assessments (CMM Based Appraisal - Internal Process Improvement (CBA-IPI)Process Improvement (CBA-IPI)• identifying and prioritizing process issuesidentifying and prioritizing process issues

Evaluations (Software Process Evaluations (SPE)Evaluations (Software Process Evaluations (SPE)• source selectionsource selection• (sub) contract monitoring(sub) contract monitoring

Process improvement effortsProcess improvement efforts• self-improvementself-improvement




GST

Using Professional Judgment(This is the most important slide in the course)

The CMM is intended for a wide range of situationsThe CMM is intended for a wide range of situations• key practices and goals allow for flexibilitykey practices and goals allow for flexibility

Interpret key practices in light of an organization's Interpret key practices in light of an organization's business needs, culture, structure and prioritiesbusiness needs, culture, structure and priorities

Objective of process management is to establish Objective of process management is to establish processes based on business needs that will be used processes based on business needs that will be used as a foundation for systematic improvementas a foundation for systematic improvement




GST

The “Key” AdjectiveThe “Key” Adjective

The CMM is not exhaustiveThe CMM is not exhaustive

There are software management and There are software management and engineering processes and practices that are engineering processes and practices that are not described in the CMMnot described in the CMM

““Key” indicates a focus on the major leverage Key” indicates a focus on the major leverage pointspoints• key process areaskey process areas• key practiceskey practices




GST

Organizational ContextOrganizational Context

Each organization must interpret levels of excellence Each organization must interpret levels of excellence in the context of that organization's business in the context of that organization's business environmentenvironment

The CMM works best when practices are interpreted The CMM works best when practices are interpreted in a way that makes sense for the organizationin a way that makes sense for the organization




GST

Size of the OrganizationSize of the Organization

The key practices in the CMM are expressed in terms of a The key practices in the CMM are expressed in terms of a large government contracting organization; however the large government contracting organization; however the CMM is widely used by commercial organizationsCMM is widely used by commercial organizations

The CMM can be, and has been, effectively used for small The CMM can be, and has been, effectively used for small projects and small organizations - with an appropriate projects and small organizations - with an appropriate interpretation of the practicesinterpretation of the practices• focus on achieving the goals of the key process areasfocus on achieving the goals of the key process areas• Interpret the key process area practices in the context of the Interpret the key process area practices in the context of the





GST

Mapping Roles and FunctionsMapping Roles and Functions

It is useful to map the role names (e.g., It is useful to map the role names (e.g., project software manager) and group names project software manager) and group names (e.g., software engineering group) used in the (e.g., software engineering group) used in the CMM to the terminology used in the CMM to the terminology used in the organization and projects being appraised.organization and projects being appraised.




GST

Process Improvement Using the CMMProcess Improvement Using the CMM

Software process improvement occurs within the Software process improvement occurs within the context of:context of:• the organization’s strategic plansthe organization’s strategic plans• its business objectivesits business objectives• its organizational structureits organizational structure• the technologies in usethe technologies in use• its social cultureits social culture• its management systemits management system




GST

Assessment and Process Improvement Model

Contact andAwareness

Contact andAwareness

Action PlanImplementation

Action PlanImplementation

ExpectationSetting

ExpectationSetting

VisioningVisioning

SponsorshipBuilding andCommitment

SponsorshipBuilding andCommitment

Action PlanDevelopment

Action PlanDevelopment

CollaborativeConsultingTraining

CollaborativeConsultingTraining

AssessmentFocus

AssessmentFocus

SEPGPreparation

SEPGPreparation

Recommendationsand Final Report

Generation

Recommendationsand Final Report

Generation




GST

Interpreting the CMM Interpreting the CMM

The CMM is applicable to different types of The CMM is applicable to different types of organizationsorganizations

Key practices have to be interpretedKey practices have to be interpreted




GST

CMM CommunityCMM Community

The CMM provides a principled, public model for The CMM provides a principled, public model for appraising software development capabilityappraising software development capability

The CMM is owned by the national software The CMM is owned by the national software community (and is broadly accepted abroad.)community (and is broadly accepted abroad.)

The SEI exercises stewardship of the CMM by:The SEI exercises stewardship of the CMM by:• evolving the CMM from industry experienceevolving the CMM from industry experience• Performing empirical researchPerforming empirical research• developing CMM-based improvement methodsdeveloping CMM-based improvement methods




GST

Revisions to the CMMRevisions to the CMM

Continuous improvement applies to the CMMContinuous improvement applies to the CMM

he SEI accepts change requests and provides he SEI accepts change requests and provides feedback from the CMM user communityfeedback from the CMM user community

The SEI is engaged in efforts to maintain harmony The SEI is engaged in efforts to maintain harmony with the International Organization for with the International Organization for Standardization (ISO) - SPICEStandardization (ISO) - SPICE

Current plans are to develop CMM v2 in the 1997-Current plans are to develop CMM v2 in the 1997-1998 time frame.1998 time frame.




GST

The CMM is a ModelThe CMM is a Model A model A model

• is a hypothetical or stylized representationis a hypothetical or stylized representation• is inertis inert• cannot solve anythingcannot solve anything

The management of an organization is responsible The management of an organization is responsible for satisfying business objectives. The CMM, as a for satisfying business objectives. The CMM, as a model, and currently the best software process model, and currently the best software process model in existence, can help an organization improve model in existence, can help an organization improve software processes when it is diligently applied by software processes when it is diligently applied by knowledgeable individuals backed by management knowledgeable individuals backed by management commitmentcommitment




GST

ConclusionsConclusions

Software development and maintenance is Software development and maintenance is difficult even with a disciplined processdifficult even with a disciplined process

The CMM is one (but not the only) tool for The CMM is one (but not the only) tool for understanding and describing the software understanding and describing the software processprocess




GST

QuestionsQuestionsandand

AnswersAnswers

QuestionsQuestionsandand

AnswersAnswers

introduction to the software engineering institute’s (sei) capability maturity model (cmm) global...

Documents

projects software engineering

management activities

appropriate slide

tailored version

specific needs