Senior management has asked a risk practitioner to develop technical risk scenarios related to a recently developed enterprise resource planning (ERP) system. These scenarios will be owned by the system manager.
Which of the following would be the BEST method to use when developing the scenarios?
Correct Answer: A
A cause-and-effect diagram, also known as a fishbone diagram or an Ishikawa diagram, is a graphical tool that helps to identify and analyze the potential causes and effects of a problem or an event. A cause-and-effect diagram can be used to develop technical risk scenarios related to a recently developed ERP system, because it can help to:
* Break down the complex problem or event into manageable and measurable categories and subcategories of causes and effects
* Visualize the relationships and interactions among the various factors that contribute to the problem or event
* Identify the root causes and the most significant effects of the problem or event
* Generate ideas and hypotheses for testing and validating the problem or event
* Communicate and present the problem or event clearly and logically to the stakeholders1 A cause-and-effect diagram can be constructed by following these steps:
* Define the problem or event and write it in a box on the right side of the diagram
* Draw a horizontal line from the box to the left side of the diagram, representing the main spine of the fishbone
* Identify the major categories of causes that affect the problem or event, such as people, process, technology, environment, etc., and write them on the branches of the spine
* For each category, brainstorm and list the possible subcategories and specific causes that influence the problem or event, and write them on the sub-branches of the spine
* For each cause, identify and list the possible effects or consequences that result from the problem or event, and write them on the sub-sub-branches of the spine
* Analyze the diagram and prioritize the causes and effects based on their frequency, severity, and controllability
* Develop technical risk scenarios based on the most critical causes and effects, and describe how they could affect the ERP system and the organization1