L4M2 Exam Dumps : Defining Business Needs

Explanation

A business case is developed during the early stages of a project and outlines the why, what, how, and who necessary to decide if it is worthwhile continuing a project. One of the first things you need to know when starting a new project are the benefits of the proposed business change and how to communicate those benefits to the business.

Preparing the business case involves an assessment of:

- Business problem or opportunity

- Benefits

- Risk

- Costs including investment appraisal

- Technical solutions

- Timescale

- Impact on operations

- Organizational capability to deliver the project outcomes

These project issues are an important part of the business case. They express the problems with the current situation and demonstrate the benefits of the new business vision. Making business case with multiple options and choices also prompts the procurement and senior management to consider alternatives. As a result, the organisation may opt out the best option.

The business case brings together the benefits, disadvantages, costs, and risks of the current situa-tion and future vision so that executive management can decide if the project should go ahead.

Explanation

Cracks on the jet engine is a closed-end problem. A typical problem solving process has 8 steps:

Step 1: Define the Problem

- What is the problem?

- How did you discover the problem?

- When did the problem start and how long has this problem been going on?

- Is there enough data available to contain the problem and prevent it from getting passed to the next process step? If yes, contain the problem.

Step 2: Clarify the Problem

- What data is available or needed to help clarify, or fully understand the problem?

- Is it a top priority to resolve the problem at this point in time?

- Are additional resources required to clarify the problem? If yes, elevate the problem to your leader to help locate the right resources and form a team.

- Consider a Lean Event (Do-it, Burst, RPI, Project).

- Ensure the problem is contained and does not get passed to the next process step.

Step 3: Define the Goals

- What is your end goal or desired future state?

- What will you accomplish if you fix this problem?

- What is the desired timeline for solving this problem?

Step 4: Identify Root Cause of the Problem

- Identify possible causes of the problem.

- Prioritize possible root causes of the problem.

- What information or data is there to validate the root cause?

Step 5: Develop Action Plan

- Generate a list of actions required to address the root cause and prevent problem from getting to others.

- Assign an owner and timeline to each action.

- Status actions to ensure completion.

Step 6: Execute Action Plan

- Implement action plan to address the root cause.

- Verify actions are completed.

Step 7: Evaluate the Results

- Monitor and Collect Data.

- Did you meet your goals defined in step 3? If not, repeate th 8-Step Process.

- Were there any unforeseen consequences?

- If problem is resolved, remove activities that were added previously to contain the problem.

Step 8: Continuously Improve

- Look for additional opportunities to implement solution.

- Ensure problem will not come back and communicate lessons learned.

- If needed, repeat the 8-Step Problem Solving Process to drive further improvements.

ANA has already known what is going on, the next step they should adopt is collecting more infor-mation on the problem. If the airline is hurry to the solution, it may choose 'Generate options ad-dressing the issue'. The crack on turbine blade can be welded, or the airline replaces a new blade. However, jumping to solution without knowing the root cause does not completely solve the prob-lem. The root cause is unaddressed, then it may occur in the future. Therefore, the airline should still collect information to find the root cause, then remove it.