CMMI Case Study by Dan Fleck

Slides:



Advertisements
Similar presentations
Definitions Innovation Reform Improvement Change.
Advertisements

More CMM Part Two : Details.
Stepan Potiyenko ISS Sr.SW Developer.
LARGE SYSTEMS IMPLETATION PROCESS  Overview Review process diagram homework practice.
Capability Maturity Model (CMM) in SW design
1 Chapter 6 Risk Management. 2 Project Risks What can go wrong? What is the likelihood? What will the damage be? What can we do about it?
Software Engineering: A Practitioner’s Approach, 6/e Chapter 2 Process: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Practitioners versus Academics Software Engineering Problems Academics Practitioners.
Industrial Standards Framework and Energy Management Aimee McKane, Lawrence Berkeley National Laboratory.
Capability Maturity Model
CMM Level 3 KPA’s CS4320 Fall Organizational Process Focus (Goals) Software process development and improvement activities are coordinated across.
CMMI Course Summary CMMI course Module 9..
What ISO 9000 Mandates The requirements for a quality system have been standardized - but many organizations like to think of themselves as unique. So.
PART 2: A FRAMEWORK FOR SOFTWARE PROCESS IMPROVEMENT (SPI) Jean Charles Salvin Markus Erlandsson Jan-Peter Nilsson.
N By: Md Rezaul Huda Reza n
SCHOOLWIDE INTEGRATED FRAMEWORK FOR TRANSFORMATION
GTEP Resource Manual Training 2 The Education Trust Study (1998) Katie Haycock “However important demographic variables may appear in their association.
1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.
A Project ’ s Tale: Transitioning From SW-CMM to CMMI-SE/SW Warren Scheinin Systems Engineer, NG Mission Systems CMMI Technology Conference & User Group.
Control Dr. Penny Wilkins. Today’s Agenda Check in Review Unit 5 Overview of unit 6 Topic - Control.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
EngMat/JWS.PPT 10/17/ CMMI ® Today – The Current State CMMI ® Technology Conference 2003 November 18, 2003 Ron Paulson Vice President, Engineering.
EARLY WARNING SYSTEMS EARLY ADOPTERS’ SURVEY Interpretive Summary Highlights of EWS Early Adopters Learning and Sharing Summit Survey, George W. Bush Institute,
Georgia Institute of Technology CS 4320 Fall 2003.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
Experiences during the introduction of CMMI. Seite 2 © evosoft Hungary Kft. History Background Preparation Appraisal Experiences Lessons learned Benefits.
CMMI. 1.Initial - The software process is characterized as ad hoc, and occasionally even chaotic. Few processes are defined, and success depends on individual.
CMMI Case Study by Dan Fleck Reference: A CMMI Case Study: Process Engineering vs. Culture and Leadership by Jeffrey L. Dutton,Jacobs Sverdrup Reference:
© 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v
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…
Unit 6 Seminar – Control.  Unit 5 Review  What’s Due in Unit 6?  Four Steps of Control Systems  The Role of Six Sigma  Internal vs. External Audits.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming.
1 Lecture 12: Chapter 16 Software Quality Assurance Slide Set to accompany Software Engineering: A Practitioner’s Approach, 7/e by Roger S. Pressman Slides.
CMMI The quality of a software product is only as good as the process used to develop and maintain it. Whether a software organization is competing in.
Capability Maturity Model. What is CMM? n CMM: Capability Maturity Model n Developed by the Software Engineering Institute of the Carnegie Mellon University.
Personal and professional development
Pipeline Safety Management Systems
PERSPECTIVE OF HUMAN RESOURCE MANAGEMENT
CHAPTER 1: AN INVESTMENT PERSPECTIVE OF HUMAN RESOURCE MANAGEMENT
Project Management.
Transition/Change Management How You Can Improve Project Success
CLE Introduction to Agile Software Acquisition
Software Quality Control and Quality Assurance: Introduction
Software Quality Assurance
CHAPTER 1: AN INVESTMENT PERSPECTIVE OF HUMAN RESOURCE MANAGEMENT
Professional Learning Communities
State of Michigan Achieving Software Process Improvement with
Chapter 18 Maintaining Information Systems
External Validation of Quality Programs
9 Management of Quality.
Presented To: 3rd Annual CMMI Technology Conference and User Group
Transforming The Way We Think and Work
Comprehensive Planning
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Learning’s Critical Role in Supporting Change Management
TSMO Program Plan Development
ENTERPRISE BUSINESS SYSTEMS
CMMI – Staged Representation
Quality management standards
Work-force planning involves two major activities
Project Management.
Management, Leadership, and Internal Organization
Multi-Tiered System of Support
Capability Maturity Model
Prepared and Presented By:- Abhishek Rautela
Urban Engineers ISO 9001:2015 General Overview
Georgia’s Tiered System of Supports for Students Karen Suddeth, Project Director Carole Carr, Communications & Visibility Specialist
Finalization of the Action Plans and Development of Syllabus
Capability Maturity Model
Definition of Project “An organized endeavor aimed at accomplishing a specific non-routine or low-volume task.” Definition of Project Management “The.
Presentation transcript:

CMMI Case Study by Dan Fleck Reference: A CMMI Case Study: Process Engineering vs. Culture and Leadership by Jeffrey L. Dutton,Jacobs Sverdrup Coming up: Overview

Overview Jacobs Sverdup’s Advanced Systems Group 400 employees Seven states Wide range of services and products to all 4 military branches and NASA Range of sizes (40 people, 4 years to 2 people, 12 months) Coming up: Beginnings…

Beginnings… Chartered Software Engineering Process Group (SEPG) SEPG trained field office Process Action Teams (PATs) Idea: Buy-in would be easier with PATs in the field offices Coming up: Reality

Reality PAT teams had problems with buy-in, non-participation -- no one likes process Attempts: Tying perf appraisal to PAT participation Positive feedback systems Newsletters Intense training Coming up: Plan 2: EPIC

Plan 2: EPIC SEPG reformed into Engineering Process Improvement Center (EPIC) Created 2 person core team and got buy-in from field office leads (heads of field offices) Adopted life-cycle framework from ISO/IEC 12207 Coming up: EPIC progress

EPIC progress Over two years defined six major work products: An integrated engineering handbook for project managers, engineers, and management. An engineering performance improvement program plan for the EPIC. A process and product quality assurance plan for quality assurance. A measurement and analysis plan for the entire organization. A purchasing manual for contract managers and project managers. A knowledge management plan. Coming up: New Mechanisms Adopted

New Mechanisms Adopted A life cycle that is both flexible and recursive, allowing tailoring to support the needs of the project and the customer. A repeatable tailoring approach that accommodates services, systems, and hardware and software development for small to large project sizes. The use of principal managers and leaders in the organization to teach critical courses. The early development of an automated measurement database. The development (later than we wanted) of a distributed work environment to support process engineering and information sharing. Coming up: Results?

Results? External audits noted they still had buy-in and institutionalization lacking Realized they needed more external audits because “organizational delusion” did not let them see the problems. Refocused on knowledge management to fix these issues Added pilot projects, all levels of review (low level to senior management), quality reviews, etc… Coming up: Does it ever end?

Does it ever end? Pilot projects showed numerous areas for improvements Eventually organizational culture of change emerged helped by a strong leadership culture willing to change and everyone with a feeling of “People are our greatest asset” and “Growth is imperative” Coming up: Challenges and Lessons Learned

Challenges and Lessons Learned Leaders that got into leadership by providing their own “stovepipe processes” Leaders asked to abandon tried and true processes Needed people to trust EPIC to promote buy-in Needed to respond quickly and positively to criticism and challenges to the process Coming up: Leadership Didn’t Know

Leadership Didn’t Know The CMMI really does change the way every part of the organization operates. The costs associated with adoption of the CMMI are real and cannot be avoided. Routine actions have to be conducted in accordance with the standard process, as well as corrective and near-crisis actions. A CMMI process improvement effort is not just another project, where the work products are the most important output. Some of the people you have worked with and trusted for years will resist the improvement effort for various well-intentioned reasons. Assessments cannot be used to provide feedback and evaluate the performance of individual elements of the organization. The CMMI process improvement effort must be carefully aligned with the goals of the organization to make it worthwhile. The management and leadership style that has served to bring leaders this far in the organization now must be negotiated with the unseen authors of a complex model they are just beginning to appreciate. Coming up: You should know

You should know There will be more challenges then you expect Some heros will leave the company It will cost more than you expect Leadership must believe in the process and be willing to weather the storm Leaders must also know and trust their people who are implementing the program Coming up: What do you get?

What do you get? 20% reduction in unit s/w costs - Lockheed Martin 15% decrease in defect find and fix cost - Lockheed Martin Costs dropped 48% from a baseline prior to CMM as the achieved CMMI-3 - DB Systems GambH Estimation accuracy improved 72% on average in three technical areas - Siemens Percentage of milestones met improved from approximately 50 percent to approximately 85 percent following organization focus on CMMI - General Motors Many many more at: http://www.sei.cmu.edu/cmmi/results/results-by-category.html Coming up: What do you get?