 | This article needs additional citations for verification .(October 2018) |
 |
The seven management and planning tools have their roots in operations research work done after World War II and the Japanese total quality control (TQC) research. [1] [2]
| | This article needs additional citations for verification .(October 2018) |
| |
The seven management and planning tools have their roots in operations research work done after World War II and the Japanese total quality control (TQC) research. [1] [2]
Affinity diagrams are a special kind of brainstorming tool that organize large amount of disorganized data and information into groupings based on natural relationships.
It was created in the 1960s by the Japanese anthropologist Jiro Kawakita. It is also known as KJ diagram, after Jiro Kawakita. An affinity diagram is used when:
Interrelationship diagrams (IDs) displays all the interrelated cause-and-effect relationships and factors involved in a complex problem and describes desired outcomes. The process of creating an interrelationship diagram helps a group analyze the natural links between different aspects of a complex situation.
This tool is used to break down broad categories into finer and finer levels of detail. It can map levels of details of tasks that are required to accomplish a goal or solution or task. Developing a tree diagram directs concentration from generalities to specifics.
This tool is used to prioritize items and describe them in terms of weighted criteria. It uses a combination of tree and matrix diagramming techniques to do a pair-wise evaluation of items and to narrow down options to the most desired or most effective. Popular applications for the prioritization matrix include return on investment (ROI) or cost–benefit analysis (investment vs. return), time management matrix (urgency vs. importance), etc.
This tool shows the relationship between two or more sets of elements. At each intersection, a relationship is either absent or present. It then gives information about the relationship, such as its strength, the roles played by various individuals or measurements. The matrix diagram enables you to analyze relatively complex situations by exposing interactions and dependencies between things. Six differently shaped matrices are possible: L, T, Y, X, C, R and roof-shaped, depending on how many groups must be compared.
A useful way of planning is to break down tasks into a hierarchy, using a tree diagram. The process decision program chart (PDPC) extends the tree diagram a couple of levels to identify risks and countermeasures for the bottom level tasks. Different shaped boxes are used to highlight risks and identify possible countermeasures (often shown as "clouds" to indicate their uncertain nature). The PDPC is similar to the failure modes and effects analysis (FMEA) in that both identify risks, consequences of failure, and contingency actions; the FMEA also rates relative risk levels for each potential failure point.
This tool is used to plan the appropriate sequence or schedule for a set of tasks and related subtasks. It is used when subtasks must occur in parallel. The diagram helps in determining the critical path (longest sequence of tasks). The purpose is to help people sequentially define, organize, and manage a complex set of activities.
Risk management is the identification, evaluation, and prioritization of risks followed by coordinated and economical application of resources to minimize, monitor, and control the probability or impact of unfortunate events or to maximize the realization of opportunities.
Systems engineering is an interdisciplinary field of engineering and engineering management that focuses on how to design, integrate, and manage complex systems over their life cycles. At its core, systems engineering utilizes systems thinking principles to organize this body of knowledge. The individual outcome of such efforts, an engineered system, can be defined as a combination of components that work in synergy to collectively perform a useful function.
Safety engineering is an engineering discipline which assures that engineered systems provide acceptable levels of safety. It is strongly related to industrial engineering/systems engineering, and the subset system safety engineering. Safety engineering assures that a life-critical system behaves as needed, even when components fail.
Ishikawa diagrams are causal diagrams created by Kaoru Ishikawa that show the potential causes of a specific event.
Fault tree analysis (FTA) is a type of failure analysis in which an undesired state of a system is examined. This analysis method is mainly used in safety engineering and reliability engineering to understand how systems can fail, to identify the best ways to reduce risk and to determine event rates of a safety accident or a particular system level (functional) failure. FTA is used in the aerospace, nuclear power, chemical and process, pharmaceutical, petrochemical and other high-hazard industries; but is also used in fields as diverse as risk factor identification relating to social service system failure. FTA is also used in software engineering for debugging purposes and is closely related to cause-elimination technique used to detect bugs.
Project management software are computer programs that help plan, organize, and manage resources.
A Gantt chart is a bar chart that illustrates a project schedule. It was designed and popularized by Henry Gantt around the years 1910–1915. Modern Gantt charts also show the dependency relationships between activities and the current schedule status.
In the field of science and engineering, root cause analysis (RCA) is a method of problem solving used for identifying the root causes of faults or problems. It is widely used in IT operations, manufacturing, telecommunications, industrial process control, accident analysis, medicine, healthcare industry, etc. Root cause analysis is a form of inductive and deductive inference.
Failure mode and effects analysis is the process of reviewing as many components, assemblies, and subsystems as possible to identify potential failure modes in a system and their causes and effects. For each component, the failure modes and their resulting effects on the rest of the system are recorded in a specific FMEA worksheet. There are numerous variations of such worksheets. An FMEA can be a qualitative analysis, but may be put on a quantitative basis when mathematical failure rate models are combined with a statistical failure mode ratio database. It was one of the first highly structured, systematic techniques for failure analysis. It was developed by reliability engineers in the late 1950s to study problems that might arise from malfunctions of military systems. An FMEA is often the first step of a system reliability study.
Reliability engineering is a sub-discipline of systems engineering that emphasizes the ability of equipment to function without failure. Reliability is defined as the probability that a product, system, or service will perform its intended function adequately for a specified period of time, OR will operate in a defined environment without failure. Reliability is closely related to availability, which is typically described as the ability of a component or system to function at a specified moment or interval of time.
Task management is the process of overseeing a task through its lifecycle. It involves planning, testing, tracking, and reporting. Task management can help individuals achieve goals or enable groups of individuals to collaborate and share knowledge for the accomplishment of collective goals. Tasks are also differentiated by complexity, from low to high.
DMAIC or define, measure, analyze, improve and control refers to a data-driven improvement cycle used for optimizing and stabilizing business processes and designs. The DMAIC improvement cycle is the core tool used to drive Six Sigma projects. However, DMAIC is not exclusive to Six Sigma and can be used as the framework for other improvement applications.
Failure mode effects and criticality analysis (FMECA) is an extension of failure mode and effects analysis (FMEA).
Threat modeling is a process by which potential threats, such as structural vulnerabilities or the absence of appropriate safeguards, can be identified and enumerated, and countermeasures prioritized. The purpose of threat modeling is to provide defenders with a systematic analysis of what controls or defenses need to be included, given the nature of the system, the probable attacker's profile, the most likely attack vectors, and the assets most desired by an attacker. Threat modeling answers questions like "Where am I most vulnerable to attack?", "What are the most relevant threats?", and "What do I need to do to safeguard against these threats?".
Eight Disciplines Methodology (8D) is a method or model developed at Ford Motor Company used to approach and to resolve problems, typically employed by quality engineers or other professionals. Focused on product and process improvement, its purpose is to identify, correct, and eliminate recurring problems. It establishes a permanent corrective action based on statistical analysis of the problem and on the origin of the problem by determining the root causes. Although it originally comprised eight stages, or 'disciplines', it was later augmented by an initial planning stage. 8D follows the logic of the PDCA cycle. The disciplines are:
Requirements traceability is a sub-discipline of requirements management within software development and systems engineering. Traceability as a general term is defined by the IEEE Systems and Software Engineering Vocabulary as (1) the degree to which a relationship can be established between two or more products of the development process, especially products having a predecessor-successor or primary-subordinate relationship to one another; (2) the identification and documentation of derivation paths (upward) and allocation or flowdown paths (downward) of work products in the work product hierarchy; (3) the degree to which each element in a software development product establishes its reason for existing; and (4) discernible association among two or more logical entities, such as requirements, system elements, verifications, or tasks.
Process Decision Program Chart (PDPC) is a technique designed to help prepare contingency plans. The emphasis of the PDPC is to identify the consequential impact of failure on activity plans, and create appropriate contingency plans to limit risks. Process diagrams and planning tree diagrams are extended by a couple of levels when the PDPC is applied to the bottom level tasks on those diagrams.
The affinity diagram is a business tool used to organize ideas and data. It is one of the Seven Management and Planning Tools. People have been grouping data into groups based on natural relationships for thousands of years; however, the term affinity diagram was devised by Jiro Kawakita in the 1960s and is sometimes referred to as the KJ Method.
The project management triangle is a model of the constraints of project management. While its origins are unclear, it has been used since at least the 1950s. It contends that:
Event tree analysis (ETA) is a forward, top-down, logical modeling technique for both success and failure that explores responses through a single initiating event and lays a path for assessing probabilities of the outcomes and overall system analysis. This analysis technique is used to analyze the effects of functioning or failed systems given that an event has occurred.