Zahran: Software Process Improvement Part I Jan Dielewicz Kai Petersen Sebastian Stein.

Slides:



Advertisements
Similar presentations
Develop an Information Strategy Plan
Advertisements

University of York Planning for Process Review. Using our Vision, Strategy and Medium Term Planning to inform our business and process change agenda..
Gallup Q12 Definitions Notes to Managers
A presentation from June 20, 2000 Jim Brosseau The ‘How-To’ of Software Process Improvement.
CHAPTER 18 1 Use with BUSINESS TO BUSINESS MARKETING MANAGEMENT: A GLOBAL PERSPECTIVE ISBN Published by Routledge 2013.
Chapter 2 The Software Process
Chapter 10 Schedule Your Schedule. Copyright 2004 by Pearson Education, Inc. Identifying And Scheduling Tasks The schedule from the Software Development.
2-1 The Organizational Context: Strategy, Structure, and Culture Chapter 2 © 2007 Pearson Education.
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 2-1 The Organizational Context: Strategy, Structure, and Culture Chapter 2.
Stepan Potiyenko ISS Sr.SW Developer.
McGraw-Hill/Irwin 2010 Modified by Jackie Kroening 2011 TEAMS IN QUALITY ORGANIZATIONS Chapter 9.
Making Software Process Improvements Happen Jimmie Johansson Richard Berntsson-Svensson Kashif Ahmed Kahn.
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.
CMMI Overview Quality Frameworks.
Understanding Organisational Context 2e
Organizational Project Management Maturity: Roadmap to Success
Standardization. Introduction A standard is a document. It is a set of rules that control how people should develop and manage materials, products, services,
Chapter 24 - Quality Management
SOFTWARE QUALITY ASSURANCE Asst. Prof. Dr. Selim BAYRAKLI Maltepe University Faculty of Engineering SE 410.
Welcome ISO9001:2000 Foundation Workshop.
Privileged and Confidential Strategic Approach to Asset Management Presented to October Urban Water Council Regional Seminar.
CMM Level 3 KPA’s CS4320 Fall Organizational Process Focus (Goals) Software process development and improvement activities are coordinated across.
1 Software Process Improvement. 2 Introduction Instructors Course Where are we? What would we learn from this course?
CMMI Course Summary CMMI course Module 9..
Software Project Management Lecture # 8. Outline Chapter 25 – Risk Management  What is Risk Management  Risk Management Strategies  Software Risks.
Capability Maturity Model. Reflection Have you ever been a part of, or observed, a “difficult” software development effort? How did the difficulty surface?
Business Analysis: A Business Unit Perspective International Institute of Business Analysis January 18, 2012.
Software Engineering II Lecture 1 Fakhar Lodhi. Software Engineering - IEEE 1.The application of a systematic, disciplined, quantifiable approach to the.
Comparison of CMM Level 2 and eXtreme Programming Copyright, 2002 © Bartosz Walter Quality Connection 2002, Helsinki Poznan University of Technology Poznan,
Prof Barry Dwolatzky JCSE at Wits University Government CIO Summit Towards reducing costs of doing business in government and contributing towards achieving.
PART 2: A FRAMEWORK FOR SOFTWARE PROCESS IMPROVEMENT (SPI) Jean Charles Salvin Markus Erlandsson Jan-Peter Nilsson.
Capability Maturity Model Part One - Overview. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First.
N By: Md Rezaul Huda Reza n
University of Nevada, Reno Data-Driven Organization Governance 1 Governing a data-driven organization (4/24/2014)  Define governance within organizations.
Organization of the Information Systems Function Chapter 14.
Software Project Management Lecture # 8. Outline Earned Value Analysis (Chapter 24) Topics from Chapter 25.
J. R. Burns, Texas Tech University Capability Maturity Model -- CMM n Developed by the Software Engineering Institute (SEI) in 1989 –SEI is a spinoff.
CS3100 Software Project Management Week 26 - Quality Dr Tracy Hall.
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
Project Management Chapter 9 Project Quality Management Dr. Jana Jagodick Polytechnic of Namibia, 2012.
When Partnering Fails… Gayle Waldron President, The Management Edge.
Business benefit of software process improvement Presentation –Johan Andersson –Christian Lindblom.
CSI - Introduction General Understanding. What is ITSM and what is its Value? ITSM is a set of specialized organizational capabilities for providing value.
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.
1 ISO 9001:2000 ISO 9001 is the creation of the International Organisation for Standardisation (ISO), a Swiss-based federation of national standards bodies.ISO.
Georgia Institute of Technology CS 4320 Fall 2003.
Blekinge Institute of Technology SE Karlskrona MARKETING MANAGEMENT Chaudhry Muhammad Nadeem Faisal Cell:
Glen Fields - Final Project Presentation. What Sets CSI Apart... GBA 573 Consultants Company Background Located in San Diego, CA 5 Engineering Consultants.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
Chapter 17 Organizational Goals and Structures The key is to match structures to goals.
Chapter 4 프로세스 모델 Process Models
Chapter 3 Strategic Information Systems Planning.
Requirements Development in CMMI
Building Operational Effectiveness Presented by Sharon McCollick.
COMP 6710 Course NotesSlide 3-0 Auburn University Computer Science and Software Engineering Course Notes Set 3: Software Process Maturity Computer Science.
Software Project Management Lecture # 9. Outline Chapter 25 – Risk Management  What is Risk Management  Risk Management Strategies  Software Risks.
Software Engineering (CSI 321) Software Process: A Generic View 1.
SEN 460 Software Quality Assurance. Bahria University Karachi Campus Waseem Akhtar Mufti B.E(C.S.E) UIT, M.S(S.E) AAU Denmark Assistant Professor Department.
CMMI Overview Quality Frameworks. Slide 2 of 146 Outline Introduction High level overview of CMMI Questions and comments.
Human Resource Practices
CS4311 Spring 2011 Process Improvement Dr
Quality Management chapter 27.
Chapter 10 Software Quality Assurance& Test Plan Software Testing
Software Engineering (CSI 321)
Information Technology Project Management – Fifth Edition
Chapter 12 Implementing strategy through organization
Chapter 12 Implementing strategy through organization
Requirements Development in CMMI
Presentation transcript:

Zahran: Software Process Improvement Part I Jan Dielewicz Kai Petersen Sebastian Stein

Blekinge Institute of Technology SE Karlskrona Agenda 1.Process Thinking 2.Process Discipline 3.Effective Process Environment 4.Process Maturity: The Second Wave of the Software Industry (short)

Blekinge Institute of Technology SE Karlskrona Aspects of the Process Sommerville: “A software process is the set of activities and associated results that produce a software product.” Zahran:  The process must be defined.  The process performers must be trained in the process.  A process must be monitored and enforced.

Blekinge Institute of Technology SE Karlskrona Process Thinking  “Process thinking differs from conventional thinking” … “Process thinking is a natural way of thinking.” [Zahran, p. 13]  car driving as a process  valid example?  process = skill?  a group following ONE process is streamlined

Blekinge Institute of Technology SE Karlskrona Process Focus vs. Product Focus  product focus:  vertical integration  several departments  process focus:  horizontal integration  crossing several departments  matrix organisation?  product focus leads to chaos  process focus leads to stable organisation

Blekinge Institute of Technology SE Karlskrona Internalization and Institutionalization  internalization:  individual level  following process without thinking  steering, breaking, accelerating without having to think about it  institutionalization:  organisational level  everybody in organisation follows ONE process  process is enforced in organisation

Blekinge Institute of Technology SE Karlskrona Process Maturity  degree how well process is applied  how developed the process is  process is central nervous system  ties together all parts of a company like:  people  technology  organisational structure  management

Blekinge Institute of Technology SE Karlskrona Process Discipline  Discipline is “the system of rules used to maintain control or order over a group of people” ~ Concise Oxford Dictionary  For a process to be effective it must be enforced  A disciplined process is a mature process  A mature process is defined, trained, enforced, followed and continuously improving

Blekinge Institute of Technology SE Karlskrona Weaken negative effects  A bureaucratic process may inhibit performance  Process users must take part in designing the process  Process discipline may impede creativity  If creativity required, process has to encourage creativity  Example: brainstorming

Blekinge Institute of Technology SE Karlskrona Process documentation  Can process focus exist without documentation?  Absence of process definition takes the risk with:  Dependence on individuals  ‘Gurus’ joining the team  Disruptive new joiners  Inconsistency of process knowledge Is this different when there is a process definition?

Blekinge Institute of Technology SE Karlskrona Benefits of process discipline (1/3)  Every individual strives for the common goal of the team.  Orchestra example  Without a maestro (the process is not managed)  Without musical notes (the process is not documented)  Without practise (the process is not trained)  With everyone playing his or her notes (the process is not enforced) Well, ok. But what about Jazz and the improvisational solos? They perform according to some basic rules and guidelines – not a detailed defined process!

Blekinge Institute of Technology SE Karlskrona Benefits of process discipline (2/3)  Life critical situations  Crew flying plane, surgical team, high-risk mission (space shuttle)  All following a mature process: defined, trained, enforced, followed and continuously improving  What if something unexpected happens?  Say: “Sorry, nothing stated in the process documentation for this case”  Say: “Sorry no form available” Then skills and knowledge (intelligence) is in demand!

Blekinge Institute of Technology SE Karlskrona Benefits of process discipline (3/3)

Blekinge Institute of Technology SE Karlskrona Process discipline and product quality  Good process  good quality  Good process  bad quality  Bad process  good quality  Bad process  bad quality

Blekinge Institute of Technology SE Karlskrona Process-focussed organisations (1/3)  “You could say that the mature process, like the mature adult, looks boring, and you could be right!” ~ Zahran  In a mature (in contrast to an immature) process,  roles and responsibilities are well defined  people follow a planned process constantly  people share and learn from experience  problems are analysed from a basis of sound knowledge  estimates are accurate  the progress predictable

Blekinge Institute of Technology SE Karlskrona Process-focussed organisations (2/3)  In process-focussed organisation  the process spreads across organisational functions  teams are empowered to make decisions relating the complete process  the process is customer focussed  the responsibility is shared across the functional divisions  the process goes align with the organisation’s goals

Blekinge Institute of Technology SE Karlskrona Process-focussed organisations (3/3)  Landmarks indicating process-focussed organisations  Central role of the process  Process consists of 3 components: document, training, enforcement-mechanism to follow the process  The process is more than a set of activities  End-to-end coverage  In software projects 3 main process types: management, engineering, support

Blekinge Institute of Technology SE Karlskrona Process Myths and Realities  Documentation Myth  Trust Myth  Verification Myth  Stability Myth  Sponsorship Myth  Continuous Enforcement Myth

Blekinge Institute of Technology SE Karlskrona Process Effectiveness and Efficiency REALITY?

Blekinge Institute of Technology SE Karlskrona Making the Process more Efficient External Factors provide feedback, too!

Blekinge Institute of Technology SE Karlskrona Feedback from External Factors  Laws (Standards, Trade Laws etc.)  Regulations (Industry- and Product-Specific)  Inspections and Certification  What else?

Blekinge Institute of Technology SE Karlskrona Process Culture

Blekinge Institute of Technology SE Karlskrona Megatrends in Software Industry  3 waves in software industry 1.Structured methods, Waterfall, diagrams 2.Process improvements, process maturity 3.Mechanisation of software production  in the middle of 2 nd wave:  formally define processes  try to steadily improve processes

Blekinge Institute of Technology SE Karlskrona History of Process Maturity  Total Quality Management (see e.g. green book by Bergman et al. chapter 3)  Humphrey, W. late 1990 th  Software Engineering Institute

Blekinge Institute of Technology SE Karlskrona Software Process Maturity Standards and Initiatives  Capability Maturity Model (CMM) by SEI  ISO 9000  ISO/IEC  Bootstrap  TickIT

Blekinge Institute of Technology SE Karlskrona Levels of Process Institutionalization 1.Corporate and Organisational Level  process aligned to business goals  team members from different vertical departments formed 2.Project and Team Management Level  staff management through monitoring the process performance and NOT the individual  rewards for good process work 3.Personal Level  personal software process (PSP)

Blekinge Institute of Technology SE Karlskrona References  Bergman, B. and Klefsjö, B. (2003). Quality: from Customer Needs to Customer Satisfaction. Studentlitteratur  Sommerville, I. (2004). Software Engineering. Pearson Education  Zahran, S. (1998). Software Process Improvement. Addison-Wesley