Business benefit of software process improvement Presentation –Johan Andersson –Christian Lindblom.

Slides:



Advertisements
Similar presentations
Robust Design History of Robust Design Robust Design method is essential to improving engineering productivity. It was pioneered by Dr. Genichi Taguchi.
Advertisements

Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
Chapter 2 The Software Process
Computer Engineering 203 R Smith Project Tracking 12/ Project Tracking Why do we want to track a project? What is the projects MOV? – Why is tracking.
©2006 OLC 1 Process Management: The Foundation for Achieving Organizational Excellence Process Management Implementation Worldwide.
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
Overview Lesson 10,11 - Software Quality Assurance
SE 470 Software Development Processes James Nowotarski 12 May 2003.
School of Computing, Dublin Institute of Technology.
SE 450 Software Processes & Product Metrics 1 Quality Systems Frameworks.
Capability Maturity Model (CMM) in SW design
Computer Engineering 203 R Smith Process/Plan Model 7/ Development Process Models Development Process Models are different ways to look at the processes.
1 R&D SDM 1 Software Project Management Capability Maturity Model 2009 Theo Schouten.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 28 Slide 1 Process Improvement.
Strategic cost analysis 2
Organizational Project Management Maturity: Roadmap to Success
Using A Defined and Measured Personal Software Process Watts S. Humphrey CS 5391 Article 8.
Change Request Management
Standardization. Introduction A standard is a document. It is a set of rules that control how people should develop and manage materials, products, services,
Capability Maturity Model
Oversight CHAPTER SIXTEEN Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
1 First, some interesting numbers: ~2,000 ~80 2 >200 [To be defined on March 23]
Project Management Methodology More about Quality Control.
Six Sigma By: Tim Bauman April 2, Overview What is Six Sigma? Key Concepts Methodologies Roles Examples of Six Sigma Benefits Criticisms.
How get your project management or professional services organization ISO 9001 certified.
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
Integrated Capability Maturity Model (CMMI)
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Software Development *Life-Cycle Phases* Compiled by: Dharya Dharya Daisy Daisy
Chapter 2 The process Process, Methods, and Tools
CLEANROOM SOFTWARE ENGINEERING.
N By: Md Rezaul Huda Reza n
Software Quality Assurance Activities
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 31 Slide 1 Process Improvement u Understanding, Modelling and Improving the Software Process.
A Project ’ s Tale: Transitioning From SW-CMM to CMMI-SE/SW Warren Scheinin Systems Engineer, NG Mission Systems CMMI Technology Conference & User Group.
Zahran: Software Process Improvement Part I Jan Dielewicz Kai Petersen Sebastian Stein.
CSI - Introduction General Understanding. What is ITSM and what is its Value? ITSM is a set of specialized organizational capabilities for providing value.
IT Requirements Management Balancing Needs and Expectations.
Software Engineering Saeed Akhtar The University of Lahore Lecture 8 Originally shared for: mashhoood.webs.com.
SOFTWARE ENGINEERING MCS-2 LECTURE # 3. SOFTWARE PROCESS  A software development process, also known as a software development life- cycle (SDLC), is.
IPMA Executive Conference Value of IT September 22, 2005.
IIL’s International Project Management Day, 2007 The Power of the Profession: A Lesson Learned and Solution Implemented Becomes a Best Practice in Project.
University of Sunderland CIFM03Lecture 2 1 Quality Management of IT CIFM03 Lecture 2.
Georgia Institute of Technology CS 4320 Fall 2003.
©Ian Sommerville 2004 Software Engineering. Chapter 28Slide 1 Chapter 28 Process Improvement.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
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.
Quality is Job 1. In the Beginning… Deming – the name of quality Think of autos In software –Program mistakes –Development time –Originally inspect final.
Rational Unified Process (RUP) Process Meta-model Inception Phase These notes adopted and slightly modified from “RUP Made Easy”, provided by the IBM Academic.
CSI—The Lifecycle Stage
COMP 6710 Course NotesSlide 3-0 Auburn University Computer Science and Software Engineering Course Notes Set 3: Software Process Maturity Computer Science.
Copyright 2012 John Wiley & Sons, Inc. Chapter 12 Project Auditing.
Chapter 2 – Software Processes Lecture 2 1Chapter 2 Software Processes.
1 Lecture 2.4a: SEF SE Planning and the SEP (SEF Ch 16) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
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)
Cmpe 589 Spring Fundamental Process and Process Management Concepts Process –the people, methods, and tools used to produce software products. –Improving.
Change Request Management
Strategic Information Systems Planning
BANKING INFORMATION SYSTEMS
The V Model The V Model Damian Gordon Damian Gordon.
Introducing Requirements Change Management Process into ISO/IEC 12207
KEY PROCESS AREAS (KPAs)
Capability Maturity Model
Capability Maturity Model
Metrics That Work for You
PROJECT MANAGEMENT MATURITY MODEL (PMMM)
Requirements Development in CMMI
Presentation transcript:

Business benefit of software process improvement Presentation –Johan Andersson –Christian Lindblom

Proof of benefits from software process improvement Often quoted examples –US Air Force Logistics Command: invested ~$5 million direct savings ~$2 million –Hughes Aircraft: invested ~$0.5 million over one year saved ~$2 million –Raytheon: invested ~$1 million over four years saved ~$16 million Blekinge Institute of Technology SE Karlskrona

Results of software process improvements Improved product quality Shorter time to market More productivity Which in turn leads to saved money Blekinge Institute of Technology SE Karlskrona

Evidence given in book –7 case studies –4 Europe –3 USA Blekinge Institute of Technology SE Karlskrona

Evidence from Europe Quality initiatives/studies –European Systems and Software Initiative (ESSI) –IBM’s European software development benchmark Blekinge Institute of Technology SE Karlskrona

Evidence from Europe Improving the project estimation process –Engineering Ingegneria Informatica SPA –Formal specification for non-functional requirements –Allowed for tracing impact on development time throughout development cycles –With each iteration more data is gathered allowing for better estimates –Applied experimentally to six projects, all showing lower deviation from estimates –Better results could be related to “luck”, low number of non-functional requirements Blekinge Institute of Technology SE Karlskrona

Evidence from Europe Using formal specification methods to improve subcontracting methods –ENEL SPA CRA –Improved structure of requirements specification allowing for improved maintainability of outsourced projects –Two similar projects tracked the one with improved specifications got a reduced cost –Improved requirements specifications simplified acceptance phase –Better results for the project where improvements were made can be due to other factors Blekinge Institute of Technology SE Karlskrona

Evidence from Europe Introduction to configuration management –Datamat Ingegneria dei Sistemi SpA –Introduced configuration management in the development of financial products –Initially began with studying the objects that were to be managed –Showed improvements in managing change, reproducibility of product releases, validation of product versions and the passing of components between workers –Results could be due to improved knowledge about the objects that were to be managed Blekinge Institute of Technology SE Karlskrona

Evidence from Europe Establishing a software process organizational and management infrastructure –Computer-Logic SA –Used CMM for validation of the company –Tried to make up for the weak parts –Benefited from a general improvement of the company's infrastructure –Could be the improved quality awareness that caused the improvement Blekinge Institute of Technology SE Karlskrona

Evidence from the USA Quality organisation –The Software Engineering Institute (SEI) Blekinge Institute of Technology SE Karlskrona

Evidence from the USA Software Engineering Division at Hughes Aircraft –Started using CMM to evaluate themselves continuously –Decisions of improvements based in the fault found during assessments –Improved quality in general –Knowledge about things to improve are always helpful –Can improvements actually be seen from year to year after several years of use? Blekinge Institute of Technology SE Karlskrona

Evidence from the USA Raytheon: another pioneer of software process improvement –Adopted a three-phased paradigm for process improvement –Conducted a self-assessment and where rated at level 1 –Initiated a process improvement program –Created an organizational infrastructure to support process improvement –resulted in 7.7 times more money saved than invested and a two-fold increase in productivity Blekinge Institute of Technology SE Karlskrona

Evidence from the USA Space Shuttle Onboard Software –Poor project management, especially the inability to manage within the constraints set by cost, schedule, functionality and quality –Driving projects from schedule, not quality requirements –Failure to control the contents of requirements and software product baselines –Failure to track errors and to make progress changes that eliminate their causes Blekinge Institute of Technology SE Karlskrona

Lessons learned Alignment with business needs and customer satisfaction Focused investment makes significant benefits possible Demonstrate the benefits Benefits will materialize in the mid to long term Take an incremental approach Sell the idea to the whole organization Blekinge Institute of Technology SE Karlskrona

General questions raised To few case studies No criticism towards the results Only success stories Necessity of separating European and American companies? Do the American and European companies differ in their reasoning for attempting quality improvements? Blekinge Institute of Technology SE Karlskrona

Epilogue Process maturity: another buzzword The role of standards Industrialization of software development What is the next step? Blekinge Institute of Technology SE Karlskrona