Using the CMMI in small Organisations Stephen Fletcher PAS Ltd, UK.

Slides:



Advertisements
Similar presentations
Multivendor Interoperability
Advertisements

Introduction to ORYX. Agility without Control  Unacceptable rate of error (88%*)  Highly manual, with …  … limited automation potential  Lack of audit.
Integrated Project Management IPM (Without IPPD) Intermediate Concepts of CMMI Project meets the organization Author: Kiril Karaatanasov
Process and Product Quality Assurance (PPQA)
Implementing CMMI® for Development Version 1.3
Kelemen Zádor Dániel  About ISO 9001: 2000  About CMMI v1.2  Main differences  Differences in terminology  Similarities 
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
More CMM Part Two : Details.
ITIL: Service Transition
Copyright 2005 CMMI and ITIL Alison Adams & Kieran Doyle.
Copyright 2003 CMMI: Executive Briefing Presented by Kieran Doyle
Sarbanes Oxley & CMMI Mazars / Lamri
ERP Implementation Strategies
PERFORMANCE FOR ALL The Project & the System. A HE project co-ordinated by University of Bristol, open to HE internationally. Developing the requirements.
Copyright © 2006 Software Quality Research Laboratory DANSE Software Quality Assurance Tom Swain Software Quality Research Laboratory University of Tennessee.
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.
Aust. AM Collaborative Group (AAMCOG) An introduction to ISO “What to do” guide 20th October 2014.
Chapter 3 The Structure of the CMM
CMMI Overview Quality Frameworks.
Readiness Index – Is your application ready for Production? Jeff Tatelman SQuAD October 2008.
Process: A Generic View
CMMI Course Summary CMMI course Module 9..
8. CMMI Standards and Certifications
CS3500 Software Engineering How does a “program” differ from a “software system”? Program System Tens to hundreds of lines of code Thousands to millions.
The Capability Maturity Model in Software Development Paul X. Harder, JD Government Micro Resources, Inc. September 14, 2004.
Test Organization and Management
Software Engineering Reuse.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
Thirteenth Lecture Hour 8:30 – 9:20 am, Sunday, September 16 Software Management Disciplines Process Automation (from Part III, Chapter 12 of Royce’ book)
1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
A Project ’ s Tale: Transitioning From SW-CMM to CMMI-SE/SW Warren Scheinin Systems Engineer, NG Mission Systems CMMI Technology Conference & User Group.
Chapter 2 Process: A Generic View
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.
Lecture Topics covered CMMI- - Continuous model -Staged model PROCESS PATTERNS- -Generic Process pattern elements.
Capability Maturity Model CS3300 Fall The Problem Contractors over budget and late. Need a way to rank how likely a software company is to deliver.
Application of the CMMI SM to Plan and Control Life Cycle Costs Dr. Mary Anne Herndon Science Applications International Corporation (SAIC) November, 2003.
Georgia Institute of Technology CS 4320 Fall 2003.
1 © Mahindra Satyam 2009 Mahindra Satyam Confidential Welcome To CMMI Introduction.
 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
An Introduction. Objective - Understand the difference between CMM & CMMI - Understand the Structure of CMMI.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
Copyright © | Trade secret and confidential Page 1 Innovative, Professional, Fact Based and Eustressed© Maruthi Quality Management Services Ptv. Ltd..,
 CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze.
MSA Orientation – v203a 1 What’s RIGHT with the CMMI?!? Pat O’Toole
CMMI Overview Quality Frameworks. Slide 2 of 146 Outline Introduction High level overview of CMMI Questions and comments.
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
© 2004 Tangram Hi-Tech Solutions Project Management According to the CMMI1 Project Management according to the Capability Maturity Model (CMMI)
Practical IT Research that Drives Measurable Results Get Started Bringing Order to Help Desk Request Chaos.
CS223: Software Engineering Lecture 32: Software Maintenance.
Organizing and leading the IT function Two set of tensions guide policies for developing, deploying and managing IT systems. 1.Innovation and control a.How.
Figures – Chapter 26. Figure 26.1 Factors affecting software product quality.
Serving IT up with ITIL By Thane Price. IT is the laboratory’s pit crew  Goal : Make technology transparent while accomplishing valuable internal customer.
ITIL: Service Transition
Workplace Projects.
BIL 424 NETWORK ARCHITECTURE AND SERVICE PROVIDING.
Chapter 10 Software Quality Assurance& Test Plan Software Testing
CMMI Overview Quality Frameworks.
Building an effective business case for PPM software
IEEE Std 1074: Standard for Software Lifecycle
Presented To: 3rd Annual CMMI Technology Conference and User Group
CMMI – Staged Representation
CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE
Software Engineering: A Practitioner’s Approach, 6/e Chapter 2 Process: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Small Organizations are Different?
Engineering Processes
Requirements Development in CMMI
Presentation transcript:

Using the CMMI in small Organisations Stephen Fletcher PAS Ltd, UK.

Copyright PAS Ltd, Uk. Roadmap What is a small organisation? Problems small organisations’ face A brief look at the process categories A case study of a small service organisation

Copyright PAS Ltd, Uk. What is a small organisation? Project staffed with 3 people A Department of 20 people Maintaining a network and infrastructure Service department running a level 1 helpdesk Projects that last 5 days Emergency fixes and quick changes “Specials”, “one off projects”, “prototypes”

Copyright PAS Ltd, Uk. Typical problems a small organisation faces Limited resource for process improvement Few Individuals covering multiple roles Too many model practices Sometimes very simple interfaces with stakeholders Sometimes very complex interfaces with stakeholders

Copyright PAS Ltd, Uk. What are the attributes that change a process definition? Or why can one process not fit all organisations: Number of stakeholders When the stakeholders are involved Level of complexity of the engineering Customers needs (Process and Quality) Internal or External customers

Copyright PAS Ltd, Uk. Some things never change Most Managers would like: –Better resource and cost planning –Better control of the group –Increased Productivity –Less problems and fire fighting They don’t always realise they can achieve this in their small org.

Copyright PAS Ltd, Uk. There is always a need to plan The basic Project Management PA’s apply to all areas of business But these can be challenging to a small organisation: –Consider a maintenance shop that deals with operational problems –A service desk that handles customer and internal problem calls These organisations at first look to be reactive

Copyright PAS Ltd, Uk. Engineering is Engineering Engineering is a transformation of: –Requirement into a design –Implementing the design –Integrating new/modified components –Verifying and Validating Leaving a documentation trail of what you have done and of the current state of the product An engineering lifecycle is used even when the smallest change is made to a product

Copyright PAS Ltd, Uk. The support process areas are always required Configuration Management is essential for product integrity PPQA for process compliance and adherence to standards Measurement and Analysis for understanding of process and product quality.

Copyright PAS Ltd, Uk. Organisation Infrastructure This posses more of a problem for the small organisation The cost of building organisational assets can be high The return on investment is often less visible to management

Copyright PAS Ltd, Uk. Case study – A small service organisation Staff of 5 people running a help desk –Logs initial call –Handles the level 1 issues Staff of 15 people handling and fixing the level 2 and level 3 issues Level 4 issues get transferred to the software development group as a product requirement change

Copyright PAS Ltd, Uk. Initial State All the service calls handled in a reactive manner No resource planning in place Little documented knowledge of system configurations Undocumented changes made to live configurations to fix problems quickly “We don’t have time to record everything we do, we are so busy and under resourced”

Copyright PAS Ltd, Uk. Process Improvement Infrastructure The Software development group already at CMM Level 2, transitioning to CMMI Maturity Level 2 A Process improvement group is in place with central resource One full time Process Improvement staff was allocated to the service group to help them forward. Decided on a continuous approach

Copyright PAS Ltd, Uk. Approach The action plan had the following steps: 1.Record all the configurations of the systems 2.Implement rigorous change management 3.Implement Causal Analysis and Resolution on the level 2 and 3 problems that are logged 4.Remove the cause of the problem by changing (or creating) process 5.Gather data from change management system on call profiles, time to fix and effort to fix 6.Use data to build resource and service level models to base the future resource planning

Copyright PAS Ltd, Uk. CAR used early CAR meetings held every two weeks, to identify the next problem to fix. Based on frequency, severity and cost Processes built and documented based on the problems the group identifies Monthly reports to senior managers showing fault catagories fixes, estimated cost saved, and profiles of help desk performance Note – CAR used in this way is not how an ML5 org approaches PI.

Copyright PAS Ltd, Uk. Continuous Profile Configuration Management (CM) PPQA ( to ensure the CM process is rigorously followed) Measurement and Analysis (MA) to collect and analyse the data CAR to analyse the causes of the issues and seek to remove the cause Project Management (PP and PMC) for the resource planning

Copyright PAS Ltd, Uk. Summary The CMMI can be used effectively in a small organisation. Focus on areas of the model that give benefit. Realise that some practices mean more to a small organisation than others. Understand the risk and consequence of each model practice, and use common sense when interpreting them