A Lightweight Supplier Evaluation based on CMMI



Similar documents
Software Quality. Process Quality " Martin Glinz. Chapter 5. Department of Informatics!

Distributed and Outsourced Software Engineering. The CMMI Model. Peter Kolb. Software Engineering

Towards a new approach of continuous process improvement based on CMMI and PMBOK

SW Process Improvement and CMMI. Dr. Kanchit Malaivongs Authorized SCAMPI Lead Appraisor Authorized CMMI Instructor

CMMI for Development Introduction & Implementation Roadmap

CAPABILITY MATURITY MODEL INTEGRATION

Project Management. 06 Requirements Management. IT M a t u r i t y. S e r v i c e s

CMMI KEY PROCESS AREAS

Software Engineering. Standardization of Software Processes. Lecturer: Giuseppe Santucci

An Integrated Model of ISO 9001:2000 and CMMI for ISO Registered Organizations

A unified model for the implementation of both ISO 9001:2000 and CMMI by ISO-certified organizations

Software Quality Standards and. from Ontological Point of View SMEF. Konstantina Georgieva

Manage the acquisition of products from suppliers for which there exists a formal agreement.

CMMI meets ITIL. Dr. Ute Streubel

Software Configuration Management. Wingsze Seaman COMP250SA February 27, 2008

An OWL Ontology for Representing the CMMI-SW Model

CMS Policy for Capability Maturity Model Integration (CMMI)

Capability Maturity Model Integration (CMMI SM ) Fundamentals

A Report on The Capability Maturity Model

Leveraging CMMI framework for Engineering Services

SOFTWARE QUALITY ASSURANCE IN CAPABILITY MATURITY MODEL INTEGRATION

The Advantages of ISO 9001 Certification

Capability Maturity Model Integration (CMMI)

Usability in SW-Engineering-Prozessen und in CMMI

Engineering Standards in Support of

Developing CMMI in IT Projects with Considering other Development Models

Truly Managing a Project and Keeping Sane While Wrestling Elegantly With PMBOK, Scrum and CMMI (Together or Any Combination)

MKS Integrity & CMMI. July, 2007

Case Study of CMMI implementation at Bank of Montreal (BMO) Financial Group

The Compelling Case For CMMI-SVC: CMMI-SVC, ITIL & ISO20000 demystified

Custom Development Management and Resource Planning. Eric Halbur, Application Development Manager

Software Quality Assurance: VI Standards

Software Project Management and Support - Practical Support for CMMI -SW Project Documentation: Using IEEE Software Engineering Standards

Software Process Improvement Framework for Software Outsourcing Based On CMMI Master of Science Thesis in Software Engineering and Management

Maturity Assesment for Processes in IT

Software Quality Management II

Introduction to SEIs Capability Maturity Model Integration (CMMI)

Foredragfor Den Norske Dataforening, den

Lessons Learned from Adopting CMMI for Small Organizations

Match point: Who will win the game, ITIL or CMMI-SVC? NA SEPG 2011 Paper Presentation

CMMI for Development, Version 1.3

Interpreting Capability Maturity Model Integration (CMMI ) for Service Organizations a Systems Engineering and Integration Services Example

ITIL-CMMII Comparison

Synergism of the CMMI Development and Services Constellations in a Hybrid Organization

Agenda. CMMI, ITIL & ISO A Mutually Supportive Relationship

You Want to Use Scrum, You are Told to Use CMMI

CMMI Version 1.2. SCAMPI SM A Appraisal Method Changes

CMMI for Development, Version 1.3

Aligning CMMI & ITIL. Where Am I and Which Way Do I Go? cognence, inc.

wibas Team CMMI-ITIL IT Maturity S e r v i c e s

Comparing Scrum And CMMI

CMMI: Specific Goals and Practices

Role of Software Quality Assurance in Capability Maturity Model Integration

How CMMI contributes to Software Testing

Is the CMMI¹ of Value for Flight Software? Dr. Gary M. Heiligman Space Department The Johns Hopkins University Applied Physics Laboratory

ISO 9001/TL 9000 and CMMI Comparison

How to use CMMI to bring your project management process to the next level A CMMI Implementation Case Study

How To Understand And Understand The Cmm

Process Improvement. From the Software Engineering Institute:

Capability Maturity Model Integrated (CMMI)

Process Improvement -CMMI. Xin Feng

Implementation of Multiple Quality Frameworks An Analysis

Quantitative CMMI Assessment for Offshoring Through the Analysis of Project Management Repositories

CMMI for Acquisition, Version 1.3

Capability Maturity Model Integration (CMMI ) Overview

CMMI: What do we need to do in Requirements Management & Engineering?

Software Process Maturity Model Study

Automotive SPICE & ISO/CD Their Mutual Relationship

Data Management Maturity (DMM) Model Update

Measurement Strategies in the CMMI

CMMI-Services Visao Geral & CMMI v1.3 Plans

A SURVEY OF ARTIFICIAL INTELLIGENCE TECHNIQUES FOR CAPABILITY MATURITY MODEL INTEGRATION (CMMI)

A common core ITIL Version 3.0 and CMMi-SVC

Exploring CMMI-ISO ISO 9001:2000 Synergy when Developing a Process Improvement Strategy

Software Process Training

Software and Systems Engineering. Software and Systems Engineering Process Improvement at Oerlikon Aerospace

Contrasting CMMI and the PMBOK. CMMI Technology Conference & User Group November 2005

Integrating CMMI with COBIT and ITIL

Software Quality Management

ISO/IEC Part 1 the next edition. Lynda Cooper project editor for ISO20000 part 1

Risk Repository. Prepare for Risk Management (SG 1) Mitigate Risks (SG 3) Identify and Analyze Risks (SG 2)

Steve Masters (SEI) SEPG North America March Carnegie Mellon University

CMMI and IBM Rational Unified Process

A QUESTIONNAIRE BASED METHOD FOR CMMI LEVEL 2 MATURITY ASSESSMENT

Frameworks for IT Management

Capability Maturity Model Integration (CMMI ) Overview

SOFTWARE PROCESS IMPROVEMENT AT SYSGENIC

Evaluation and Integration of Risk Management in CMMI and ISO/IEC 15504

Software Engineering CSCI Class 50 Software Process Improvement. December 1, 2014

Controlling software acquisition: is supplier s software process capability determination enough?

Software Process Improvement Software Business. Casper Lassenius

Software Maintenance Capability Maturity Model (SM-CMM): Process Performance Measurement

Transcription:

A Lightweight Supplier Evaluation based on CMMI Stefan Böcking, Pavlos Makridakis, Gerhard Koller, Frank Meisgen Vodafone Holding GmbH Global Web Enablement Mannesmannufer 2 40213 Düsseldorf Stefan.Boecking@vodafone.com Pavlos.Makridakis@vodafone.com sd&m AG Carl-Wery-Straße 42 81739 München gerhard.koller@sdm.de frank.meisgen@sdm.de Abstract: Software for international companies is often developed by a multiplicity ofsuppliers using different approaches and processes. Only a few of these suppliers are already rated according to CMMI, ISO 15504 or ISO 9001. Therefore Vodafone Global and sd&m have developed an approach to evaluate and to monitor the quality of suppliers development processes with selfassessments based on a detailed questionnaire. This article gives a short introduction to CMMI, describes the selection of the relevant process areas, the creation of the questionnaire, and the automated evaluation of the results. 1 Motivation, Scope and CMMI Vodafone, the leading global mobile telecommunications company, has many national Operational Companies (OpCo's). The software systems of Vodafone s Intranet are developed by both internal and external development centers. The underlying development processes are different, the quality and results vary. Vodafone wants to ensure that the different development processes for software projects worldwide will deliver predictable results with high quality. An alignment of the different development processes to a common standard was not possible. Because of this, Vodafone and sd&m have developed an approach to evaluate and to monitor the quality of the development processes. The assessment method used is based on CMMI (Capability Maturity Model Integration) V1.1. CMMI is a framework of management, engineering, and support best practices organized into 25 topics, called process areas [Cm02]. It has been developed by the Software Engineering Institute (SEI) at Carnegie Mellon University and can be 274

thought of as a set of process requirements that help guide an organization to define and implement processes related to the 25 topics. CMMI was chosen as the basis for the assessment due to the fact that it covers various disciplines, it is based on practical best-practices, and it not only defines process requirements but also offers possibilities for constructive assessment of organizations. An international standard appropriate f or large organizations was also one of the requirements for choosing the basic framework. Furthermore, there was a trend observed that more and more suppliers start with CMMI improvement programs. So it was convenient to speak the same language. The requirements for assessing the capability according to CMMI are defined in [Cm00]. Since conducting a class A appraisal like SCAMP I SM [Me01] is very time-consuming, research is concentrating on developing class B or C appraisals [Ha03]. The goal of our work was to define a customized supplier evaluation using CMMI as a basis, not to invent a new general assessment method. To define the terms used inthe following sections, w egive a short summary of the CMMI concepts. For more details please refer to [CKS02] or [Kn02]. CMMI models are organized in two representations, continuous and staged. The continuous representation measures capability levels whereas in the staged representation an organization has to fulfill some areas to reach a maturity level. In our work we have chosen the continuous representation, since in this, an organization can select the process areas inwhich it wants to improve and the degree of capabilities. Therefore, capability levels (0-5) are used to express the capabilities and to measure the improvement within each selected process area. The basic concepts in CMMI for assessing the capability are goals and practices. To reach a capability level some goals must be achieved by conforming to some expected practices. CMMI differentiates between Specific Goals and Practices (SP), which are specific to a certain Process Area, and Generic Goals and Practices (GP), which are applicable to all Process Areas. 2 Selecting the relevant process areas The criteria for selecting the process areas are: 1. The process areas shall address a reasonable maturitylevel. 2. The supplier shall be responsible for performing the process area. 3. The process of the supplier has an interface to a Vodafone process. Add 1.) In the regarded context it is enough that the supplier achieves a maturity level of 3. Thus all process areas which correspond to level 4 and 5 in the staged representation were omitted (Organizational Process Performance, Organizational Innovation and Deployment, Quantitative Project Management, Causal Analysis and Resolution ). These may come into focus after all essential suppliers have reached capability level 3 in all relevant process areas. 275

Add 2.) Based on work split it is necessary to distinguish for which process areas Vodafone is more responsible for and for which the supplier is mainly responsible. In the investigated organization the supplier contributes only minor parts to the process areas Requirement Development, Product Integration and Validation. The process areas Supplier Agreement Management and Integrated Project Management are mainly under control of Vodafone. Add 3.) Project Planning and Project Monitoring and Control are strongly connected to the Vodafone planning and control process. The Risk Management of the supplier has to be integrated into the overall Risk Management of the project at Vodafone. The requirements of Vodafone are handled by the Requirements Management of the supplier. The Technical Solution has to follow Vodafone development guidelines and has to be accepted by Vodafone. By Verification the supplier has to fulfill some predef ined quality gates. Finally Configuration Management is strongly related with the Configuration Management of Operations. Each of these areas will be checked by a detailed questionnaire. The remaining process areas are checked by Generic Practices and not byindividual questionnaires. The main reason for this is that Vodafone is mainly interested in the results of these processes and not on the processes themselves. For example regard the process area Organizational Training. Vodafone is mainly interested that the staff is well trained for the job they do, e.g. designing the architecture of a web application. How to arrange this is left to the supplier. Therefore Organizational Training is checked within other questionnaires through the generic practice Train People (GP 2.5). The same holds for the process areas Organizational Process Focus (GP 2.1 and GP 3.2), Organizational Process Definition (GP 3.1), Process and Product Quality Assurance (GP 2.9), Measurement and Analysis (GP 2.8), and Decision Analysis and Resolution (by SP). 3 Proposed Solution The main requirements of Vodafone for the implementation of the questionnaires for the above process areas are: The questionnaires can be used for self assessment and for Vodafone appraisals. Answering the questionnaires requires only a basic understanding ofcmmi (especially not a SCAMPI Certification). The questions should be as concrete as possible, to avoid mistakable answers in self-assessments (and to detect them in Vodafone appraisals). The proposed solution is an Excel application, containing one sheet (questionnaire) for each of the seven process areas, one sheet for the assessment details, and one sheet for the presentation of results. Furthermore it supports the import, the evaluation and the export of assessment results. Especially the suppliers will not see the results and the formulas when filling out the self-assessment sheet. This is necessary to avoid that the 276

supplier answers the questions in a way optimizing the results. Another contribution is a part in the contract that agrees on penalties for answers which can not be verified in a succeeding appraisal. Each questionnaire begins with a short description of the process area. According to the structure of CMMI, each questionnaire inspects first the specific goals and then the generic goals. Each goal is checked by specific practices or by generic practices. Since the specific and generic practices ofcmmi are formulated very generally, for each practice some concrete checks are posed. These checks are focused to the type of supplier work which has to be performed when delivering products to Vodafone. Only these concrete checks have to be answered. The answer has to be given from the following range: Yes : The statement is true in all aspects for all examined projects. Partially : The statement is true in most aspects for the most examined projects. No : otherwise. A check answered with Yes is weighed with 100%, No is weighed with 0%, and Partially is weighed with 50%. The average of all checks of a practice will give a percentage scale from zero to one hundred percent. This is mapped to an estimated rating according to [Is98], section 6.7.2. To reach a capability level for a process area, the evaluated compliance for this level has to be at minimum Largely. To reach a capability level greater than 1, all previous levels must have an evaluated compliance Fully (analog to Satisfied in [Me01], Section 2.4.2). In contrast to SCAMPI it is possible to give practices a weight ( Low, Medium, High ) according to the requirements of Vodafone. Since Vodafone wants to measure some so-called key performance i ndicators (KPI) for each process area, those KPIs are explicitly defined in the questionnaires. To fulfill the generic practice 2.8 the supplier has to record and report these KPIs to Vodafone. These KPIs are used by Vodafone e.g. to define quality gates (e.g. for entering the next stage in the product life cycle). Capability Evaluation Evaluated Target PP 100% CM 75% 50% PMC 25% Sin g le Process Areas PP PMC RSKM REQM TS 86% Fully 70% Largely 71% Largely 89% Fully 71% Largely 63% Largely 65% Largely 88% Fully 47% Partially 69% Largely 67% Largely 50% Partially 83% Largely 50% Partially 67% Largely VER 0% RSKM 5 2 2 4 2 Level 2 Level 1 Level 1 Level 1 Level 1 TS REQM Figure1: Import of questionnaire and representation of evaluation results 277

After the supplier has answered all questions, the questionnaire is imported by Vodafone as shown in Figure 1. Thus for each process area the evaluated compliance to each capability level and the total evaluated capability level are calculated. The results are shown in a summary table and displayed as a spider graph, see Figure 1. Afterwards Vodafone delivers the supplier the results of the evaluation and plans steps for improvement. The scope of a self-assessment will be a first evaluation of a new supplier or repeated evaluation to check process improvements alternating with appraisals by Vodafone. 4 Conclusion In this article we have described a lightweight approach for using CMMI for internal assessments. We think that the proposed method to reduce the complexity ofcmmi is useful in other contexts. From our point of view, CMMI gives ve ry detailed guidance for software engineering, but the topics support and operations were not directly addressed. Furthermore we made the experience, that the influence of Level 2 practices on the assessment results is not easy to understand for the user. These two points are planned to be addressed in CMMI 1.2 and later versions [Ph05]. Currently the developed instruments are introduced at Vodafone and we are interested in comparing the results to previous assessments. The views expressed in this article are not necessarily those of Vodafone. Vodafone is a trademark of the Vodafone Group. Other product and company names mentioned herein may be the trademarks of their respective owners. 5 Literature [CKS03] Chrissis, M.B.; Konrad, M.; Shrum, S.: CMMI: Guidelines for Process Integration and Product Improvement, Addison-Wesley Professional, 2003. [Cm00] CMMI Product Development Team, ARC SM, V1.0 Assessment Requirements for CMMI, Version 1.1, Technical Report CMU/SEI-2001-TR-034 [Cm02] CMMI Product Team: Capability Maturity Model Integration (CMMI SM ), Version 1.1, CMMISM for Software Engineering (CMMI-SW, V1.1), Continuous representation, CMU/SEI-2002-TR-028. [Ha03] Hayes, W.: A Family of SCAMPI Appraisal Methods, SEPG 2003. [Is98] ISO 15504: Information technology Software process assessment A reference [Kn02] model for processes and process capability, Technical Report ISO/IEC TR 15504-2:1998 Kneuper, Ralf: CMMI. Verbesserung von Softwareprozessen mit Capability Maturity Model Integration November 2002, dpunkt.verlag. [Me01] Members of the Assessment Method Integrated Team: Standard CMMI Appraisal Method for Process Improvement (SCAMPI), Version 1.1: Method Definition Document, CMU/SEI-2001-HB-001. [Ph05] Mike Phillips, CMMI Today, January 24, 2005. 278