ESTM Associates, Inc. Excellence in Science, Technology and Management 1www.estm.biz Applying Six Sigma to Software Development: A Practical Guide Dr.

Slides:



Advertisements
Similar presentations
Project Management and Software Quality See accompanying Word file “Software PM tools 3”
Advertisements

Test Inventory A “successful” test effort may include: –Finding “bugs” –Ensuring the bugs are removed –Show that the system or parts of the system works.
ITIL: Service Transition
©2006 OLC 1 Process Management: The Foundation for Achieving Organizational Excellence Process Management Implementation Worldwide.
Management: Analysis and Decision Making
LeanSigma ® Facilitator Training Module 4 – Voice of the Customer.
Managing Quality Chapter 5.
© Copyright Richard W. Selby and Northrop Grumman Corporation. All rights reserved. 0 Process Synchronization and Stabilization February 2007 Rick.
02/25/06SJSU Bus David Bentley1 Chapter 12 – Design for Six Sigma (DFSS) QFD, Reliability analysis, Taguchi loss function, Process capability.
1 Software Quality Metrics Ch 4 in Kan Steve Chenoweth, RHIT What do you measure?
C LO GO. your family site your site here LOG O Six Sigma has become a popular quality performance tool in many organisations to drive out variability,
Overview of Lean Six Sigma
Barry Murash MBBit Nortel 2007
Capability Maturity Model
SIX SIGMA. What is six sigma? Sigma is a measure of “goodness: the capability of a process to produce perfect work. A “defect” is any mistake that results.
Six Sigma What is Six Sigma?
Product Lifecycle Management Cost of Quality Pasi Kaipainen, Mika Huhta.
Software Performance Engineering Failure Modes and Effects Analysis Presented by Kevin Mobley.
Six Sigma By: Tim Bauman April 2, Overview What is Six Sigma? Key Concepts Methodologies Roles Examples of Six Sigma Benefits Criticisms.
© 2002 Systex Services Capability and Improvement - from Cpk to Six Sigma.
Operations Management
Using Microsoft Project for Implementation of Six Sigma Projects A Tools and Tips Presentation Nora Gessert, Pcubed.
Group: Anju, Ashok, Justin, Joe, Christina.  D-Define  M- Measure  A-Analyze  I-Improve  C-Control.
6 Sigma Hazırlayanlar : Emine Yılmaz Cansın Eminoğlu.
S T A M © 2000, KPA Ltd. Software Trouble Assessment Matrix Software Trouble Assessment Matrix *This presentation is extracted from SOFTWARE PROCESS QUALITY:
Achieving Better Reliability With Software Reliability Engineering Russel D’Souza Russel D’Souza.
By Anthony W. Hill & Course Technology 1 User Support Management Beisse.
1 Software Quality Engineering CS410 Class 5 Seven Basic Quality Tools.
SIX-SIGMA QUALITY Chapter Understand total quality management. 2. Describe how quality is measured and be aware of the different dimensions of quality.
System Analysis and Design
N By: Md Rezaul Huda Reza n
© 2007 Towers Perrin Does being a Top Employer make a difference in employee engagement? How - And Why - Top Employers Are Building An Oasis for Talent.
CPIS 357 Software Quality & Testing
Resources Performance time. resources Performance time 2.
HOW CAN PROFICY SERVE THE ENERGY ISSUE? by Coleman Easterly Feb 2008.
Chapter 3: Software Maintenance Process Omar Meqdadi SE 3860 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
1.  Project: temporary endeavor to achieve some specific objectives in a defined time  Project management ◦ Dynamic process ◦ Controlled and structured.
NDIA Systems Engineering Supportability & Interoperability Conference October 2003 Using Six Sigma to Improve Systems Engineering Rick Hefner, Ph.D.
ASQ Raleigh ASQ Raleigh Section 1113 Six Sigma SIG DMAIC Series.
CS532 Term Paper Applying Six Sigma Methodology In Software Engineering Sourabh Bandyopadhyay.
Software Metrics – part 2 Mehran Rezaei. Software Metrics Objectives – Provide State-of-art measurement of software products, processes and projects Why.
Putting the “Engineering” in Software Engineering: Technology Infrastructure in Process Improvement Adam Kolawa, Ph.D. CEO, Parasoft.
1 Requirements Management - General concepts - Noureddine Abbadeni King Saud University College of Computer and Information Sciences Based on “Software.
Radhakrishna.Thatavarti Six Sigma The Continuous Improvement Culture Presentation By Thatavarti Venkata RadhaKrishna
Copyright © Six Sigma Academy International, LLC All Rights Reserved Executive Case Study Credit Card Declines.
© 2001 Six Sigma Academy © 2003 Six Sigma Academy1 Champion Workshop Key Concepts.
SOFTWARE METRICS. Software Process Revisited The Software Process has a common process framework containing: u framework activities - for all software.
1 66 1 Six Sigma – Basic overview. 2 66 2 WHAT IS THIS SIX SIGMA ? A Philosophy A Statistical Measurement A Metric A Business Strategy make fewer.
Project Storyboard (Page 1 of 2)
© G. A. Motter, 2006, 2008 & 2009 Illustrated by Examples Quality Function Deployment and Selection Matrices Customer Driven Product Development.
Six Sigma 6s.
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
UNIT 5.
IT Project Management, Third Edition Chapter 8 1 Chapter 5: Project Quality Management.
Done By: Asila AL-harthi Fatma AL-shehhi Fakhriya AL-Omieri Safaa AL-Mahroqi.
NATIONAL IT AUTHORITY MODULE 5 PROCESS HANDLING SKILLS AND KNOWLEDGE.
Product Lifecycle Management
ITIL: Service Transition
Six Sigma.
Software Configuration Management
Project Management PTM721S
DRIVING IMPROVEMENTS Through Six MahindraSatyam
Six Sigma Approach.
TechStambha PMP Certification Training
Software Requirements
Software Project Sizing and Cost Estimation
Chapter 1 (pages 4-9); Overview of SDLC
DMAIC Roadmap DMAIC methodology is central to Six Sigma process improvement projects. Each phase provides a problem solving process where-by specific tools.
Software metrics.
Six Sigma Introduction 1 1.
Presentation transcript:

ESTM Associates, Inc. Excellence in Science, Technology and Management 1www.estm.biz Applying Six Sigma to Software Development: A Practical Guide Dr. Bill Eventoff ESTM Associates, Inc. 8 Morningside Drive ♦ Toms River, NJ (732) ♦ © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 2www.estm.biz Motivation Software Development Large Opportunity for Improvement Approximately 25% of software projects are canceled Average project exceeds –Costs by 90% –Schedule by 120% Risk of project failure increases with size © 2002 ESTM Associates, Inc. Six Sigma Well-defined improvement approach Impressive track record of achievements Adaptable

ESTM Associates, Inc. Excellence in Science, Technology and Management 3www.estm.biz But Software Development is Not a Typical Application Process Oriented, but –Inputs often ill-defined –Outputs often difficult to fully evaluate –Performance highly influenced by human factors (e.g., knowledge, skills, experience, etc.) Significant natural variation © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 4www.estm.biz Key Factors in Software Project Failures Risk Factor% of “MIS” Projects Requirements Failures Creeping Requirements80% Expectation Failures Excessive Schedule Pressure65% Execution Failures Low Quality60% Cost Overruns55% Inadequate Configuration Management 50%

ESTM Associates, Inc. Excellence in Science, Technology and Management 5www.estm.biz Applying Six Sigma to Software Development © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 6www.estm.biz Fuzzy Front End Six Sigma DFSS © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 7www.estm.biz Balance the VOC and the VOB Voice of the Customer Voice of Business

ESTM Associates, Inc. Excellence in Science, Technology and Management 8www.estm.biz VOC – Voice of the Customer Understand Internal and External Customers and Target Environment © 2002 ESTM Associates, Inc.

Building a Customer Matrix Segments Types of Customers Lead User Demanding Lost Lead Had But Lost U.S. Europe Asia © 2002 Six Sigma Advantage, LLC

ESTM Associates, Inc. Excellence in Science, Technology and Management 10www.estm.biz VOC – Voice of the Customer Understand Internal and External Customers and Target Environment Identify, Characterize and Verify Critical to Quality (CTQ) Requirements –Interviews, focus groups, use cases, etc. –Preference surveys and Kano analysis © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 11www.estm.biz Kano Analysis Dissatisfiers (or basic requirements) –“Must be” requirements –These features must be present to meet minimal expectations of customers Satisfiers (or variable requirements) –The better or worse you perform on these requirements, the higher or lower will be your rating from customers Delighters (or latent requirements) –These are features, factors, or capabilities that go beyond what customers expect, or that target needs customers can’t express themselves © 2002 ESTM Associates, Inc.

The Kano Model How the Customer Feels Neutral Satisfier Must-Be Delighter Level of Functionality Delivered for a particular requirement Low to None High Delighted Very Dissatisfied Satisfied, but I expect it this way I can live with it © 2002 Six Sigma Advantage, LLC

ESTM Associates, Inc. Excellence in Science, Technology and Management 13www.estm.biz VOC Output: Prioritized CTQs RequirementUse-caseKanoPriority Manage database interfaces Verifying data content integrity S4 Manage Network I/O Moving client- server data M3 Optimizing data transfer D3.5 Provide real-time user access Minimizing system response time M5 © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 14www.estm.biz VOC – Voice of the Customer Understand Internal and External Customers and Target Environment Identify, Characterize and Verify Critical to Quality (CTQ) Requirements –Interviews, focus groups, use cases, etc. –Preference surveys and Kano analysis Establish measures for CTQ requirements © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 15www.estm.biz VOC Output: Fully Characterized CTQs Requirements Use-Case KanoPriority Measure Manage Database Interfaces MinimumAverageStrong Verifying data content integrity S4 ≤ 1 record/1,000≤ 1 record/10,000≤ 1 record/100,000 Manage Network I/O Moving client- server data M3 100 records/min.500 records/min.800 records/min. Optimizing data transfer D3.5 Hooks for user supplied compression Top 5 compression schemes supplied Top 10+ compression schemes supplied and fully integrated © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 16www.estm.biz VOB - Voice of Business Analyze Design Options –Estimate customer satisfaction –Level of effort –Capability to deliver –Balance VOC and VOB © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 17www.estm.biz Analyze Design Options RequirementUse-CaseKanoPriorityBaseFullBase Effort Full Effort Manage database interfaces Verifying data content integrity S Manage Network I/O Moving client- server data M Optimizing data transfer D Customer Sat. Score Effort Score Design Options Level of Effort © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 18www.estm.biz Analyze Design Options RequirementUse-CaseKanoPriorityBaseFullBaseE ffort Full Effort Manage database interfaces Verifying data content integrity S Manage Network I/O Moving client- server data M Optimizing data transfer D Customer Sat. Score Effort Score = F(Kano, Priority, Feature Level) © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 19www.estm.biz Analyze Design Options RequirementUse-CaseKanoPriorityBaseFullBaseE ffort Full Effort Manage database interfaces Verifying data content integrity S Manage Network I/O Moving client- server data M Optimizing data transfer D Customer Sat. Score Effort Score = ∑ Effort Estimates © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 20www.estm.biz Concept Selection © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 21www.estm.biz Computing Productivity Historically, for each project we should know Size, Effort, and Duration )( )( / /34 31 * (SLOC) yearsDuration B StaffYearsEffort Size PP      © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 22www.estm.biz Schedule Compression 3 )( )( torelates yearsDuration StaffYearsEffort MBI Buildup RateEquation Output 1Slow7.3 2Mod. Slow14.7 3Moderate26.9 4Rapid55 5Very Rapid89 Manpower Buildup Index, MBI © 2002 ESTM Associates, Inc.

Rayleigh Curve © 2002 Six Sigma Advantage, LLC

ESTM Associates, Inc. Excellence in Science, Technology and Management 24www.estm.biz MBI = 1 (Slow)Concept 1 Duration (months)15.2 Effort (staff months)77.3 Released Defects14.1 Effort Cost$966,250 Duration Adjustment Defect Repair Cost$239,700 Net Value$19,482,050 MBI = 3 (Moderate)Concept 1 Duration (months)13 Effort (staff months)119.4 Released Defects267 Effort Cost$1,492,500 Duration Adjustment$1,400,000 Defect Repair Cost$453,900 Net Value$20,141,600 Balancing VOC and VOB Business Value$20,000,000 Feature Value$688,000 © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 25www.estm.biz Balancing VOC and VOB MBI = 5 (Very Rapid)Concept 1 Duration (months)11.7 Effort (staff months)220.7 Released Defects508 Effort Cost$2,758,750 Duration Adjustment$1,400,000 Defect Repair Cost$663,600 Net Value$18,665,650 MBI = 3 (Moderate)Concept 1 Duration (months)13 Effort (staff months)119.4 Released Defects267 Effort Cost$1,492,500 Duration Adjustment$1,400,000 Defect Repair Cost$453,900 Net Value$20,141,600 Business Value$20,000,000 Feature Value$688,000 © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 26www.estm.biz VOB - Voice of Business Analyze Design Options –Estimate customer satisfaction –Level of effort –Capability to deliver –Balance VOC and VOB Select Concept and Approach –Flesh out concept QFD FEMA –Verify and refine approach Defect analysis Schedule simulation © 2002 ESTM Associates, Inc.

Capability to Deliver on Time Probabilistic Scheduling Frequency Chart Certainty is 94.90% from -Infinity to days ,000 Trials 4 Outliers Forecast: F52 How much confidence should we have in the schedule? … At a 95% confidence level latest mid March, 2003 (+ 43 days) earliest mid January, 2003 (- 15 days) Upper Spec Limit (USL) © 2002 Six Sigma Advantage, LLC

ESTM Associates, Inc. Excellence in Science, Technology and Management 28www.estm.biz Process Improvement Standard Six Sigma DMAIC Process © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 29www.estm.biz Application to Software X Prerequisites: Processes must be well defined © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 30www.estm.biz DMAIC Example Problem Statement –Post release maintenance has increased by 30% since the end of last fiscal year and is now limiting new product development. Goal Statement –Reduce post release maintenance by 40% by the end of Q4’2003. © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 31www.estm.biz Measure – Data Collection Total Problems Fixed Prior to Release Per Project –Pre-Release Defects: defects found and fixed during development and testing Total Post Release Problems Per Project –Released Defects: defects reported by customers Types of Post Release Problems –All projects –Per project © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 32www.estm.biz Analysis Pre-Release Defects = f(Size) © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 33www.estm.biz Analysis Escaped defects proportional to pre-release defects –No significant variation in Defect Containment Effectiveness DCE = Pre-Release Defects/(Pre-Release Defects + Escaped Defects) © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 34www.estm.biz Analysis Most Escaped Defects are Code Related © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 35www.estm.biz Improve Improve the Effectiveness of Code Inspections –Factors Size of unit (LOC) Preparation time (LOC/hour) Inspection time (LOC/hour) Number of reviewers –Measure Number of identified defects © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 36www.estm.biz Improve Improve the Effectiveness of Code Inspections –Conduct DOE Determine most effective combination of factors –Verify DOE results Pilot test using real project © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 37www.estm.biz Control Establish Performance Standard for Code Inspections –Defects/KLOC Monitor Performance –Take action when unacceptable performance observed © 2002 ESTM Associates, Inc.

ESTM Associates, Inc. Excellence in Science, Technology and Management 38www.estm.biz Questions © 2002 ESTM Associates, Inc.