NDIA Systems Engineering Supportability & Interoperability Conference 20-23 October 2003 Using Six Sigma to Improve Systems Engineering Rick Hefner, Ph.D.

Slides:



Advertisements
Similar presentations
Kai H. Chang COMP 6710 Course NotesSlide CMMI-1 Auburn University Computer Science and Software Engineering Capability Maturity Model Integration - CMMI.
Advertisements

More CMM Part Two : Details.
1 Brief Descriptions of CMM KPAs CEN 6070 Summer 2004.
1 State of Michigan Achieving Software Process Improvement with Capability Maturity Model (CMM)
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.
© Copyright Richard W. Selby and Northrop Grumman Corporation. All rights reserved. 0 Process Synchronization and Stabilization February 2007 Rick.
Stepan Potiyenko ISS Sr.SW Developer.
Introduction to Business Process Reengineering
18 th International Forum on COCOMO and Software Cost Modeling October 2003 Use of Historical Data by High Maturity Organizations Rick Hefner, Ph.D.
Copyright 2005 Northrop Grumman Corporation Is CMMI High Maturity Worth the Investment? Southern California SPIN 2 February 2007 Rick Hefner, Ph.D. Director,
Software Quality Processes – Part II CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 19, 2007.
Rick Hefner. Marilee J. Wheaton TRW
Lecture 11 CMM CSCI – 3350 Software Engineering II Fall 2014 Bill Pine.
Overview of Lean Six Sigma
Capability Maturity Model
Space and Airborne Systems NDIA/SEI CMMI Technology Conference Presented by N. Fleischer 1 Raytheon’s Six Sigma Process and Its Application for CMMI By.
Product Lifecycle Management Cost of Quality Pasi Kaipainen, Mika Huhta.
Six Sigma By: Tim Bauman April 2, Overview What is Six Sigma? Key Concepts Methodologies Roles Examples of Six Sigma Benefits Criticisms.
Using Six Sigma to Achieve CMMI Levels 4 and 5
CMMI Course Summary CMMI course Module 9..
6 Sigma Hazırlayanlar : Emine Yılmaz Cansın Eminoğlu.
Integrated Capability Maturity Model (CMMI)
CMMI Technology Conference and User Group November 2003 Experiences with Leveraging Six Sigma to Implement CMMI Levels 4 and 5 Jeff Facemire & Hortensia.
The Capability Maturity Model in Software Development Paul X. Harder, JD Government Micro Resources, Inc. September 14, 2004.
Capability Maturity Model Part One - Overview. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First.
N By: Md Rezaul Huda Reza n
J. R. Burns, Texas Tech University Capability Maturity Model -- CMM n Developed by the Software Engineering Institute (SEI) in 1989 –SEI is a spinoff.
CMMi What is CMMi? Basic terms Levels Common Features Assessment process List of KPAs for each level.
People First … Mission Always Capability Maturity Model Integration (CMMI ® ) Millee Sapp 2 Dec 08 Warner Robins Air Logistics Center.
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 Lecture # 17
CMS 00_ Copyright 2002 Raytheon Company All Rights Reserved CMMI – What a Difference a Sponsor Makes! Ann Turner Raytheon Company
By: Nick Blank March 1, Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development.
CSI - Introduction General Understanding. What is ITSM and what is its Value? ITSM is a set of specialized organizational capabilities for providing value.
ASQ Raleigh ASQ Raleigh Section 1113 Six Sigma SIG DMAIC Series.
10/16/2015Bahill1 Organizational Innovation and Deployment Causal Analysis and Resolution 5 Optimizing 4 Quantitatively Managed 3 Defined 2 Managed Continuous.
Software Process Assessment and Improvement
Thomas L. Gilchrist Testing Basics Set 4: Strategies & Metrics By Thomas L. Gilchrist, 2009.
Putting the “Engineering” in Software Engineering: Technology Infrastructure in Process Improvement Adam Kolawa, Ph.D. CEO, Parasoft.
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.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
SWEN 5130 Requirements Engineering 1 Dr Jim Helm SWEN 5130 Requirements Engineering Requirements Management Under the CMM.
Software Engineering - I
CMMI. 1.Initial - The software process is characterized as ad hoc, and occasionally even chaotic. Few processes are defined, and success depends on individual.
The Value Driven Approach
Requirements Development in CMMI
________________________________________________________________________ Jonsson School of Engineering and Computer Science Dr. Mark C. Paulk 2015 ASEE.
Purpose: The purpose of CMM Integration is to provide guidance for improving your organization’s processes and your ability to manage the development,
CMMI Benefits at Northrop Grumman Mission Systems Rick Hefner, Northrop Grumman Dean Caccavo, Northrop Grumman
An Introduction. Objective - Understand the difference between CMM & CMMI - Understand the Structure of CMMI.
Minimizing SCAMPI Costs via Quantitative Methods Ron Ulrich, Northrop Grumman Rick Hefner, Northrop Grumman CMMI.
Copyright © | Trade secret and confidential Page 1 Innovative, Professional, Fact Based and Eustressed© Maruthi Quality Management Services Ptv. Ltd..,
Software Engineering (CSI 321) Software Process: A Generic View 1.
MSA Orientation – v203a 1 What’s RIGHT with the CMMI?!? Pat O’Toole
Project Management Strategies Hidden in the CMMI Rick Hefner, Northrop Grumman CMMI Technology Conference & User Group November.
UNIT 5.
Certification: CMMI Emerson Murphy-Hill. Capability Maturity Model Integration (CMMI) Creation of the Software Engineering Institute (SEI) at Carnegie.
A Comparison of CMMI & SPICE
Overview of CMMI Global Certification Consultant is aiming to designed CMMI Presentation to share knowledge about CMMI,
Product Lifecycle Management
Six Sigma.
Software Engineering (CSI 321)
Information Technology Project Management – Fifth Edition
CMMI – Staged Representation
Quality Management Six Sigma
Capability Maturity Model
Measure Phase Wrap Up and Action Items
Capability Maturity Model
Requirements Development in CMMI
Presentation transcript:

NDIA Systems Engineering Supportability & Interoperability Conference October 2003 Using Six Sigma to Improve Systems Engineering Rick Hefner, Ph.D. Senior Manager, Process Initiatives Northrop Grumman

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 2 What is Six Sigma?  Six Sigma is a management philosophy based on meeting business objectives by striving for perfection –A disciplined, data-driven methodology for decision making and process improvement  Six Sigma consists of several integrated methods: –Process Management –Voice of the Customer –Change Management –Tools for Measuring Variation and Change –Business Metrics  The focus is on understanding and reducing variation

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 3 DMAIC Steps DEFINE Set project goals and objectives MEASURE Narrow range of potential causes and establish baseline capability level ANALYZE Evaluate data/information for trends, patterns, causal relationships and “root causes” IMPROVE Develop, implement and evaluate solutions targeted at identified root causes CONTROL Make sure problem stays fixed and new methods can be further improved over time Define Measure Analyze Improve Control

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 4 Applying Six Sigma to Systems Engineering  Software and system processes are fuzzy –Production of software or systems engineering "parts" is less predictable than manufacturing of physical parts –Greater variation in human cognitive processes can prevent rigorous application of the Six Sigma methodology –Process variation can never be eliminated and may not even reduced below a moderate level  Results often cannot be measured in clear $ savings returned to organization –Benefits are reduced risk, increased customer satisfaction, more competitive bids, …

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 5 Our Six Sigma Approach Engaged with External Customers Visibility Participation Linked with Business Planning and Oversight Business planning Project selection Enabled by Infrastructure Training Tools Awareness Database SPM Integrated with Quality Program Integrated Training, Awareness, & Policies Integrated CMMI & Six Sigma projects Integrated tracking and reporting via DB, PRA, etc. Tied to Employee Performance Goals, awards Job and career paths Quantitatively Driven Six Sigma improvements are quantified Startit! – a NGMS product Quantitative Process Capability Measurement and Assessment Report

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 6 Six Sigma Implementation  Starting implementing Six Sigma in 2001  Trained over 3000 Green Belts (80 hours), and over 200 Black Belts (160 hours)  Completed several hundred projects covering all functional areas –Customer involvement and award fee citations  About half of the projects are improving an engineering process

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 7 Causal Analysis and Resolution Organizational Innovation and Deployment 5 Optimizing 4 Quantitatively Managed 3 Defined 2 Managed Continuous process improvement Quantitative management Process standardization Basic project management Quantitative Project Management Organizational Process Performance Organizational Process Focus Organizational Process Definition Organizational Training Integrated Project Management Risk Management Decision Analysis and Resolution Requirements Development Technical Solution Product Integration Verification Validation Requirements Management Project Planning Project Monitoring and Control Supplier Agreement Management Measurement and Analysis Process and Product Quality Assurance Configuration Management 1 Performed Process AreasLevel Focus Level 5 Focus is on preventing defects and innovation (addressing common causes of variation) Level 4 Focus is on understanding and managing special causes of variation, at both the project and organizational levels Capability Maturity Model Integrated

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 8 Maturity Level 4 Organization  Establishes organizational goals  Establishes standard process  Characterizes process performance and quality of the standard process Project  Establishes project goals  Tailors standard organizational process to create project’s defined process  Selects critical subprocesses to quantitatively manage Understanding and managing special causes of variation RUN CHART

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 9 Quantitative Management Example (not real data) Peer Reviews – Understanding the Process  How many errors does the team typically find in reviewing an interface specification?  Useful in evaluating future reviews –Was the review effective? –Was the process different? –Is the product different?

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 10 Quantitative Management Example (not real data) Peer Reviews – Improving the Process  Reduce the variation –Train people on the process –Create procedures/checklists –Strengthen process audits  Increase the effectiveness (increase the mean) –Train people –Create checklists –Reduce waste and re-work –Replicate best practices from other projects

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 11 Maturity Level 5 Organization  Identifies incremental and innovative improvements  Pilots improvements  Deploys and measures (quantitatively) the results Project  Identifies causes of defects and other problems  Takes actions to prevent them from occurring in the future Preventing defects and innovation (addressing common causes of variation) RUN CHART

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 12 Results  Organizational-wide adoption and training has resulted in a workforce that understands variation –Common language –Common toolset –Common focus on reducing variation  Results have been seen in our rapid achievement of CMMI Levels 4 and 5 –Transition from Level 3 to 5 typically takes about 18 months –Our organizations have been transitioning in 9 months!