Tor Stålhane IDI / NTNU Geir Skylstad SINTEF / IKT

Slides:



Advertisements
Similar presentations
SOFTWARE PROCESS IMPROVEMENT “Never Stop Learning”
Advertisements

Group 7 - Chapter 3 Steven Shroyer - Introduction, ad hoc, level 2 Xiao Jingshan - Levels 3 and 4 Dusting Marker - Level 5 and example companies Definintions.
Process 18:11 19/04/2015 Geir Skylstad SINTEF DELAB 1 ITUF 61.UP.93 miniseminar Programvareutviklingsprosessen, 16 sep 1993, Holmenkollen Restaurant Utviklingsparadigmer.
Chapter 2 The Software Process
©2006 OLC 1 Process Management: The Foundation for Achieving Organizational Excellence Process Management Implementation Worldwide.
Copyright 2003 CMMI: Executive Briefing Presented by Kieran Doyle
CMMI Overview Dr. Korson Software Engineering. 2 Immature organizations can be successful on occasion, but ultimately run into difficulties because –Success.
The Systems Security Engineering Capability Maturity Model (ISO 21827)
SEI White Paper: Process Maturity Model Present by Hui Huang November 16, 2000 ® CMM is Registered in the US Patent and Trademark Office.
Capability Maturity Model (CMM) in SW design
SOFTWARE ENGINEERING LECTURE-3 CSE-477.
Questions: Choice the correct answer: 1-Capability Maturity Model for Software (SW-CMM) is used to: a- increase software process capability. b- increase.
CMM Overview - 1 © Paul Sorenson CMPUT Software Engineering refs. IEEE Software, March 1988, 73-79, and IEEE Software, July 1993, (Capability.
Process management Basic concepts and stat-of-the art research.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 28 Slide 1 Process Improvement.
Chapter 3 The Structure of the CMM
CMMI Overview Quality Frameworks.
Organizational Project Management Maturity: Roadmap to Success
Standardization. Introduction A standard is a document. It is a set of rules that control how people should develop and manage materials, products, services,
Lecture 11 CMM CSCI – 3350 Software Engineering II Fall 2014 Bill Pine.
Capability Maturity Model
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 28 Slide 1 Process Improvement 2.
Chapter : Software Process
Capability Maturity Model. Reflection Have you ever been a part of, or observed, a “difficult” software development effort? How did the difficulty surface?
N By: Md Rezaul Huda Reza n
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
Software Engineering - Spring 2003 (C) Vasudeva Varma, IIITHClass of 39 CS3600: Software Engineering: Standards in Process Modeling CMM and PSP.
Software Engineering Lecture No:16. Lecture # 7 CMMI Fahim Khan Assistant Professor of Computer Science UOL, Sargodha
Software Engineering Lecture # 17
University of Sunderland CIFM03Lecture 2 1 Quality Management of IT CIFM03 Lecture 2.
Adaptive Processes Overview Adaptive Processes©. Adaptive Processes © Adaptive ProcessesSimpler, Faster, Better2 Objective To provide an over view of.
Quality Concepts within CMM and PMI G.C.Reddy
Software Project Management Lecture 7A SEI - Capability Maturity Model.
Lecture Topics covered CMMI- - Continuous model -Staged model PROCESS PATTERNS- -Generic Process pattern elements.
1 ISO 9001:2000 ISO 9001 is the creation of the International Organisation for Standardisation (ISO), a Swiss-based federation of national standards bodies.ISO.
1 © Mahindra Satyam 2009 Mahindra Satyam Confidential Welcome To CMMI Introduction.
Software Engineering - I
CS Process Improvement CMM Hans Van Vliet, Software Engineering, Principles and Practice, 3 rd edition, John Wiley & Sons, Chapter 6. W. Humphrey,
©Ian Sommerville 2004 Software Engineering. Chapter 28Slide 1 Chapter 28 Process Improvement.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
CMMI. 1.Initial - The software process is characterized as ad hoc, and occasionally even chaotic. Few processes are defined, and success depends on individual.
CMMI FRAMEWORK SRIKANTH DEVINENI. Process failure is recognised when Project is delivered late Too much redundancy Customer complaints after delivery.
Ch-1 Introduction The processes used for executing a software project have major effect on quality of s/w produced and productivity achieved in project…
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Page 1 The Capability Maturity Model (CMM) distinguishes between immature and mature software organizations. Immature software organizations are typically.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming.
1 SEI Capability Maturity Model Advanced Software Engineering COM360 University of Sunderland © 2000.
SOFTWARE PROCESS IMPROVEMENT
Software Engineering (CSI 321) Software Process: A Generic View 1.
CMMI Overview Quality Frameworks. Slide 2 of 146 Outline Introduction High level overview of CMMI Questions and comments.
CMMI for Services, Version 1.3
CMMI Certification - By Global Certification Consultancy.
Capability Maturity Model. What is CMM? n CMM: Capability Maturity Model n Developed by the Software Engineering Institute of the Carnegie Mellon University.
CS4311 Spring 2011 Process Improvement Dr
CMMI Overview Quality Frameworks.
Software Engineering (CSI 321)
CMMI Overview.
Chapter Objectives To understand the operational environment in which you execute your project To understand the need and role of oversight in managing.
Where We Are Now. Where We Are Now Project Oversight Project Oversight Oversight’s Purposes: A set of principles and processes to guide and improve.
Capability Maturity Model Integration (CMMI)
Exercise 3 Tor Stålhane IDI / NTNU.
Focus on Software Process
Software Engineering Lecture 16.
Software Engineering I
Introduction Chapter 1 Copyright ©2016 Pearson Education, Inc.
Capability Maturity Model
SVV Lec: software process assurance.
Capability Maturity Model
Software Verification and Validation
Presentation transcript:

Tor Stålhane IDI / NTNU Geir Skylstad SINTEF / IKT An introduction to CMM Tor Stålhane IDI / NTNU Geir Skylstad SINTEF / IKT

SEI Maturity Model for Software Process A maturity level is a well-defined evolutionary plateau towards achieving a mature process. Each maturity level provides a layer in the foundation for continuous process improvement. Each level comprises a set of process goals that stabilize an important component of the software process. Achieving each level of the maturity framework establishes a component in the process, resulting in an increase in the process capability of the organization.

Organization maturity levels (stages) Progreff Initial (1) Repeatable (2) Defined (3) Managed (4) Optimizing (5) Disciplined process Standard, consistent Predictable Continuously improving

Driving force: Quality Improvement

Visibility improve for each level 5 In Out 4 In Out 3 In Out 2 In Out 1 In Out

Predictability increases 5 Performance continuously improves in Level 5 organizations Time/$/... Based on quantitative understanding of process and product, performance continues to improve in Level 4 organizations 4 Time/$/... 3 With well-defined processes, performance improves in Level 3 organizations Time/$/... 2 Plans based on past performance are more realistic in Level 2 organizations Time/$/... 1 Schedule and cost targets are typically overrun by Level 1 organizations. Time/$/...

Maturity Model Hierarchy Maturity Levels contain Key Process Areas contain Common Features contain Key Practices