PROCESS ASSESSMENT AND IMPROVEMENT. Process Assessment  A formal assessment did not seem financially feasible at the onset of the company’s process improvement.

Slides:



Advertisements
Similar presentations
Requirements Engineering Processes – 2
Advertisements

©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 25 Slide 1 Chapter 25 Process Improvement.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 25 Slide 1 Chapter 25 Process Improvement.
IS301 – Software Engineering V:
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 28 Slide 1 Process Improvement 1.
More CMM Part Two : Details.
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
Chapter 26 – Process improvement
Quality Management & Process Improvement
Process Improvement.
Stepan Potiyenko ISS Sr.SW Developer.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 28 Slide 1 Process Improvement.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 28 Slide 1 Process Improvement.
People in the process People are an organisation’s most important assets The tasks of a manager are essentially people oriented. Unless there is some.
Software Development Process Models. The Waterfall Development Model.
A GOAL-BASED FRAMEWORK FOR SOFTWARE MEASUREMENT
Capability Maturity Model (CMM) in SW design
Fundamentals of Information Systems, Second Edition
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Requirements Engineering Processes
1 R&D SDM 1 Software Project Management Capability Maturity Model 2009 Theo Schouten.
CMM Overview - 1 © Paul Sorenson CMPUT Software Engineering refs. IEEE Software, March 1988, 73-79, and IEEE Software, July 1993, (Capability.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 28 Slide 1 Process Improvement.
Software Process CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 17, 2002.
Software Process and Product Metrics
Standardization. Introduction A standard is a document. It is a set of rules that control how people should develop and manage materials, products, services,
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 28 Slide 1 Process Improvement 2.
Chapter : Software Process
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management 1.
Chapter 26 – Process improvement
Integrated Capability Maturity Model (CMMI)
COMPGZ07 Project Management Presentations Graham Collins, UCL
Org Name Org Site CMM Assessment Kick-off Meeting Dates of assessment.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
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.
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 31 Slide 1 Process Improvement u Understanding, Modelling and Improving the Software Process.
Software Engineering - Spring 2003 (C) Vasudeva Varma, IIITHClass of 39 CS3600: Software Engineering: Standards in Process Modeling CMM and PSP.
CSI - Introduction General Understanding. What is ITSM and what is its Value? ITSM is a set of specialized organizational capabilities for providing value.
Software Project Management With Usage of Metrics Candaş BOZKURT - Tekin MENTEŞ Delta Aerospace May 21, 2004.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 25 Slide 1 Process Improvement l Understanding, Modelling and Improving the Software Process.
Software process improvement Framework for SPI SPI support groups, maturity and immaturity models Assessment and gap analysis Education and training Selection.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
University of Sunderland CIFM03Lecture 2 1 Quality Management of IT CIFM03 Lecture 2.
Lecture Topics covered CMMI- - Continuous model -Staged model PROCESS PATTERNS- -Generic Process pattern elements.
Software Metrics – part 2 Mehran Rezaei. Software Metrics Objectives – Provide State-of-art measurement of software products, processes and projects Why.
Georgia Institute of Technology CS 4320 Fall 2003.
SWEN 5130 Requirements Engineering 1 Dr Jim Helm SWEN 5130 Requirements Engineering Requirements Management Under the CMM.
©Ian Sommerville 2004 Software Engineering. Chapter 28Slide 1 Chapter 28 Process Improvement.
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 Chapter 3 1.Quality Management, 2.Software Cost Estimation 3.Process Improvement.
Computing and SE II Chapter 15: Software Process Management Er-Yu Ding Software Institute, NJU.
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…
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming.
Making knowledge work harder Process Improvement.
McGraw-Hill/Irwin © 2013 The McGraw-Hill Companies, Inc., All Rights Reserved. Chapter 5 Information Systems Concepts.
SOFTWARE PROCESS IMPROVEMENT
Process improvement 1. Topics covered  The process improvement process  Process measurement  Process analysis  Process change  The CMMI process improvement.
COMPGZ07 Project Management CMMI Project Planning Lecture 5b Graham Collins, UCL.
Process Improvement Understanding, Modelling and Improving the Software Process.
Process Improvement IS301 – Software Engineering Lecture # 23 – M. E. Kabay, PhD, CISSP Dept of Computer Information Systems Norwich University.
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
1 Software Engineering Muhammad Fahad Khan Software Engineering Muhammad Fahad Khan University Of Engineering.
Chapter 25 Process Improvement.
Requirements Engineering Process
CMMI Q & A.
Chapter 26 – Process improvement
Software Quality Assurance
Presentation transcript:

PROCESS ASSESSMENT AND IMPROVEMENT

Process Assessment  A formal assessment did not seem financially feasible at the onset of the company’s process improvement efforts.  In lieu of a formal assessment, the decision was made to utilize the SEItechnical report, A Method for Assessing the Software Engineering Capability of Contractors.  All members of the Development Group completed the questionnaire associated with this report.  The major findings were mapped to Humphrey’s suggestions for an organization to improve its processes With the objective of moving from the Ad Hoc level to the SEI CMM Level 2 key process areas

Self assessment  The areas identified as target items on which to focus were:  Commitment Review  Quarterly Status Review  Phase Review  The organization elected to have resources expend effort in three KPAs from CMM Level 2—Project Planning, Project Tracking, and Software Configuration Management. The process areas were:  Project Process  Project Tracking Process  Environment Documentation

CMMI-Based Assessment for Internal Process Improvement  The CMMI model  An integrated capability model that includes software and systems engineering capability assessment.  The model has two instantiations  Staged where the model is expressed in terms of capability levels;  Continuous where a capability rating is computed.

CMMI model components  Process areas  24 process areas that are relevant to process capability and improvement are identified. These are organised into 4 groups.  Goals  Goals are descriptions of desirable organisational states. Each process area has associated goals.  Practices  Practices are ways of achieving a goal - however, they are advisory and other approaches to achieve the goal may be used.

CMMI process areas

CMMI assessment  Examines the processes used in an organisation and assesses their maturity in each process area.  Based on a 6-point scale:  Not performed;  Performed;  Managed;  Defined;  Quantitatively managed;  Optimizing.

The staged CMMI model

The continuous CMMI model  This is a finer-grain model that considers individual or groups of practices and assesses their use.  The maturity assessment is not a single value but is a set of values showing the organizations maturity in each area.  The CMMI rates each process area from levels 1 to 5.  The advantage of a continuous approach is that organizations can pick and choose process areas to improve according to their local needs.

PROCESS IMPROVEMENT

Topics covered  Process and product quality  Process classification  Process measurement  Process analysis and modelling  Process change  The CMMI process improvement framework

The process improvement cycle

Process improvement stages  Process measurement  Attributes of the current process are measured. These are a baseline for assessing improvements.  Process analysis  The current process is assessed and bottlenecks and weaknesses are identified.  Process change  Changes to the process that have been identified during the analysis are introduced

Process measurement  Wherever possible, quantitative process data should be collected  However, where organisations do not have clearly defined process standards this is very difficult as you don’t know what to measure. A process may have to be defined before any measurement is possible.  Process measurements should be used to assess process improvements  But this does not mean that measurements should drive the improvements. The improvement driver should be the organizational objectives.

Classes of process measurement  Time taken for process activities to be completed  E.g. Calendar time or effort to complete an activity or process.  Resources required for processes or activities  E.g. Total effort in person-days.  Number of occurrences of a particular event  E.g. Number of defects discovered.

Process analysis and modelling  Process analysis  The study of existing processes to understand the relationships between parts of the process and to compare them with other processes.  Process modelling  The documentation of a process which records the tasks, the roles and the entities used;  Process models may be presented from different perspectives.

Process analysis and modelling  Study an existing process to understand its activities.  Produce an abstract model of the process. You should normally represent this graphically. Several different views (e.g. activities, deliverables, etc.) may be required.  Analyse the model to discover process problems. This involves discussing process activities with stakeholders and discovering problems and possible process changes.

Process analysis techniques  Published process models and process standards  It is always best to start process analysis with an existing model. People then may extend and change this.  Questionnaires and interviews  Must be carefully designed. Participants may tell you what they think you want to hear.  Ethnographic analysis  Involves assimilating process knowledge by observation. Best for in-depth analysis of process fragments rather than for whole-process understanding.

Process change  Involves making modifications to existing processes.  This may involve:  Introducing new practices, methods or processes;  Changing the ordering of process activities;  Introducing or removing deliverables;  Introducing new roles or responsibilities.  Change should be driven by measurable goals.

The process change process

Process change stages  Improvement identification.  Improvement prioritization.  Process change introduction.  Process change training.  Change tuning.

Key points  The three types of process metrics used in the measurement process are time metrics, resource utilisation metrics and event metrics.  Process models include descriptions of tasks, activities, roles, exceptions, communications, deliverables and other processes.  The CMMI process maturity model integrates software and systems engineering process improvement.  Process improvement in the CMMI model is based on reaching a set of goals related to good software engineering practice.

Key points  Process improvement involves process analysis, standardisation, measurement and change.  Processes can be classified as informal, managed, methodical and improving. This classification can be used to identify process tool support.  The process improvement cycle involves process measurement, process analysis and process change.  Process measurement should be used to answer specific process questions, based on organisational improvement goals.