Copyright © 2003 by Cooliemon TM, LLC 1 Presenter: Ralph Williams, President SEI Authorized CBA IPI Lead Assessor (CMM ® ) SCAMPI Lead Appraiser SM (CMMI.

Slides:



Advertisements
Similar presentations
Copyright © 2003 by Cooliemon TM, LLC 1 Causal Analysis & Resolution (CAR) at Level 1 Presenter: Ralph Williams, President SEI Authorized CBA IPI Lead.
Advertisements

Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department of Defense © 2001 by Carnegie Mellon.
Copyright 2005 CMMI and ITIL Alison Adams & Kieran Doyle.
Copyright 2003 CMMI: Executive Briefing Presented by Kieran Doyle
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Requirements Analysis Concepts & Principles
Analysis Concepts and Principles
Capability Maturity Model Integration (CMMI). CMMI Enterprise-wide process improvement framework Focuses on processes for improved product Process areas:
200209–CSSA0001 – 16/27/ :25 PM CSSA Cepeda Systems & Software Analysis, Inc. GENERIC.
CMMI Overview Quality Frameworks.
Software Process CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 17, 2002.
Organizational Project Management Maturity: Roadmap to Success
Lecture 11 CMM CSCI – 3350 Software Engineering II Fall 2014 Bill Pine.
Capability Maturity Model Integration (CMMI) COMP Group Assignment #1 Ario Nejad, Davit Stepanyan, Ian Jackman, Sebastian Henneberg, Wan Chi Chio.
Process: A Generic View
Integrated Capability Maturity Model (CMMI)
Comparing CMMI® and OPM3®
Model-Based Process Improvement Module 2. Module Objectives This module will enable students to recall information about the history of CMMI fundamentals.
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
CMMi What is CMMi? Basic terms Levels Common Features Assessment process List of KPAs for each level.
Requirements Engineering How do we keep straight what we are supposed to be building?
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Chapter 2 Process: A Generic View
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Process Management Process Management in software started in late 1960’s (but informally and inconsistently) Software Engineering Institute (SEI) is the.
EngMat/JWS.PPT 10/17/ CMMI ® Today – The Current State CMMI ® Technology Conference 2003 November 18, 2003 Ron Paulson Vice President, Engineering.
Software Engineering Principles Principles form the basis of methods, techniques, methodologies and tools Principles form the basis of methods, techniques,
Application of the CMMI SM to Plan and Control Life Cycle Costs Dr. Mary Anne Herndon Science Applications International Corporation (SAIC) November, 2003.
Requirements Gathering How do we find out what we are supposed to be building?
Everything You Ever Wanted to Know About CMMI in 30 Minutes or LESS CCS TECHNICAL SERVICES (484) CCS TECHNICAL SERVICES (484) William.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Lecture-3.
Software Engineering - I
CSE4002CMMI Capability Maturity Model Integration (CMMI) CMMI is replacing the well established CMM rating for software developers and systems engineers.
 Copyright ProcessVelocity, LLP Slides intended for informational purposes only. CMM and Capability Maturity Model are registered in the U.S. Patent.
Requirements Development in CMMI
CMMI FRAMEWORK SRIKANTH DEVINENI. Process failure is recognised when Project is delivered late Too much redundancy Customer complaints after delivery.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Process: A Generic View Software Engineering: A Practitioner’s Approach, 7/e Chapter 2.
Chapter 12 Translating Expectations to Specifications CEM 515: Project Quality Management Prof. Abdulaziz A. Bubshait King Fahd University of Petroleum.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Pittsburgh, PA Sponsored by the U.S. Department of Defense © 2003 by Carnegie Mellon University This material is approved for public release.
 CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze.
Introduction to the Personal Software Process. Overview Process Fundamentals PSP Concepts and Structure PSP Planning and Measurement PSP Quality Management.
Pittsburgh, PA CMMI Acquisition Module - Page M5-1 CMMI ® Sponsored by the U.S. Department of Defense © 2005 by Carnegie Mellon University This.
Requirements Gathering
Copyright © by Quality Improvement Consultants, Inc. (QIC) Slide 1 World-Class Quality Measurably Improving Your Requirements Based on the CMMI.
CMMI Overview Quality Frameworks. Slide 2 of 146 Outline Introduction High level overview of CMMI Questions and comments.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 2 Process: A Generic View Software Engineering: A Practitioner’s Approach, 6/e Chapter 2.
© 2004 Tangram Hi-Tech Solutions Project Management According to the CMMI1 Project Management according to the Capability Maturity Model (CMMI)
Certification: CMMI Emerson Murphy-Hill. Capability Maturity Model Integration (CMMI) Creation of the Software Engineering Institute (SEI) at Carnegie.
A Comparison of CMMI & SPICE
CMMI Certification - By Global Certification Consultancy.
Beyond the BACoE: Developing Business Analysis Maturity.
 System Requirement Specification and System Planning.
Staged or Continuous: Which Model Should I Choose?
A Program of Training for CMMI®-based Process Improvement
Successful Verification
Compliance and Audit Block 17 Block 17.
CMMI Overview Quality Frameworks.
Process Maturity Profile
Information Technology Project Management – Fifth Edition
CMMI Overview.
Quality management standards
Interpretive Guidance Project: What We Know CMMI User’s Conference
Software Engineering: A Practitioner’s Approach, 6/e Chapter 2 Process: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Acknowledgment of achievement
Copyright © by Quality Improvement Consultants, Inc. (QIC) 1 World-Class Quality Staged or Continuous: Which Model Should I Choose? ® CMM is.
Requirements Development in CMMI
Capability Maturity Model
Presentation transcript:

Copyright © 2003 by Cooliemon TM, LLC 1 Presenter: Ralph Williams, President SEI Authorized CBA IPI Lead Assessor (CMM ® ) SCAMPI Lead Appraiser SM (CMMI ® ) ® CMM and CMMI is registered in the U.S. Patent and Trademark Office. SM IDEAL is a service mark of Carnegie Mellon University. CMMI Requirements Development (RD) Listening to the Voice of the Customer

Copyright © 2003 by Cooliemon TM, LLC 2 Special Permission Special permission to reproduce and adapt portions of: Software Engineering Process Group Guide, CMU/SEI-90-TR-024, (c) 1990 by Carnegie Mellon University Capability Maturity Model ® Integration (CMMI ® ), Version 1.1 (CMMI SM - SE/SW/IPPD/SS, V1.1) Continuous Representation, CMU/SEI-2002-TR-011, (c) 2002 by Carnegie Mellon University Capability Maturity Model ® Integration (CMMI ® ), Version 1.1 (CMMI SM - SE/SW/IPPD/SS, V1.1) Staged Representation, CMU/SEI-2002-TR-012, (c) 2002 by Carnegie Mellon University Standard CMMI SM Assessment Method for Process Improvement: Method Definition, Version 1.1 (SCAMPI SM, V1.1), CMU/SEI-2001-HB-2001, (c) 2001 by Carnegie Mellon University is granted by the Software Engineering Institute. ® CMMI, CMM and Capability Maturity Model are registered in the U.S. Patent and Trademark Office. SM IDEAL and SCAMPI are service marks of Carnegie Mellon University.

Copyright © 2003 by Cooliemon TM, LLC 3 About Cooliemon, LLC The mission of Cooliemon, LLC is: “helping organizations achieve excellence through process improvement” Our goal is to focus your process improvement efforts to: improve quality and productivity reduce operating costs (i.e., reduce rework, waste and duplicate effort) capture the market with high quality products and services help you become the industry standard by which your competitors measure themselves

Copyright © 2003 by Cooliemon TM, LLC 4 Objectives Review CMMI RD Process Area, specifically how to develop customer requirements (Specific Goal 1). Provide an overview of how Juran’s version of Quality Function Deployment (QFD) can be used to identify the different customer(s) and their needs. Review a practical spreadsheet (Juran’s product design spreadsheet) to capture the the needs of the customer. Answer any of your questions.

Copyright © 2003 by Cooliemon TM, LLC 5 Agenda RD Process Area (CMMI) Juran’s version of QFD Identify Customers Discover Customer Needs Summary

Copyright © 2003 by Cooliemon TM, LLC 6 RD Specific Goals Purpose: The purpose of Requirements Development (RD) is to produce and analyze customer, product, and product component requirements. Specific Goal 1: Develop Customer Requirements* Specific Goal 2: Develop Product Requirements Specific Goal 3: Analyze and Validate Requirements Reference: “CMMI -SE/SW/IPPD, V Continuous Representation”,CMU/ SEI-2000-TR-031

Copyright © 2003 by Cooliemon TM, LLC 7 SG 1 - Develop Customer Requirements SP 1.1-1: Collect Stakeholder Needs - may not be in technical terms SP 1.1-2: Elicit Needs - proactively identify additional requirements/needs not explicitly provided by customer SP 1.2-1: Transform Stakeholder Needs, Expectations, Constraints, and interfaces into Customer Requirements - Document Customer Needs Reference: “CMMI -SE/SW/IPPD, V Continuous Representation”,CMU/ SEI-2000-TR-031

Copyright © 2003 by Cooliemon TM, LLC 8 Agenda RD Process Area (CMMI) Juran’s version of QFD Identify Customers Discover Customer Needs Summary

Copyright © 2003 by Cooliemon TM, LLC 9 QFD in a Nutshell QFD is a pointed way of listening to customers to learn exactly what they want, and then using a logical system to determine how best to fulfill those needs with available resources QFD can be viewed by answering 3 questions: 1. What are the qualities the customer desires? 2. What function(s) must this product serve and what functions must we use to provide this product or service? 3. Based upon the resources we have available, how can we best provide what our customer wants?

Copyright © 2003 by Cooliemon TM, LLC 10 Juran’s version of QFD - 1 Juran’s version of QFD 1. Identify Customers* 2. Discover Customer Needs* 3. Develop Product 4. Develop Process 5. Develop Process Controls/Transfer to Operations © 1994 Juran Institute, Inc.

Copyright © 2003 by Cooliemon TM, LLC 11 Juran’s Version of QFD Identify Customers Construct high-level flow diagram Create List of all external customers Create List of all internal customers Prioritize customer lists 2. Discover Customer Needs (*Difficult!) Plan to collect customers’ needs Collect list of customers’ needs in their language Examine and prioritize customers’ needs Translate their needs into your language Establish units of measurements and sensors © 1994 Juran Institute, Inc.

Copyright © 2003 by Cooliemon TM, LLC 12 Juran’s Product Design Spreadsheet Adapted from Juran, “Leadership for Quality”, 1989

Copyright © 2003 by Cooliemon TM, LLC 13 Agenda RD Process Area (CMMI) Juran’s version of QFD Identify Customers Discover Customer Needs Summary

Copyright © 2003 by Cooliemon TM, LLC 14 Who Are Your Customers? A customer is defined as anyone who is affected by the product or the process to create it. Generally there are two primary groups of customers: the external customers - those outside your organization the internal customers - those inside your organization

Copyright © 2003 by Cooliemon TM, LLC 15 Identify Customers Identify Customers: Construct high-level flow diagram Create List of all external customers Create List of all internal customers Prioritize customer lists © 1994 Juran Institute, Inc.

Copyright © 2003 by Cooliemon TM, LLC 16 Construct High Level Flow Diagram Purpose: The process ends with... CUSTOMER(S) Output(s) SUPPLIER(S) Input(s) The process begins with... Department ADepartment BDepartment C

Copyright © 2003 by Cooliemon TM, LLC 17 Example: Family on Vacation © Adapted from 1994 Juran Institute, Inc.

Copyright © 2003 by Cooliemon TM, LLC 18 Agenda RD Process Area (CMMI) Juran’s version of QFD Identify Customers Discover Customer Needs Summary

Copyright © 2003 by Cooliemon TM, LLC 19 Definitions of Customer Needs Need (Voice of the Customer): A condition of desiring something; an issue to be resolved. Product Feature (Voice of the Engineer): A property or characteristic possessed by a product; what it does. Benefit: What the customer will gain or how his/her problem will be solved by possessing a particular product feature; what it does for the customer. © 1994 Juran Institute, Inc.

Copyright © 2003 by Cooliemon TM, LLC 20 Discover Customer Needs Discover Customer Needs (*Difficult!) Plan to collect customers’ needs Collect list of customers’ needs in their language Examine and prioritize customers’ needs Translate their needs into your language Establish units of measurements and sensors © 1994 Juran Institute, Inc.

Copyright © 2003 by Cooliemon TM, LLC 21 Us Them Customer Satisfaction Study

Copyright © 2003 by Cooliemon TM, LLC 22 Voice of the Customer - 1 There are 4 levels of customer requirements: Expecters: The basic qualities you must offer to be competitive and remain in business are Expectors These are characteristics customers assume as part of the product or service. Spokens: Specific features customers say they want in a product or service are Spokens. They are items a company is willing to provide to satisfy its customer.

Copyright © 2003 by Cooliemon TM, LLC 23 Voice of the Customer - 2 Unspokens: Product or service characteristics customers don’t talk about are Unspokens. Unspokens fall into 3 groups: -Didn’t remember to tell you -Didn’t want to tell you -Didn’t know what it was Exciters: Unexpected features of a product or service are Exciters. These features make the product unique and distinguish it from the competition.

Copyright © 2003 by Cooliemon TM, LLC 24 Example: Customer Needs

Copyright © 2003 by Cooliemon TM, LLC 25 © 1994 Juran Institute, Inc.

Copyright © 2003 by Cooliemon TM, LLC 26 Agenda RD Process Area (CMMI) Juran’s version of QFD Identify Customers Discover Customer Needs Summary

Copyright © 2003 by Cooliemon TM, LLC 27 There are basically 2 types of customers, internal and external, to consider when eliciting requirements. An effective way of eliciting requirements is using Juran’s version of QFD and the Product Design Spreadsheet. It is important to distinguish the different voices of the customer (i.e., product features versus customer needs). Summary

Copyright © 2003 by Cooliemon TM, LLC 28 One to Grow On Most people listen NOT with the intent to understand BUT with the intent to reply

Copyright © 2003 by Cooliemon TM, LLC 29

Copyright © 2003 by Cooliemon TM, LLC 30 One to Grow On “The competitor to be feared is one who never bothers about you at all, but goes on making his own business better all the time.” (Henry Ford, Sr.)

Copyright © 2003 by Cooliemon TM, LLC 31 Contact Information Ralph Williams, President 129 Liberty Road, Harmony, PA Tel: Fax: