Work break down structure (WBS)

From apppm
(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
 
'''Abstract'''
 
'''Abstract'''
  
Taking on a project can be a confusing task for even the most experienced project manager. In the start-up phase of a project the goal is defined, and it is expected to estimate a budged and a timeframe of the project. Often several things will happen doing the elapse of the project, that in the end will lead up to the final reaching of the project goal or scope. To create a better view of the project it can be helpful to part the project and the goal onto sub-goals or sub-events – to break down the project. By estimating the timeframe and budget of the sub-events or sub-goals, the timeframe of the project can be estimated as well as the budged. This method is referred to as Work Breakdown Structure (WBS), as it is a way to structure the project by breaking it down. This is the addressed subject of this article.
 
  
  
The article consists of the following sections:
+
== '''Introduction''' ==
  
- What is Work Breakdown Structure?
+
[[File:Problem.png||150px|Root cause illustration| frameless|thumb]]
  
- Why is Work Breakdown Structure an important tool in project management?
 
  
- How to implement Work Breakdown Structure?
+
== '''Process of Root cause Analysis''' ==
  
- What are the limitations of Work Breakdown Structure?
+
[[File:RCA2.png|700px||Process of Root cause Analysis]]
  
  
In each section, the question will be answered.
 
  
This article is a part of the final deliverable in the course 42433 Advanced engineering project, program and portfolio management taught in the spring of 2022 on DTU. It is written by a student for other students taking the same course and with an academic background corresponding to a Bachelor's degree.
+
 
  
  
'''What is Work Breakdown Structure?'''
+
== '''Root cause analysis tools''' ==
  
A work breakdown structure is defined by the ISO Standard 21502 as "decomposition of the defined scope of a project or programme into progressively lower levels consisting of elements of work" [1]. In other words: when the scope of a project or programme is defined in the very beginning of this project- or programmes lifespan, it might be favorable to look at the work that is needed in order to fulfill the scope and deliver on the project/programme.  
+
==='''Five Why analysis '''===
 +
[[File:RCA3.png|400px|thumb|Five Why analysis]]
  
  
When planning the project, an estimation of time or deadline is needed as well as a budget including every expense throughout the project. This expense covers resources, salary and administrative fee as well as setting a realistic amount of money aside for unforeseen occurrences. The process of estimating time and budget is essential in order to evaluate whether the scope of a project is achievable as this two TING is the backbone and key factors of a project. This is the factors the important stakeholders and investors of a project will evaluate the project on. If the important stakeholders and investors does not find that the scope of a project equalize the time needed and the budget estimated, the project will in all probability not been effected.
+
'''Steps to perform five why analysis'''
  
A Work Breakdown Structure is often visualized as a schedule or a table. The schedules or tables can have different structures. For instance, the schedules can be formed as a tree structure or a waterfall model. The tables can be made as hierarchies or outlines. Common to all this different schedules and tables is what they should include; [2]
+
# Take a particular problem
 +
# Question “WHY” it occurred and note down the answer.
 +
# If that is not the exact root cause then you can ask another “WHY” question to that answer .Note down the new answer.
 +
# Follow these steps till you identify the root cause. It can take any number of “WHY” to reach the cause. [https://www.slideshare.net/ExerciseLeanLLC/5-why-training-slides-oct-14-2009 [3]]
  
  
- A description of the work that needs to be done to achieve the sub-goal. The work needed to achieve the sub-goals that occurs when breaking down a project into smaller projects is seen as smaller work packages or works.
+
'''Example '''
  
- The product produced by the work done in a work package. It is important to match the expectations of the work between the project manager, the stakeholders, and the person reasonable for the work.
 
  
- The cost of the work done. Both in terms of resources needed, salaries for the workers and other payments.
 
  
- Who is responsible for the work and thereby responsible for the quality of the delivered product.
+
==='''Fishbone diagram'''===
  
 +
 +
'''Steps to analysis fishbone diagram'''
  
 +
# Determine and state the effect or the problem that has to be analyzed.
 +
# Determine the primary causes or categories of the effect.Methods, machines, people, materials, environment or measurements are popular primary causes.
 +
# Under each primary categories identify the other sub causes on it. Sub causes can be identified through various methods like five why analysis or 4Ps method (Policies, Procedures, People and Plant) 
 +
# This procedure of analyzing each cause is repeated until the problem's root causes are found. The team then analyzes the fishbone diagram until a conclusion and future steps are reached.[https://whatis.techtarget.com/definition/fishbone-diagram#:~:text=A%20fishbone%20diagram%20is%20a,type%20of%20mind%20map%20template. [5]]
  
'''Why is Work Breakdown Structure an important tool in project management?'''
 
  
 +
'''Example'''
  
The Work Breakdown Structure is an important tool for a project manager when estimating a time schedule and budget of a project as already stated. When breaking down the work into smaller projects or work packages an overview of the project is created. It is giving the project manager the ability to analyses the needs of a work package or a sub-goal of the project in terms of workload, resources needed, risks linked to the specific work and preparations needed to fulfill a certain work. The work packages or smaller projects can be scheduled in a model such as a schedule or table. This is in fact what makes the Work Breakdown Structure a great tool, as an overview of the hole project is secured and estimated. Also, this way of scheduling the work in smaller work packages makes it easier for the project manager to watch out for delays on curtain areas of the project, inform the different stakeholders and investors and handle the work-, risk- and resources-flow as the project proceeds.
+
[[File:RCA4.png|400px||Example of Fish Bone Diagram. Image recreated from Wall street mojo]]
  
 +
==='''Scatter chart'''===
  
'''How to implement Work Breakdown Structure'''
 
  
 +
Scatter chart represents the relationship between dependent and independent variables for the root cause. The dependent and independent variables data is represented by numerical value. [https://asq.org/quality-press/display-item?item=H1460 [7]]
  
The Work Breakdown Structure should be implemented in the planning of the execution of a project. To what extent the work should be broken down and the level of details planed in every work package or sub-project depends on the size of the project. The bigger the project is, the more risks will occur. The more risks in the project, the more planning is needed in order to fulfill the project scope to a satisfactory extend. When something goes wrong, it must be detected as quickly as possible and dealt with. This is easier if the work and project is scheduled to a proper degree of details for the size of the project.
+
'''Steps to create a scatter plot'''
  
 +
# Choose two variables to analyze (Pair of dependent and independent variables).
 +
# Measure the equivalent value of the dependent variable for each value of the independent variable.
 +
# On the chart, plot the numbers from each data pair.
 +
# On the horizontal axis, place the independent or expected cause variable, and on the vertical axis, place the dependent or intended effect variable.
 +
# In the chart, plot and examine the acquired data values. [https://asq.org/quality-press/display-item?item=H1460 [7]]
  
How to implement the Work Breakdown Structure depends on the needs of the project manager. One way to implement this is by making a tree structures schedule as seen in figure 1. The project scope is shown on top of the schedule. Underneath the scope is broken down into smaller works, that is needed to fulfill the overall scope of the project. These smaller works are again broken down into smaller works and analyzed for cost and work. Then the small works are analyzed the total cost of the project can be summed.
+
'''Example '''
  
[I'm sorry, I'm not able to upload the picture yet. The picture is available on the website.]
+
[[File:RCA7.PNG|500px|Thumb|Example of scatter plot]]
  
'''''Figure 1:''' Tree structured Work Breakdown Structure Schedule. This shows the scope of the project is broken down into smaller scopes and how these smaller scopes are broken down into even smaller scopes. [3]''
+
[[File:RCA5.png|400px|thumb|Gantt charts]]
  
 +
==='''Gantt charts '''===
  
Another way to implement Work Breakdown structure is to use a Gantt Chart. In order to do so, the project must of course be divided into smaller projects or sub-goals. These tasks are then organized in area of work, contact person and firm. It is also important to state who is responsible for the sub-goal to be finished to the expected time and at the agreed quality.  Then this is examined, it is identified if any of the works or sub-goals or deliverables are overlapping and which of the works that are depending on each other. These works must be done in a certain order. After this identification, the time estimated for each work is determined and the works are ready to be scheduled.
 
  
 +
'''Steps to create a Gantt chart'''
  
This can be done in two ways; Firstly, it can be done from the starting point of the project. The works are then scheduled from a date and forward until the estimated time for the given work is up. This step needs to take in to account that holidays may occur in the timespan of the project. When a deadline is set for one work, the next work dependent on the first work can be scheduled and so on.  
+
# Make a list of all tasks and activities.
The second way to do the time-scheduling is to begin from the deadline of the project and do the scheduling backwards. This is a good way to optimate the timespan of a project, because this provides the project manager with the fasted time schedule in a natural way. An example of a Gantt Chart can be seen in figure 2.[4]  
+
# Calculate the latest finishing date and the earliest start date for each activity, as well as the duration and any interdependence on other activities.
+
# Arrange the tasks in a blank Gantt chart, with the timeline indicating the project's overall duration.
 +
# Draw bars that match to the duration of the activities to schedule them.
 +
# Use diamonds to represent plan milestones. [https://asq.org/quality-press/display-item?item=H1460 [7]]
 +
 
 +
 
 +
==='''Flowcharts'''===
 +
 
 +
Flowchart represent the process flow which was used through a simplified representation. [https://asq.org/quality-press/display-item?item=H1460 [7]]
 +
 
 +
'''Steps to create flowcharts'''
 +
 
 +
# Gather all of the team members in the process in a meeting room with a whiteboard and plenty of colorful sticky note
 +
# Define the process's beginning and end points, as well as the borderline between other parallel processes.
 +
# List the primary actions or tasks that were completed during the procedure 
 +
# Use different colored adhesive notes to represent actions, items, documents, and other process elements.
 +
# Draw a diagram of the process by shifting the notes about on the board until they reflect the most accurate representation of the process. [https://asq.org/quality-press/display-item?item=H1460 [7]]
 +
 
 +
'''Symbols '''
 +
 
 +
[[File:RCA6.png|300px||Example of Fish Bone Diagram. Image recreated from Wall street mojo]]
 +
 
 +
==='''Pareto analysis'''===
 +
 
 +
Png over a considerable amount of time. It also supports in handling multiple organizational challenges. [https://www.geeksforgeeks.org/advantages-and-disadvantages-of-pareto-chart/ [9]]
 +
 
 +
'''Steps to perform pareto analysis'''
 +
 
 +
# Collect the number defect occurrence.
 +
# Sort that data from highest to lowest based on the number of occurrences.
 +
# Calculate the cumulative percentage.
 +
# Plot a bar graph where X-axis is the defect causes and Y-axis is the cumulative percentage.
 +
# Plot another line graph in that bar graph for the cumulative percentage.
 +
# To separate the important root cause draw a line from Y-Axis at 80% to the line graph and then drop to the X-Axis. The causes that are left side to the line are the 80% defect driving factors. [https://www.slideshare.net/himanshuhora/pareto-analysis-28873221 [8]]
 +
 
 +
'''Example'''
 +
 
 +
 
 +
[[File:RCA10.PNG|500px||Example of scatter plot]]
 +
 
 +
==='''Histogram'''===
 +
 
 +
 
 +
'''Steps to create a histogram'''
 +
 
 +
# Split the obtained data into an appropriate number of categories if it hasn't already been done.
 +
# Make a bar chart with area for the number of data categories on the X axis and the maximum data point on the vertical axis.
 +
# For each data point, make a bar with a height that matches to the recorded data.
 +
# Look for trends in the histogram results. Reevaluate the number of categories and the data division into the categories if your result with a graph with very few bars, all bars almost equal, or a comb-like design. [https://asq.org/quality-press/display-item?item=H1460 [7]]
 +
 
 +
'''Example '''
 +
 
 +
 
 +
[[File:RCA8.png|300px|Thumb|Example of Histogram]]
 +
 
 +
==='''Brainstorming'''===
 +
 
 +
The goal of brainstorming is to generate as much thoughts as possible which are probable factors for the event under study, even wild ideas. [https://asq.org/quality-press/display-item?item=H1460 [7]]
 +
 
 +
'''Steps to do brainstorming session'''
 +
 
 +
#Get a whiteboard or a flip chart to write down your ideas.
 +
#Encourage everyone to engage by opening the stage to attendees for the intent of launching ideas.
 +
#Make a list of all the ideas you've come up with, using the same language as the original proposal.
 +
#During the session, don't really debate, criticize, or evaluate ideas.
 +
#Allow for a period of stagnation in the flow of thoughts because it will generally take up again; end the session when very few fresh ideas come.
 +
#Sort ideas into categories of decreasing importance to review them. [https://asq.org/quality-press/display-item?item=H1460 [7]]
 +
 
 +
==='''Impact effort matrix '''===
 +
 
 +
It's a method for determining which of many possible solutions should be executed. It shows which ideas look to be the simplest to implement and which have the greatest impact. [https://asq.org/quality-press/display-item?item=H1460 [7]]
 +
 
 +
'''Steps to create the Impact effort matrix'''
 +
 
 +
# Lookup past discussions' possible solutions.
 +
# Create a blank diagram, dividing it into four quadrants, with the effort necessary to implement the solution on the x axis and the impact of the approach on the y axis.
 +
# Evaluate effort and impact, and then position each option in the graph based on your findings. To identify each reason, use figures, shades, or titles.
 +
# The options in the upper left quadrant will provide the best value and should be prioritized.  [https://asq.org/quality-press/display-item?item=H1460 [7]]
 +
 
 +
'''Example'''
 +
 
 +
[[File:RCA9.png|400px|Thumb|Example of Histogram]]
 +
 
 +
=='''Significance of root cause analysis ''' ==
 +
 
 +
# For a long team perspective, Root Cause Analysis is typically helpful in discovering and identifying defects as well as their fundamental causes and remedy can be found, reducing the risk of recurrence .
 +
# It helps with the development of a logical approach to solving issues.
 +
# After determining the primary source of the problem, one will attempt to determine and identify important problem-solving methods using information currently available. Once the fault has been identified, we can decide what adjustments are necessary to enhance quality.
 +
# We can identify existing and future needs for organizational and system development.
 +
# It also aids in the development of repeatable and acceptable step-by-step procedures, where one process may corroborate the outcome of another. [https://www.geeksforgeeks.org/advantages-and-disadvantages-of-root-cause-analysis/#:~:text=RCA%20usually%20helps%20in%20determining,logical%20approach%20to%20solving%20problems. [10]]
 +
 
 +
== '''Limitations of Root cause Analysis''' ==
 +
 
 +
# The primary issue with Root cause analysis is that it only assumes, or focuses on, one root cause of failure. However, in fact, the issue may be more complicated. There might be several underlying causes for a fault. As a result, one must concentrate on all areas of the fault and consider the underlying causes of the issue.
 +
# Few root cause analysis tools like fishbone diagram or five why analysis doesn’t use data or other statistical tools, so without data the outcome won’t be more reliable
 +
# The brainstorming process might create both irrelevant and relevant underlying factors, causing confusion and wasting time.
 +
# Multiple components in complex diagrams might result in a confused mess that is difficult to show in a fishbone chart.  
 +
#Root cause analysis alone would not give any results, it has to be used as part of a bigger problem-solving effort aimed at improving quality.[https://www.geeksforgeeks.org/advantages-and-disadvantages-of-root-cause-analysis/#:~:text=RCA%20usually%20helps%20in%20determining,logical%20approach%20to%20solving%20problems. [10]]
 +
 
 +
== '''Thinks to know''' ==
 +
#The information you gather will determine the quality of your root cause analysis.
 +
#Before you can know why something happened, you must first know what really happened.
 +
#Sometime lack of knowledge of tools can be a obstruct of root cause analysis.
 +
#Even when the main cause is identified, people frequently fail to recognize good corrective steps.
 +
#All investigations do not have to be identical (but some processes can be ignored).[https://www.scribd.com/presentation/426356451/Root-Cause-Presentation-Tampa. [11]]
 +
 
 +
== '''Annotated Bibliography''' ==
 +
 
 +
'''1.Root Cause Analysis Handbook: A Guide to Efficient and Effective Incident Management, 3rd Edition''' by ABS Consulting , Lee N Vanden Heuvel , Donald K Lorenzo , Walter E Hanson
 +
 
 +
 
 +
'''2.The ASQ Pocket Guide To Root Cause Analysis''', Bjørn Andersen, Tom Natland Fagerhaug
  
[I'm sorry, I'm not able to upload the picture yet. The picture is available on the website.]
 
  
'''''Figure 2:''' Gantt Chart. It is seen that the chart provides a timeline for the project. This is a great way to get an overview of the works that needs to be done in a specific order, or at the same time. [5]''
 
  
 +
'''3.Root Cause Analysis: A Step-By-Step Guide to Using the Right Tool at the Right Time 1st Edition''',by Matthew A. Barsalou
  
Common to the two ways to schedule a Work Breakdown Structure is that both of them brings an overview of the project.
 
  
 +
== '''References''' ==
  
'''What are the limitations of Work Breakdown Structure?'''
 
  
 +
[[https://asq.org/quality-resources/root-cause-analysis 1]]WHAT IS ROOT CAUSE ANALYSIS (RCA)? By ASQ
  
As a project manager it is important to know what you don’t know - and to expect the unexpected. A Work Breakdown Structure of a project might give a great overview of a project but as much as this scheduling of the smaller work packages provides a sound estimation of the project, everything can still go wrong. The overview provides a good opportunity to do risk analysis on the project in details. It is also a good way to keep track of the time spend on the project and the different work packages. On that note it is easy to keep track of deviations from the schedule early in the process and act on these to provide some kind of damage control.  
+
[https://www.mindtools.com/pages/article/newTMC_5W.htm#:~:text=Origins%20of%20the%205%20Whys,it%20to%20solve%20problems%20today. [2]] 5 Whys by mindtools
  
 +
[https://www.slideshare.net/ExerciseLeanLLC/5-why-training-slides-oct-14-2009 [3]] 5 Why Training Slides by slide share
  
To summarize: The Work Breakdown Structure is a good way to make a sound estimation of a project in terms of timespan and budged. But as a rule of thumb, something will deviate form the project plan at some point doing a project. A good Work Breakdown Structure schedule will provide an overview for the project manager, who in case of deviation from the schedule can act on them at an early state and reduce any harm to either the product delivered in the end, the time schedule, or the budget. As so, a Work Breakdown Structure can be seen as a work in progress and not a finished product.
+
[https://scholar.cu.edu.eg/?q=hmostafa/files/fishbone_diagram.pdf [4]] Fishbone Diagram by Cairo University
  
 +
[https://whatis.techtarget.com/definition/fishbone-diagram#:~:text=A%20fishbone%20diagram%20is%20a,type%20of%20mind%20map%20template. [5]] Fishbone Diagram by Whatis
  
'''Links/ref'''
+
[https://www.wallstreetmojo.com/fishbone-diagram/ [6]] Examples of Fishbone by wall street mojo
  
[1] Ref: ISO Standard 21502, Project Management: ISO 21502 (2021 Edition)
+
[https://asq.org/quality-press/display-item?item=H1460 [7]] The ASQ Pocket Guide To Root Cause Analysis, Bjørn Andersen, Tom Natland Fagerhaug
  
[2] Ref: Course notes, Author: DTU ProjectLab, 42430 - Week 2 - Part 3 - Complexity slides, Link: https://learn.inside.dtu.dk/d2l/le/content/102752/viewContent/401279/View
+
[https://www.slideshare.net/himanshuhora/pareto-analysis-28873221 [8]] Pareto analysis by slide share
  
[3] Figure 1: Picture of tree schedule, Author: WorkBreakdownStructure.com, Website: https://www.workbreakdownstructure.com/
+
[https://www.geeksforgeeks.org/advantages-and-disadvantages-of-pareto-chart/ [9]] Advantages and Disadvantages of Pareto Chart – geeks for geeks
  
[4] Ref: ADEACA, What is a work breakdown structure?, Author: Matt Mong, Website: https://www.adeaca.com/blog/faq-items/what-is-a-work-breakdown-structure/
+
[https://www.geeksforgeeks.org/advantages-and-disadvantages-of-root-cause-analysis/#:~:text=RCA%20usually%20helps%20in%20determining,logical%20approach%20to%20solving%20problems. [10]] Advantages and Disadvantages of Root Cause Analysis - geeks for geeks
  
[5] Figure 2: Picture of Gantt Chart, Author: Roger Duke, Website: https://www.gantt.com/
+
[https://www.scribd.com/presentation/426356451/Root-Cause-Presentation-Tampa. [11]]Root Cause Presentation Tampa

Revision as of 01:35, 19 March 2022

Abstract


Contents

Introduction

Root cause illustration


Process of Root cause Analysis

Process of Root cause Analysis




Root cause analysis tools

Five Why analysis

Five Why analysis


Steps to perform five why analysis

  1. Take a particular problem
  2. Question “WHY” it occurred and note down the answer.
  3. If that is not the exact root cause then you can ask another “WHY” question to that answer .Note down the new answer.
  4. Follow these steps till you identify the root cause. It can take any number of “WHY” to reach the cause. [3]


Example


Fishbone diagram

Steps to analysis fishbone diagram

  1. Determine and state the effect or the problem that has to be analyzed.
  2. Determine the primary causes or categories of the effect.Methods, machines, people, materials, environment or measurements are popular primary causes.
  3. Under each primary categories identify the other sub causes on it. Sub causes can be identified through various methods like five why analysis or 4Ps method (Policies, Procedures, People and Plant) 
  4. This procedure of analyzing each cause is repeated until the problem's root causes are found. The team then analyzes the fishbone diagram until a conclusion and future steps are reached.[5]


Example

Example of Fish Bone Diagram. Image recreated from Wall street mojo

Scatter chart

Scatter chart represents the relationship between dependent and independent variables for the root cause. The dependent and independent variables data is represented by numerical value. [7]

Steps to create a scatter plot

  1. Choose two variables to analyze (Pair of dependent and independent variables).
  2. Measure the equivalent value of the dependent variable for each value of the independent variable.
  3. On the chart, plot the numbers from each data pair.
  4. On the horizontal axis, place the independent or expected cause variable, and on the vertical axis, place the dependent or intended effect variable.
  5. In the chart, plot and examine the acquired data values. [7]

Example

Example of scatter plot

Gantt charts

Gantt charts

Steps to create a Gantt chart

  1. Make a list of all tasks and activities.
  2. Calculate the latest finishing date and the earliest start date for each activity, as well as the duration and any interdependence on other activities.
  3. Arrange the tasks in a blank Gantt chart, with the timeline indicating the project's overall duration.
  4. Draw bars that match to the duration of the activities to schedule them.
  5. Use diamonds to represent plan milestones. [7]


Flowcharts

Flowchart represent the process flow which was used through a simplified representation. [7]

Steps to create flowcharts

  1. Gather all of the team members in the process in a meeting room with a whiteboard and plenty of colorful sticky note
  2. Define the process's beginning and end points, as well as the borderline between other parallel processes.
  3. List the primary actions or tasks that were completed during the procedure 
  4. Use different colored adhesive notes to represent actions, items, documents, and other process elements.
  5. Draw a diagram of the process by shifting the notes about on the board until they reflect the most accurate representation of the process. [7]

Symbols

Example of Fish Bone Diagram. Image recreated from Wall street mojo

Pareto analysis

Png over a considerable amount of time. It also supports in handling multiple organizational challenges. [9]

Steps to perform pareto analysis

  1. Collect the number defect occurrence.
  2. Sort that data from highest to lowest based on the number of occurrences.
  3. Calculate the cumulative percentage.
  4. Plot a bar graph where X-axis is the defect causes and Y-axis is the cumulative percentage.
  5. Plot another line graph in that bar graph for the cumulative percentage.
  6. To separate the important root cause draw a line from Y-Axis at 80% to the line graph and then drop to the X-Axis. The causes that are left side to the line are the 80% defect driving factors. [8]

Example


Example of scatter plot

Histogram

Steps to create a histogram

  1. Split the obtained data into an appropriate number of categories if it hasn't already been done.
  2. Make a bar chart with area for the number of data categories on the X axis and the maximum data point on the vertical axis.
  3. For each data point, make a bar with a height that matches to the recorded data.
  4. Look for trends in the histogram results. Reevaluate the number of categories and the data division into the categories if your result with a graph with very few bars, all bars almost equal, or a comb-like design. [7]

Example


Example of Histogram

Brainstorming

The goal of brainstorming is to generate as much thoughts as possible which are probable factors for the event under study, even wild ideas. [7]

Steps to do brainstorming session

  1. Get a whiteboard or a flip chart to write down your ideas.
  2. Encourage everyone to engage by opening the stage to attendees for the intent of launching ideas.
  3. Make a list of all the ideas you've come up with, using the same language as the original proposal.
  4. During the session, don't really debate, criticize, or evaluate ideas.
  5. Allow for a period of stagnation in the flow of thoughts because it will generally take up again; end the session when very few fresh ideas come.
  6. Sort ideas into categories of decreasing importance to review them. [7]

Impact effort matrix

It's a method for determining which of many possible solutions should be executed. It shows which ideas look to be the simplest to implement and which have the greatest impact. [7]

Steps to create the Impact effort matrix

  1. Lookup past discussions' possible solutions.
  2. Create a blank diagram, dividing it into four quadrants, with the effort necessary to implement the solution on the x axis and the impact of the approach on the y axis.
  3. Evaluate effort and impact, and then position each option in the graph based on your findings. To identify each reason, use figures, shades, or titles.
  4. The options in the upper left quadrant will provide the best value and should be prioritized. [7]

Example

Example of Histogram

Significance of root cause analysis

  1. For a long team perspective, Root Cause Analysis is typically helpful in discovering and identifying defects as well as their fundamental causes and remedy can be found, reducing the risk of recurrence .
  2. It helps with the development of a logical approach to solving issues.
  3. After determining the primary source of the problem, one will attempt to determine and identify important problem-solving methods using information currently available. Once the fault has been identified, we can decide what adjustments are necessary to enhance quality.
  4. We can identify existing and future needs for organizational and system development.
  5. It also aids in the development of repeatable and acceptable step-by-step procedures, where one process may corroborate the outcome of another. [10]

Limitations of Root cause Analysis

  1. The primary issue with Root cause analysis is that it only assumes, or focuses on, one root cause of failure. However, in fact, the issue may be more complicated. There might be several underlying causes for a fault. As a result, one must concentrate on all areas of the fault and consider the underlying causes of the issue.
  2. Few root cause analysis tools like fishbone diagram or five why analysis doesn’t use data or other statistical tools, so without data the outcome won’t be more reliable
  3. The brainstorming process might create both irrelevant and relevant underlying factors, causing confusion and wasting time.
  4. Multiple components in complex diagrams might result in a confused mess that is difficult to show in a fishbone chart.
  5. Root cause analysis alone would not give any results, it has to be used as part of a bigger problem-solving effort aimed at improving quality.[10]

Thinks to know

  1. The information you gather will determine the quality of your root cause analysis.
  2. Before you can know why something happened, you must first know what really happened.
  3. Sometime lack of knowledge of tools can be a obstruct of root cause analysis.
  4. Even when the main cause is identified, people frequently fail to recognize good corrective steps.
  5. All investigations do not have to be identical (but some processes can be ignored).[11]

Annotated Bibliography

1.Root Cause Analysis Handbook: A Guide to Efficient and Effective Incident Management, 3rd Edition by ABS Consulting , Lee N Vanden Heuvel , Donald K Lorenzo , Walter E Hanson


2.The ASQ Pocket Guide To Root Cause Analysis, Bjørn Andersen, Tom Natland Fagerhaug


3.Root Cause Analysis: A Step-By-Step Guide to Using the Right Tool at the Right Time 1st Edition,by Matthew A. Barsalou


References

[1]WHAT IS ROOT CAUSE ANALYSIS (RCA)? By ASQ

[2] 5 Whys by mindtools

[3] 5 Why Training Slides by slide share

[4] Fishbone Diagram by Cairo University

[5] Fishbone Diagram by Whatis

[6] Examples of Fishbone by wall street mojo

[7] The ASQ Pocket Guide To Root Cause Analysis, Bjørn Andersen, Tom Natland Fagerhaug

[8] Pareto analysis by slide share

[9] Advantages and Disadvantages of Pareto Chart – geeks for geeks

[10] Advantages and Disadvantages of Root Cause Analysis - geeks for geeks

[11]Root Cause Presentation Tampa

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox