Org Name Org Site CMM Assessment Kick-off Meeting Dates of assessment.

Slides:



Advertisements
Similar presentations
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.
Advertisements

Integrated Product Team (IPT) Process Training
Process 18:11 19/04/2015 Geir Skylstad SINTEF DELAB 1 ITUF 61.UP.93 miniseminar Programvareutviklingsprosessen, 16 sep 1993, Holmenkollen Restaurant Utviklingsparadigmer.
DataSource & SEI’s Capability Maturity Model (CMM ® )
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
More CMM Part Two : Details.
1 Brief Descriptions of CMM KPAs CEN 6070 Summer 2004.
How ISO9001 Compares with CMM Mark C. Paulk JAN,1995 CMM version 1.1 ISO9001 July 1994 presented by Zhilan Zhou.
1 State of Michigan Achieving Software Process Improvement with Capability Maturity Model (CMM)
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
Process Improvement.
SE 470 Software Development Processes James Nowotarski 12 May 2003.
Capability Maturity Model (CMM) in SW design
Computer Engineering 203 R Smith Process/Plan Model 7/ Development Process Models Development Process Models are different ways to look at the processes.
Road Map to CMM Implementation
COMP2002 Lecturecopyright DMU 2001 COMP2002 Quality Basics.
CMM Overview - 1 © Paul Sorenson CMPUT Software Engineering refs. IEEE Software, March 1988, 73-79, and IEEE Software, July 1993, (Capability.
Chapter 3 The Structure of the CMM
Software Process CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 17, 2002.
How to write a Report On Assessment Source: AUN Secretariat.
Capability Maturity Model
CMM Level 3 KPA’s CS4320 Fall Organizational Process Focus (Goals) Software process development and improvement activities are coordinated across.
CMMI Course Summary CMMI course Module 9..
What ISO 9000 Mandates The requirements for a quality system have been standardized - but many organizations like to think of themselves as unique. So.
S T A M © 2000, KPA Ltd. Software Trouble Assessment Matrix Software Trouble Assessment Matrix *This presentation is extracted from SOFTWARE PROCESS QUALITY:
Integrated Capability Maturity Model (CMMI)
COMPANY CONFIDENTIAL Page 1 Final Findings Briefing Client ABC Ltd CMMI (SW) – Ver 1.2 Staged Representation Conducted by: QAI India SM - CMMI is a service.
Software Engineering II Lecture 1 Fakhar Lodhi. Software Engineering - IEEE 1.The application of a systematic, disciplined, quantifiable approach to the.
Test Organization and Management
Capability Maturity Model Part One - Overview. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First.
Process Assessment Motivation SEI Capability Maturity Model
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.
CMMi What is CMMi? Basic terms Levels Common Features Assessment process List of KPAs for each level.
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 31 Slide 1 Process Improvement u Understanding, Modelling and Improving the Software Process.
A Project ’ s Tale: Transitioning From SW-CMM to CMMI-SE/SW Warren Scheinin Systems Engineer, NG Mission Systems CMMI Technology Conference & User Group.
Software Engineering - Spring 2003 (C) Vasudeva Varma, IIITHClass of 39 CS3600: Software Engineering: Standards in Process Modeling CMM and PSP.
Capability Maturity Models Software Engineering Institute (supported by DoD) The problems of software development are mainly caused by poor process management.
Capability Maturity Model. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First version published in.
By Ritesh Reddy Nagaram.  Organizations which are developing software processes are facing many problems regarding the need for change of already existing.
Team Assignment 15 Team 04 Class K15T2. Agenda 1. Introduction 2. Measurement process 3. GQM 4. Strength Weakness of metrics.
Process Management Process Management in software started in late 1960’s (but informally and inconsistently) Software Engineering Institute (SEI) is the.
March 26-28, 2013 SINGAPORE CDIO Asian Regional Meeting and Workshop on Engineering Education and Policies for Regional Leaders Programme Evaluation (CDIO.
Software process improvement Framework for SPI SPI support groups, maturity and immaturity models Assessment and gap analysis Education and training Selection.
Quality Concepts within CMM and PMI G.C.Reddy
Process Assessment Method
Georgia Institute of Technology CS 4320 Fall 2003.
SWEN 5130 Requirements Engineering 1 Dr Jim Helm SWEN 5130 Requirements Engineering Requirements Management Under the CMM.
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.
COMP 6710 Course NotesSlide 3-0 Auburn University Computer Science and Software Engineering Course Notes Set 3: Software Process Maturity Computer Science.
Making knowledge work harder Process Improvement.
The Capability Maturity Model for Software: An Overview
A Tailorable Software Process Mini-Assessment Method SEPG ‘99 Conference Diane L. McDonald Carol A. Pilch GTE Government Systems Government Systems.
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
Cmpe 589 Spring Fundamental Process and Process Management Concepts Process –the people, methods, and tools used to produce software products. –Improving.
1 Software Engineering Muhammad Fahad Khan Software Engineering Muhammad Fahad Khan University Of Engineering.
PROCESS ASSESSMENT AND IMPROVEMENT. Process Assessment  A formal assessment did not seem financially feasible at the onset of the company’s process improvement.
Capability Maturity Model. What is CMM? n CMM: Capability Maturity Model n Developed by the Software Engineering Institute of the Carnegie Mellon University.
School of Business Administration
State of Michigan Achieving Software Process Improvement with
CMMI Q & A.
A possible solution: Personal Software Process (PSP)
Version 0.1Assessment Method Overview - 1 Process Assessment Method An objective model-independent method to assess the capability of an organization to.
Software Engineering Lecture 16.
Capability Maturity Model
Capability Maturity Model
Presentation transcript:

Org Name Org Site CMM Assessment Kick-off Meeting Dates of assessment

Kick-off Meeting Agenda Assessment Team Introductions Assessment Purpose & Definition Assessor Qualifications On-site Assessment Process Assessment Scoring Assessment Outputs On-site schedule Questions

Assessment Team Introductions Team Leader: Name, Org, x years Software Team Member: Name, Org x years Software

Assessment Purpose Assessment of organization’s software development process and improvement process Independent Progress Check Drives continuous improvement Effectiveness of continuous improvement team Institutionalization of processes created (since the last assessment) Findings drive action plan Sharing of best practices

What the assessment team needs from you A Candid Discussion with all the Assessment Participants (All Interview Groups, etc.) covering Goals and Expectations and some other key issues: No Punishment, no personal attribution for opinions and findings discussed during group interview sessions, positive attitudes Openness and honesty is expected Collaborative effort to assess the organization

Assessment Definition Appraisal of software development processes by objective team (4 assessors) 3 external assessors & 1 internal assessor Self-assessment for organizations to internally measure improvement progress

Assessor Qualifications Collectively, assessment team must have 25 years of software development experience At least one member with 6 years project management experience Lead Assessors must have 10 years software development experience Direct experience in multiple KPAs Three external assessors & 1 internal assessor, each with CMM knowledge training, & experience

Assessment Scoring KPAs scored on a 0-10 scale Scored on 18 CMM KPAs Score is based on KPA Goal Satisfaction CMM “Score” is a Maturity Level (2,3,4, or 5)

On-site Scoring Rating System(s) Explanations Satisfied: The organization’s practices associated with the CMM component are implemented and institutionalized either as defined in the CMM or with an adequate alternative. Not satisfied There are significant weaknesses in the organization's implementation and institutionalization of practices associated with the CMM component, as defined, and no adequate alternative is in place Not applicable The CMM practices associated with the CMM component are not applicable in the organization environment Not rated The associated assessment findings do not meet coverage criteria, or the CMM component falls outside the scope of the assessment

KPAs for Maturity level 2 Repeatable KPAsGoal 1Goal 2Goal 3Goal 4 Fully Satisfied Not Satisfied Not Applicable Not Rated Requirements management Project planning Project tracking and oversight Software subcontract management Software quality assurance Configuration management

KPAs for Maturity Level 3 Defined KPAsGoal 1Goal 2Goal 3Goal 4 Fully Satisfied Not Satisfied Not Applicable Not Rated Organisation process focus Organisation process definition Training program Integrated software management Software product engineering Intergroup co-ordination Peer reviews

KPAs for Maturity Level 4 Managed KPAsGoal 1Goal 2Goal 3Goal 4 Fully Satisfied Not Satisfied Not Applicable Not Rated Quantitative Process Management Software Quality Management

KPAs for Maturity Level 5 Optimising KPAsGoal 1Goal 2Goal 3Goal 4 Fully Satisfied Not Satisfied Not Applicable Not Rated Defect Prevention Technology Change Management Process Change Management

Motorola KPAs Goal 1Goal 2Goal 3Goal 4 Fully Satisfied Not Satisfied Not Applicable Not Rated Security & Disaster Recovery Motorola Quality Metrics

Ratings of Assessment The CMM level is: Level A MAJOR ACHIEVEMENT!

Assessment Outputs CMM maturity Level Strengths of Organization Findings for Organization (Opportunities) For each KPA: referenced to KPA goal Subsequent action plan addresses the findings Recommendations All Outputs aggregated at organization level

Findings Summary Level 2 KPAs: Level 3 KPAs: Level 4 KPAs: Level 5 KPAs:

On-site Assessment Process Functional area discussions (typically 4 groups) Project Leaders (PLs), Engineers/developers/Testers (FAR1), Sponsors or Managers & other key people affecting software process (Mgrs & other key people) Software process Engineering (SEPG)/ SQA/Configuration Management (CM), & System Administration (FAR2)

On-site Assessment Process (cont.) Functional area discussions Covers Goals, expectations, & other key issues Cross sample of representatives Groups of 6-10 representatives 2 to 3 hour discussions with opinions & findings Collaborative effort with organization Review of defined & documented process Review of evidence (application of defined process)

On-Site Schedule

Managers Software Quality Assurance Organization Process Focus Organization Process Definition Training Program Intergroup Coordination Quantitative Process Management Software Quality Management Motorola Quality Metrics Project Leaders Requirements Management Software Project Planning Software Project Tracking and Oversight Software Configuration Management Integrated Software Management Software Product Engineering Peer Reviews Defect Prevention CMM KPAs to Consider for Groups

FAR1 Requirements Management Software Project Planning Software Project Tracking and Oversight Training Program Integrated Software Management Software Product Engineering Intergroup Coordination Peer Reviews FAR2 Software Quality Assurance Software Configuration Management Organization Process Focus Organization Process Definition Quantitative Process Management Software Quality Management Technology Change Management Process Change Management Motorola Quality Metrics CMM KPAs to Consider for Groups