Program Evaluation and Review Technique

Critical path method

Work breakdown structure

Kaizen

Total quality management

PDCA

source: wiki

In an Analysis, decision trees are used in a context of a identifying a strategy most likely to reach a goal.



software for decision tree - SmartDraw




lectures:






Wiki

CRoss Industry Standard Process for Data Mining

Process Model

Phases of the CRISP-DM Process Model


Shearer C., “The CRISP-DM model: the new blueprint for data mining”,
Journal of Data Warehousing 5 (2000) 13-22 (see also www.crisp-dm.org)

Definition - In information technology, gap analysis is an assessment tool to help identify differences between information systems or applications. A gap is sometimes called "the space between where we are and where we want to be." A gap analysis helps bridge that space by highlighting which requirements are being met and which are not.

In software development, for instance, a gap analysis can be used to document which services and/or functions have been accidentally left out, which ones have been deliberately eliminated and which still need to be developed. In compliance, a gap analysis can be used to compare what is required by law to what is currently being done.

Technique for determining the steps to be taken in moving from a current state to a desired future-state.

List of steps to be taken:

1. Listing of characteristic factors (such as attributes, competencies, performance levels) of the present situation ("what is")

2. Cross-lists factors required to achieve the future objectives ("what should be")

3. Highlights the 'gaps' that exist and need to be 'filled.' Also called need-gap analysis, needs analysis, and needs assessment.

Activities and steps
Requirements · Specification Architecture · Design Implementation · Testing Deployment · Maintenance
Models
Agile · Cleanroom · DSDM Iterative · RAD · RUP · Spiral Waterfall · XP · Scrum · Lean V-Model · FDD
Supporting disciplines
Configuration management Documentation Quality assurance (SQA) Project management User experience design
Tools
Compiler · Debugger · Profiler GUI designer Integrated development environment

Manifesto for Agile Software Development

MoSCoW method

"The Old Seven."

"The First Seven."

"The Basic Seven."

Quality pros have many names for these seven basic tools of quality, first emphasized by Kaoru Ishikawa, a professor of engineering at Tokyo University and the father of “quality circles.”

1. Cause-and-effect diagram (also called Ishikawa or fishbone chart): Identifies many possible causes for an effect or problem and sorts ideas into useful categories.

2. Check sheet: A structured, prepared form for collecting and analyzing data; a generic tool that can be adapted for a wide variety of purposes.

3. Control charts: Graphs used to study how a process changes over time.

4. Histogram: The most commonly used graph for showing frequency distributions, or how often each different value in a set of data occurs.

5. Pareto chart: Shows on a bar graph which factors are more significant.

6. Scatter diagram: Graphs pairs of numerical data, one variable on each axis, to look for a relationship.

7. Stratification: A technique that separates data gathered from a variety of sources so that patterns can be seen (some lists replace "stratification" with "flowchart" or "run chart").

Excerpted from Nancy R. Tague’s The Quality Toolbox, Second Edition, ASQ Quality Press, 2004, page 15.

If categorization is not done correctly than the Pareto can be misleading in the way that resource being spent on trivial problem instead of vital.

Ishikawa diagrams (also called fishbone diagrams or cause-and-effect diagrams) are diagrams that show the causes of a certain event.

A common use of the Ishikawa diagram is in product design, to identify potential factors causing an overall effect.

For more info see here

FMEA (Failure mode and effects analysis) is a part of DMAIC in Six Sigma

Is a step after C&E Matrix ant it is used for analysis of potential failure modes within a system

Every defect is measured by Severity, Occurrence and Detection. The multiplication of these elements gives the Risk prioritization (Risk Priority Number RPN) for every case.

Uses of FMEA

• Development of system requirements that minimize the likelihood of failures.
• Development of methods to design and test systems to ensure that the failures have been eliminated.
• Evaluation of the requirements of the customer to ensure that those do not give rise to potential failures.
• Identification of certain design characteristics that contribute to failures, and minimize or eliminate those effects.
• Tracking and managing potential risks in the design. This helps avoid the same failures in future projects.
• Ensuring that any failure that could occur will not injure the customer or seriously impact a system.
• To produce world class quality products

Advantages

• Improve the quality, reliability and safety of a product/process
• Improve company image and competitiveness
• Increase user satisfaction
• Reduce system development timing and cost
• Collect information to reduce future failures, capture engineering knowledge
• Reduce the potential for warranty concerns
• Early identification and elimination of potential failure modes
• Emphasis problem prevention
• Minimize late changes and associated cost
• Catalyst for teamwork and idea exchange between functions
• Reduce the possibility of same kind of failure in future

For more information see here

A very useful article about C&E Matrix

Need Help Making Decisions?
by Ron Pereira on June 11th, 2007

Posted using ShareThis

Here is a list of the main Process Analysis methods:

• Cause and Effect - Fishbone
• 5 Whys Analysis
• Process Mapping
• Value Stream Mapping
• Mind Mapping
• SIPOC
• C&E Matrix
• Value-Add Analysis
• Waste Analysis
• FMEA
• Pair-wise Comparison