Last Attempt CBAP Questions

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

The change-driven approach is an agile method that focuses on delivering value to the customer in short iterations and adapting to changing requirements. The change-driven approach favors defining requirements through team interaction, as this allows for more collaboration, feedback, and learning among the stakeholders. The change-driven approach also uses minimal documentation and relies on working software as the primary measure of progress. The change-driven approach is suitable for projects that have high uncertainty, complexity, and volatility. References:

• Business Analysis Approach (BA Planning & Monitoring)
• Adapting Your Requirements Practices | StickyMinds
• Requirements definition and management — English - SFIA

The work breakdown structure (WBS) is not an element of the solution scope, but rather a project management tool that decomposes the project scope into manageable deliverables and tasks. The WBS is created after the solution scope is defined and approved, and it helps to plan, monitor, and control the project execution.

The other options are elements of the solution scope, which are:

• B. Implementation approach, which describes how the solution will be delivered, such as the methodology, the phases, the roles and responsibilities, and the quality measures.
• C. Solution scope definition, which describes what the solution is, what it does, and what it does not do, in terms of the features, functions, and characteristics that address the business need.
• D. Dependencies, which describe the relationships and interactions between the solution and other internal or external factors, such as other projects, systems, processes, or stakeholders.

References:

• CBAP® Handbook, page 15, section 4.1.2.3
• BABOK® Guide, page 32, section 3.2.3
• Solution Scope – An Insight
• How To Write a Project Scope in 5 Steps (With Example)

 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