UNIVERSITY OF MARYLAND CENTER FOR ADVANCED TRANSPORTATION TECHNOLOGY Organizational Maturity Prepared for the Operations Summit by Philip J. Tarnoff.

Slides:



Advertisements
Similar presentations
PRD Group Maturity Matrix 31/07/08. Maturity Matrix Guidance Notes Aims of the Matrix The Maturity Matrix is a tool aimed to support groups during their.
Advertisements

SOFTWARE PROCESS IMPROVEMENT “Never Stop Learning”
More CMM Part Two : Details.
Chapter 2 The Software Process
Software Process Improvement Robin B. Hunter, Ph.D. Vol 2., p Presented by: Andrew Wheeler.
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
SE 470 Software Development Processes James Nowotarski 12 May 2003.
Capability Maturity Model (CMM) in SW design
Business Driven Enterprise Architecture Assessment Methodology Josh Arceneaux August 16, 2011.
Operations Planning Organizing for Travel Time Reliability Ohio Planning Conference July 15, 2014.
CMMI Overview Quality Frameworks.
Software Process CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 17, 2002.
Organizational Project Management Maturity: Roadmap to Success
How ISO 9001 Fits Into The Software World? Management of Software Projects and Personnel CIS 6516 March 6, 2006 Prepared by Olgu Yilmaz Swapna Mekala.
Standardization. Introduction A standard is a document. It is a set of rules that control how people should develop and manage materials, products, services,
Lecture 11 CMM CSCI – 3350 Software Engineering II Fall 2014 Bill Pine.
Capability Maturity Model
Capability Maturity Model Integration (CMMI) COMP Group Assignment #1 Ario Nejad, Davit Stepanyan, Ian Jackman, Sebastian Henneberg, Wan Chi Chio.
INTRODUCTION Performance management is a relatively new concept to the field of management.
© 1998 Concept Five Technologies Enterprise Application Integration Capability Maturity Model.
Chapter : Software Process
Process: A Generic View
What ISO 9000 Mandates The requirements for a quality system have been standardized - but many organizations like to think of themselves as unique. So.
UNIT-II Chapter : Software Quality Assurance(SQA)
Capability Maturity Model. Reflection Have you ever been a part of, or observed, a “difficult” software development effort? How did the difficulty surface?
Prof Barry Dwolatzky JCSE at Wits University Government CIO Summit Towards reducing costs of doing business in government and contributing towards achieving.
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
Institutional Architectures to Advance Operational Strategies Maryland Transportation Operations Summit Steve Lockwood Parsons Brinckerhoff May 1, 2008.
J. R. Burns, Texas Tech University Capability Maturity Model -- CMM n Developed by the Software Engineering Institute (SEI) in 1989 –SEI is a spinoff.
OntarioMD’s EMR Maturity Model & Reporting Advancing Optimization and Use e-Health 2013 Accelerating Change Conference Presented By: Darren Larsen, MD,
S Q A.
Chapter 2 Process: A Generic View
Lecture 1 Introduction to Software Engineering
Software Engineering Lecture # 17
Capability Maturity Model. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First version published in.
NCHRP Study (30) Performance Measures for Context Sensitive Solutions – A Guidebook for State DOTs As presented by Sally Oldham at the 2005 Midwest.
Models of Quality Assessment
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.
CS Process Improvement CMM Hans Van Vliet, Software Engineering, Principles and Practice, 3 rd edition, John Wiley & Sons, Chapter 6. W. Humphrey,
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.
Michael Campe U.S. Army Aviation and Missile Command NDIA TID Technical Information Division Symposium Royal Sonesta Hotel, New Orleans, LA August 2003.
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.
Page 1 The Capability Maturity Model (CMM) distinguishes between immature and mature software organizations. Immature software organizations are typically.
Update on Actions to Improve Regional Transportation Communications and Coordination During Incidents Prepared for the Transportation Planning Board Presented.
SOFTWARE PROCESS IMPROVEMENT
CMMI The quality of a software product is only as good as the process used to develop and maintain it. Whether a software organization is competing in.
Software Engineering (CSI 321) Software Process: A Generic View 1.
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.
Done By: Asila AL-harthi Fatma AL-shehhi Fakhriya AL-Omieri Safaa AL-Mahroqi.
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
CMMI for Services, Version 1.3
Capability Maturity Model. What is CMM? n CMM: Capability Maturity Model n Developed by the Software Engineering Institute of the Carnegie Mellon University.
CS4311 Spring 2011 Process Improvement Dr
CMMI Overview Quality Frameworks.
Software Engineering (CSI 321)
Information Technology Project Management – Fifth Edition
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
CMMI Overview.
Software Engineering Lecture 16.
Software Engineering I
Capability Maturity Model
Chapter # 8 Quality Management Standards
Capability Maturity Model
Capability Maturity Model
Presentation transcript:

UNIVERSITY OF MARYLAND CENTER FOR ADVANCED TRANSPORTATION TECHNOLOGY Organizational Maturity Prepared for the Operations Summit by Philip J. Tarnoff

UNIVERSITY OF MARYLAND CENTER FOR ADVANCED TRANSPORTATION TECHNOLOGY Agenda What is organizational maturity? History of the concept Relationship to the transportation community Application to incident management Application to transportation organizations (Lockwood)

UNIVERSITY OF MARYLAND CENTER FOR ADVANCED TRANSPORTATION TECHNOLOGY Organizational Maturity – What is it? A technique for evaluating the effectiveness of an organization’s processes Defined in terms of five levels Objectives include: –Repeatability –Effectiveness –Performance measurement –Optimization

UNIVERSITY OF MARYLAND CENTER FOR ADVANCED TRANSPORTATION TECHNOLOGY Organizational Maturity – What it isn’t It is NOT another quality initiative (TQM, ISO9000, etc.) It is NOT a prescriptive approach defining processes to be followed It is NOT a directive from external organizations or senior management It IS a way of “getting your act together”

UNIVERSITY OF MARYLAND CENTER FOR ADVANCED TRANSPORTATION TECHNOLOGY Maturity Levels Incomplete Performed Managed Established Predictable Level 0 Level 1 Level 2 Level 3 Level 4 Disorganized Ad hoc operation. Relationships not coordinated Processes fully documented & staff trained Fully coordinated operation. Performance data systematically collected and applied Strong sense of teamwork, with full understanding of processes and performance objectives Most of today’s agencies Goal for the future

UNIVERSITY OF MARYLAND CENTER FOR ADVANCED TRANSPORTATION TECHNOLOGY Interpretation of Levels LevelNameCharacteristics 1IncompleteAd hoc processes 2PerformedProcedures defined & tracked 3Managed Process is managed & measured 4EstablishedContinuous analysis

UNIVERSITY OF MARYLAND CENTER FOR ADVANCED TRANSPORTATION TECHNOLOGY Identifying a Level CharacteristicLevel 1Level 2Level 3Level 4 People Process Technology Measurement

UNIVERSITY OF MARYLAND CENTER FOR ADVANCED TRANSPORTATION TECHNOLOGY Maturity Rules Level determined by the weakest characteristic Levels cannot be skipped Levels determined using an appraisal process Process should: –Involve all management levels –Be collaborative –Actionable Observe non-attribution of data

UNIVERSITY OF MARYLAND CENTER FOR ADVANCED TRANSPORTATION TECHNOLOGY An Interesting History Developed by Carnegie Mellon U. (CMU) Known as the Capability Maturity Model (CMM) Developed for IT projects CMM funded by DoD Adopted by more than 30 organizations

UNIVERSITY OF MARYLAND CENTER FOR ADVANCED TRANSPORTATION TECHNOLOGY CMM Family Tree Service Delivery Acquisition IT Development CMM

UNIVERSITY OF MARYLAND CENTER FOR ADVANCED TRANSPORTATION TECHNOLOGY Planting a Second Tree Service Delivery Acquisition IT Development CMM For DOTs

UNIVERSITY OF MARYLAND CENTER FOR ADVANCED TRANSPORTATION TECHNOLOGY Impacts of CMM on IT Projects

UNIVERSITY OF MARYLAND CENTER FOR ADVANCED TRANSPORTATION TECHNOLOGY Improvements for Systems Integration Projects Performance CategoryMedian Improvement Cost34% Schedule60% Productivity61% Quality48% Customer Satisfaction14% Benefit Cost Ratio4:1

UNIVERSITY OF MARYLAND CENTER FOR ADVANCED TRANSPORTATION TECHNOLOGY Incident Management Objectives If an incident occurred today… 1)It would be managed the same way tomorrow 2)Effective response would be assured 3)Everyone would work as a team 4)Participation of key individuals would not be required 5)The agency would never be “caught by surprise” (e.g. evacuations)

UNIVERSITY OF MARYLAND CENTER FOR ADVANCED TRANSPORTATION TECHNOLOGY Application to Incident Management CharacteristicLevel 1Level 2Level 3Level 4 People Fire fighting Uncoordinated Trained Expectations understood Work as integrated teams Strong sense of teamwork Process Few stable processes Processes documented and stable Integrated with other organizational processes Understood & systematically improved Technology Intro of new technology is risky Technology used to support stable activities New technologies evaluated qualitatively New technologies are evaluated quantitatively Measurement Ad Hoc data collection Performance measured selectively Performance systematically measured for all processes Data used to understand and improve the process

UNIVERSITY OF MARYLAND CENTER FOR ADVANCED TRANSPORTATION TECHNOLOGY Achieving a Higher Maturity Level Step 1: Form a Maturity group (involve senior management) Step 2: Agree on business objectives Step 3: Agree on a reference model (matrix) Step 4: Formally appraise existing system Step 5:Define actionable appraisal results for moving to the next level

UNIVERSITY OF MARYLAND CENTER FOR ADVANCED TRANSPORTATION TECHNOLOGY Closing Thoughts Don’t forget the key principles: –Confidentiality –Non-attribution of data –Collaboration Preliminary efforts have demonstrated the value of the concept