Online CBAP Questions Video

 A change-driven approach to business analysis is one that adapts to the changing needs and priorities of the stakeholders and the business environment. It focuses on delivering business value in short iterations, rather than following a fixed and detailed plan. A change-driven approach is often associated with agile methodologies, such as Scrum, Kanban, or XP, which emphasize collaboration, feedback, and continuous improvement. A change-driven approach can help business analysts respond to uncertainty, complexity, and ambiguity, and deliver solutions that meet the customer’s expectations and satisfaction. References:

• Defining Business Analysis, section 1.3.2, page 7
• How to Choose the Right Business Analysis Approach, paragraph 4
• Business Analysis Approach, paragraph 2
• The Agile Business Analysis Approach Means…, paragraph 1
• Defining the Business Analysis Approach in 2023, paragraph 2

According to the BABOK® Guide, the purpose of the Assess Proposed Solution task is to determine how well a proposed solution meets the business need and to identify any gaps, risks, or shortcomings before committing resources to its implementation. This task involves evaluating the solution against the requirements, the solution scope, and the solution acceptance criteria. Paul is performing this task by examining a single solution to determine its business value and feasibility. References: BABOK® Guide v3, Section 6.4: Assess Proposed Solution; CBAP® Handbook, Section 4: Review the Exam Blueprint.

According to the BABOK Guide, textual requirements are one of the forms of specifying and modeling requirements. Textual requirements are written statements that describe the characteristics of the solution in a clear, concise, and consistent manner. Textual requirements typically consist of three components: the capability of the solution, the condition under which the requirement is applicable, and the constraint that may limit the solution. The capability describes what the solution must or should do, the condition describes the situation or scenario in which the requirement is relevant, and the constraint describes the restriction or limitation that may affect the solution’s ability to meet the requirement. For example, a textual requirement for a banking system could be:

The system shall allow customers to withdraw cash from any ATM machine (capability) within the network (condition) up to a maximum of $500 per day (constraint).

References:

• [A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 402, section 10.31.2.11
• Textual Requirement Artifacts - Blueprint Online Help - HelpDocs, paragraph 1
• How to Model Textual Requirements - Formal Mind GmbH, paragraph 2

A plan-driven approach to business analysis follows a sequential and linear process, where each phase must be completed before moving on to the next. This approach requires thorough planning upfront, reducing uncertainties later on. Therefore, communication in a plan-driven approach is likely to be formal, structured, and documented. Formal communication ensures that information is relayed in a clear, consistent, and accurate manner, and that stakeholders are aware of their roles and responsibilities. Formal communication also helps to manage changes, risks, and issues that may arise during the project lifecycle. Formal communication may include written reports, presentations, meetings, emails, and memos. References:

• How to create a business analysis communication plan
• How to Choose the Right Business Analysis Approach
• Plan Business Analysis Approach - iiba.org
• Defining the Business Analysis Approach in 2023 | Free Template