CBAP Exam Dumps - Certified Business Analysis Professional

A business case is a document that provides the rationale and justification for initiating a project or an investment. It describes the business problem or opportunity, the proposed solution, the expected benefits, costs, risks, and assumptions. A business case also includes an analysis of the alternatives and a recommendation for the best option. A business case helps management to make a go/no go decision based on the value proposition and the return on investment of the project. A business case is one of the key outputs of the enterprise analysis process, which involves defining the business need, assessing the capability gaps, determining the solution approach, defining the solution scope, and defining the business case1234. References: 1: BABOK Guide v3, section 3.4, pages 68-77 2: CBAP / CCBA Certified Business Analysis Study Guide, chapter 4, pages 107-108 3: Business Analysis Techniques: Developing the Business Case, pages 25-26 4: How to Write a Business Case: 4 Steps to a Perfect Business Case Template

 A task list is a tool that helps to organize and track the business analysis activities. Each task in the task list must have a unique number that identifies it and allows it to be referenced and tracked. The unique number can also be used to link the task to other elements, such as requirements, deliverables, stakeholders, or risks. The unique number can be assigned sequentially or based on a coding scheme that reflects the task hierarchy or category. References: BABOK Guide v3, page 38; CBAP / CCBA Certified Business Analysis Study Guide, page 77.

 Voting is a technique of requirements prioritization that involves asking the stakeholders to express their preferences for the requirements using various methods, such as ranking, rating, or allocating points or money. Voting helps to achieve consensus and alignment among the stakeholders and to identify the most important and valuable requirements. In this scenario, the business analyst is using a voting method that assigns play money to the requirements, which reflects the relative importance and benefit of each requirement. The requirements with the highest amount of play money are prioritized over the ones with lower amounts.

References:

• BABOK® Guide, p. 55, 376-377
• CBAP / CCBA Certified Business Analysis Study Guide, p. 165-166
• Certified Business Analysis Professionalâ„¢ (CBAP®) | Coursera, Course 2, Week 1, Video: “Requirements Prioritization”

A control chart is a quality control chart that tracks trends in project execution by plotting the values of a quality metric over time against established control limits. A control chart can help the project team monitor the variation and stability of a process, identify the causes of variation, and take corrective actions if the process goes out of control. A control chart can also show the performance of a process in relation to the customer specifications and expectations. A control chart is different from a RACI chart, which shows the roles and responsibilities of project team members. A control chart is also different from a PERT chart, which shows the sequence and duration of project activities. A control chart isnot a Pareto chart, which shows the frequency and impact of problems or defects. References:

• Quality Control in Project Management, paragraph 6
• 15 Quality management tools in project management, paragraph 3
• Control Chart: A Key Tool for Ensuring Quality and Consistency, paragraph 1
• Control Chart - Project Management Knowledge, paragraph 1

 Business or technical risk is a requirements prioritization approach that involves ranking the requirements based on the potential negative consequences or uncertainties associated with their implementation or non-implementation. This approach can help to identify and mitigate the most critical risks early in the project and reduce the likelihood of project failure. Business or technical risk can be assessed by considering factors such as the impact on the business value, the feasibility of the solution, the complexity of the requirements, the dependencies among the requirements, the volatility of the requirements, and the stakeholder satisfaction. Business or technical risk is one of the common criteria for requirements prioritization, as it helps to balance the benefits and costs of the requirements1234. References: 1: Requirement prioritization3 2: The Ultimate Guide to Requirements Prioritization4 3: Business Analysis Techniques: Prioritizing Requirements5 4: Requirements Prioritization: How to Prioritize Requirements

The T in SWOT analysis stands for Threats. These are external factors that may pose risks or challenges to the organization, its projects, or its solutions. Threats can be related to the market, the industry, the technology, the environment, the society, the regulation, or the competition. Business analysts should identify and assess the potential threats and their impact on the organization’s objectives and strategies, and recommend ways to mitigate or avoid them. References:

• CBAP® Handbook, page 15, section 4.1.2.3
• BABOK® Guide, page 32, section 3.2.3
• SWOT Analysis: How To With Table and Example
• SWOT Analysis Threats: Definition & Examples

Opportunities to prioritize requirements is not something that Rachel should include in her business case, as it is not relevant for the decision-making process. A business case is a document that clearly identifies the reasoning for initiating a project to justify the resources required. It includes the following items12:

• A business problem or opportunity
• Possible solutions and their benefits and disadvantages
• Risks associated with the main solution
• Costs
• Implementation timeline
• Consequences for implementing a solution and for retaining the status quo

Opportunities to prioritize requirements is not one of these items, as it is part of the business analysis process, not the business case. Prioritizing requirements is a technique that helps to rank the requirements in order of importance, urgency, or value for the stakeholders. It helps to determine which requirements should be implemented first, and which ones can be deferred or excluded. Prioritizing requirements is useful for managing the scope, schedule, and budget of the project, but it is not a factor that influences the approval or rejection of the project34.

The other options are things that Rachel should include in her business case, as they are relevant for the decision-making process. A. Time to break even is the period of time required for the project to recover its initial investment. It is a measure of the profitability and feasibility of the project, and it helps to compare different solution options5. C. Follow-on opportunities are the potential benefits or outcomes that can be achieved after the completion of the project, such as new markets, customers, products, or services. They are part of the qualitative and quantitative benefits of the project, and they help to demonstrate the value and alignment of the project with the business vision and strategy. D. Qualitative and quantitative benefits are the positive impacts or results that the project will deliver to the organization and the stakeholders, such as increased revenue, customer satisfaction, efficiency, or quality. They are expressed in both non-numerical and numerical terms, and they help to justify the costs and risks of the project. References:

• How to Write a Business Case (Template Included) - ProjectManager
• How to Write a Business Case | Smartsheet
• Prioritizing Requirements - IIBA®
• How to Prioritize Requirements: Techniques, Tools, and Examples
• Break-Even Analysis - Definition, Formula, Example, and Advantages
• [How to Write a Business Case (with Examples & Template to Help) - Pingboard]
• [Cost-Benefit Analysis: A Quick Guide with Examples and Templates]

 A cost-benefits justification is a term that matches management’s request to include the projected costs and benefits to be realized and how those and benefits will be assessed and evaluated in the business case. A cost-benefits justification is a process that compares the costs of implementing a project or a solution with the benefits that it will generate, both in monetary terms. It helps to determine the feasibility, profitability, and return on investment of the project or solution, and to support the decision-making process. A cost-benefits justification also includes the methods and criteria for measuring and evaluating the costs and benefits, such as net present value, internal rate of return, payback period, or cost-benefit ratio12. References:

• Cost-Benefit Analysis: A Quick Guide with Examples and Templates
• Cost-Benefit Analysis: What It Is & How to Do It