CBAP Exam Dumps - IIBA Certified Business Analysis Professional Questions and Answers

The scope management plan defines how the project scope should be created, executed, monitored and controlled, and then validated. The scope management plan is a document that describes the processes and procedures for defining, managing, and controlling the project scope throughout the project life cycle. The scope management plan also defines the roles and responsibilities of the stakeholders involved in the scope management, the scope change control system, the scope verification and validation methods, and the scope baseline. The scope management plan is a component of the project management plan, which also includes other subsidiary plans, such as the schedule management plan, the cost management plan, and the quality management plan. References: [IIBA BABOK Guide v3], section 5.1.2, page 162; [CBAP / CCBA Certified Business Analysis Study Guide], chapter 6, page 233; Free CBAP CBAP® Exam Questions - IIBA CBAP Exam - Study4Exam, question 255.

The BA should ensure the business needs are articulated from the enterprise perspective, because this will help to align the needs with the strategic goals and objectives of the organization, and to ensure the needs are relevant, feasible, and beneficial for the enterprise as a whole. The other options are not the primary focus of the BA at this stage of defining the business opportunity. While traceability, solution description, and risk assessment are important aspects of business analysis, they are more relevant for later stages of the business analysis process, such as requirements analysis, solution design, and solution evaluation. References: CBAP Handbook, CBAP Study Guide, BABOK Guide

The BA needs to consider metrics and key performance indicators (KPIs) when using basic statistical sampling concepts to measure the objective of a solution implemented. Metrics and KPIs are quantitative measures that are used to evaluate the performance, progress, and value of a solution, process, or activity. They can help the BA to determine if the solution is meeting the expected outcomes and benefits, and to identify any gaps, issues, or opportunities for improvement. Metrics and KPIs can also help the BA to communicate the results and impact of the solution to the stakeholders and the organization. Some examples of metrics and KPIs that can be used to measure the objective of increasing the number of customer calls resolved per hour are: average call duration, first call resolution rate, customer satisfaction score, and call resolution efficiency. Frequency and timing, financial analysis, and benchmarking and market analysis are not the best options to consider when using basic statistical sampling concepts, because they are either too general, too specific, or not directly related to the objective of the solution. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 8: Solution Evaluation, page 337

Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 8: Solution Evaluation, section 8.2: Analyze Performance Measures, page 153

Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 8: Solution Evaluation, page 337

The possible reason why the solutions’ team was unable to accurately assess the merits of each of the proposed solutions is that the requirements and design options were not detailed enough. This means that the requirements and design options did not provide sufficient information, clarity, or specificity for the solutions’ team to understand, evaluate, and compare the different approaches for implementing the feature. The lack of detail may also lead to ambiguity, inconsistency, or incompleteness in the requirements and design options, which can affect the quality and feasibility of the solutions. The BA should ensure that the requirements and design options are detailed enough to meet the needs and expectations of the stakeholders, and to support the decision making and implementation processes. Requirements are not allocated to solution components, too many approaches are dividing the team, or business needs are unclear to the team are not the best options for the possible reason, because they are either irrelevant, inaccurate, or not the root cause of the problem. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 7: Requirements Analysis and Design Definition, page 280

Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 7: Requirements Analysis and Design Definition, section 7.5: Specify and Model Requirements, page 133

Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 7: Requirements Analysis and Design Definition, page 280

 A dependent task is a task that belongs to a certain work entity (project or process) and relates to other tasks of the same work entity in a way that ensures their interconnection and common direction. A dependent task can be a sub-task of a larger activity. It causes an effect to other tasks and sub-tasks. A dependent task cannot start until other tasks are completed, because it relies on the output, input, or resource of those tasks. A dependent task is also referred to as a logical relationship, because it shows the logical order or sequence of the tasks1. An analysis task is a task that involves examining, evaluating, or interpreting data, information, or requirements. An analysis task can be a dependent task or an independent task, depending on whether it requires the completion of other tasks or not. An analysis task can also be a predecessor task or a successor task, depending on whether it precedes or follows other tasks. An analysis task is a common type of task in business analysis2. A predecessor task is a task that comes before another task in a sequence or a network of tasks. A predecessor task can be a dependent task or an independent task, depending on whether it affects or is affected by other tasks or not. A predecessor task can also be an analysis task or a different type of task, depending on its nature and purpose. A predecessor task can start before other tasks are completed, as long as it does not depend on them3. An independent task is a task that does not belong to a certain work entity (project or process) or does not relate to other tasks of the same work entity. An independent task can be a standalone activity or a part of a larger activity. It does not cause an effect to other tasks or sub-tasks. An independent task can start at any time, regardless of the completion of other tasks, because it does not rely on the output, input, or resource of those tasks. An independent task is also referred to as a discrete task, because it is separate and distinct from other tasks1. References:

CBAP® Handbook

Predecessor Task - iiba.org

Dependent Task - iiba.org

A Pareto chart is a quality control tool that displays the frequency of defects or problems in descending order of importance. It helps to identify the most significant causes of poor quality and prioritize improvement actions. A Pareto chart is based on the Pareto principle, also known as the 80-20 rule, which states that 80% of the effects come from 20% of the causes. By using a Pareto chart, a business analyst can focus on the vital few causes that account for most of the defects or problems, rather than the trivial many that have little impact. References:

BABOK Guide v3, section 10.36 Pareto Chart

IIBA Business Analysis Competency Model, version 4.0, section 5.2.3.1.2 Pareto Chart

 A formal approach is suitable for a project that has a high level of complexity, uncertainty, and risk, as well as a high degree of stakeholder involvement and scrutiny. A project to expand into new markets is likely to have these characteristics, especially in the banking industry, which is highly regulated and competitive. A formal approach would help ensure that the project scope, objectives, and requirements are clearly defined, communicated, and approved by the relevant stakeholders, such as the CEO and the CFO. A formal approach would also provide more control and traceability over the project deliverables and changes, as well as more visibility and accountability for the project progress and outcomes. References: CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 2: Business Analysis Planning and Monitoring, page 59; Business Analysis Body of Knowledge (BABOK ®) Guide, Chapter 2: Business Analysis Planning and Monitoring, section 2.1.4: Selecting the Business Analysis Approach, pages 28-29.

A business analyst is responsible for preparing the business architecture, feasibility studies, and business cases. A business analyst is a professional who analyzes the needs and problems of an organization and its stakeholders, and proposes solutions that deliver value to them. A business analyst performs various tasks, such as eliciting, analyzing, validating, and managing requirements, conducting stakeholder analysis, modeling business processes, designing solutions, assessing risks, and evaluating alternatives. A business analyst also prepares various documents, such as business architecture, feasibility studies, and business cases, to communicate the business needs and the proposed solutions to the relevant stakeholders and decision-makers. A business architecture is a description of the current and future state of the business, including its vision, goals, objectives, strategies, capabilities, processes, and organizational structure. A business architecture helps to align the business and IT strategies, and to identify the gaps and opportunities for improvement. A feasibility study is an assessment of the technical, financial, and operational viability of a proposed project or initiative. A feasibility study helps to determine if the project is worth pursuing, and if it can be successfully implemented within the given constraints and resources. A business case is a document that provides the justification and rationale for a proposed project or initiative, based on its expected costs, benefits, risks, and impacts. A business case helps to secure the approval and funding for the project, and to measure its performance and outcomes. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, pages 3-4, 47, 343

Business Analysis Professional Resources | IIBA®, under Business Analysis Body of Knowledge (BABOK ®) Guide, Business Analysis Standard, and Standards, Regulations, and Best Practices

The Differences Between Feasibility Studies and Business Cases

The improvement opportunity that this situation represents is to enhance access to the relevant information. This means that the group of companies needs to improve the way they collect, store, share, and use the data that is essential for making decisions on handling materials and allocating resources. By enhancing access to the relevant information, the group of companies can increase their efficiency, effectiveness, and profitability, as well as their competitiveness in bidding for government contracts. Enhancing access to the relevant information may involve deploying a new system across the companies or developing a repository of information from each company, but these are not the improvement opportunities themselves, but rather possible solutions or approaches to achieve the improvement opportunity. Creating a business model canvas to outline business needs is not the improvement opportunity, but rather a technique that can help to define and communicate the value proposition and the strategic direction of the group of companies. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Strategy Analysis, page 249

Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 5: Strategy Analysis, section 5.4: Define Change Strategy, page 103

Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 6: Strategy Analysis, page 249

One of the possible reasons for the disagreement among the stakeholders is that they have different interpretations of the requirements, which may lead to conflicting expectations, assumptions, and preferences. The BA should use various techniques to elicit, analyze, validate, and communicate the requirements clearly and consistently to all the stakeholders, and to resolve any ambiguities or discrepancies. The BA should also ensure that the requirements align with the business need and the solution scope that were formally approved by the stakeholders at the beginning of the project.