CMMI Awareness Training
CMMI Awareness Training
CMMI Awareness Training
Objectives of Training
Familiarize with concepts of CMMI models Nomenclature used Contents and interpretation Process improvements Familiarize with Yashs Approach For CMMI Initial gap analysis External services from CQAL for implementation & Assessment Broad roadmap Where we are
Contents
Quality standards / models and their relevance to our operations Capability maturity models, evolution of CMMI Comparative study of ISO and CMMI CMMI Representations CMMI Model Structure, Components Maturity levels, Disciplines, Process Areas One process area details ref to PDF and its structure ISO- CMMI Integrated quality system QMS CMMI model Mapping Audits and Assessments CMMI Initiatives at YASH Action plans
Model Selection
Quality models are designed for specific purposes.
ISO 9001:2000 - Standard is a quality standard which can be adopted by any organization - software, manufacturing, services etc. It gives a basic framework for the process implementation in the organization.
CMMI - Capability Maturity Model Integration, is more specific to software industry to evaluate a software contractors capability to deliver quality software. Six Sigma Quality - Motorola developed a concept called Six Sigma Quality that focuses on defect rates, only 3.4 items per million are outside of the acceptable level. TQM - Strategic, integrated management system for achieving customer satisfaction, which involves all managers and employees and uses quantitative methods to continuously improve an organization's processes.
What is CMMI?
CMMI is: a model that provides a set of best practices that address productivity, performance, costs, and stakeholder satisfaction a model which provides a structured view of process improvement across an organization CMMI can help: set process improvement goals and priorities provide guidance for quality processes provide a yardstick for appraising current practices CMMI is NOT: a set of bolt-on processes that last only as long as the wheel is squeaking. CMMI provides a consistent, enduring framework that accommodates new initiatives. restricted to a single discipline (i.e. Software Engineering or Systems Engineering). CMMI focuses on the total software intensive system problem and integrates multiple disciplines into one process-improvement framework that eliminates inconsistencies and reduces duplication
CMMI History
CMMI History
In 1987 a study was conducted by the Dept. of Defense (DOD). 17 projects Estimated duration of 28 months Actual duration exceeded estimate by an average of 20 months DOD worked with the Software Engineering Institute (SEI) to develop a model to improve the development process. CMM was implemented in 1991. CMMI came about in 1997 as an integration of 3 different models.
CMM v1.0 was developed in August 1991 by SEI for Software industry
Different structures, formats, terms, ways of measuring maturity Causes confusion, especially when using more than one model
Hard to integrate them in a combined improvement program Hard to use multiple models in supplier selection
FAA
iCMM
CMMI Models
Source Models
Capability Maturity Model for Software (SW-CMM)
System Engineering Capability Model (SECM) Integrated Product Development Capability Maturity Model (IPDCMM)
CMMI Model
CMMI V 1.1: An integrated model of the above - released in 2002 CMMI V 1.2 is scheduled in Aug 2006
Disciplines
CMMI model encompasses
Systems engineering (SE)
Covers the development of total systems, which may or may not include software Focus on transforming customer needs, expectations, and constraints into product solutions and supporting those product solutions throughout the product life cycle
Software (SW)
Covers the development of software systems Focus on applying systematic, disciplined, and quantifiable approaches to the development, operation and maintenance of software
CMMI
Model Detailed Progressive steps Institutionalization and guidance Designed specifically for software organizations.
TEST
CMMI Is it a standard or a model?
Model - A model is a simplified representation, which contains all the essential elements. List the four disciplines of CMMI Model.. What is YASHs option? SE, SW, IPPD, SS: Yash opted for SE/SW
Representations
Two representations
Staged: Focus is on a Maturity Level by mastering sets of Process Areas that are grouped into 5 Maturity Levels Continuous: Focus is on selected portions of Process Areas to achieve a Process Capability Level
Managed
(7)
Performed
5
5 Optimizing 4 Quantitatively Managed
Capability
4 3 2 1 0
3 Defined
2 Managed
1 Performed 0 Incomplete
REQM PP
PMC
etc
Capability Levels Yash has opted for Staged model of CMMI SE/SW.
Process Area
An Example
Model Components
Process Areas: A process area is a cluster of related practices Specific Goals: Address the unique characteristics that describe what must be implemented to satisfy the process area. Specific Practices: An activity that is considered important in achieving the associated specific goal. Common Features: Four common features organized as the generic goals and practices of each process
Commitment to Perform (CO) Ability to Perform (AB) Directing Implementation (DI) Verifying Implementation (VE)
Model Components(Contd)
Typical Work Products: Output from a specific or generic
practice.
Maturity Levels
7 Process Areas
Requirements Management (REQM)
11 Process Areas
Requirements Definition(RD) Technical Solution (TS) Product Integration(PI) Verification(Ver) Validation (Val) Decision Analysis & Resolution (DAR)
Org. Process Focus(OPF) Org. Process Definition (OPD) Org. Training (OT)
Level 4: Quantitatively Managed - Quantitative analysis of processes and products for monitoring and control
MANAGE PROJECTS QUANTITATIVELY Statistically manage the projects processes and subprocesses MANAGE THE ORGANIZATION QUANTITATIVELY Understand process performance; Quantitatively manage the organizations projects
2 process Areas
Quantitative Project Management (QPM)
2 Process Areas
Causal Analysis and Resolution (CAR) Organizational Innovation & Deployment (OID)
ADOPT IMPROVEMENTS
Identify and deploy new tools and process improvements to meet needs and business objectives
Dept. A
Middle Management
Div. AA
Dept. B Div. BB
Dept. C
Projects
Project 1
Project 2
Project 3
Project 4
Processes
Dept. A
Div. AA
Dept. B
Dept. C
Middle Management
Div. BB
Projects
Project 1
Project 2
Project 3
Project 4
Processes
Dept. A Div. AA
Dept. B Div. BB
Dept. C
Projects Processes
Project 1
Project 2
Project 3
Project 4
Process Areas
Maturity Level - 2 Process Areas
Requirements Management Project Planning Project Monitoring and Control
Configuration Management
Practices
1.1 Estimate the scope of the project 1.2 Establish estimates of work product and task attributes 1.3 Define project life cycle 1.4 Determine estimates of effort and cost 2.1 Establish the budget and schedule 2.2 Identify project risks 2.3 Plan for data management 2.4 Plan for project resources 2.5 Plan for needed knowledge and skills 2.6 Plan stakeholder involvement 2.7 Establish the Project Plan 3.1 Review plans that affect the project 3.2 Reconcile work and resource levels 3.3 Obtain plan commitment (see 10 generic practices)
SG3 Commitments to the plan are established GG2 The process is institutionalized as a managed process
Generic Goals
A generic goal describes what institutionalization must be achieved to satisfy a process area.
Each process area at maturity level 2 contains the following generic goal:
GG 2 Institutionalize a Managed Process
Each process area at maturity level 3 or higher contains the following generic goal:
GG 3 Institutionalize a Defined Process
4 Common Features
Common features are model components that are not rated in any way. They are only groupings that provide a way to present the generic practices.
1. 2. 3. Commitment to Perform (CO): Creating policies and securing sponsorship. Ability to Perform (AB): Acquiring resources Directing Implementation (DI): Managing the performance of the process, integrity of its work products, and involving relevant stakeholders. Verifying Implementation (VE): Review by higher level management and objective evaluation of conformance to process descriptions, procedures, and standards.
4.
Process Area
RM
Elaboration
This policy establishes organizational expectations for managing requirements and identifying inconsistencies between the requirements and the project plans and work products.
This policy establishes organizational expectations for estimating the planning parameters, making internal and external commitments, and developing the plan for managing the project The plan called for in this generic practice would address the comprehensive planning for all of the specific practices in this process area, from estimating the scope of the project all the way to obtaining commitment for the project plan. In other words, this generic practice calls for one to plan the plan. This plan for performing the organizational process performance process may be included in or referenced by the organization's process-improvement plan Examples of Resources:Cost tracking systems, Effort reporting systems, Action-item-tracking systems, Project management and scheduling programs
PP
PP
OPP
PMC
Process Area
MA
Elaboration
Measurement personnel may be employed full time or part time. A measurement group may or may not exist to support measurement activities across multiple projects.
Examples of training: Application domain of the product and product components, Design methods, Interface design, Unit testing techniques, Standards (e.g., product, safety, human factors, environmental Examples of training: Application domain, Product integration procedures and criteria, Organization's facilities for integration and assembly, Assembly methods, Packaging standards Examples of work products: Specifications of base and derived measures, Base and derived measurement data sets, Data analysis tools Examples of work products: Access lists, Change status reports, Change request database, CCB meeting minutes, Archived baseline
TS
PI
MA
CM
Work Product: Any artifact produced by a process. Tailoring Guidelines: Tailoring guidelines cover (1) selecting a standard
process, (2) selecting an approved life-cycle model, and (3) tailoring the selected standard process and life-cycle model to fit project needs.
Validation: Confirms that the product, as provided, will fulfill its intended
use.
Navigate through CMMI PDF file for a process area Compare existing QMS activities with CMMI PAs,Specific goals, sp. Practices and work products
Practice Area
Requirements Management
QMS Procedure
PRP-004 Requirements Management Procedure PRP-010 Change Management Procedure
Project Planning
PRP-001Software Estimation Procedure PRP-015 Project Initiation Procedure PRP-017 Data Collection and Storage Procedure PRP-020 Project Planning Procedure PRP-022 Risk Management Procedure PRP-013 Project Monitoring and Control Procedure FCM-001 Maintain Approved Suppliers List Procedure FCM-002 Purchase Products and Services Procedure FCM-003 Receive the Purchase Materials PRP-012 Project Quality Management Procedure PRP-013 Project Monitoring and Control Procedure
Practice Area
Process and Product Quality Assurance
QMS Procedure
CQS-006 Internal Quality Audit Procedure
Configuration Management
Practice Area
Requirements Development
QMS Procedure
PRP-004 Requirements Management Procedure PRP-005 High Level Design procedure PRP-023 PRP-005 High Level Design procedure PRP-006 Low Level Design procedure PRP-007 Coding Procedure PRP-021 Product Integration Procedure
Technical Solution
PRP-008 Reviews Procedure PRP-012 Quality management Procedure PRP-009 Testing procedure PRP-012 Quality management Procedure
Practice Area
Organizational Process Focus Organizational Process Definition
QMS Procedure
CQS-001 Organizational Process Improvements Procedure CQS-005 QMS Implementation CQS-002 QMS Establishment and Maintenance Procedure CQS-003 Control of Documents CQS-004 Control of Records Procedure TRN-001Training Needs Assessment and Planning Procedure TRN-002 Organize Training procedure TRN-003 Training Evaluation and Follow-up Procedure PRP-022 Risk Management Procedure PRP-021Product Integration Procedure CQS-008 Organization Process Performance & Measurement Procedure
Organizational Training
Practice Area
Quantitative Project Management
Decision Analysis and Resolution
QMS Procedure
PRP-020 Project Planning Procedure
CMN-002 Decision Analysis and Resolution Procedure CQS-009 Continual Improvements and Deployment
Level 5
Audit Analysis Reports/Noncompliance reports Corrective Actions Review the activities, status, and results with higher level management
ISO
Internal Training will be given to identified members to do internal audits.
Every year surveillance audit will be conducted. Internal audits will be conducted by internal auditors. The organization shall continually improve effectiveness of QMS through the use of the quality policy, objectives, audit results, analysis of data, corrective and preventive action and management review (Clauses from 4 to 8)
Question paper