background preloader

5 Whys (Causes de dysfonctionnement)

5 Whys (Causes de dysfonctionnement)
The 5 Whys is an iterative question-asking technique used to explore the cause-and-effect relationships underlying a particular problem.[1] The primary goal of the technique is to determine the root cause of a defect or problem. (The "5" in the name derives from an empirical observation on the number of iterations typically required to resolve the problem.) Example[edit] The vehicle will not start. (the problem)Why? - The battery is dead. The questioning for this example could be taken further to a sixth, seventh, or higher level, but five iterations of asking why is generally sufficient to get to a root cause. It is interesting to note that the last answer points to a process. A key phrase to keep in mind in any 5 Why exercise is "people do not fail, processes do". History[edit] The technique was originally developed by Sakichi Toyoda and was used within the Toyota Motor Corporation during the evolution of its manufacturing methodologies. Techniques[edit] Criticism[edit] See also[edit]

http://en.wikipedia.org/wiki/5_Whys

Related:  Scope managementProject ManagementProblem Analysis & Problem Solvingshaneimm

How to create and use predictive project scheduling « Fear No Pr I was a bit naïve when I accepted the challenge to manage my first software project. I didn’t quite understand the “wink-wink, nod-nod” I got from the software veterans when I began asking for their input to the project task detail and schedule. Now many years and many projects later, I understand their skepticism. They had too often been victims of schedules that were not worth the paper or time used to develop them. They had seen schedule chicken played by professionals and had worked countless hours of overtime trying to meet unrealistic, unattainable deadlines. However, I continue to believe whole-heartedly in the value of predictive schedules.

5-whys Analysis using an Excel Spreadsheet Table Find out how to visualize your five-whys analysis by putting it into a spreadsheet, including a downloadable five why template and tutorial. Part 2 of a four part series on 5-whys. By Karn G. Bulsuk Why–because analysis Why–because analysis (WBA) is a method for accident analysis.[1] It is independent of application domain and has been used to analyse, among others, aviation-, railway-, marine-, and computer-related accidents and incidents. It is mainly used as an after the fact (or a posteriori) analysis method. WBA strives to ensure objectivity, falsifiability and reproducibility of results. WBA in detail[edit]

Five Ws The Five Ws, Five Ws and one H, or the Six Ws are questions whose answers are considered basic in information-gathering. They are often mentioned in journalism (cf. news style), research, and police investigations.[1] They constitute a formula for getting the complete story on a subject.[2] According to the principle of the Five Ws, a report can only be considered complete if it answers these questions starting with an interrogative word:[3] Who did that?

Why Software Projects Fail « Fear No Project – A Project Managem While there is great debate over why software projects fail, it is commonly believed that many— if not most—software projects fail in some way. Because of the fear of probable failure, many organizations continue to run their organization with antiquated or outdated software and processes rather than attempt a new software implementation. As it turns out, Gartner, Inc. a leading information technology research and advisory company assessed the frequency of software project failure rates last year. Although not quite as high as 50%, the failure rate is significant.

An Introduction to 5-why Learn how to find root causes of a problem by using 5-why analysis, so you can fix the issues where it matters most. First in a series of four articles explaining this powerful tool. By Karn G. Bulsuk Causality The Illustrated Sutra of Cause and Effect. 8th century, Japan In common usage, causality is also the relation between a set of factors (causes) and a phenomenon (the effect). Anything that affects an effect is a factor of that effect. A direct factor is a factor that affects an effect directly, that is, without any intervening factors.

Five W’s and a H that should come *after* every story (A model for the 21st century newsroom: pt3) « Online Journalism Blog So far this model has looked at sourcing stories in the new media age, and reporting a news story in the new media age. In this third part I look at what should happen after a news story has been reported, using a familiar framework: the 5 Ws and a H – who, what, where, why, when and how. A web page – unlike a newspaper, magazine or broadcast – is never finished – or at least, can always be updated. Why project managers get no respect There is not a child alive who dreams of being a project manager. Maybe a firefighter, a rock star or an astronaut, but not a PM. There is something inherently dull about the words “project” and “manager” – even the flames of a bright imagination would consider smothering itself to death in their presence. And it follows that in professional ranks, saying you are a project manager won’t get you much respect either. To many being a PM means you fit this unfortunate stereotype: you were not good enough in your field to be an engineer or a programmer, and through politics and self-inflation, you find ways to take credit for the hard work done by others.

Ishikawa diagram Ishikawa diagrams (also called fishbone diagrams, herringbone diagrams, cause-and-effect diagrams, or Fishikawa) are causal diagrams created by Kaoru Ishikawa (1968) that show the causes of a specific event.[1][2] Common uses of the Ishikawa diagram are product design and quality defect prevention, to identify potential factors causing an overall effect. Each cause or reason for imperfection is a source of variation. Causes are usually grouped into major categories to identify these sources of variation. Eight Disciplines Problem Solving Eight Disciplines Problem Solving (8D) is a method used to approach and to resolve problems, typically employed by quality engineers or other professionals. Its purpose is to identify, correct and eliminate recurring problems, and it is useful in product and process improvement. It establishes a permanent corrective action based on statistical analysis of the problem (when appropriate) and focuses on the origin of the problem by determining its root causes.

The Five W's (and H) approach A few days ago, I was trying to explain some technical concepts to a friend. After a bit of explaining I tried listing out reasons, places and times where those concepts would be applicable. I still thought that I had left out something. Collaboration tools for Virtual Project Teams « Fear No Project Wow – lots of feedback on the last week’s post “Project Management: Keys to managing a remote project team”! Thanks for all the comments and stories. Based on the questions I am expanding on the topic today.

Related:  5W5 Whys