cmmi

18
Capability Maturity Model Integrated Short Overview Quality Framework s Presented By: AHM Pervej Kabir ERA-InfoTech Limited.

Upload: ahm-pervej-kabir

Post on 13-Apr-2017

355 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: CMMI

Capability Maturity Model IntegratedShort Overview

Quality Frameworks

Presented By: AHM Pervej Kabir ERA-InfoTech Limited. +8801757051005

Page 2: CMMI

Slide 2 of 18

Outline

• Introduction • High level overview of CMMI • Questions and comments

Page 3: CMMI

Slide 3 of 18

What is CMMI?

• CMMI (Capability Maturity Model Integration) is a proven industry framework to improve product quality and development efficiency for both hardware and software– CMMI has been established as a model to improve

business results– Emphasis on business needs, integration and

institutionalization

• CMMI (Capability Maturity Model Integration) not asks What to do? It asks, How to do?

Page 4: CMMI

Slide 4 of 18

How can CMMI help?• CMMI provides a way to focus and manage hardware and

software development from product inception through deployment and maintenance.– ISO-9000 are still required. CMMI interfaces well with them.

CMMI and TL are complementary - both are needed since they address different aspects.

• ISO-9000 is a process compliance standard• CMMI is a process improvement model

• Behavioral changes are needed at both management and staff levels. Examples:– Increased personal accountability– Tighter links between Product Management, Development,

SCN, etc.• Initially a lot of investment required – but, if properly managed,

we will be more efficient and productive while turning out products with consistently higher quality.

Page 5: CMMI

Slide 5 of 13

CMMI Models within the Framework

• Models:– Systems Engineering + Software Engineering (SE/SW)– Systems Engineering + Software Engineering + Integrated Product

and Process Development (IPPD) – Systems Engineering + Software Engineering + Integrated Product

and Process Development + Supplier Sourcing (SS)– Software Engineering only

• Representation options:– Staged – Continuous

.

Page 6: CMMI

Slide 6 of 13

CMMI Staged Representation - 5 Maturity Levels

Level 5

Initial

Level 1

Processes are unpredictable, poorly controlled, reactive.

Managed

Level 2

Processes are planned, documented, performed, monitored, and controlled at the project level. Often reactive.

Defined

Level 3 Processes are well characterized and understood. Processes, standards, procedures, tools, etc. are defined at the organizational (Organization X ) level. Proactive.

Quantitatively Managed

Level 4 Processes are controlled using statistical and other quantitative techniques.

Optimizing Pr

oces

s Matu

rity

Process performance continually improved through incremental and innovative technological improvements.

Page 7: CMMI

Slide 7 of 18

Behaviors at the Five Levels

Initial

Managed

Defined

QuantitativelyManaged

Optimizing

Process is unpredictable,poorly controlled, and reactive

Process is characterized for projects and is oftenreactive

Process is characterizedfor the organization andis proactive

Process is measuredand controlled

Focus is on continuousquantitative improvement

Maturity Level Process Characteristics Behaviors

Focus on "fire prevention";improvement anticipated anddesired, and impacts assessed.

Greater sense of teamwork and inter-dependencies

Reliance on defined process. People understand, support and follow the process.

Over reliance on experience of goodpeople – when they go, the processgoes. “Heroics.”

Focus on "fire fighting";effectiveness low – frustration high.

Page 8: CMMI

Slide 8 of 18

CMMI Levels……..

Page 9: CMMI

Slide 9 of 18

Level Wise Process Areas

.

Page 10: CMMI

Slide 10 of 18

Maturity Level Project Managment Engineering Process Management Support5

OptimizingOrganizational Innovation & Deployment Causal Analysis & Resolution

4Quantitatively

Managed

Quantitative Project Mngt Organizational Process Performance

3Defined

Integrated Project MngtRisk Management

Requirements DevelopmentTechnical SolutionProduct IntegrationVerificationValidation

Organizational Process FocusOrganizational Process DefinitionOrganizational Training

Decision Analysis & Resolution

2Managed

Project PlanningProject Monitoring & ControlSupplier Agreement Mngt

Requirements Mngt Measurement & AnalysisProcess & Product Quality AssuranceConfiguration Mngt

1Initial

CMMI Process Areas

Page 11: CMMI

Slide 11 of 18

CMMI Components

Page 12: CMMI

Slide 12 of 18

CMMI Terminology & StructureMaturity Levels (1- 5)

GenericPractices

GenericGoals

Process Area 2

Common Features

Process Area 1 Process Area n

VerifyingImplementation

SpecificGoals

SpecificPractices

Abilityto Perform

DirectingImplementation

RequiredRequired

Sub practices, typical work products, discipline amplifications, generic practice elaborations, goal and

practice titles, goal and practice notes, and references

Commitmentto Perform

Sub practices, typical work products, discipline amplifications, generic practice elaborations, goal and

practice titles, goal and practice notes, and references

InformativeInformative

Required. Specific for each process area.

Required. Common across all process areas.

Page 13: CMMI

Slide 13 of 18

CMMI Pitfalls of implementation

• Implementing CMM does not occur overnight.• Implementing CMM is not merely a “paper drill”.• Typical times for implementation:

– 3-6 months of preparation– 6-12 months of implementation– 3 months of assessment preparation– 12 months for each new level

How Long Does it Take?

Page 14: CMMI

Slide 14 of 18

Pitfalls of CMMI implementation

Is It Perfect?

• No! Some implementations do more harm than good.– Complete re-vamp of processes to “get certified”

instead of smartly adapting processes.– Process focus used more as a stick than as a carrot.– Focusing on compliance instead of improvement.

Page 15: CMMI

Slide 15 of 13

Advantage of CMMI implementation

•Defect rates have dropped•Defect detection occurs earlier•User requirements are documented, controlled, and managed with monitoring

•Especially important when users change their minds!

•Estimating improves and becomes more precise•Risk management is a practice•Development processes remain agile!

Page 16: CMMI

Slide 16 of 18

CMMI Implementation Best Practices

•Be Realistic – Some processes will be more ready than others.•Be Flexible – Allowing tailoring is key to adoption.•Be Open – The key is to learn how to do things better, not how to “comply”.•Be Patient – It does not happen overnight.

Page 17: CMMI

Slide 17 of 18

CMMI Resources

• Software Engineering Institute's CMMI website:

http://www.sei.cmu.edu/cmmi/

Page 18: CMMI

Slide 18 of 18

THANKS to ALL