1 Quantitative Management A Paradigm Shift Madhusudana Rao Parella Sreerama Murthy Yellayi Sumeeta Hari Satyam Computer Services.

Slides:



Advertisements
Similar presentations
Quality control tools
Advertisements

Formal Process of QA and quality related certifications Formal Process of QA and quality related certifications MIM 3 rd year – Sem V Abhishek Mishra –
More CMM Part Two : Details.
1 Brief Descriptions of CMM KPAs CEN 6070 Summer 2004.
Root Cause Analysis Procedure (IMSP525) Training
CMMI PMC Group Members Inam ul Haq Sajjad Raza Nabeel Azam
18 th International Forum on COCOMO and Software Cost Modeling October 2003 Use of Historical Data by High Maturity Organizations Rick Hefner, Ph.D.
SE 470 Software Development Processes James Nowotarski 12 May 2003.
1 R&D SDM 1 Software Project Management Capability Maturity Model 2009 Theo Schouten.
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
Quality evaluation and improvement for Internal Audit
Project Management Methodology (PMM)
Paul Prunty The 7 Basic Quality Tools ~ The DMAIC Process Continuous Improvement and … To a hammer, everything’s a nail … How many tools do you have in.
Using A Defined and Measured Personal Software Process Watts S. Humphrey CS 5391 Article 8.
Standardization. Introduction A standard is a document. It is a set of rules that control how people should develop and manage materials, products, services,
Tools, Training and Transformation Readying the Healthcare Workforce for Transformation Norma Morganti – Executive Director Health Information Technology.
Capability Maturity Model
IMPROVEMENT TOOLS Mahendrawathi ER, Ph.D. Outline  Classification of improvement tools  Purpose of the tools  Extent of change  Time and resource.
Using Six Sigma to Achieve CMMI Levels 4 and 5
1 Industrial Design of Experiments STAT 321 Winona State University.
Even More SQA: CAPA Corrective and Preventive Actions.
8/27/20151NeST Controlled. 2 Communication Transportation Education Banking Home Applications.
Tools for Process Improvement
© Mahindra Satyam 2009 Project Metrics QMS Training.
COMPGZ07 Project Management Presentations Graham Collins, UCL
Quality Control Tools A committee for developing QC tools affiliated with JUSE was set up in April Their aim was to develop QC techniques for.
1 Software Quality Engineering CS410 Class 5 Seven Basic Quality Tools.
CMMI Technology Conference and User Group November 2003 Experiences with Leveraging Six Sigma to Implement CMMI Levels 4 and 5 Jeff Facemire & Hortensia.
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.
C ONTINUOUS Q UALITY I MPROVEMENT M ODEL The Deming cycle: Originally developed by Walter Shewart, but renamed in 1950s because Deming promoted it extensively.
Lecture 1 Introduction to Software Engineering
Software Engineering - Spring 2003 (C) Vasudeva Varma, IIITHClass of 39 CS3600: Software Engineering: Standards in Process Modeling CMM and PSP.
Software Engineering Lecture # 17
NDIA Systems Engineering Supportability & Interoperability Conference October 2003 Using Six Sigma to Improve Systems Engineering Rick Hefner, Ph.D.
Software Project Management With Usage of Metrics Candaş BOZKURT - Tekin MENTEŞ Delta Aerospace May 21, 2004.
By Ritesh Reddy Nagaram.  Organizations which are developing software processes are facing many problems regarding the need for change of already existing.
Software Engineering Principles Principles form the basis of methods, techniques, methodologies and tools Principles form the basis of methods, techniques,
Thomas L. Gilchrist Testing Basics Set 4: Strategies & Metrics By Thomas L. Gilchrist, 2009.
1 Presentation Template: Instructor Comments u The following template presents a guideline for preparing a Six Sigma presentation. An effective presentation.
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.
Computing and SE II Chapter 15: Software Process Management Er-Yu Ding Software Institute, NJU.
Project quality management. Introduction Project quality management includes the process required to ensure that the project satisfies the needs for which.
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…
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming.
Software Quality Assurance SOFTWARE DEFECT. Defect Repair Defect Repair is a process of repairing the defective part or replacing it, as needed. For example,
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
Traditional Economic Model of Quality of Conformance
The seven traditional tools of quality I - Pareto chart II – Flowchart III - Cause-and-Effect Diagrams IV - Check Sheets V- Histograms VI - Scatter Diagrams.
Data Collection & Analysis ETI 6134 Dr. Karla Moore.
© 2005 Wiley1 Total Quality Management Chapter 5.
Job Analysis. The process of collecting and organizing information about jobs performed in the organization and the principle elements involved in performing.
Software Engineering (CSI 321) Software Process: A Generic View 1.
COMPGZ07 Project Management CMMI Project Planning Lecture 5b Graham Collins, UCL.
UTA/ARRI. Enterprise Engineering for The Agile Enterprise Don Liles The University of Texas at Arlington.
Mahindra Satyam Confidential Quality Management System Software Defect Prevention.
Introduction to Quality and Statistical Process Control
CS4311 Spring 2011 Process Improvement Dr
Software Engineering (CSI 321)
Information Technology Project Management – Fifth Edition
Overview (1 of 2) Definition Use within organizations
Quality Certification
Abdulla Jassim Abdulla
Capability Maturity Model
Chapter 10 Quality Improvement.
Fishbone Diagrams (cause and effect, or Ishikawa diagrams)
Capability Maturity Model
Presentation transcript:

1 Quantitative Management A Paradigm Shift Madhusudana Rao Parella Sreerama Murthy Yellayi Sumeeta Hari Satyam Computer Services

2 Before we proceed… A phenomenon will be said to be controlled when, through the use of past experience, we can predict, at least within limits, how the phenomenon may be expected to vary in the future. Walter A. Shewhart, 1931

3 Agenda Time to transition from one Maturity Level (ML) to other Process at ML 3 Issues with ML 3 Process Variation Process and Tools at ML4 What is different at ML4 Importance of statistical thinking Conclusion

4 What SEI data shows? Moving to ML 4 from ML 3 takes longest time Source: CMMI Maturity Profile, SEPG 2003

5 Peer Reviews at Maturity Level 3 Peer Review process at level 3 –Identify work products for peer review –Prepare for peer review –Identify peer review team –Conduct peer review –Track and close action items –Analyze peer review data Effectiveness of the peer review process-unknown Process capability of peer review process is based on intuition, judgment

6 Peer Reviews at Maturity Level 3 If the peer review speed is –10 pages/hour –30 pages/hour Which is an effective peer review? The one with 10 pages/hour or the one with 30 pages/hour ? How to find the reasonable peer review speed ?

7 Peer Review data at Maturity Level 3 Data not available from all peer reviews Available data forms are not complete Unable to reach any conclusions on process capability Measures –Code review speed –Document review speed Wide variation in data

8 Why Quantitative Management? If all the projects are following the same organizational processes, why the huge variation in the process performance parameters? Causes of Variation? How do we know that the process is improving? How do we arrive at the process capability?

9 Understanding Variation Quantitative Measurement Quantitative Management Quantitative Improvement

10 Issues that Contribute to Variation The range of tailoring of peer review process: from almost no tailoring (taking organization process as is) to development of detailed peer review procedure Size and complexity of work products reviewed Issues like knowledge and skill level of reviewers

11 Issues that contribute to Variation Peer Reviews Definition of a defect Recording of defects Specify standard measures Completeness of data Training and competence Duration of peer review Preparation for peer review Team size ComplexityReference Standards New/Reusable code

12 Tools Most of the seven Quality Control (QC) tools –Run Chart –Pareto Chart –Flow Chart –Histogram –Cause and Effect Diagram –Scatter Diagram –Control Chart Control Chart is widely used tool

13 Peer Review Process at ML 4 Organization peer review process was updated based on the issues identified Peer review process was further divided into –Document review (Complexity Level 3) –Code review (Complexity Level 2) –Design review (Complexity Level 1) Special causes of variation are eliminated there by bringing the process under statistical control The process capability was established for all sub processes

14 How maturity level 4 differ.. Maturity levels 2 and 3 are about implementation of processes Level 4 is understanding the effectiveness and efficiency of the processes –Effectiveness measures the extent to which the process produces intended results –Efficiency measures how well we use our process to produce results At Level 4 understand, measure and control variation in a process

15 How maturity level 4 differ.. At maturity level 4 the processes are aimed towards a goal, thereby setting a benchmark for process performance The process interactions has impact on the variation A prescriptive approach may not help beyond maturity level 3 Use of past data for predictive models development

16 Importance of statistical thinking The underlying principles are: –All work occurs in a system of interconnected processes –Variation exists in all processes –Understanding and reducing variation are the keys to success Holistic process approach and key to quantitative management

17 Conclusion An organization at maturity levels 2 and 3 focus on milestones When the same processes are quantitatively managed, the organization shifts the focus to variation or exceptions in the process performance Quantitative Management is a key for the organizational transformation from ‘Management by milestones’ to ‘Management by exceptions’