CMMI Benefits at Northrop Grumman Mission Systems Rick Hefner, Northrop Grumman Dean Caccavo, Northrop Grumman

Slides:



Advertisements
Similar presentations
6 SIGMA VS. KAIZEN/LEAN Manufacturing Systems Analysis.
Advertisements

More CMM Part Two : Details.
Chapter 2 The Software Process
©2006 OLC 1 Process Management: The Foundation for Achieving Organizational Excellence Process Management Implementation Worldwide.
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.
Transition from SW-CMM to CMMI: Yes or No?
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.
Copyright 2005 Northrop Grumman Corporation Is CMMI High Maturity Worth the Investment? Southern California SPIN 2 February 2007 Rick Hefner, Ph.D. Director,
Requirements Analysis INCOSE Systems Engineering Boot Camp
Software Quality Processes – Part II CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 19, 2007.
1 R&D SDM 1 Software Project Management Capability Maturity Model 2009 Theo Schouten.
Rick Hefner. Marilee J. Wheaton TRW
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.
Effective Methods for Software and Systems Integration
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..
Copyright © 2009, Systems and Software Consortium, Inc. Introduction to an Integrated Lean Thinking, Six Sigma  and CMMI  Approach for Process Improvement.
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
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.
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
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
CSI - Introduction General Understanding. What is ITSM and what is its Value? ITSM is a set of specialized organizational capabilities for providing value.
NDIA Systems Engineering Supportability & Interoperability Conference October 2003 Using Six Sigma to Improve Systems Engineering Rick Hefner, Ph.D.
VALUE BASED SYSTEMS ENGINEERING THE VALUE ADDED PATH FORWARD Joseph Maley October 8, 2015.
10/16/2015Bahill1 Organizational Innovation and Deployment Causal Analysis and Resolution 5 Optimizing 4 Quantitatively Managed 3 Defined 2 Managed Continuous.
Software process improvement Framework for SPI SPI support groups, maturity and immaturity models Assessment and gap analysis Education and training Selection.
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.
Georgia Institute of Technology CS 4320 Fall 2003.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Software Engineering - I
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.
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.
Requirements Development in CMMI
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.
Purpose: The purpose of CMM Integration is to provide guidance for improving your organization’s processes and your ability to manage the development,
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.
Software Engineering (CSI 321) Software Process: A Generic View 1.
CMMI1 Capability Maturity Model Integration Eyal Ben-Ari 8/2006.
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.
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
Driving Value from IT Services using ITIL and COBIT 5 July 24, 2013 Gary Hardy ITWinners.
Certification: CMMI Emerson Murphy-Hill. Capability Maturity Model Integration (CMMI) Creation of the Software Engineering Institute (SEI) at Carnegie.
A Comparison of CMMI & SPICE
School of Business Administration
CS4311 Spring 2011 Process Improvement Dr
Information Technology Project Management – Fifth Edition
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Level - 3 Process Areas (CMMI-DEV)
CMMI – Staged Representation
Software Engineering Lecture 16.
Software Engineering I
Capability Maturity Model
Use of CMMI in an Acquisition Context Using CMMI for Process Improvement at USAF Space and Missile Systems Center (SMC) Dr. Jack R. Ferguson
Capability Maturity Model
Requirements Development in CMMI
Presentation transcript:

CMMI Benefits at Northrop Grumman Mission Systems Rick Hefner, Northrop Grumman Dean Caccavo, Northrop Grumman CMMI Technology Conference & User Group November 2003

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 2 Agenda  Establishing ROI  The Value of High Maturity  Six Sigma Measures  Quantitative and Qualitative Impacts

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 3 Treasury Communications System Intercontinental Ballistic Missile Program Guardrail Northrop Grumman Mission Systems  A leading global integrator of complex systems –Based on information technology and systems engineering expertise –Integrated solutions: architecture, development and sustainment  $3.9 B Estimated 2003 Sales  15,000+ Employees  Diverse business base –Presence in over 20 countries, 50 states –2,000 active contracts and task orders  Near-term goal to achieve CMMI Level 5 at all sites –Started in 2002 with all sites at SW-CMM Level 3

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 4 Establishing ROI  It is difficult to quantify the value of an improvement initiative  How do you measure the change? –Multiple levels – organizational, management, engineering, support –Multiple causes – awareness, knowledge, infrastructure –Short-term vs. long-term – Hawthorne effect  How do you measure the investment? –What would we have done instead?  How do you determine the value of the measured change? –Increased predictability – what’s the value? –Increased productivity – who gets the benefit? –Better competitive position – how measured? –Time-frame

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 5 Why Do We Need ROI Data?  Management wants to invest overhead resources wisely –Similar investment decisions often based on “gut feel”, not hard data – does anything else seem more likely to yield results? –Investment decisions may be more driven by balance of short-term performance tactics and long-term marketing strategy –Key question is whether you could make similar progress with less resources (or progress faster with the same resources)  Projects want to justify the investment to their customers –Difficult to convince process skeptics –People view the problem from their own experiences and skills Beware of ROI as a smokescreen for process skepticism

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 6 A Long-Term Focus  Northrop Grumman Mission Systems focused on the long-term culture change –More data-driven decision making –Identifying and meeting the customers’ needs –Disciplined project management –Improved engineering first-time quality to reduce re-work –Efficient organizational infrastructure –Use of industry best-practices –Capturing of internal best-practices  Understanding the value is used to guide the CMMI deployment strategy, not justify the initiative

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 7 3 Keys to Competitive Leverage Six Sigma CMMI Six Sigma is a business strategy to deliver value and develop a sustainable competitive advantage Knowledge Management KM provides a strategy to utilize data and transform it into knowledge to enable informed and decisive management leadership CMMI provides guidance for measuring, monitoring and managing processes

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 8 Best Possible Schedule Classic- Mistake Avoidance Development Fundamentals Risk Management Schedule- Oriented Practices Strategies for Rapid Development Steve McConnell, Rapid Development  Avoid classic mistakes  Apply development fundamentals  Manage risks to avoid catastrophic setbacks  Use schedule-oriented practices –Practices that improve development speed, allowing you to deliver software faster –Practices that reduce schedule risk, allowing you to avoid huge schedule overruns –Practices that make progress visible, allowing you to dispel the appearance of slow development

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 9 CMM Level 3CMMI Level 3Organization Process Focus Organization Process Definition Training ProgramOrganizational Training Integrated Software MgmtIntegrated Project Management Risk Management Software ProductRequirements Development EngineeringTechnical Solution Product Integration Intergroup Coordination Verification Peer Reviews Validation Decision Analysis and Resolution CMM Level 2CMMI Level 2Requirements Management Software Project PlanningProject Planning Software Project Tracking & OversightProject Monitoring and Control Software Subcontract MgmtSupplier Agreement Management Software Quality AssuranceProduct & Process Quality Assurance Software Configuration MgmtConfiguration Management Measurement and Analysis Value in Transitioning from CMM to CMMI - 1 Development fundamentals Manage risks Reduce schedule risk Make progress visible

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 10 Value in Transitioning from CMM to CMMI - 2  CMMI provides little help in avoiding classic mistakes  CMMI clarifies the importance of a defined strategy for the development fundamentals –See following chart  CMMI more clearly specifies the risk management practices  CMMI indirectly addresses schedule-oriented practices –Few practices that explicitly improve development speed –More emphasis on reducing schedule risk –More emphasis on making progress visible Best Possible Schedule Development Fundamentals Risk Management Schedule- Oriented Practices Classic- Mistake Avoidance “Proof” to process skeptics that CMMI doesn’t have value!

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 11 A Defined Strategy Verification Process Area SG 1 Prepare for Verification Preparation for verification is conducted. SP 1.1Select Work Products for Verification Select the work products to be verified and the verification methods that will be used for each. SP 1.2Establish the Verification Environment Establish and maintain the environment needed to support verification. SP 1.3Establish Verification Procedures and Criteria Establish and maintain verification procedures and criteria for the selected work products. Decide/document how verification will be done Test facilities and tools, conference room for peer reviews “Procedures” ensure the verification activity is effective Deciding how verification will be done, and under what conditions the work product is considered verified Further details in: “Project Management Strategies Hidden in the CMMI”, 2003 CMMI

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 12 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. 13 Six Sigma Provides a Way to Connect Process Improvement and Business Value  The typical Mission Systems Six Sigma project –Six month duration –4-6 Green Belt team members (2 weeks of training) –Black Belt leader (4 weeks of training)  Six Sigma projects can help focus and measure CMMI-driven process improvements –Identify the customer’s needs, maximize the value/cost –Measure the change in capability – especially helpful at Levels 4 and 5 –Institutionalize improvements -- drive the cultural change Charter team, map process & specify CTQs Measure process performance Identify & quantify root causes Select, design & implement solution Institutionalize improvement, ongoing control DEFINE MEASURE ANALYZE CONTROL IMPROVE

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 14 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. 15 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. 16 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. 17 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. 18 Program Performance Trends  Improvement in the number of successful projects, based on critical program performance categories

Copyright 2003 Northrop Grumman Space and Mission Systems Corp. All Rights Reserved. 19 Conclusions  Value of transitioning from CMM to CMMI is difficult to quantify  CMMI strengthens generally accepted principles of sound program management  Levels 4 and 5 allow both the project and organization to focus and measure specific improvements  Six Sigma is an enabler for measuring the value of specific improvements