© 2008-2011, Leffingwell, LLC. All rights reserved. Inspect and Adapt Workshop Toolkit Improving Release Outcomes (or any other problem) with Root Cause.

Slides:



Advertisements
Similar presentations
Facilitated by Joanne Fraser RiverSystems
Advertisements

Quality Management System Corrective and Preventive Actions Argenis Osorio – Manager, Quality Assurance 19 September 2013 FACULTY MANAGEMENT.
Title: The title should accurately describe the issue to be addressed and can never contain a proposed countermeasure. Overview Note: Remember that the.
©2014 IDBS, Confidential Statistical Process Control Workshop An Introduction to the Principles behind SPC Ilca Croufer.
The Systems Analysis Toolkit
ECE44x SCRUM Overview slides adapted from Marty Stepp
© Timothy Korson Page 1 Scrum by Dr. Korson For CPTR 209 Software Engineering Version
ISHIKAWA DIAGRAM – Tool for quality management Marit Laos IS Project Management
Chapter 8: Project Quality Management
Group Techniques John A. Cagle California State University, Fresno.
W5HH Principle As applied to Software Projects
Modern Systems Analysis and Design Third Edition
QUALITY MANAGEMENT DEFINITIONS AND CONCEPTS QUALITY MANAGEMENT TOOLS QA / QC PROCESS COMPUTERS AND PROJECT QUALITY.
Lecture 2b: Software Project Management CSCI102 - Introduction to Information Technology B ITCS905 - Fundamentals of Information Technology.
Chapter 8: Quality Management Project Quality Management
Management Quality Tools
1 CE-407 Project Planning, Management & Engg. Economics, 02 Credit Hours Spring 2015 Lecture 02 Work Breakdown Structure by Faisal Rehman Department of.
Inspect and Adapt Workshop Toolkit
Principles for Implementing Lean Manufacturing Lecture 3: Overview 1.Lean Methodology and Building Blocks 2.Kaizen Methodology 3.The 5 Whys 4.Fishbone.
Project Planning Day 2 An Old Adage: Fail to Plan... and You Plan to Fail!
Sharif University of Technology Session # 4.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
Overview of DMAIC A Systematic Framework for Problem Solving
Strategic Planning and Goal Setting: Overview In this lesson you’ll learn about the: – Importance of Strategic Planning and Goal Setting – Factors that.
OSSE School Improvement Data Workshop Workshop #4 June 30, 2015 Office of the State Superintendent of Education.
Integrated Capability Maturity Model (CMMI)
Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Logic and Problem Solving Advanced Computer Programming.
1 Software Quality Engineering CS410 Class 5 Seven Basic Quality Tools.
Striving for Quality Using continuous improvement strategies to increase program quality, implementation fidelity and durability Steve Goodman Director.
Everyone Has A Role and Responsibility
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
BIS 360 – Lecture Two Ch. 3: Managing the IS Project.
Chapter 7: A Summary of Tools Focus: This chapter outlines all the customer-driven project management tools and techniques and provides recommendations.
Project monitoring and Control
[PROJECT] FINDINGS AND RECOMMENDATIONS FEBRUARY 28,2010.
Problem Solving.
Scrum Santhosh Srinivasan. Outline What is Scrum What is Scrum Why Scrum Why Scrum Scrum Practices Scrum Practices Why Scrum works Why Scrum works Pros.
How to Complement ISO 9001:2000 with Six Sigma. ISO 9001:2000 introduces a strong focus on measurement, analysis and improvement. This section will discuss.
Lecture : 5 Problem Identification And Problem solving.
Het einde van het beroep van tester - Wat Agile, DevOps en Scrum betekenen voor het testvak -
Project Quality Management.  Define project quality management.  Describe quality planning and its relationship to project scope management.  Discuss.
Managing Chapter 01 Copyright © 2011 by the McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
/0904 © Business & Legal Reports, Inc. BLR’s Training Presentations Creative Problem-Solving.
Root Cause Analysis Analyze Kaizen Facilitation. Objectives Learn and be able to apply a fishbone diagram Utilize “Why” analysis technique to uncover.
1 Project Quality Management QA and QC Tools & Techniques Lec#10 Ghazala Amin.
© 2003 Six Sigma Academy0 The Roles of Six Sigma Champion Workshop.
IT Project Management, Third Edition Chapter 8 1 Chapter 5: Project Quality Management.
Corrective Action Training Document World Class Solutions for Global Applications Riverhawk.
Planning and Organizing Chapter 13. The Planning Function Planning for a business should stem from the company’s Business Plan – The business plan sets.
1 © Scaled Agile, Inc. and Leffingwell, LLC. All rights reserved. © Scaled Agile, Inc. and Leffingwell, LLC. Scaled Agile Framework.
Last Updated: MONTH, YEAR Team: M. W. (Team Leader)R. F. T. D.M.G. T. L.D. J. (Sponsor) Green Belt Project Objective: TITLE Green Belt Project Objective:
A Quick Review of the Components THE DMAIC CYCLE.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
5 Why analysis By its very nature, a Lean Six Sigma program requires a number of changes throughout the organization. That’s what we are trying to do right?
Helping Students Examine Their Reasoning
Lean Six Sigma DMAIC Improvement Story
Participant and Leader Training
Accident Causation.
Overview (1 of 2) Definition Use within organizations
Chapter 3: The Project Management Process Groups: A Case Study
Lean Six Sigma DMAIC Improvement Story
GETTING TO ROOT CAUSE / COUNTERMEASURES
Vision Facilitation Template
Lean Six Sigma DMAIC Improvement Story
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Quality Circle -A.M. Joshi.
Lean Methodology and Building Blocks Kaizen Methodology The 5 Whys
Modern Systems Analysis and Design Third Edition
Understanding the Problem
Fishbone Diagrams (cause and effect, or Ishikawa diagrams)
Modern Systems Analysis and Design Third Edition
Presentation transcript:

© , Leffingwell, LLC. All rights reserved. Inspect and Adapt Workshop Toolkit Improving Release Outcomes (or any other problem) with Root Cause Analysis and Corrective Action 1

© , Leffingwell, LLC. All rights reserved. Predictive vs. Empirical Process If a process is too unpredictable or too complicated for the planned, (predictive) approach, then the empirical approach (measure and adapt) is the method of choice. ̶ Ken Schwaber If a process is too unpredictable or too complicated for the planned, (predictive) approach, then the empirical approach (measure and adapt) is the method of choice. ̶ Ken Schwaber 2

© , Leffingwell, LLC. All rights reserved. Kaizen Mind 70% of improvement processes that require change fail, mainly due to a lack of sense of urgency amongst leadership. ̶ John Kotter, Harvard Business School 70% of improvement processes that require change fail, mainly due to a lack of sense of urgency amongst leadership. ̶ John Kotter, Harvard Business School There is a sense of danger. ̶ Koki Konishi, Toyota City Technical Skills Academy There is a sense of danger. ̶ Koki Konishi, Toyota City Technical Skills Academy We need “kaizen mind” an unending sense of crisis behind the company’s constant drive to improve. ̶ Jeff Sutherland – co-creator of Scrum We need “kaizen mind” an unending sense of crisis behind the company’s constant drive to improve. ̶ Jeff Sutherland – co-creator of Scrum 3

© , Leffingwell, LLC. All rights reserved. Excerpt from a board presentation from a high performing agile program in year 4 of agile adoption Kaizen Mind Example 4

© , Leffingwell, LLC. All rights reserved. Continuously solving root problems drives organizational learning – Go and See for yourself to thoroughly understand the situation – Make decisions slowly by consensus, thoroughly considering all options; implement decisions rapidly; – Become a learning organization through relentless reflection ̶ The Toyota Way Kaizen Mind and Lean Thinking Image taken from: 5

© , Leffingwell, LLC. All rights reserved. Exercise ‒ Gap Analysis  All release objectives were assigned a business value from 1-10  Review and rate your release achievements –How well did you do against your stated objectives, including a) timeliness, b) content and c) quality? –Scale: (1-10), max being max total business value  Average these across all objectives and give yourself a percent achievement score Timebox: ?  All release objectives were assigned a business value from 1-10  Review and rate your release achievements –How well did you do against your stated objectives, including a) timeliness, b) content and c) quality? –Scale: (1-10), max being max total business value  Average these across all objectives and give yourself a percent achievement score Timebox: ? 6

© , Leffingwell, LLC. All rights reserved. Problem Solving Workshop (or) 7

© , Leffingwell, LLC. All rights reserved. 1.Root Cause Analysis (Fishbone) Diagram 2.Pareto Chart 3.Corrective Action Plan Problem Solving Tools 8

© , Leffingwell, LLC. All rights reserved.  Definition: A graphic tool used to explore and display opinion about sources of variation in a process. – Also called a Cause-and-Effect, Ishikawa Diagram (who first used the technique in the 1960s.) or Fishbone Diagram.  Purpose: To arrive at a few key sources that contribute most significantly to the problem being examined. – These sources are then targeted for improvement. – Also illustrates the relationships among the wide variety of possible contributors to the effect.  The name of a basic problem of interest is entered at the right of the diagram at the end of the main "bone". Root Cause Analysis Diagram Source: wikipedia 9

© , Leffingwell, LLC. All rights reserved. Root Cause Analysis (Fishbone) Diagram Our main “bones” represent typical sources of problems in software 10

© , Leffingwell, LLC. All rights reserved.  The main possible causes of the problem (the effect) are drawn as bones off of the main backbone.  The starting bones represent all possible influences.  Brainstorming is typically done to add possible causes to the main "bones" and more specific causes to the "bones" on the main "bones".  This subdivision into ever increasing specificity continues as long as the problem areas can be further subdivided.  The practical maximum depth of this tree is usually four or five levels.  When the fishbone is complete, one has a complete picture of all the possibilities about what could be the root cause for the designated problem. Root Cause Analysis Diagram, contd. Source: wikipedia 11

© , Leffingwell, LLC. All rights reserved.  The 5 Whys is a question-asking method used to explore the cause/effect relationships underlying a particular problem. Ultimately, the goal of applying the 5 Whys method is to determine a root cause of a defect or problem.  A critical component of problem solving training integral to the Toyota Production System.  The architect of the Toyota Production System, Taiichi Ohno, (Toyota Chairman) described the 5 whys method as " by repeating why five times, the nature of the problem as well as its solution becomes clear.”  The tool has seen widespread use beyond Toyota, and is now used within Kaizen, lean manufacturing, and Six Sigma. The 5 Why’s Source: wikipedia 12

© , Leffingwell, LLC. All rights reserved.  Questioning could be taken further to a sixth, seventh, or greater level.  This would be legitimate, as the "five" in 5 Whys is not gospel; rather, it is postulated that five iterations of asking why is generally sufficient to get to a root cause.  The key is to avoid assumptions and logic traps  Instead trace the chain of causality in direct increments from the effect to a root cause that still has some connection to the problem. Example ‒ The 5 Why’s My car will not start. (the problem)  Why? – The battery is dead. (first why)  Why? – The alternator is not functioning. (second why)  Why? – The alternator belt has broken. (third why)  Why? – The alternator belt was well beyond its useful service life and has never been replaced. (fourth why)  Why? – I have not been maintaining my car according to the recommended service schedule. (fifth why, root cause) My car will not start. (the problem)  Why? – The battery is dead. (first why)  Why? – The alternator is not functioning. (second why)  Why? – The alternator belt has broken. (third why)  Why? – The alternator belt was well beyond its useful service life and has never been replaced. (fourth why)  Why? – I have not been maintaining my car according to the recommended service schedule. (fifth why, root cause) Source: wikipedia 13

© , Leffingwell, LLC. All rights reserved. Root Cause Analysis (Fishbone) Diagram Cause 1 Cause of cause 1 Cause of cause of cause 1 Cause of cause of cause of cause 1 14

© , Leffingwell, LLC. All rights reserved. Exercise- Root Cause Analysis  Succinctly state the problem you are addressing  Create a fishbone diagram for your problem statement  Brainstorm potential causes of the problem, and place them on the chart  For each cause identified, use the 5 whys technique to get to a potential root cause  Prepare to present your result Timebox: ? minutes  Succinctly state the problem you are addressing  Create a fishbone diagram for your problem statement  Brainstorm potential causes of the problem, and place them on the chart  For each cause identified, use the 5 whys technique to get to a potential root cause  Prepare to present your result Timebox: ? minutes 15

© , Leffingwell, LLC. All rights reserved. 1.Root Cause Analysis (Fishbone) Diagram 2.Pareto Chart 3.Corrective Action Plan Problem Solving Tools 16

© , Leffingwell, LLC. All rights reserved.  Pareto analysis is a statistical technique in decision making that is used for selection of a limited number of tasks that produce significant overall effect.  It uses the Pareto principle – 20% of the work can generate 80% of the advantage of doing the entire job.  In terms of quality improvement, a large majority of problems (80%) are produced by a few key causes (20%). Pareto Analysis 17

© , Leffingwell, LLC. All rights reserved.  Useful where many possible courses of action are competing for your attention.  The problem-solver estimates the benefit delivered by each action, then selects a number of the most effective actions that deliver a total benefit reasonably close to the maximal possible one.  Helps stimulate thinking and organize thoughts. Pareto Analysis, contd. Source: wikipedia 18

© , Leffingwell, LLC. All rights reserved. Prioritize Root Causes Cause 1 Cause of cause 1 Cause of cause of cause 1 Cause of cause of cause of cause 1 Cause of cause 1 19

© , Leffingwell, LLC. All rights reserved. Pareto Analysis 20

© , Leffingwell, LLC. All rights reserved. Exercise- Pareto Analysis  Use a cumulative voting technique to do a Pareto analysis of each identified root cause  Each team member gets 10 votes  Place your votes on as few or as many (limit 5 votes per item) root causes as appropriate  Refactor, re-aggregate causes as appropriate  Use that data to create a big visible histogram chart  Prepare to present your result Timebox: ? minutes  Use a cumulative voting technique to do a Pareto analysis of each identified root cause  Each team member gets 10 votes  Place your votes on as few or as many (limit 5 votes per item) root causes as appropriate  Refactor, re-aggregate causes as appropriate  Use that data to create a big visible histogram chart  Prepare to present your result Timebox: ? minutes 21

Group Review of Root Cause Analysis and Pareto Charts Timebox: ?

© , Leffingwell, LLC. All rights reserved. 1.Root Cause Analysis (Fishbone) Diagram 2.Pareto Chart 3.Corrective Action Plan Problem Solving Tools 23

© , Leffingwell, LLC. All rights reserved. After we determine we have a problem, what’s next? a.Ignore it - the problem may go away b.Blame it on another team c.Blame it on the business owner d.Blame it on another program e.Create a Corrective Action Plan Answer: e.Create a Corrective Action Plan Houston, we have a problem. Image taken from: 24

© , Leffingwell, LLC. All rights reserved. What is a Corrective Action Plan anyway?  C orrective – A different course of action  A ction – Active steps we can realistically accomplish  P lan – Organized, purposeful, accountable, measurable Corrective Action Plan 25

© , Leffingwell, LLC. All rights reserved. 1.State the new problem (the selected root cause) succinctly 2.Brainstorm a solution. Divide into discrete activities. 3.Establish accountability 4.Specify measurable results 5.Set achievable deadlines 6.Monitor progress Effective Corrective Action Plans 26

© , Leffingwell, LLC. All rights reserved. 1.State the new problem succinctly – Pick one specific root cause, i.e. the top root causes that you identified in your analysis – Restate that as the new problem Corrective Action Plan Components 27

© , Leffingwell, LLC. All rights reserved. 2.Brainstorm a solution – Brainstorm prospective solutions with the team – Cumulative vote on suggested next steps Corrective Action Plan Components How do you eat an elephant? One bite at a time. 28

© , Leffingwell, LLC. All rights reserved. 3.Establish accountability – Identify the stories you’ll need to effect the solution – Take responsibility for stories – Prepare to put the stories on your release plan – Escalate those impediments that are outside of your control Corrective Action Plan Components 29

© , Leffingwell, LLC. All rights reserved. 4.Specify measurable results – What measures can we use to track progress? Corrective Action Plan Components 30

© , Leffingwell, LLC. All rights reserved. 5.Set achievable deadlines – Not to fast – Not to slow – Not TBD Corrective Action Plan Components Action 1 3/16/20011 Action 2 4/11/2011 Action 3 5/01/

© , Leffingwell, LLC. All rights reserved. 6.Monitor Progress – How will we track our action steps? – How will we know when this is no longer the biggest problem? – Define what “done” means for the CAP Corrective Action Plan Components 32

© , Leffingwell, LLC. All rights reserved. 1.State the problem succinctly 2.Brainstorm a solution. Divide into discrete parts. 3.Establish accountability 4.Specify measurable results 5.Set achievable deadlines 6.Monitor progress Effective Corrective Action Plans 33

© , Leffingwell, LLC. All rights reserved. Exercise- Corrective Action Plans  Pick the top root cause on your Pareto chart  Build a corrective action plan  Prepare to present your results Timebox: ? minutes  Pick the top root cause on your Pareto chart  Build a corrective action plan  Prepare to present your results Timebox: ? minutes 34

Group Review of Corrective Action Plans Timebox: ? minutes 1 …… 2 ….. 3 ….. 4 ….. 5 ….. 6 ….. 1 …… 2 ….. 3 ….. 4 ….. 5 ….. 6 …..