The document provides information about root cause analysis and fishbone diagrams. It defines a fishbone diagram and its typical categories of causes (people, methods, machines, materials, measurements, environment). It then discusses how fishbone diagrams are used in the Six Sigma measure phase and the Business Analysis Body of Knowledge. The document provides guidance on when to create a fishbone diagram, how to select branches and organize it, and includes examples. It also discusses communication challenges, shortcomings in the industry, and supplemental information like templates.
This Texavi presentation walks you through the tools, techniques and methodologies to help you master the art and science of Business Analysis. In this presentation, you will learn the core aspects and essential toolkit for transforming into the New-age Business Analyst!
In this advanced business analysis training session, you will learn OOA and UML. Topics covered in this session are:
• Business Imperatives
• Enterprise Modeling
• Stakehollders
• Value Chains
• Business Processes
• Business Engineering
• System Level Model
• Mapping to Layered Architecture
• Conclusion
For more information, click here: https://www.mindsmapped.com/courses/business-analysis/advanced-business-analyst-training/
This slidedeck from Texavi dwells on the essential tools, methods and techniques for the New-age Business Analyst. It also touches upon the methodologies, notations and software tools and applications to help with the analysis.
This Texavi presentation walks you through the tools, techniques and methodologies to help you master the art and science of Business Analysis. In this presentation, you will learn the core aspects and essential toolkit for transforming into the New-age Business Analyst!
In this advanced business analysis training session, you will learn OOA and UML. Topics covered in this session are:
• Business Imperatives
• Enterprise Modeling
• Stakehollders
• Value Chains
• Business Processes
• Business Engineering
• System Level Model
• Mapping to Layered Architecture
• Conclusion
For more information, click here: https://www.mindsmapped.com/courses/business-analysis/advanced-business-analyst-training/
This slidedeck from Texavi dwells on the essential tools, methods and techniques for the New-age Business Analyst. It also touches upon the methodologies, notations and software tools and applications to help with the analysis.
Workshops with subject matter experts to elicit insights for the discovery phase or requirements for a new solution should follow a disciplined approach described in this slide deck.
In this advanced business analysis training session, you will learn Enterprise Analysis. Topics covered in this session are:
• Strategic Planning
• Process and Elements
• Zachman Framework
• POLDAT
• Entity Analysis
• Business Architecture
• Key Stakeholders
• SWOT Analysis
• Cost-Benefit Analysis
For more information, click here: https://www.mindsmapped.com/courses/business-analysis/advanced-business-analyst-training/
A user story is a tool used in Agile software development to capture a description of a software feature from an end-user perspective. The user story describes the type of user, what they want and why. A user story helps to create a simplified description of a requirement.User stories are short, simple descriptions of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system. They typically follow a simple template
Use Case and User Story Explained with example
By David Zimmer
It seems epidemic. In meetings, in job ads, in performance reviews and even in lunch conversations, we discuss our need to increase our critical thinking skills. Some use the term “critical thinking” in a general sense meaning all problem solving approaches. Others refer to the specific thinking modality of critical thinking. Unfortunately, we miss eight thinking modalities equally important when solving problems, developing new concepts or simply living life.
In this session, we provide an overview of the 9 thinking modalities, their characteristics and differences, and demonstrate their approaches to an example problem.
From this session, you will:
Learn the 9 Thinking Modalities.
Understand the characteristics and differentiators of each modality.
Recognize appropriate uses of each modality.
Learn how to overcome the Critical Thinking monopoly.
In this advanced business analysis training session, you will learn Stakeholder Management. Topics covered in this session are:
• Problem Description
• Stakeholder Management
• Identify your Stakeholders
• Analyze your Stakeholders
• Prioritize your Stakeholders
• Engaging your Stakeholders
• Managing Expectations
For more information, click here: https://www.mindsmapped.com/courses/business-analysis/advanced-business-analyst-training/
Summarizing a problem and solution on one page. Brief training to understand how and why to use A3 Report methodology. Presented by Utah Manufacturing Extension Center, training starts on slide 5.
This examines the potential for the application of Design Science principles to the solution design process within solution architecture to improve the rigour and accuracy of solution designs.
Design Science is the structured and systematic process for creating designs that resolve problems. It is concerned with the structured process for the acquisition and application of knowledge in relation to the problems to the resolved and the solution knowledge to be applied.
The application of Design Science must be a means to an end – better solution quality – and not an end in itself – an incentive for the design function is to become large.
Solution architecture requires a (changing) combination of technical, leadership, interpersonal skills, experience, analysis, appropriate creativity, reflection and intuition applied in a structured manner.
Knowledge management – problem knowledge and solution knowledge – is at the core of the application of design science principles.
Knowledge management requires good management of the solution architecture function.
In this advanced business analysis training session, you will learn User Stories from Scenarios. Topics covered in this session are:
• What is a Use Case?
• The Purpose of Use Case Analysis
• Managing the Building of Product
• The Basic Development Loop
• Analysis paralysis – how much is enough
• Conceptual model development
• Style Guide development
• Usability testing during agile increments
For more information, click here: https://www.mindsmapped.com/courses/business-analysis/advanced-business-analyst-training/
The Agile Manager: Empowerment and AlignmentSoftware Guru
In today’s business climate, change occurs at an ever-increasing pace. Managers and executives are increasingly challenged to build an organization that is able to respond effectively to this change. This is the essence of agility.
This talk will provide the latest thinking on building the agile organization, moving beyond the command and control paradigm to one that balances employee empowerment and business alignment.
Full-day pre-conference workshop given at the IA Summit 2007. This is the slide deck we ended up with after the workshop. This version contains participants' comments, discussions, work products, etc. The "Before" version has blank slides that anticipate workshop products.
My goal with this talk was to provide developers and tech folks with an understanding of requirements gathering. Key concepts and resources that they can use to make their own coding practice better. Part of being a professional coder
Based on the popular book: Understanding A3 Thinking: A Critical Component of Toyota's PDCA Management System (2008), by Durward K. Sobek II, a synopsis has been presented here.
Business requirements gathering and analysisMena M. Eissa
Business analysis and requirements management are a key to project success.
This workshop helps candidates perform better based on sharing real life experience with them.
Workshops with subject matter experts to elicit insights for the discovery phase or requirements for a new solution should follow a disciplined approach described in this slide deck.
In this advanced business analysis training session, you will learn Enterprise Analysis. Topics covered in this session are:
• Strategic Planning
• Process and Elements
• Zachman Framework
• POLDAT
• Entity Analysis
• Business Architecture
• Key Stakeholders
• SWOT Analysis
• Cost-Benefit Analysis
For more information, click here: https://www.mindsmapped.com/courses/business-analysis/advanced-business-analyst-training/
A user story is a tool used in Agile software development to capture a description of a software feature from an end-user perspective. The user story describes the type of user, what they want and why. A user story helps to create a simplified description of a requirement.User stories are short, simple descriptions of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system. They typically follow a simple template
Use Case and User Story Explained with example
By David Zimmer
It seems epidemic. In meetings, in job ads, in performance reviews and even in lunch conversations, we discuss our need to increase our critical thinking skills. Some use the term “critical thinking” in a general sense meaning all problem solving approaches. Others refer to the specific thinking modality of critical thinking. Unfortunately, we miss eight thinking modalities equally important when solving problems, developing new concepts or simply living life.
In this session, we provide an overview of the 9 thinking modalities, their characteristics and differences, and demonstrate their approaches to an example problem.
From this session, you will:
Learn the 9 Thinking Modalities.
Understand the characteristics and differentiators of each modality.
Recognize appropriate uses of each modality.
Learn how to overcome the Critical Thinking monopoly.
In this advanced business analysis training session, you will learn Stakeholder Management. Topics covered in this session are:
• Problem Description
• Stakeholder Management
• Identify your Stakeholders
• Analyze your Stakeholders
• Prioritize your Stakeholders
• Engaging your Stakeholders
• Managing Expectations
For more information, click here: https://www.mindsmapped.com/courses/business-analysis/advanced-business-analyst-training/
Summarizing a problem and solution on one page. Brief training to understand how and why to use A3 Report methodology. Presented by Utah Manufacturing Extension Center, training starts on slide 5.
This examines the potential for the application of Design Science principles to the solution design process within solution architecture to improve the rigour and accuracy of solution designs.
Design Science is the structured and systematic process for creating designs that resolve problems. It is concerned with the structured process for the acquisition and application of knowledge in relation to the problems to the resolved and the solution knowledge to be applied.
The application of Design Science must be a means to an end – better solution quality – and not an end in itself – an incentive for the design function is to become large.
Solution architecture requires a (changing) combination of technical, leadership, interpersonal skills, experience, analysis, appropriate creativity, reflection and intuition applied in a structured manner.
Knowledge management – problem knowledge and solution knowledge – is at the core of the application of design science principles.
Knowledge management requires good management of the solution architecture function.
In this advanced business analysis training session, you will learn User Stories from Scenarios. Topics covered in this session are:
• What is a Use Case?
• The Purpose of Use Case Analysis
• Managing the Building of Product
• The Basic Development Loop
• Analysis paralysis – how much is enough
• Conceptual model development
• Style Guide development
• Usability testing during agile increments
For more information, click here: https://www.mindsmapped.com/courses/business-analysis/advanced-business-analyst-training/
The Agile Manager: Empowerment and AlignmentSoftware Guru
In today’s business climate, change occurs at an ever-increasing pace. Managers and executives are increasingly challenged to build an organization that is able to respond effectively to this change. This is the essence of agility.
This talk will provide the latest thinking on building the agile organization, moving beyond the command and control paradigm to one that balances employee empowerment and business alignment.
Full-day pre-conference workshop given at the IA Summit 2007. This is the slide deck we ended up with after the workshop. This version contains participants' comments, discussions, work products, etc. The "Before" version has blank slides that anticipate workshop products.
My goal with this talk was to provide developers and tech folks with an understanding of requirements gathering. Key concepts and resources that they can use to make their own coding practice better. Part of being a professional coder
Based on the popular book: Understanding A3 Thinking: A Critical Component of Toyota's PDCA Management System (2008), by Durward K. Sobek II, a synopsis has been presented here.
Business requirements gathering and analysisMena M. Eissa
Business analysis and requirements management are a key to project success.
This workshop helps candidates perform better based on sharing real life experience with them.
"Live Coverage Here http://www.golflivestreaming.net/ 2015 RBC Canadian Open returns to the beautiful Glen Abbey Golf Club in Oakville, July 20 – 26. Some of the world’s most talented golf stars will tee off for the championship
Live Coverage Here http://www.golflivestreaming.net/
Live Coverage Here http://www.golflivestreaming.net/
Live Coverage Here http://www.golflivestreaming.net/"
Ponencia realizada en el Simposio: “El Sistema Alimentario Venezolano (SAV): Evolución reciente, balance y perspectiva”, en el marco del XX Aniversario del Centro de Investigaciones Agroalimentarias "Edgar Abreu Olivo" (CIAAL-EAO) de la FACES-ULA, consistente en la presentación de avances de investigación del proyecto “La integración de Venezuela al MERCOSUR: impactos potenciales sobre el comercio internacional. El caso del sector agrícola venezolano” (Plan II, ULA).
Objetivo principal: Analizar la evolución del comercio agroalimentario de Venezuela con el Mercosur en el último decenio.
Universidad de Los Andes, Mérida (Venezuela), 21 de mayo de 2015.
The A3 -Tool for Continuous ImprovementWillie Carter
The A3 management process is a problem-solving and continuous improvement methodology that originated from the Toyota Production System (TPS) and is commonly used in Lean management and Six Sigma approaches. It gets its name from the paper size typically used for the A3 report, which is a concise and visual one-page document used to present information and guide problem-solving efforts.
The A3 management process encourages a structured and visual approach to problem-solving, making it easier for teams to collaborate, communicate, and drive improvements. It emphasizes data-driven decision-making and encourages a culture of continuous improvement within organizations.
UX Field Research Toolkit - Updated for Big Design 2018Kelly Moran
Looking for practice with in-depth UXR fieldwork methods? You may have read about these techniques in the past, but methods must be practiced to be understood. projekt202 has been employing the experience research craft with great success since 2003. This workshop is your opportunity to try these tools of the trade in a structured environment without pressing deadlines or looming stakeholders. Our experienced research and design professionals will share industry tips and tricks that will help you put theory to practice.
The workshop will be hands-on and interactive; instructional elements will be reinforced with stories of impact to real projects. We will not only cover methods of gathering user data, but the importance of spending time internalizing and analyzing the data through activities such as affinity diagramming, persona building, and journey mapping. Participants will gain exposure to these important practices in a low-pressure atmosphere and with the guidance of experienced professionals.
Business analysis goes beyond writing user stories… get it right with the techniques from backlogs to wireframes, from use cases to data models, and MoScoW prioritisation to tee-shirt sizing estimation! Texavi's Tech Bootcamp will equip you to be job-ready with practical and real-time insights, as well as offering access to our treasure of insightful, high-quality resources and materials.
In this part of the course, we will discuss the nuances that would help us understand the different methods, techniques and tools in software estimation. Though we will discuss the broader estimation aspects, focus is on agile estimation methods and techniques such as user story points, relative size estimation, planning poker, tee-shirt sizing and more.
Highlights and summary of long-running programmatic research on data science; practices, roles, tools, skills, organization models, workflow, outlook, etc. Profiles and persona definition for data scientist model. Landscape of org models for data science and drivers for capability planning. Secondary research materials.
People-Centric Design Approach in Application LifecycleRofiqi Setiawan
This slide was made for 'User Testing Day'. It's a talk targeted for UX practitioners or anyone who wants to know about UX design process with the goal to give the audience better ideas of designing UX with less assumption by doing better research. The slides present about and how UX design process can be integrated in application lifecycle as a part of DX (developer experience). The slides also introduce UX design process using a user-centered design approach borrowing techniques from scenario-focused engineering (SFE) practices.
1. Root Cause AnalysisRoot Cause AnalysisRoot Cause AnalysisRoot Cause Analysis
in Project Management
and Software Development
Addressing Common Problems
ASEE
February 20, 2016
Barbara DeVries
2. Table of ContentsTable of ContentsTable of ContentsTable of Contents
• Definition
• Six Sigma Measure Phase
• BABOK
• Approach — How To
• Examples
• Communication
• Shortcomings
• Supplemental Information
• Instructions
• Templates: Visio, PowerPoint, Excel
2
3. DefinitionDefinitionDefinitionDefinition
https://en.wikipedia.org/wiki/Ishikawa_diagram
Ishikawa diagrams (also called fishbone diagrams and cause-and-effect diagrams) are
causal diagrams created by Kaoru Ishikawa (1968) that show the causes of a specific event.
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. The categories typically include:
• People: Anyone involved with the process
• Methods: How the process is performed and the specific requirements for doing it, such
as policies, procedures, rules, regulations and laws
• Machines: Any equipment, computers, tools, etc. required to accomplish the job
• Materials: Raw materials, parts, pens, paper, etc. used to produce the final product
Measurements: Data generated from the process that are used to evaluate its quality
• Environment: The conditions, such as location, time, temperature, and culture in which
the process operates
3
4. Six SigmaSix SigmaSix SigmaSix Sigma ---- Ishikawa, Cause and Effect, Root Cause AnalysisIshikawa, Cause and Effect, Root Cause AnalysisIshikawa, Cause and Effect, Root Cause AnalysisIshikawa, Cause and Effect, Root Cause Analysis
ProcessProcessProcessProcess Mapping and Potential Vital FewMapping and Potential Vital FewMapping and Potential Vital FewMapping and Potential Vital Few InputsInputsInputsInputs
4
5. Six SigmaSix SigmaSix SigmaSix Sigma ---- Ishikawa, Cause and Effect, Root Cause AnalysisIshikawa, Cause and Effect, Root Cause AnalysisIshikawa, Cause and Effect, Root Cause AnalysisIshikawa, Cause and Effect, Root Cause Analysis
Process Mapping and Potential Vital FewProcess Mapping and Potential Vital FewProcess Mapping and Potential Vital FewProcess Mapping and Potential Vital Few InputsInputsInputsInputs
The C&E diagram:The C&E diagram:The C&E diagram:The C&E diagram:
-Is a visual brainstorming tool to identify potential causes for your problemIs a visual brainstorming tool to identify potential causes for your problemIs a visual brainstorming tool to identify potential causes for your problemIs a visual brainstorming tool to identify potential causes for your problem
-Enables alignment of potential causes to the inputs identified in process mapEnables alignment of potential causes to the inputs identified in process mapEnables alignment of potential causes to the inputs identified in process mapEnables alignment of potential causes to the inputs identified in process map
5
6. BABOKBABOKBABOKBABOK ----A Guide to theA Guide to theA Guide to theA Guide to the Business Analysis Body of Knowledge®Business Analysis Body of Knowledge®Business Analysis Body of Knowledge®Business Analysis Body of Knowledge®
Version 2.0 Section 9.25 pageVersion 2.0 Section 9.25 pageVersion 2.0 Section 9.25 pageVersion 2.0 Section 9.25 page 202202202202
• A fishbone diagram (also known as an Ishikawa or cause-and-effect diagram) is used to
identify and organize the possible causes of a problem. This tool helps to focus on the
cause of the problem versus the solution and organizes ideas for further analysis. The
diagram serves as a map depicting possible cause-and-effect relationships.
• Steps to develop a cause-and-effect diagram include:
• Capture the issue or problem under discussion in a box at the top of the diagram.
• Draw a line from the box across the paper or white board (forming the spine of the
fishbone).
• Draw diagonal lines from the spine to represent categories of potential causes of the
problem. The categories may include people, process, tools, and policies.
• Draw smaller lines to represent deeper causes.
• Brainstorm categories and potential causes of the problem and capture them under the
appropriate category
• Analyze the results. Remember that the group has identified only potential causes of the
problem. Further analysis is needed to validate the actual cause, ideally with data.
• Brainstorm potential solutions once the actual cause has been identified.
6
8. ApproachApproachApproachApproach ———— When would I want to create a fishboneWhen would I want to create a fishboneWhen would I want to create a fishboneWhen would I want to create a fishbone?
• You are in Production support. Some problems, issues, defects recur
which seem to be related.
• You are reviewing the procedures for a line of business that you
support. Some of the procedures are repeatable steps to address a
step in the "unhappy" path of operations.
• You are reviewing the quality control process for a line of business
• A new issue has emerged in production that is somewhat
mysterious and the reasons are not fully known
• You are analyzing a process which has interrelated properties.
For example: the triple constraint in project management — time,
quality, and cost.
8
9. How do I select the branches and organize theHow do I select the branches and organize theHow do I select the branches and organize theHow do I select the branches and organize the fishbonesfishbonesfishbonesfishbones????
Brainstorm Approach
• Ask your team to contribute their thoughts on what is
causing the problem.
• If they are stumped, ask them to list things which MIGHT
impact the outcome
• Ask who is involved and what they contribute
• Ask who provides the initial information
• Ask who uses the resulting information
• Ask where the information comes from
• Ask how long the process takes. Is there a delay? Is
anything impacting the delay?
• Is this related to a particular time or season? Is it only at
night? Is it spring, fall, winter or on a holiday? Is it during
the week or the weekend?
• Does the size vary?
• Does the content vary?
Structured Approach
• Label the branches: people, process, environment
(physical),materials (inputs)
• Label the branches with the steps in the process to
perform QC
• Label the branches with the steps in the procedures
• After you work with the diagram, please feel free to
rename the branches, move the fishbones and reorganize
the diagram.
• There is no right or wrong answer. This is an analysis
technique. There are no Ishikawa police.
9
15. Communication: One Size Does Not Fit All
• Interpretation Differs
• Visual, Spoken, Felt (Emoted), Kinetic
• Different Types of Diagrams
• Process Maps, Process Flows, Swim Lanes
• UML
• Venn Diagrams
• Context Diagrams – Business, System, Groups – Input, Output
• Different Expressions
• Business Requirements, System Requirements
• Use Cases
• User Stories
• Design Specifications
• Test Plans, Test Cases, Test Scripts, Test Results
• And Then….. The Code and The Executables
15
16. Shortcomings in Our Industry
• Total Cost of Ownership
• Cost on a Project Basis
• Maintenance, Operations, Business as Usual Separate from Enhancements and New
Functions
• Replace Cost and Value
• Unused or Obsolete Functions
• Requirements Management
• Requirements on a Project Basis
• No Documentation outside of Project
• Few Training Materials or Job Aids
• No User Help
• Business Procedures
• Replace a System – Reinvent
• Evolution
• New Business, New Functions,
• Expansion or Replacement – Little Sharing
• Non-Functional Requirements – Maintenance, Performance, Scalability
• No Reuse, Only Reinvention – Parts Not Compatible
16
19. Translation, Reuse, Rosetta Stone
19
Machine Language, Binary
Language 1
Language 2
Language 3
Requirements and Specifications (Embedded)
Future Language
21. BiographyBiographyBiographyBiography
https://www.linkedin.com/in/bdevries
Barbara DeVries has over 20 years of experience in software
development and technology implementations, with vertical expertise
in banking and finance. She has held positions ranging from software
developer and system analyst to Vice-President of Software and Data
Architecture, managing initiatives, programs, projects and teams. She
holds multiple Bachelor and Master’s degrees, as well as certifications
in project management, network engineering, scrum master and Scaled
Agile Framework. She has worked with companies from startup to
Fortune 500, banks on the east coast and west coast, software
development and consulting companies as well as investment
firms. She holds standards in high esteem, but people and
relationships in higher esteem.
21
22. Supplemental Information
• Templates
• How to Create a Diagram
• Examples of Other Diagrams
• Process Maps, Process Flows, Swim Lanes
• UML
• Venn Diagrams
• Context Diagrams – Business, System, Groups – Input, Output
• Requirements Tracking
22
25. Create a cause and effectCreate a cause and effectCreate a cause and effectCreate a cause and effect diagramdiagramdiagramdiagram
Microsoft OfficeMicrosoft OfficeMicrosoft OfficeMicrosoft Office----ExcelExcelExcelExcel
Cause and effect diagrams document all the factors that contribute to or affect a given situation: all the causes,
that is, that lead to a certain effect. They are also called Ishikawa, fishbone, or characteristic diagrams.
The Cause and Effect Diagram template opens a drawing page that already contains a spine shape (effect) and
four category boxes (causes) to help start your drawing. This template also provides a variety of shapes
representing primary and secondary causes that can be used to add even greater detail
• On the File menu, point to New, point to Business, and then click Cause and Effect Diagram.
• Select the spine (the horizontal arrow) on the drawing page, and then type text that describes the effect, problem, or objective.
• Determine the number of cause categories that contribute to the effect, and then do one of the following:
• To add a category, drag a Category 1 or Category 2 shape onto the drawing page and position it so that the arrowhead is touching
the spine.
• To delete a category, select the shape and then press the DELETE key.
• For each category shape on the drawing page, select the shape, and then type the name of the cause category.
• To represent major causes contributing to the categories, drag Primary cause shapes onto the drawing page and snap the
arrowheads to category lines.
• To represent secondary causes contributing to primary causes, drag Secondary cause shapes onto the drawing page and snap the
arrowheads to primary cause lines.
• NOTES
• To label a primary or secondary cause shape, select the shape and then type.
• To change the direction of a secondary cause arrow, use the Rotate or Flip commands on the Shape menu.
25
26. Examples of Diagrams
• Process Maps, Process Flows, Swim Lanes
• UML
• Venn Diagrams
• Context Diagrams – Input, Output
• Business, System, Groups
26
29. Example Venn Diagram: Security Design
User Profiles & Permissions
Documents Images Access
Role Based Department/Loan Based
Manager/Administrator
all documents
Document
Supervisor
Document
Image User
Loan Access
by Type
Loan
Supervisor
Manager All loan types,
including celebrity, high
net worth
30. Image Repository
Context Diagram for Image Inputs (Source)
Proposed System Perspective
Business Unit
Folders
FTP
Customer Service
Letters/Fax
User Access
Scanner –
Original and Trailing
Documents
Internal
Documents
Word Docs
RightFax
Scan, Fax
CD or
Hard Drive
Exceptions
Sweep Process
External
Corrected
Verify
Mail Room
Scanning
Format Error
PDF or TIFF
Business Unit
converts native
format
Email
Attachments
Manual
Conversion–
Rename
MIN#
to Loan#
Vendors