IIBA CBAP Dumps

The stakeholders that were missed in the requirements are the end users. End users are the people who will use the solution or be affected by its outcomes. They are a key source of requirements, as they can provide valuable insights into the needs, expectations, preferences, and pain points of the solution. The BA should elicit requirements from the end users, as well as validate and verify them with their feedback. The BA should also ensure that the end users are involved throughout the project lifecycle, from planning to testing to implementation. The other options are not the stakeholders that were missed, as they are either not directly related to the solution or not the primary source of requirements. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 2: Business Analysis Key Concepts, Section 2.3: Stakeholders, p. 59-60
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 2: Business Analysis Key Concepts, Section 2.3: Stakeholders, p. 28-29
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 4: Elicitation and Collaboration, Section 4.1: Prepare for Elicitation, p. 97-98

A communication plan should consider the preferences of the stakeholders, such as how they like to receive information, how often, and in what format. E-mail may not be the best choice for all stakeholders, especially if they prefer face-to-face meetings, phone calls, or other methods of communication. The BA should also consider the impact, urgency, and confidentiality of the information when choosing the communication channel. The business objectives, retention, and presentation materials are not directly related to the stakeholder analysis, but rather to the communication requirements and strategy. References:

• CBAP Handbook, page 6, section 2.4.4
• [BABOK Guide], page 417, section 10.3.2.3

 In the context of risk assessment, the impact of a risk is often calculated by multiplying the Probability of Occurrence (POC) with the Cost of Impact. For each risk in this scenario:

• Natural disasters: 0.2 * 15,000 = 3,000
• Power surges: 0.5 * 20,000 = 10,000
• Human errors: 0.9 * 3,000 = 2,700
• System security: 0.4 *16,000 =6,400

Power surges have the highest negative impact to value at $10,000.

References: The calculation is based on standard risk assessment practices which involve evaluating both the probability and impact of risks to prioritize them effectively; as per Business Analysis Professional (CBAP) learning documents or resources

Return on investment (ROI) is a financial calculation that measures the profitability of a solution proposal by comparing its benefits and costs. ROI is expressed as a percentage or a ratio of the net benefits (benefits minus costs) to the total costs. ROI can help to determine which solution is worth investing in based on its breakeven point, which is the point where the net benefits equal zero, or the benefits equal the costs. The solution with the highest ROI has the lowest breakeven point, meaning that it recovers its costs faster and generates more net benefits over time. Discount rate is a financial calculation that measures the present value of future cash flows by applying a discount factor that reflects the time value of money and the risk of the investment. Discount rate can help to compare the present values of different solution proposals, but it does not indicate the breakeven point. Net present value (NPV) is a financial calculation that measures the difference between the present value of the benefits and the present value of the costs of a solution proposal. NPV can help to determine which solution has the highest value in today’s terms, but it does not indicate the breakeven point. Internal rate of return (IRR) is a financial calculation that measures the annualized effective compounded return rate of a solution proposal by finding the discount rate that makes the NPV equal zero. IRR can help to determine which solution has the highest return rate, but it does not indicate the breakeven point. References: BABOK Guide v3, Chapter 10: Techniques, Section 10.23: Financial Analysis, p. 529-531; Free CBAP IIBA Actual Exam Questions & Answers, Question 464.

The BA is using this technique to manage stakeholder collaboration. This technique is known as affinity diagram, which is a technique that helps organize and categorize a large number of ideas, issues, or requirements into logical groups based on their natural relationships or common themes. Affinity diagram can help to manage stakeholder collaboration by facilitating brainstorming, encouraging participation, building consensus, and resolving conflicts among the stakeholders. Affinity diagram can also help to elicit, analyze, and prioritize requirements, but that is not the primary purpose of this technique. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Elicitation and Collaboration, Section 4.3: Confirm Elicitation Results, p. 175-176
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 4: Elicitation and Collaboration, Section 4.3: Confirm Elicitation Results, p. 108-109
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 9: Underlying Competencies, Section 9.3: Collaboration and Teamwork, p. 350-351

 Quantitative and qualitative data are two types of data that can help the end users evaluate the effectiveness of a solution. Quantitative data are numerical, measurable, and objective, such as cost, time, scope, quality, and customer satisfaction. Qualitative data are descriptive, subjective, and interpretive, such as feedback, opinions, perceptions, and experiences. By using both types of data, the end users can assess the solution from different perspectives and dimensions, and compare the results with the predefined success criteria for the initiative. References:

• Project Success Criteria Guide, Smartsheet
• 7 Project Success Criteria Examples, Indeed.com
• IIBA BABOK Guide, Section 5.4, Evaluate Solution Performance

Effectiveness is a performance measure that evaluates how well the work products meet the intended goals and objectives. It can be assessed by comparing the actual outcomes with the expected outcomes, and by measuring the degree of stakeholder satisfaction and value realization. Effectiveness can help the BA to determine the quality and impact of the business analysis work, and to identify any gaps or areas for improvement123. References:

• 1: BABOK Guide v3, Chapter 2: Business Analysis Planning and Monitoring, Section 2.5: Plan Business Analysis Performance Improvements
• 2: BABOK Guide v3, Chapter 10: Techniques, Section 10.35: Root Cause Analysis, Section 10.36: Scope Modeling
• 3: Performance Measurement - What Is It, Example, Methods, Types(https://www.wallstreetmojo.com/performance-measurement/)

 A risk-averse organization is one that prefers to minimize or eliminate the exposure to risks, even if it means sacrificing some potential benefits or opportunities. A risk avoidance strategy is one that involves changing the project plan, scope, schedule, or budget to avoid the risk or its impact. A risk avoidance strategy is suitable for a risk-averse organization, as it reduces the uncertainty and the potential negative consequences of the risk. In this scenario, the BA has identified an assumption that has a high degree of uncertainty and may affect the validity of the requirements. The BA has added the assumption to the risk register and performed a risk analysis to handle this situation. If the organization is risk-averse, the BA may use a risk avoidance strategy to modify the requirements or the solution design to eliminate the dependency on the assumption, or to seek more information or evidence to validate the assumption. A risk acceptance strategy is one that involves acknowledging the risk and its impact, but not taking any action to prevent or reduce it. A risk acceptance strategy is suitable for a risk-seeking or risk-neutral organization, or for risks that have low probability or impact. A risk transfer strategy is one that involves shifting the responsibility or ownership of the risk or its impact to a third party, such as a vendor, a partner, or an insurer. A risk transfer strategy is suitable for risks that have high impact but low probability, or for risks that require specialized skills or resources to manage. A risk mitigation strategy is one that involves taking actions to reduce the probability or impact of the risk, such as implementing contingency plans, preventive measures, or backup solutions. A risk mitigation strategy is suitable for risks that have high probability and impact, or for risks that can be controlled or influenced by the project team. References: BABOK Guide v3, Chapter 10: Techniques, Section 10.51: Risk Analysis and Management, p. 567-569; Free CBAP IIBA Actual Exam Questions & Answers, Question 467.

 Scalability is a non-functional requirement that refers to the ability of a system to handle increasing workloads or demands without compromising its performance or functionality. System B supports scalability over System A, as it can process double the number of claims that System A can, and it rarely goes offline. System A, on the other hand, would be at capacity if it were to process all of the company’s claims, and it must go offline for two hours each day. References: The answer can be verified from the Business Analysis Professional (CBAP) learning documents or resources, such as:

• IIBA BABOK Guide, Section 4.2.3, Non-Functional Requirements
• Non-Functional Requirements: Definition, Types, and Examples, ReQtest
• Non-Functional Requirements: Scalability, Software Engineering Stack Exchange

 According to the BABOK® Guide, one of the tasks of the business analyst (BA) is to assess solution performance and value. This involves measuring the actual outcomes and benefits of the implemented solution and comparing them with the expected ones. The BA also identifies any gaps or issues that may affect the solution’s performance or value and recommends actions to address them. One of the actions that the BA can recommend is to remove or minimize any interfaces and activities that do not contribute to the final product either directly or indirectly, as they may cause waste, inefficiency, or complexity. This is consistent with the lean principles of eliminating waste and optimizing value. References: BABOK® Guide v3, Section 7.6: Assess Solution Performance and Value, p. 291-292; BABOK® Guide v3, Section 10.22: Lean, p. 512-513.

 A data flow diagram is a technique that helps to create a high-level overview of a business process by showing the movement and transformation of data between entities and processes. A data flow diagram uses graphical symbols and arrows to represent the sources and destinations of data, the processes that manipulate data, the data stores that store data, and the data flows that transfer data. A data flow diagram can help the BA to understand the current state of the business process, to identify the data requirements and dependencies, and to communicate the data logic and structure to the stakeholders. An entity relationship diagram is a technique that helps to represent the data and information needs of an organization or a solution using graphical or textual symbols and relationships. An entity relationship diagram shows the entities that are relevant to the domain, the attributes that describe the entities, and the relationships that exist between the entities. An entity relationship diagram can help the BA to define and analyze the data requirements, but it does not show the movement and transformation of data between entities and processes. A scope model is a technique that helps to define the boundaries and context of a project or a solution. A scope model shows the elements that are within the scope, the elements that are out of scope, and the interfaces and interactions between the elements. A scope model can help the BA to clarify the scope and objectives of the project or solution, but it does not show the movement and transformation of data between entities and processes. A process model is a technique that helps to represent the activities and tasks that are performed to achieve a specific goal or outcome. A process model shows the sequence and flow of the activities and tasks, the roles and responsibilities of the performers, the inputs and outputs of each activity or task, and the rules and conditions that govern the process. A process model can help the BA to define and analyze the business process, but it does not show the movement and transformation of data between entities and processes. References: BABOK Guide v3, Chapter 10: Techniques, Section 10.18: Data Flow Diagrams, p. 522-524; Section 10.19: Data Modeling, p. 525-527; Section 10.42: Scope Modeling, p. 554-556; Section 10.43: Process Modeling, p. 557-559.

Decision analysis is a technique that helps the BA evaluate and compare different alternatives based on their costs, benefits, and risks, and select the best option that meets the objectives and criteria. In this case, the BA needs to determine if one of the systems (Sys A or Sys B) is better suited to be modified and upgraded, based on the upgrade cost and cost new of each feature. The BA can use the table in the image to calculate the total cost of upgrading or creating new features for each system, and compare them with the expected value and return on investment of each system. The BA can also consider other factors, such as the feasibility, compatibility, reliability, and maintainability of each system, and the preferences and expectations of the stakeholders. By using decision analysis, the BA can make an informed and rational choice that maximizes the value and minimizes the risk of the solution. References:

• IIBA BABOK Guide, Section 10.23, Decision Analysis
• Decision Analysis for the Professional, SmartOrg
• Decision Analysis: Making Justifiable, Defensible Decisions, MindTools

 A business analysis checklist is a technique that helps to ensure that all the required business analysis activities and deliverables are completed and verified. A business analysis checklist can include items such as the scope statement, the stakeholder list, the requirements documentation, the traceability matrix, the validation criteria, the change requests, and the approval signatures. A business analysis checklist can help to mitigate the concern of the project board by providing a clear and comprehensive overview of the business analysis work and its quality. A data model is a technique that helps to represent the data and information needs of an organization or a solution using graphical or textual symbols and relationships. A data model can help to define and analyze the data requirements, but it does not ensure that all the requirements are verified. A use case diagram is a technique that helps to depict the interactions between a system and its actors using graphical symbols and relationships. A use case diagram can help to define and analyze the functional requirements, but it does not ensure that all the requirements are verified. A risk register is a technique that helps to identify, analyze, and manage the uncertainties and threats that may affect the project or the solution. A risk register can help to mitigate the potential impacts of the risks, but it does not ensure that all the requirements are verified. References: BABOK Guide v3, Chapter 10: Techniques, Section 10.8: Business Analysis Checklist, p. 504-505; Section 10.18: Data Modelling, p. 522-524; Section 10.50: Use Case Diagram, p. 564-566; Section 10.51: Risk Analysis and Management, p. 567-569.

The business analysis approach is the set of processes, activities, tasks, deliverables, and techniques that are used to conduct business analysis. The business analysis approach should be aligned with the needs, preferences, and expectations of the stakeholders, as well as the characteristics and constraints of the project and the organization. The level of formality is one of the factors that influences the business analysis approach. It refers to the degree of rigor, detail, and documentation that is required for the business analysis work. The level of formality may vary depending on the type, size, complexity, and risk of the project, as well as the regulatory and governance requirements, the stakeholder involvement, and the organizational culture. In this scenario, the BA is dealing with two main stakeholders that have different levels of formality. The government agency is highly regulated and may require a formal approach that follows strict standards, policies, and procedures, and produces detailed and comprehensive documentation. The private company is less formal and may prefer a flexible and collaborative approach that allows for rapid changes, feedback, and experimentation, and produces minimal and concise documentation. Therefore, the BA’s strategy should be to develop consensus on a tailored approach for formality that balances the needs and expectations of both stakeholders, and that is suitable for the project context and objectives. The BA should facilitate a meeting with the representatives from each entity and discuss the advantages and disadvantages of different levels of formality, and how they can be adapted and customized to meet the project requirements and deliver value. The BA should also consider the impact of the level of formality on the other aspects of the business analysis approach, such as the planning, elicitation, analysis, validation, and management of the requirements and design specifications. The BA should seek to achieve a common understanding and agreement among the stakeholders on the level of formality and the business analysis approach. Option B is incorrect because using a formal approach to appeal to the government entity’s higher authority may not satisfy the needs and preferences of the private company, and may create conflict and dissatisfaction among the stakeholders. Option C is incorrect because employing the standard business analysis level of formality may not be appropriate or effective for the project and the organization, and may not address the specific needs and expectations of the stakeholders. Option D is incorrect because asking the government entity to accept a flexible collaborative approach may not comply with the regulatory and governance requirements, and may create resistance and distrust among the stakeholders. References: BABOK Guide v3, Chapter 2: Business Analysis Planning and Monitoring, Section 2.2: Plan Business Analysis Approach, p. 28-32; Chapter 10: Techniques, Section 10.6: Business Analysis Approach, p. 501-502.

As part of identifying enterprise limitations, the BA should perform a stakeholder impact and operational analysis. This technique involves assessing how the proposed change will affect the stakeholders and the current operations of the enterprise. It can help to identify the potential benefits, costs, risks, and issues of the change, as well as the readiness and resistance of the stakeholders. The BA should consider the impact of the change on the following aspects of the enterprise:

• Strategy and goals
• Processes and policies
• Structure and roles
• Culture and values
• Systems and technology
• Performance and quality

In this case, the BA should analyze how the merger proposal will impact the stakeholders and operations of Manufacturer O, especially in the scenario of Manufacturer K moving headquarters and closing the current Manufacturer O site. The BA should also consider the impact of the regulatory environment and the potential changes in the future. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 5: Strategy Analysis, Section 5.1: Analyze Current State, p. 207-208
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 5: Strategy Analysis, Section 5.1: Analyze Current State, p. 107-108
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 10: Solution Evaluation, Section 10.5: Assess Organizational Readiness, p. 281-282

A BA should identify any potential constraints that may affect the requirements or the solution and communicate them to the relevant stakeholders for resolution. In this case, the policies are a constraint that may prevent the implementation of the requirement or require a change to the policies. The BA should review the constraint with management and seek their guidance on how to proceed. The BA should not modify the policies or the requirements without proper approval or justification. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 5: Requirements Analysis and Design Definition, page 214
• Business Analysis Body of Knowledge (BABOK ®) Guide, Version 3, Section 5.2: Analyze Current State, page 112
• Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 3: Requirements Analysis and Design Definition, Week 2: Analyze Current State, video: “Identify Constraints”

The appropriate model type to assist the stakeholders in testing the performance and visual aspects of requirements 3 through 11 is a usability prototype. A usability prototype is a model that simulates the look and feel of the user interface of the solution, such as the layout, navigation, colors, fonts, and graphics. A usability prototype can help the stakeholders to evaluate the user experience, the ease of use, the accessibility, and the satisfaction of the solution. A usability prototype can also help to identify and resolve any usability issues or defects before the final implementation of the solution. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Requirements Analysis and Design Definition, Section 6.4: Model and Validate Requirements, p. 265-266
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 6: Requirements Analysis and Design Definition, Section 6.4: Model Requirements, p. 161-162
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 10: Solution Evaluation, Section 10.6: Validate Solution, p. 283-284

 The BA can use organizational modeling to highlight the required changes to the structure. Organizational modeling is a technique that involves creating a graphical representation of the roles, responsibilities, relationships, and reporting lines within an organization. It can help to illustrate the current and future states of the organization, identify the gaps and impacts of the change, and communicate the proposed solution to the stakeholders. In this case, the BA can use organizational modeling to show how the process for the first contact resolution for customer issues will be streamlined by having a single point of contact instead of two separate divisions. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 5: Strategy Analysis, Section 5.1: Analyze Current State, p. 207-208
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 5: Strategy Analysis, Section 5.1: Analyze Current State, p. 107-108
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 10: Solution Evaluation, Section 10.5: Assess Organizational Readiness, p. 281-282

An elicitation activity plan is a technique that helps to plan and prepare the activities and tasks that are required to elicit the information and requirements from the stakeholders. An elicitation activity plan defines the objectives, scope, approach, methods, techniques, tools, resources, schedule, and deliverables of the elicitation process. An elicitation activity plan can help the BA to create an output of the initial meeting with experts, as it can help to identify the stakeholders, their roles and responsibilities, their information and communication needs, their availability and preferences, and their expectations and constraints. An elicitation activity plan can also help the BA to select the most appropriate and effective elicitation techniques, such as interviews, workshops, observation, or document analysis, to obtain the relevant and reliable information and requirements from the experts. An entity relationship diagram is a technique that helps to represent the data and information needs of an organization or a solution using graphical or textual symbols and relationships. An entity relationship diagram shows the entities that are relevant to the domain, the attributes that describe the entities, and the relationships that exist between the entities. An entity relationship diagram can help the BA to define and analyze the data requirements, but it is not an output of the initial meeting with experts. A current state flowchart is a technique that helps to create a graphical representation of the activities and tasks that are performed to achieve a specific goal or outcome in the current state of the organization or the solution. A current state flowchart shows the sequence and flow of the activities and tasks, the roles and responsibilities of the performers, the inputs and outputs of each activity or task, and the rules and conditions that govern the process. A current state flowchart can help the BA to understand and document the current state of the delivery process, but it is not an output of the initial meeting with experts. An information management approach is a technique that helps to plan and manage the storage, access, distribution, and retention of the information and requirements throughout the project lifecycle. An information management approach defines the format, structure, level of detail, and quality of the information and requirements, the tools and techniques to be used, the roles and responsibilities of the information and requirements owners and users, and the policies and procedures to be followed. An information management approach can help the BA to ensure the consistency, accuracy, completeness, and security of the information and requirements, but it is not an output of the initial meeting with experts. References: BABOK Guide v3, Chapter 10: Techniques, Section 10.12: Elicitation Activity Plan, p. 513-514; Section 10.19: Data Modeling, p. 525-527; Section 10.43: Process Modeling, p. 557-559; Section 10.14: Information Management Approach, p. 516-517.

 In addition to existing regulations and contracts, the BA also checks the policies of the organization that may constrain the project. Policies are the guidelines or principles that govern the decision making and actions of the organization. They reflect the values, vision, and mission of the organization and provide a framework for achieving its goals and objectives. Policies can also influence the scope, feasibility, and acceptance of the project and its solution. Therefore, the BA should identify and analyze the policies that are relevant to the project and ensure that they are aligned with the requirements and the solution. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 5: Strategy Analysis, Section 5.1: Analyze Current State, p. 206-207
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 5: Strategy Analysis, Section 5.1: Analyze Current State, p. 106-107
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 10: Solution Evaluation, Section 10.3: Assess Enterprise Limitations, p. 277-278

The BA should provide process models as artifacts that can be used organization wide for the long-term. Process models are graphical representations of the activities, inputs, outputs, and interactions of a business process. They can help to document, analyze, improve, and communicate the current and future states of a process. They can also serve as a basis for developing other artifacts, such as requirements, test cases, user manuals, and training materials. Process models can be useful for various stakeholders, such as business users, managers, developers, testers, and trainers, to understand and optimize the business process. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Requirements Analysis and Design Definition, Section 6.4: Model and Validate Requirements, p. 263-264
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 6: Requirements Analysis and Design Definition, Section 6.4: Model Requirements, p. 159-160
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 9: Solution Evaluation, Section 9.5: Assess Organizational Readiness, p. 261-262

A change strategy is a plan that outlines how the project team will manage the transition from the current state to the future state of the system, and how they will address the impacts and risks of the change on the organization and the stakeholders. A change strategy is needed when system A is offline for 3 months, as this will affect the claims processing operations and the user experience. A change strategy should include the following elements:

• Change vision and objectives: This defines the purpose and scope of the change, and the expected outcomes and benefits of the system upgrade.
• Change readiness assessment: This evaluates the current level of awareness, willingness, and ability of the organization and the stakeholders to adopt the change, and identifies any gaps or barriers that need to be addressed.
• Change impact analysis: This identifies and analyzes the potential effects of the change on the business processes, roles and responsibilities, policies and procedures, systems and tools, and culture and behavior of the organization and the stakeholders.
• Change communication plan: This specifies the key messages, channels, methods, and frequency of communication with the organization and the stakeholders, and how to solicit and incorporate feedback and input.
• Change training plan: This defines the learning objectives, content, delivery modes, and evaluation methods of the training programs that will help the organization and the stakeholders acquire the necessary knowledge and skills to use the upgraded system.
• Change management roles and responsibilities: This clarifies the roles and expectations of the project team, the sponsors, the champions, the change agents, and the end users in the change process, and how they will collaborate and coordinate with each other.
• Change monitoring and evaluation plan: This establishes the metrics, indicators, and tools that will measure the progress and performance of the change process, and how to report and act on the results.

References:

• IIBA BABOK Guide, Section 5.6, Define Change Strategy
• Change Management Strategy: A Guide with Best Practices, Smartsheet
• How to Develop a Change Management Strategy, Indeed

The BA presented an opportunity to increase efficiencies by simplifying the process of shipping to new countries and reducing the dependency on IT. By eliminating the need to maintain different variations of ship-to-country and location-to-route for various freight carriers, the BA enabled the business to save time and resources, and avoid potential errors or delays. This is an example of how a BA can add value to the business by identifying and proposing solutions that improve the current state and address the root causes of the problems. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 2: Business Analysis Planning and Monitoring, page 50
• Business Analysis Body of Knowledge (BABOK ®) Guide, Version 3, Chapter 6: Solution Evaluation, section 6.5.2: Assess Enterprise Limitations, page 176
• Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 4: Business Analysis Planning and Monitoring, Week 2: Plan Business Analysis Approach, video: “Solution Evaluation”

A stakeholder engagement approach is a plan that describes how the BA will interact with the stakeholders, identify their needs and expectations, and address their concerns and issues. A stakeholder engagement approach can help the BA avoid disagreements and conflicts by ensuring that the stakeholders are involved and informed throughout the business analysis process, and that their feedback and input are considered and incorporated. A stakeholder engagement approach can also help the BA build trust and rapport with the stakeholders, and manage their expectations and influence levels. By following a stakeholder engagement approach, the BA can ensure that the business analysis approach and the budget estimates are aligned with the stakeholder needs and agreed upon by all the relevant parties. References:

• IIBA BABOK Guide, Section 3.2, Plan Stakeholder Engagement
• Five-Step Approach to Stakeholder Engagement, BSR
• 5 steps to creating a stakeholder engagement plan (with template), Asana

Before the BA can proceed with any analysis of the features, they need to confirm that the feature requests are valid and aligned with the product vision and goals. Customer support calls may not reflect the actual needs and preferences of the target market, and may include requests that are out of scope or inconsistent with the product strategy. Therefore, the BA should first validate the feature requests with the product owner and other stakeholders, and eliminate any irrelevant or invalid ones. References:

• BABOK Guide v3, section 7.2.2.1: “The business analyst validates that the requirements and designs are aligned with the business need and the solution scope.”
• Guide to building a product roadmap (with template and examples), section “How to create a product roadmap”: “The first step in creating a product roadmap is to define the product vision. This is the overarching goal or purpose of the product, and it should guide all subsequent decisions and actions.”

The BA should recommend implementing a system that coordinates order processing activities in advance with all trips. This approach aims to ensure that orders are ready for loading when the trucks arrive, eliminating the waste of both the truck’s and driver’s time. By aligning order preparation with delivery schedules, the distributor can optimize resource utilization and improve efficiency. References: I need to search for specific references from Business Analysis Professional (CBAP) Learning documents or resources to provide an exact source.

The potential success rate of the mortgage origination process can be calculated by subtracting the percentage of total rejects from 100%. The current success rate is 70%, which means the current percentage of total rejects is 30%. If the verification rejects (8.4% of the total transactions) were to be reduced by 50%, there would be only 4.2% verification rejects remaining. This would decrease the percentage of total rejects to (30% - 4.2%) = 25.8%. Therefore, the potential success rate would be (100% - 25.8%) = 74.2%. However, this answer does not account for the effect of the documentation checklists, which would also reduce the documentation rejects (12.2% of the total transactions). Assuming that the documentation checklists would eliminate all the documentation rejects, the percentage of total rejects would further decrease to (25.8% - 12.2%) = 13.6%. Therefore, the potential success rate would increase to (100% - 13.6%) = 86.4%, which can be rounded to 86%.

References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 5: Solution Assessment and Validation, p. 211-212
• Certified Business Analysis Professional™ (CBAP®) Specialization, Course 4: Business Analysis: Solution Evaluation, Week 2: Solution Performance Assessment, Video: Solution Performance Metrics
• Basic Math Operations, Khan Academy

The lead BA is trying to improve the business analysis practices by finding out the root causes of the problems and inefficiencies in the current state. By measuring the time spent on planned and unplanned activities, the lead BA can identify the typical missing or wasteful activities that are affecting the quality and timeliness of the deliverables. For example, the lead BA may discover that the BAs are spending too much time on rework, clarifications, or scope changes due to poor elicitation, validation, or prioritization techniques. The lead BA can then propose solutions to address these issues and enhance the business analysis performance and value. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 2: Business Analysis Planning and Monitoring, page 57
• Senior Business Analysis Certification CBAP® | IIBA®, Business Analysis Planning and Monitoring, page 5

An activity diagram is a technique that is used to model the dynamic aspects of a system or a domain. It shows the sequence and conditions of the actions (or activities) that are performed by the actors or components involved in a business process or a use case. An activity diagram can also show the inputs, outputs, and resources required for each action, as well as the exceptions and alternative paths that may occur. An activity diagram can help to identify and analyze the business processes that need to be performed and managed in the future state of the solution. References: The answer can be verified from the following sources:

• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 3, Chapter 9: Data Modeling, p. 326-331; Chapter 10: Data Flow Diagrams, p. 336-339; Chapter 10: Activity Diagrams, p. 340-343.
• Business Analysis for Practitioners: A Practice Guide, Chapter 5: Requirements Analysis and Design Definition, p. 125-126, 131-132.

 Risk analysis is the type of analysis that the BA can use to alleviate the stakeholders’ concerns with the level of uncertainty they are willing to accept with the solution. Risk analysis is the process of identifying, assessing, and prioritizing the potential threats and opportunities that may affect the achievement of the business objectives or the delivery of the solution. Risk analysis can help the BA to understand the sources, causes, and impacts of uncertainty, and to communicate them to the stakeholders in a clear and transparent way. Risk analysis can also help the BA to propose and implement appropriate risk responses, such as avoidance, mitigation, transfer, or acceptance, to reduce the negative effects or enhance the positive effects of uncertainty. The other options are not the best types of analysis for this purpose, as they are more focused on identifying and measuring the gaps, costs, benefits, or specifications of the solution, rather than the uncertainty. References: Risk Analysis and Management, CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, BABOK Guide

Interface analysis is a technique that identifies and specifies the information that is exchanged between systems or system components. It defines the communications protocol, data format, and timing of the information exchange. Interface analysis is useful for designing and documenting the interactions between the PS and other systems. It can also help to identify potential issues or risks related to the integration of the systems.

Vertical prototyping is a technique that creates a working model of one or more aspects of a solution, such as the user interface, functionality, or performance. It is used to validate the requirements and design of the solution, and to obtain feedback from stakeholders. It is not directly related to defining the communications protocol between the systems.

Concept modelling is a technique that defines the terms and concepts relevant to a domain or a problem. It establishes a common vocabulary and understanding of the domain among the stakeholders. It is not focused on the technical details of the system interactions.

System analysis is a broad term that refers to the process of studying and understanding the current or desired state of a system. It involves identifying the system components, functions, inputs, outputs, and relationships. It is not a specific technique for defining the communications protocol between the systems. References:

• [A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3], Chapter 10: Techniques, pp. 402-403, 414-415, 420-421, 424-425.
• [Business Analysis for Practitioners: A Practice Guide], Chapter 5: Requirements Analysis and Design Definition, pp. 123-124, 133-134, 140-141, 144-145.

A capability-centric view is a type of view that analyzes the current state of an organization based on its capabilities, which are the abilities and skills that enable the organization to achieve its goals and objectives. A capability-centric view helps to identify the strengths and weaknesses of the organization, as well as the opportunities and threats in the external environment. By proposing a change that leverages the existing capabilities of the organization, such as manufacturing vending machines, and adapts them to a new market segment, such as mobile device users, the BA used a capability-centric view to analyze the current manufacturer’s state.

The other options are not correct because they do not match the type of view that the BA used. A data-centric view is a type of view that analyzes the current state of an organization based on its data, which are the facts and information that support the organization’s operations and decision-making. A data-centric view helps to identify the sources, quality, and usage of data, as well as the data requirements and gaps. A process-centric view is a type of view that analyzes the current state of an organization based on its processes, which are the activities and tasks that transform inputs into outputs. A process-centric view helps to identify the inputs, outputs, resources, and performance of processes, as well as the process improvements and optimizations. A people-centric view is a type of view that analyzes the current state of an organization based on its people, which are the stakeholders who are involved in or affected by the organization’s activities and outcomes. A people-centric view helps to identify the roles, responsibilities, relationships, and needs of the people, as well as the people management and engagement strategies.

References:

• [BABOK Guide v3], Section 6.1: Analyze Current State, p. 158-159
• Certified Business Analysis Professional™ (CBAP®) Specialization, Course 3: Business Analysis: Strategy Analysis, Week 1: Strategy Analysis, Video: Current State Analysis
• What is Strategic Analysis? 8 Best Strategic Analysis Tools + Examples, Blog Post, July 2023

The CEO’s executive decision to start and complete the top 25 revenue-producing stores in the first year shows a risk-seeking or risk-taking attitude. This means that the CEO is willing to accept higher risks for higher rewards, and sees risks as opportunities rather than threats. The CEO is not avoiding, mitigating, or neutral to the risks involved in the remodeling project, but rather embracing them and pursuing them aggressively. This may result in increased revenue and customer satisfaction, but also exposes the organization to potential losses and disruptions. References:

• Risk Attitude in Project Management: Definition, Types & Example, Web Article, August 2022
• Risk Appetite vs. Risk Tolerance: What is the Difference?, Web Article, October 2022
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 3: Strategy Analysis, p. 95-96
• Certified Business Analysis Professional™ (CBAP®) Specialization, Course 3: Business Analysis: Strategy Analysis, Week 1: Strategy Analysis Overview, Video: Risk Analysis

Lessons learned is a technique that involves identifying and documenting the knowledge gained from a project or an activity, and sharing it with relevant stakeholders. Lessons learned can include the successes, failures, best practices, and improvement opportunities that occurred during or after the project or activity. Lessons learned can help the BA to understand the stakeholders’ level of satisfaction, to offer them an opportunity to help improve the working relationships, and to apply the learned knowledge to future projects or activities. The other options are not the best techniques for this purpose, as they are more focused on identifying and managing risks, generating and evaluating ideas, or engaging stakeholders in a fun and creative way. References: CBAP Handbook, CBAP Study Guide, BABOK Guide

The lead BA should track approvals at the level of individual requirements, as this is the first step to address the root cause of the problem, which is the lack of agreement and clarity on the requirements. By tracking approvals at the level of individual requirements, the lead BA can identify which requirements are causing the most disagreement or confusion, and focus on resolving them with the relevant stakeholders. This can also help to reduce the number of reviews and sign-offs needed, as well as the time and effort spent on them. Tracking approvals at the level of individual requirements can also provide objective evidence of the progress and quality of the requirements, and support the communication and collaboration among the stakeholders.

The other options are not the best actions to take first. Escalating the problem to the executive management may be necessary at some point, but it is not the first thing to do, as it may create more conflict and pressure, and undermine the lead BA’s credibility and authority. Setting limits on duration of sign-offs and the number of reviews may be helpful to manage the expectations and deadlines, but it does not address the underlying issue of the requirements quality and agreement. Offering the stakeholders incentives to sign off documents sooner may be counterproductive, as it may encourage hasty or superficial approvals, and compromise the validity and value of the requirements. References: The answer can be verified from the following sources:

• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 3, Chapter 6: Requirements Life Cycle Management, p. 202-203, 207-208, 211-212.
• Business Analysis for Practitioners: A Practice Guide, Chapter 4: Requirements Life Cycle Management, p. 97-98, 101-102, 105-106.

• The BA should not simply adopt the structure of the solution consultants’ requirements catalog © or the corporate standard (D), because they may not be suitable for the branch’s specific needs and preferences. The BA should analyze the existing structures and compare them with the branch’s definitions of user roles, tasks, and features, as well as with the best practices for specifying customization requirements.
• The BA should not devise a structure that best fits the branch’s definition of user roles (A), because this may not capture all the relevant aspects of the customization requirements, such as the system features, the user tasks, the dependencies, the constraints, the acceptance criteria, etc. The BA should consider all these factors and use a comprehensive and consistent structure that facilitates communication and understanding among the stakeholders.
• The BA should explore and apply best practices for specifying this type of requirements (B), because this will help the BA to create a clear, complete, and accurate specification that meets the expectations of the sponsor, the solution consultants, and the PGA staff. The BA should also ensure that the structure of the specification is aligned with the branch’s standards and conventions, and that it supports the project objectives and scope.

Verification is the process of evaluating the stated requirements to ensure that they are well-formed, consistent, complete, correct, and aligned with the organizational standards for business analysis. Verification is usually done by the BA or a peer reviewer before presenting the requirements to the stakeholders for validation or acceptance. Verification helps to ensure the quality and accuracy of the requirements, and to avoid errors, ambiguities, or misunderstandings. The other options are not the states that the BA is attempting to move the requirements into, as they are more related to the evaluation of the requirements against the business need, stakeholder expectations, or solution design. References: CBAP Handbook, CBAP Study Guide, BABOK Guide

• future state will
• be defined at a level of detail that:
• • allows for competing strategies to achieve the future state to be identified
• and assessed,
• • provides a clear definition of the outcomes that will satisfy the business
• needs,
• • details the scope of the solution space,
• • allows for value associated with the future state to be assessed, and
• • enables consensus to be achieved among key stakeholders.
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 3, Chapter 5: Strategy Analysis, p. 176-177; Chapter 10: Root Cause Analysis, p. 356-359.
• Business Analysis for Practitioners: A Practice Guide, Chapter 5: Requirements Analysis and Design Definition, p. 122-123, 129-130.

• Benchmarking and market analysis are techniques that involve comparing the performance and practices of an organization with those of its competitors or similar entities in order to identify areas for improvement or opportunities for growth1234
• The BA used benchmarking and market analysis to understand why the promotions were not being viewed by looking into other similar companies and how they targeted their promotions to their customers’ industries. The BA also surveyed the pilot customers to get their feedback and preferences on the site and the promotions.
• Use cases and scenarios are techniques that involve defining the functional requirements of a system or software by describing how a user interacts with it to achieve specific goals and how the system responds to those interactions5678
• The BA did not use use cases and scenarios to understand why the promotions were not being viewed because this technique is not suitable for analyzing the behavior and preferences of the customers or the effectiveness of the promotions.
• Observation is a technique that involves watching and listening to the activities and interactions of people or systems in order to gather information and insights910111213
• The BA did not use observation to understand why the promotions were not being viewed because this technique would require direct access to the customers and their usage of the site, which may not be feasible or ethical.
• Data mining is a technique that involves analyzing large data sets to discover patterns and trends that can provide useful information or insights141516
• The BA did use data mining to understand why the claims were not being reduced by examining the documentation of the claims and finding the common factors that caused them. However, this technique was not used to understand why the promotions were not being viewed, which was the main question.

Performance variance is the difference between the actual and expected results of a business activity or process. In this case, the business sponsor expected that the promotions would be viewed by at least 30% of the customers and that they would help reduce claims. However, the actual results showed that only 5% of the customers viewed the promotions and that claims increased by 20%. The business sponsor wanted to understand the reasons for this discrepancy and how to improve the effectiveness of the promotions.

The activity that the BA should do to determine which stores will be the first to start the renovations is to perform document analysis for stores annual records. Document analysis is a technique that involves reviewing existing documentation to elicit relevant information for the business analysis purpose. In this case, the BA needs to analyze the annual records of each store to identify the top 25 revenue-producing stores, as per the CEO’s decision. This would provide the BA with objective and reliable data to prioritize the stores for the renovation project. The other options are not as effective or efficient as document analysis, because they rely on subjective or incomplete information from the store managers, who may have different opinions or preferences on which stores should be renovated first. References:

• [BABOK Guide v3], Section 10.18: Document Analysis, p. 386-387
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Requirements Elicitation and Collaboration, p. 149-150
• Certified Business Analysis Professional™ (CBAP®) Specialization, Course 2: Business Analysis: Requirements Elicitation and Analysis, Week 1: Elicitation Techniques, Video: Document Analysis

This is an example of a corrective action, which is an action taken to bring the project performance back in line with the plan. The schedule performance index (SPI) is a measure of schedule efficiency, expressed as the ratio of earned value to planned value. An SPI of less than 1 indicates that the project is behind schedule. In this case, the SPI was 0.87, which means that the project was only 87% as far along as it should have been at milestone 6. To correct this situation, three project team members worked overtime to catch up with the planned schedule. This is a corrective action because it addresses an existing problem and aims to eliminate the root cause of the deviation. References: Schedule Performance Index (SPI) for PMP® Exam Prep, CBAP Training and Exam Preparation - IIBA Endorsed Course, CBAP Step-by-Step Application Process Guide

An operational assessment is an input that is required to perform the assessment of enterprise limitations. An operational assessment is a technique that evaluates the current state of the business operations and identifies the gaps, issues, and opportunities for improvement. An operational assessment can help to determine how the solution will affect the existing business processes, policies, procedures, roles, and responsibilities, and how these factors may limit the value realization of the solution. An operational assessment can also help to identify the dependencies, assumptions, constraints, risks, and issues that may arise from the implementation of the solution and how they can be addressed or mitigated.

The other options are not inputs for the assessment of enterprise limitations, but rather outputs or outcomes of the task. Potential value is the expected benefit that the solution will provide to the enterprise and the stakeholders, and it is determined by comparing the current state and the future state of the enterprise. Solution performance analysis is a technique that measures and evaluates the actual performance of the solution against the expected performance and the business objectives. Organizational structure is the arrangement of the roles, responsibilities, and relationships within the enterprise, and it may be affected or changed by the solution.

References:

• [BABOK Guide v3], Section 8.4: Assess Enterprise Limitations, p. 206-207
• Measure Solution Performance, Task Card: Assess Enterprise Limitations, p. 2
• How to assess enterprise limitations – The Functional BA, Blog Post, November 2019

 The BA is performing an enterprise assessment, which is the process of evaluating the current state and capabilities of the enterprise in relation to the desired future state and the proposed solution. An enterprise assessment can include reviewing the existing processes, tools, systems, culture, structure, and strategy of the enterprise, and identifying their strengths, weaknesses, opportunities, and threats. An enterprise assessment can help the BA to determine the feasibility, readiness, and risks of adopting a potential solution, and to recommend the appropriate change strategy and transition plan. The other options are not the best answers, as they are more specific types of assessments that focus on a particular aspect of the enterprise, such as the stakeholders, the organization, or the operations. References: CBAP Handbook, CBAP Study Guide, BABOK Guide

The new success rate of the mortgage closure process can be calculated by subtracting the percentage of total rejects from 100%. The current success rate is 80%, which means the current percentage of total rejects is 20%. If the documentation rejects (10% of the total transactions) are eliminated by the use of documentation checklists, there would be no documentation rejects remaining. This would decrease the percentage of total rejects to (20% - 10%) = 10%. Therefore, the new success rate would be (100% - 10%) = 90%. References: The answer and explanation are derived based on logical reasoning and calculations from the data provided in the question, as well as the following sources:

• Process Improvement Steps - Process Improvement Guide - Planview, Web Article, January 2023
• 7 Types of Process Improvement Methodologies [2023] • Asana, Web Article, January 2023
• Certified Business Analysis Professional™ (CBAP®) Specialization, Online Course, December 2023

 Completeness is one of the characteristics of good requirements, along with clarity, consistency, correctness, feasibility, testability, traceability, and prioritization. Completeness means that the requirements specify everything that is necessary and relevant for the solution, and that there are no gaps, omissions, or ambiguities in the requirements. A BA can ensure completeness by using various techniques, such as:

• Reviewing the requirements with stakeholders and subject matter experts to verify that they cover all the business needs and objectives, and that they are aligned with the solution scope and vision
• Validating the requirements against the business case, the project charter, and other relevant documents to confirm that they are consistent and coherent with the project goals and deliverables
• Analyzing the requirements for dependencies, assumptions, constraints, risks, and issues, and documenting them appropriately
• Using models, diagrams, and prototypes to illustrate the requirements and identify any missing or unclear aspects
• Applying quality standards and criteria to evaluate the requirements and ensure that they meet the expectations and requirements of the stakeholders

By ensuring completeness, a BA can avoid missing, inconsistent, and contradictory requirements that could lead to confusion, errors, rework, delays, and dissatisfaction among the stakeholders.

References:

• [BABOK Guide v3], Section 4.5: Specify and Model Requirements, p. 120-121
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Requirements Analysis, p. 153-154
• Certified Business Analysis Professional™ (CBAP®) Specialization, Course 2: Business Analysis: Requirements Analysis and Design Definition, Week 1: Requirements Analysis and Design Definition, Video: Characteristics of Good Requirements

 Business architecture is the description of how an organization creates, delivers, and captures value for its stakeholders. It includes the business model, the value proposition, the value streams, the capabilities, and the organizational structure of the organization. By evaluating the business architecture, the BA can help determine the value of the project in relation to the current state and the desired future state of the organization. The BA can also identify the gaps and opportunities for improvement that the project can address. References:

• IIBA BABOK Guide v3, Section 2.2.1: Business Architecture
• [IIBA Business Analysis Competency Model], Section 3.1.1: Business Architecture Knowledge

Tracing requirements is a task that involves identifying and documenting the relationships among requirements, stakeholders, solution components, and other artifacts. Tracing requirements can help the BA to discover the issues of missing or unsupported functionality, as it allows the BA to track the origin, allocation, dependencies, and impact of each requirement. By tracing requirements, the BA can ensure that the requirements are aligned with the business need and objectives, and that they are implemented and verified in the solution. The other options are not the tasks that the BA used to discover the issues, as they are more related to the definition, elicitation, or evaluation of the requirements, rather than the tracing of the requirements. References: Task: Trace Requirements, CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, BABOK Guide

A change in the requirement is a situation where the requirement is different from what was originally agreed upon by the stakeholders. This can happen due to various reasons, such as changing business needs, stakeholder feedback, regulatory changes, or technical constraints. To assess the change, the BA needs to conduct an impact analysis using traceability, which is a technique that involves identifying and documenting the relationships among requirements, stakeholders, solution components, and other artifacts. Traceability can help the BA to determine the scope, cost, schedule, quality, and risk implications of the change, and to communicate them to the relevant stakeholders for approval or rejection. The other options are not the best actions for assessing the change, as they are more suitable for different purposes, such as closing a defect that is not a defect, evaluating the potential threats and opportunities of the change, or finding the underlying cause of the defect. References: CBAP Handbook, CBAP Study Guide, BABOK Guide

 This requirement implies that the new web-based system will provide faster and easier access to the company’s financial information, which is an improvement over the current client-based system.

According to the CBAP competencies, one of the skills required for business analysis planning and monitoring is to guide practice in performing stakeholder analysis1. Stakeholder analysis is the process of identifying and assessing the needs, interests, and influence of stakeholders on a project or initiative2. One of the outputs of stakeholder analysis is a stakeholder list, which identifies the key stakeholders and their roles, responsibilities, and expectations3. A stakeholder list can also include information on the potential risks and issues that may arise from stakeholder involvement or lack thereof4. Therefore, developing a risk plan to anticipate negative behavior from the Director of Human Resources is a valid activity that is included in performing a stakeholder analysis. This can help the team to mitigate the impact of the Director’s bitterness and resistance on the project’s success.

The other options are not included in performing a stakeholder analysis. Comparing the expertise of the Director of Human Resources to other stakeholders is not relevant to the stakeholder analysis process, as it does not help to understand the Director’s needs, interests, or influence. Recommending excluding the Director of Human Resources as a stakeholder is not a good practice, as it may create more conflict and resentment, and ignore the Director’s legitimate role and authority in the project. Implementing all of the Director of Human Resources suggestions to relieve tension is not a realistic or effective strategy, as it may compromise the quality and feasibility of the project, and disregard the needs and interests of other stakeholders. References:

• 1: CBAP Competencies - International Institute of Business Analysis
• 2: BABOK Guide v3, Section 2.2.2: Conduct Stakeholder Analysis
• 3: BABOK Guide v3, Section 2.2.2.3: Outputs
• 4: CBAP / CCBA Certified Business Analysis Study Guide, Chapter 3: Business Analysis Planning and Monitoring, p. 83

The timing of business analysis work is the most impacted element by the organization’s change from a waterfall methodology to an agile approach. This is because the waterfall and agile methods have different ways of planning, executing, and delivering business analysis work.

In a waterfall method, the business analysis work is done in a sequential and linear manner, following predefined phases and milestones. The requirements are elicited, analyzed, and documented upfront, before the design and development stages. The changes to the requirements are minimized and controlled, and the deliverables are verified and validated at the end of the project. The timing of business analysis work is fixed and predictable, but it may also be rigid and inflexible.

In an agile method, the business analysis work is done in an iterative and incremental manner, following short cycles of development and feedback. The requirements are elicited, analyzed, and documented continuously, along with the design and development stages. The changes to the requirements are welcomed and managed, and the deliverables are verified and validated throughout the project. The timing of business analysis work is variable and adaptable, but it may also be challenging and uncertain.

Therefore, the business analyst (BA) needs to adjust the timing of business analysis work according to the agile method, which involves:

• Breaking down the requirements into smaller and manageable chunks, called user stories or features, that can be delivered in each iteration or sprint
• Prioritizing and refining the requirements backlog, which is the list of all the requirements that need to be addressed in the project, based on the business value and stakeholder feedback
• Collaborating and communicating with the project team and stakeholders frequently and effectively, using various techniques and tools, such as daily stand-ups, retrospectives, demos, etc.
• Adapting and responding to the changing requirements and business needs, using various techniques and tools, such as change requests, impact analysis, traceability, etc.

References:

• [BABOK Guide v3], Section 2.4: Plan Business Analysis Work, p. 24-27
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 2: Business Analysis Planning and Monitoring, p. 43-44
• Certified Business Analysis Professional™ (CBAP®) Specialization, Course 1: Business Analysis: Planning and Monitoring, Week 1: Introduction to Business Analysis Planning and Monitoring, Video: Waterfall vs. Agile
• Agile vs. Waterfall | Pros, Cons, and Key Differences - ProductPlan

 A business case is a document that provides the justification for initiating a change initiative, such as a project or a program. It describes the business need, the expected benefits, the costs, the risks, and the alternatives of the proposed solution. A business case is usually the first deliverable that a team of BAs produces to present to management for approval. It helps to secure the support and resources needed for the change initiative, and to align it with the strategic objectives of the organization. The other options are not the first steps that the team should do, as they are more relevant for later stages of the business analysis process, such as planning, analysis, and design. References: CBAP Handbook, CBAP Study Guide, BABOK Guide

Scope is the important factor that the BA needs to understand to ensure the workshop remains focused on the topic in question. Scope is the boundary or extent of the business analysis effort, which defines what is included and excluded from the change initiative. Scope also provides the context and direction for the requirements elicitation and analysis activities. By understanding the scope, the BA can plan and facilitate the workshop effectively, and avoid any irrelevant, out-of-scope, or conflicting discussions or issues. The other options are not the best answers, as they are not as critical as scope for keeping the workshop focused, although they may be related to the topic in question. For example, future state is the desired outcome of the change initiative, assets are the resources or capabilities of the enterprise, and risk register is the document that records the identified risks and their responses. References: CBAP Handbook, CBAP Study Guide, BABOK Guide

A process diagram is a kind of asset that the BA should provide to fully specify the approval requirement. A process diagram is a visual representation of the sequence of activities and decisions involved in a business process or a system. It shows the inputs, outputs, roles, tasks, events, conditions, and flows that occur in each step of the process. A process diagram can help the BA specify the approval requirement by showing:

• Which incident-related activities require approval and confirmation
• Who are the authorized personnel for each activity
• What are the criteria and triggers for approval and confirmation
• What are the outcomes and exceptions of approval and confirmation

A process diagram can also help the EA compare the existing application and the new application by showing the similarities and differences in the process flows, data sources, and user interfaces.

References:

• [BABOK Guide v3], Section 10.28: Process Modeling, p. 410-412
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Requirements Elicitation and Collaboration, p. 161-163
• Certified Business Analysis Professional™ (CBAP®) Specialization, Course 2: Business Analysis: Requirements Elicitation and Analysis, Week 4: Requirements Analysis Techniques, Video: Process Modeling

The solution approach is the process of defining the most feasible and appropriate way to implement a change that addresses a business need. It involves identifying and evaluating different options for creating or acquiring new capabilities, such as products, services, processes, or systems, that will deliver value to the stakeholders and solve the business problem. The solution approach also considers the constraints, risks, assumptions, and dependencies that may affect the solution. The solution approach provides the basis for defining the solution scope, which specifies the features and functions of the solution, and the project scope, which specifies the work required to deliver the solution123.

The other options are not correct definitions of the solution approach. Option A is the definition of scope change control, which is the process of managing and documenting the changes to the product scope as approved by the project stakeholders. Option C is the definition of a risk, which is an uncertain event or condition that may have a positive or negative impact on the project objectives. Option D is the definition of decomposition, which is a technique that breaks down the project scope into smaller deliverables; each deliverable is subdivided repeatedly until the deliverable cannot or should not be broken down any further4. References: 1: BABOK® Guide v3, section 11.2 Define Solution Approach, page 402 2: CBAP® Exam Prep Study Guide, chapter 9, page 323 3: How toChoose the Right Business Analysis Approach 4: PMBOK® Guide, Sixth Edition, section 5.4.2.1 Decomposition, page 156

The all out approach is a timeboxing or budgeting technique that involves excluding all the requirements for a start and then including the ones that can be implemented within the constrained time or budget. Henry is using this approach by removing the requirements from the allowed list until he meets the budget limit. This is different from the all in approach, which involves including all the requirements necessary for the solution and then removing or postponing the ones that will cause the project to exceed the deadline or budget. The parametric approach is a cost estimation technique that uses statistical relationships between historical data and other variables. The selective approach is a prioritization technique that involves ranking the requirements based on their value and urgency. References:

• CBAP Certification Study Guide v3.0, p. 223
• BABOK Guide v3, p. 156

 A dependency is a relationship or a condition that affects the completion or the quality of a task or an activity. A dependency can be internal or external, mandatory or discretionary, or positive or negative. In this case, the inspector’s signoff on the initial deliverables is a dependency because it is a condition that must be met before the task can be completed. The inspector’s signoff is an external and mandatory dependency, as it involves an outside party and it is required by the project scope or contract. A dependency is not the same as an assumption (A), which is a factor that is considered to be true without proof, a milestone ©, which is a significant point or event in the project, or a constraint (D), which is a factor that limits the options or performance of the project. References:

• What is a Dependency in Project Management? - Wrike, paragraph 1
• Project Dependencies: Types, Examples, and Tips for Project Managers, paragraph 1
• CBAP Certification Study Guide v3.0, Chapter 4: Requirements Life Cycle Management, Section 4.3: Trace Requirements, page 4-10
• [A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 402, section 10.31.3.1

 Videoconferencing is a communication technique that allows business analysts to interact with stakeholders who are not collocated. It enables real-time audio and visual communication, which can facilitate collaboration, feedback, and decision making. Videoconferencing can also help build rapport and trust among stakeholders, as well as reduce travel costs and time. Videoconferencing is one of the many communication techniques that business analysts can use to elicit information and collaborate with stakeholders in different geographical locations1234. References: 1: How to create a business analysis communication plan - Lucidchart 2: Business Analysis Techniques: Eliciting Information and Collaborating with Stakeholders 3: Key sets of BA: analysis andcommunication techniques - Exposit 4: Communication strategy for stakeholder engagement – SustaiNet

 Requirements prioritization is the process of ranking the requirements in the order of their importance or value to the stakeholders and the solution. Requirements prioritization helps to ensure that the most critical and beneficial requirements are implemented first, and that the project focuses on delivering the maximum value to the stakeholders within the available time and resources. Requirements prioritization also helps to manage the scope, schedule, budget, and quality of the project, as well as to handle changes and risks effectively123. References: 1: Five Requirements Prioritization Methods1 2: What is Requirements Prioritization?2 3: The 6 Most Important Requirements Practices3

 A plan-driven approach to business analysis is characterized by a high degree of upfront planning, detailed documentation, and formal processes. In this approach, the requirements are captured using standardized templates that provide a consistent and comprehensive format for describing the business needs, objectives, and specifications. The templates may include sections such as scope, assumptions, constraints, risks, acceptance criteria, and traceability. The templates are usually predefined by the organization or the project management office, and they help to ensure the quality, clarity, and completeness of the requirements. The templates also facilitate the communication, verification, and validation of the requirements among the stakeholders.

References:

• Plan Business Analysis Approach - iiba.org, page 1
• How to Choose the Right Business Analysis Approach, paragraph 4
• Business analysis approach planning – The Functional BA, paragraph 2

Scenario and uses cases and user stories are conduct stakeholder analysis techniques that identify stakeholder roles that may serve as a useful starting point for identifying actors and roles. These techniques describe how stakeholders interact with the solution or the business process, and what their goals, needs, and expectations are. By creating scenarios and use cases and user stories, the business analyst can identify the primary and secondary stakeholders, as well as their roles and responsibilities. These techniques can also help to elicit, validate, and prioritize the requirements, as well as to communicateand collaborate with the stakeholders1234. References: 1: Scenarios, Use Cases, and User Stories1 2: Business Analysis Techniques: Eliciting Information and Collaborating with Stakeholders2 3: Use Cases and Scenarios3 4: User Stories4

An assumption is something that is believed to be true or certain to happen, without proof. Assumptions are often used to fill in the gaps of incomplete or uncertain information, and they can affect the analysis of the current and future states. In this question, the project manager is assuming that her project team members have a certain skill, without verifying it. This is an example of an assumption that should be identified and validated as part of the assessment of capability gaps.

The other options are not assumptions, but rather:

• B. A constraint, which is a restriction or limitation that affects the performance or outcomes of a project or solution.
• C. A requirement, which is a condition or capability needed by a stakeholder to solve a problem or achieve an objective.
• D. A risk, which is an uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project or solution objectives.

References:

• CBAP® Handbook, page 14, section 4.1.2.2
• BABOK® Guide, page 30, section 3.2.1
• CBAP / CCBA Certified Business Analysis Study Guide, page 94, section 3.2.1

The business analysis approach is a plan that describes how the business analysis activities will be performed, including the deliverables, the team roles, the analysis techniques, the communication methods, the change management process, and the stakeholder engagement strategy. The business analysis approach does not define the requirements for solutions acceptance, which are the criteria that the solution must meet to be accepted by the stakeholders. The requirements for solutions acceptance are part of the solution scope, which is an output of the enterprise analysis tasks, not the business analysis approach. References:

• [A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 24, section 2.21
• [CBAP Certification Study Guide v3.0], Chapter 4: Requirements Life Cycle Management, Section 4.1: Plan Business Analysis Approach, page 4-22
• Business Analysis Approach, paragraph 1

 A top-down estimate is an estimate based on past projects to predict the current cost and/or duration of the current project. It is also called an analogous estimate, as it involves using data from previous, similar projects to estimate activity durations1. Top-down estimates are usually done at the early stages of a project, when there is notenough detail or information available to perform more accurate estimates. They are useful for providing a rough order of magnitude (ROM) or a ballpark figure for the project scope, cost and schedule. Top-down estimates are typically faster and cheaper to produce than bottom-up estimates, but they are also less accurate andreliable23. References: 2: Project Cost Estimation: How to Estimate Project Cost - ProjectManager2 3: 11 Cost Estimating Methods (With Formulas and Examples) | Indeed.com3 1: Understanding the Analogous Estimating Technique | Runn1

The business analysis process that ensures that requirements specifications and models meet the necessary standard of quality to allow them to be used effectively to guide further work is verify requirements. According to the BABOK® Guide1, this process involves checking that the requirements are well-defined, clear, consistent, complete, correct, feasible, modifiable, testable, and traceable. It also involves resolving any defects or issues that may affect the quality of the requirements. The purpose of this process is to confirm that the requirements specifications and models accurately reflect the stakeholder needs and expectations, and that they are ready for validation and approval.

The other options are not correct, but rather:

• A. Identify constraints and assumptions is a task within the assess capability gaps process, which involves comparing the current and future states of the organization to identify the gaps that must be addressed by a solution.
• B. Validate requirements is a process that ensures that the requirements support the delivery of value to the stakeholders and achieve the goals and objectives of the project or initiative. It involves evaluating the alignment, acceptability, and approval of the requirements by the stakeholders.
• D. Specify and model requirements is a process that involves defining and representing the requirements in various formats, such as textual, graphical, or tabular. It helps to communicate, analyze, and refine the requirements more effectively.

References:

• CBAP® Handbook, page 6, section 4. Review the Exam Blueprint, under Requirements Analysis and Design Definition, task 5.3: Verify Requirements
• BABOK® Guide, page 33, section 4.2.3: Verify Requirements
• How Do Business Analysts Verify Requirements? (BABOK 6.5)
• What Is Requirements Analysis? Process and Techniques

The conduct stakeholder analysis task is one of the tasks in the business analysis planning and monitoring knowledge area. According to the BABOK® Guide1, this task involves identifying and analyzing the stakeholders of a change, assessing their attitudes, expectations, influence, and interests regarding the change, and determining the best ways to engage and communicate with them. The purpose of this task is to ensure that the business analysis activities are aligned with the needs and concerns of the stakeholders, and that the stakeholders are appropriately involved and informed throughout the change.

The other options are not accurate descriptions of the conduct stakeholder analysis task, but rather:

• A. This is a partial description of the define business need task, which identifies the business problem or opportunity that requires analysis.
• C. This is a partial description of the assess capability gaps task, which compares the current and future states to identify the gaps that must be addressed by a solution.
• D. This is a vague and incomplete description of the conduct stakeholder analysis task, as it does not mention the analysis, assessment, and engagement aspects of the task.

References:

• CBAP® Handbook, page 15, section 4.1.2.3
• BABOK® Guide, page 32, section 3.2.3
• CBAP / CCBA Certified Business Analysis Study Guide, page 96, section 3.2.3
• How To Create a Stakeholder Analysis (With Example)
• How to Perform a Stakeholder Analysis | Lucidchart

 Business value is a basis for prioritizing requirements that considers the benefits and costs of each requirement to the organization. It helps to identify the most valuable requirements that can deliver the highest return on investment. Business value can be measured in terms of revenue, cost savings, customer satisfaction, market share, competitive advantage, or other criteria that are relevant to the organization’s goals and objectives. References:

• Certified Business Analysis Professional (CBAP) Handbook, page 6, section 4. Review the Exam Blueprint, Table 4.1: BABOK® Guide Knowledge Areas and Tasks
• BABOK® Guide v3, page 33, section 4.2 Prioritize Requirements
• Tips for Earning a Business Analysis Certification, section 3. Leverage a variety of study resources

 Quality control is not one of the reasons why trace requirements is useful, but a process that monitors and measures the quality of the project deliverables and outputs against the quality standards and criteria established in the quality management plan. Quality control is used to make certain that the project team members are completing the project work according to the project plan and meeting the stakeholder expectations. Quality control involves performing quality audits, inspections, tests, reviews, and validations to identify and correct any defects, errors, or deviations from the specifications1.

The other three options are valid reasons why trace requirements is useful. Trace requirements is a technique that involves establishing and documenting the relationships between requirements and other aspects of the product management process, such as design elements, test cases, releases, and incidents. Trace requirements is useful for the following purposes234:

• Impact analysis: Trace requirements helps to evaluate the impact of a potential change or a problem on the requirements and the solution. By tracing the dependencies and links between requirements and other items, the business analyst can quickly and easily assess the scope, cost, time, and risk implications of the change or the problem, and plan the appropriate response actions.
• Requirements coverage: Trace requirements helps to ensure that all the requirements are fulfilled by the solution and that all the solution components contribute to the requirements. By tracing the alignment and mapping between requirements and solution components, the business analyst can verify that the solution meets the stakeholder needs and expectations, and that there are no gaps or redundancies in the solution.
• Requirements allocation: Trace requirements helps to assign requirements to solution components and to releases. By tracing the distribution and allocation of requirements to different parts of the solution and to different phases of the project, the business analyst can prioritize and schedule the requirements based on their value, risk, dependency, and complexity, and ensure that the solution is delivered incrementally and iteratively. References: 1: Project Quality Management: Processes & Tools | Villanova University5 2: Requirements Traceability - The What, Why and How | Netmind6 3: Requirements traceability – why and how to do it?7 4: Requirements traceability : What, why and how - Modern Analyst8

Overlooking a key set of stakeholders can have serious consequences for the project, as they may have different needs, expectations, and perspectives than the existing stakeholders. Their requirements may conflict with or invalidate the ones that have been already elicited and analyzed, leading to rework, delays, and increased costs. Alternatively, they may introduce new requirements that require changes to the project scope, schedule, budget, or quality. Therefore, it is important to identify all relevant stakeholders as early as possible in the business analysis process and to engage them throughout the project lifecycle. References:

• CBAP Handbook, page 12, section 2.0 Nine-Steps to Certification, step 3. Enter Your Eligibility Details into the BA Development Log
• [BABOK Guide], page 30, section 2.2 Conduct Stakeholder Analysis, task description and output
• CBAP/CCBA Study Guide, page 55, section 2.2.3 Stakeholder Analysis, stakeholder identification and analysis techniques

 Benchmarking is a technique for comparing the performance or practices of an organization with those of other organizations, usually considered to be the best in the field. It is not a technique for identifying the solution approach, which is the process of defining the most feasible and appropriate way to implement a change that addresses a business need. The other techniques are useful for identifying the solution approach. Decision analysis helps to evaluate multiple options and select the best one based on criteria and trade-offs. Risk analysis helps to identify and assess the uncertainties and potential impacts of the solution approach. Brainstorming helps to generate and explore diverse ideas for the solution approach. References:

• BABOK® Guide v3, section 10.17 Benchmarking, section 10.18 Brainstorming, section 10.25 Decision Analysis, section 10.33 Risk Analysis and Management, section 11.2 Define Solution Approach
• CBAP® Handbook, section 5. Review the Exam Blueprint
• Tips for Earning a Business Analysis Certification, section 4. Leverage a variety of study resources

A business case is a document that clearly identifies the reasoning for initiating a project to justify the resources required. It is written to justify the resources required for the project (money or effort) and align the project objectives to the business needs. It also includes the costs, benefits, and risks of the proposed solution, and compares it with alternative options1. A business case is an important input for the project initiation and approval process, as it helps the decision makers to assess the value and feasibility of the project2.

To write a business case, you need four main inputs: feasibility study, assumptions and constraints, business need, and solution options3. A feasibility study is an analysis that evaluates the technical, economic, social, and environmental aspects of the project, and determines whether it is viable and worth pursuing4. Assumptions and constraints are factors that affect the project scope, cost, schedule, and quality, and that need to be identified and documented in the business case. Assumptions are things that are believed to be true or certain, while constraints are things that limit or restrict the project5. Business need is the problem or opportunity that the project aims to address, and that aligns withthe strategic goals and vision of the organization. Solution options are the different ways of solving the business need, and their respective costs, benefits, and risks.

Stakeholder concerns are not an input for writing a business case, but rather an output of stakeholder analysis. Stakeholder analysis is a process of identifying and prioritizing the people or groups who have an interest or influence in the project, and understanding their needs, expectations, and perspectives. Stakeholder concerns are the issues or challenges that the stakeholders face or anticipate in relation to the project, and that need to be addressed or resolved. Stakeholder concerns are important for defining the requirements, managing the communication, and ensuring the stakeholder satisfaction, but they are not directly used for writing the business case. References:

• How to Write a Business Case (Template Included) - ProjectManager
• How to Write a Business Case | Smartsheet
• Business Case Examples, explained in simple language - Chase Consulting
• Feasibility Study: Definition, Methods, and Examples
• Project Assumptions and Constraints: Examples and Differences
• [Business Need - IIBA®]
• [Solution Options - IIBA®]
• [Stakeholder Analysis: Overview, Tools and Techniques - KnowledgeHut]
• [Stakeholder Concerns - IIBA®]

 A constraint is a factor that limits the options or the performance of the project or the solution. Constraints are usually imposed by external factors, such as laws, regulations, standards, policies, resources, time, or budget. Constraints can affect the feasibility, desirability, and suitability of the solution, and may require trade-offs or compromises among the requirements. A constraint is different from a requirement, which is a condition or capability that the solution must have or meet to satisfy the stakeholder needs and expectations123.

In this question, the $300,000 represents a constraint, as it is a factor that limits the options or the performance of the solution. The customer demands that the solution should not cost more than $300,000 to implement and support for one year, which means that the solution must fit within this budget constraint. This constraint may affect the choice of technologies, processes, or features that the solution can include, and may require prioritizing or eliminating some requirements to meet the budget limit. References: 1: BABOK® Guide v3, section 3.4.2 Assess Capability Gaps, page 70 2: CBAP / CCBA Certified Business Analysis Study Guide, chapter 4, page 109 3: Business Analysis Techniques: Identifying Constraints, page 24

 A business analysis plan is a document that describes the scope of work, the deliverable Work Breakdown Structure (WBS), the activity list, and estimates for the business analysis activities. It also includes the business analysis approach, the roles and responsibilities of the business analyst and other stakeholders, the communication plan, the requirements management plan, the change management plan, and the risk management plan12. Abusiness analysis plan is an important input for the business analysis execution and monitoring process, as it helps to guide and control the business analysis work, and to ensure that the business analysis deliverables meet the quality standards and stakeholder expectations3.

The other options are not correct. A project management plan is a document that describes how the project will be executed, monitored, and controlled. It covers the project scope, schedule, cost, quality, resources, communication, risk, procurement, and stakeholder management. An implementation plan is a document that describes how the solution will be deployed, transitioned, and integrated into the business operations. It covers the implementation strategy, schedule, resources, tasks, roles, responsibilities, risks, and issues. A requirements management plan is a document that describes how the requirements will be elicited, analyzed, documented, validated, verified, prioritized, traced, and maintained throughout the project lifecycle. It is a component of the business analysis plan, not a separate document. References:

• Business Analysis Plan - IIBA®
• Business Analysis Planning and Monitoring - IIBA®
• Business Analysis Execution and Monitoring - IIBA®
• [Project Management Plan - PMI]
• [Implementation Plan - PMI]
• [Requirements Management Plan - IIBA®]

 A business analysis communication plan is a document that describes how the business analyst will communicate with the stakeholders, including the stakeholder groups, communication needs, level of formality, frequency, format, and methods of communication. It is one of the outputs of the business analysis planning and monitoring knowledge area, and it helps to ensure that the stakeholders are informed, engaged, and satisfied with the business analysis process and deliverables. A business analysis communication plan is not the same as a project communication plan, which covers the overall communication needs of the project and is typically created by the project manager. A business analysis communication plan focuses on the specific communication needs related to the business analysis activities and requirements. References:

• IIBA BABOK Guide v3, p. 36, 38, 40, 42
• How to Create a Stakeholder Management Plan Smartsheet
• CBAP 150 Practice Questions Flashcards, Question 5
• How To Create an Effective Stakeholder Communication Plan

 According to the BABOK® Guide, conflicts among stakeholders are inevitable and must be resolved before formal approval of the requirements can be obtained. The business analyst is responsible for facilitating the resolution of conflicts by using various techniques such as problem-solving, negotiation, or escalation. The business analyst should not make the decision for the stakeholders, nor should the decision be based on seniority or deferred until later. References: BABOK® Guide v3, section 4.5.5, page 142; CBAP® Handbook, section 4.4, page 6.

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

 Identifying the stakeholders early on in the business analysis duties helps the business analyst to understand the needs, expectations, and interests of the stakeholders, as well as their influence and authority on the project. This helps the business analyst to plan and manage the requirements activities, communicate effectively with the stakeholders, and address any issues or conflicts that may arise. By involving the stakeholders throughout the business analysis process, the business analyst can ensure that the requirements deliverables are aligned with the stakeholder needs and expectations, and that they are delivered on time and within budget. References:

• IIBA, A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3, 2015, p. 30-311
• IIBA, Business Analysis Competency Model, Version 4, 2018, p. 142

To calculate the break-even point, we need to compare the total costs of the internal solution and the vendor’s solution over time. The internal solution has a higher initial cost ($78,000) and a higher monthly cost ($8,765) than the vendor’s solution ($61,000 and $7,990 respectively). Therefore, the internal solution will take longer to break even with the vendor’s solution. The formula for the break-even point is:

Break-even point = (Initial cost difference) / (Monthly cost difference)

Plugging in the numbers, we get:

Break-even point = ($78,000 - $61,000) / ($8,765 - $7,990) Break-even point = $17,000 / $775 Break-even point = 21.94 months

Rounding up to the nearest whole month, we get 22 months as the break-even point. References: This question is based on the concept of financial feasibility analysis, which is part of the business analysis planning and monitoring knowledge area in the BABOK® Guide. Financial feasibility analysis is the process of comparing the costs and benefits of different solutions to determine the optimal one for the organization. One of the techniques for financial feasibility analysis is break-even analysis, which calculates the point in time when the costs of a solution equal the benefits of the solution. You can find more information about financial feasibility analysis and break-even analysis in the following sources:

• BABOK® Guide, section 3.4.5.5, pages 76-77
• CBAP / CCBA Certified Business Analysis Study Guide, chapter 3, pages 85-86
• Certified Business Analysis Professional™ (CBAP®) | Coursera, course 2, week 3, video 3.3

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

 The relationships among the requirements add to the level of complexity of the solution. Requirements can have dependencies, conflicts, overlaps, and gaps that make them more difficult to analyze, prioritize, and implement. The business analyst needs to identify and manage these relationships to ensure the solution meets the stakeholder needs and delivers value. References:

• A Guide to the Business Analysis Body of Knowledge (BABOK Guide), version 3, section 4.2.3
• Business Analysis Professional (CBAP) Certification Study Guide, version 3.0, page 131

A non-negotiable demand by a stakeholder during the requirements prioritization session is one that does not allow for any trade-offs, compromises, or alternatives. It is a demand that must be met regardless of the impact on other requirements, the feasibility of the solution, or the value to the organization. A stakeholder who insists that all requirements are ranked as high is making a non-negotiable demand, as this would prevent any meaningful prioritization and allocation of resources. Communication, cost-benefits ratio, and cost are not non-negotiable demands, as they can be negotiated,adjusted, or balanced with other factors during the requirements prioritization session. References: BABOK Guide v3, section 10.25 Requirements Prioritization; 1

 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

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

 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

 A requirements package is a document that contains a set of requirements that have been analyzed, refined, and formatted to meet the needs of various stakeholders. The primary goal of developing a requirements package is to communicate the requirements effectively and efficiently to the intended audience. A requirements package may include different levels of detail, different types of requirements, different formats and structures, and different supporting information depending on the stakeholder’s needs and preferences. A requirements package should be clear, concise, consistent, complete, correct, and testable. References:

• Certified Business Analysis Professional Handbook, page 24
• BABOK Guide, page 121

Quality is the degree to which a set of inherent characteristics fulfills requirements, according to the BABOK® Guide (p. 7). Quality is also defined as the extent to which a product or service meets the customer’s expectations and needs. Quality can be measured by various criteria, such as functionality, reliability, usability, efficiency, maintainability, and portability. Regulation, project phase, and scope are not related to the definition of quality. References:

• BABOK® Guide, p. 7
• CBAP / CCBA Certified Business Analysis Study Guide, p. 14
• Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 1, Week 1, Video: “Introduction to Business Analysis”

A bidders conference is a meeting that brings all of the potential vendors together to discuss the statement of work and the request for proposal. A bidders conference is an opportunity for the soliciting organization to clarify any questions or issues regarding the project, the requirements, the evaluation criteria, and the procurement process. A bidders conference also allows the potential vendors to network with each other and explore possible partnerships or subcontracting opportunities. A bidders conference is different from a contract bidding meeting, which is a meeting where the soliciting organization evaluates and selects the winning vendor. A bidders conference is also different from a status meeting, which is a meeting that provides updates on the progress and performance of a project. A bidders conference is not a qualified vendors meeting, which is a meeting that pre-qualifies vendors based on their capabilities and experience. References:

• RFP: A Quick Guide to Request for Proposals (Templates Included), paragraph 8
• How to Write a Statement of Work for Any Industry | Smartsheet, paragraph 9
• 50+ SAMPLE Vendor Request for Proposal in PDF, paragraph 3
• The Ultimate RFP Guide: Steps, Guidelines & Template for Requests for …, paragraph 5

 A request for quote (RFQ) is a procurement form that asks the vendor to provide only a price for a standard or fixed product or service, such as a commercial-off-the-shelf (COTS) solution. An RFQ is used when the requirements are well-defined and there is no need for negotiation or customization. An RFQ is different from a request for proposal (RFP), which asks the vendor to provide a detailed proposal for a complex or customized product or service, including the price, schedule, approach, and qualifications. An RFQ is also different from a purchase order (PO), which is a formal document that authorizes the purchase of a product or service from a specific vendor. An RFQ is also different from a request for information (RFI), which asks the vendor to provide general information about their products or services, capabilities, or references, without asking for a price or a proposal. References: CBAP / CCBA Certified Business Analysis Study Guide, Chapter 9: Solution Assessment and Validation, page 275. Certified Business Analysis Professional (CBAP®) Handbook, page 6.

Surveys are a type of requirements elicitation technique that involves sending a set of questions or statements to a large group of stakeholders and collecting their responses. Surveys can be conducted using various modes, such as online, email, phone, or paper. Surveys are useful for capturing the feelings and thoughts of a large and diverse population of stakeholders, identifying the common needs and wants of the majority, and analyzing the trends and patterns of the responses. Surveys can also help to gather quantitative and qualitative data, measure the level of satisfaction or dissatisfaction, and obtain feedback on the existing or proposed solution. Surveys are different from interviews, which are a type of requirements elicitation technique that involves asking questions and documenting the responses from a single person or a small group of people. Interviews are useful for exploring the in-depth and detailed information from the key stakeholders, probing deeper into their needs and expectations, and clarifying any ambiguities or inconsistencies. Interviews can also help to establish rapport and trust with the stakeholders, observe their non-verbal cues, and tailor the questions according to the context and situation. Surveys are also different from trend analysis, which is a type of requirements elicitation technique that involves examining the historical or current data and information to identify the changes and developments over time. Trend analysis can help to understand the past and present performance and behavior of the system or the process, predict the future outcomes and scenarios, and anticipate the opportunities and threats. Trend analysis can also help to validate and verify the requirements, evaluate the feasibility and viability of the solution, and support the decision making and planning. Surveys are not focus groups, which are a type of requirements elicitation technique that involves inviting a group of stakeholders to a moderated discussion on a specific topic or issue. Focus groups can help to generate a large number of ideas and opinions, find solutions for a specific problem, and stimulate the interaction and debate among the participants. Focus groups can also help to gain insights and perspectives from different stakeholders, identify the areas of agreement or disagreement, and foster a sense of involvement and ownership. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Elicitation and Collaboration, page 180-181.
• Top 10 Most Common Requirements Elicitation Techniques, paragraph 9
• Software Engineering | Requirements Elicitation - GeeksforGeeks, paragraph 6
• Elicitation Technique Guide | Info-Tech Research Group, paragraph 1
• Requirements Elicitation Technique (RET) : 10+ Effective RET - Skillcubator, paragraph 4

A current state domain model is a visual representation of the existing business domain, including the entities, attributes, relationships, and rules that define the current situation. A current state domain model can help identify opportunities for improvement by highlighting the gaps, issues, or inefficiencies in the current domain. A current state domain model can also help validate the solution scope with business and technical stakeholders by providing a common understanding of the current domain and its boundaries. A current state domain model can also help assist stakeholders in understanding the current state by showing the structure and logic of the current domain in a simple and clear way. However, a current state domain model cannot help the business analyst create Pareto charts for process improvement, as Pareto charts are a different type of analysis tool that show the frequency and impact of different types of problems or causes. Pareto charts are not based on the current state domain model, but rather on the data collected from the current processes or activities. References: BABOK Guide v3, page 123; CBAP / CCBA Certified Business Analysis Study Guide, page 181.

 A business case is a document that provides justification for undertaking a project, programme or portfolio. It evaluates the benefit, cost and risk of alternative options and provides a rationale for the preferred solution. The purpose of the business case is to communicate the value of the solution to the organization and help the decision-makers decide whether to approve the project or not. The business case should include the following elements:

• Executive summary: A brief overview of the problem, opportunity, solution, benefits, costs, risks and recommendations.
• Introduction: A description of the background, context, scope and objectives of the project.
• Analysis: A detailed analysis of the current state, future state, gap, options, criteria, assumptions and constraints.
• Evaluation: A comparison of the options based on the criteria, such as financial, strategic, operational, technical, social and environmental factors.
• Recommendation: A clear statement of the preferred option and the reasons for choosing it over the others.
• Implementation: A description of the implementation plan, including the schedule, resources, roles, responsibilities, governance, change management and risk management.
• Appendices: Any supporting information, such as data, calculations, charts, diagrams, references, etc.

References:

• Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 3: Business Analysis Planning and Monitoring, Section 3.4: Plan Business Analysis Approach, Task 3.4.3: Define Business Analysis Process, Technique 3.4.3.1: Decision Analysis, p. 66-67.
• What is business case? | APM
• How to Write a Business Case: Template & Examples | Adobe Workfront

Business rules analysis is a business analysis technique that involves identifying, analyzing, and documenting the rules that govern how an organization operates and makes decisions. Business rules analysis can help an organization to adapt to the change economy, new technologies, and an increase in competition by ensuring that the rules are aligned with the organizational goals and objectives, and that they are consistent, transparent, and flexible. Business rules analysis can also help to identify any gaps, conflicts, or redundancies in the existing rules, and to propose new or revised rules that can improve the organizational performance and efficiency. References: BABOK Guide v3, page 142; CBAP / CCBA Certified Business Analysis Study Guide, page 191.

 A procurement document is a document that is used to solicit proposals or quotations from potential suppliers or vendors of products or services for a project. A procurement document describes the problem or need, the desired solution, the evaluation criteria, and the contractual terms and conditions. A procurement document can be a request for proposal (RFP), a request for quote (RFQ), a request for information (RFI), or an invitation for bid (IFB). An invitation for bid (IFB) is a type of procurement document that is used to request bids from prospective sellers of products or services. An IFB describes the specifications, quantity, quality, and delivery schedule of the products or services. An IFB invites sellers to submit a sealed bid that indicates the cost of providing the products or services. An IFB is used when the buyer has a well-defined or standard problem or need, and wants to select the lowest bidder among the qualified sellers123. A project work breakdown structure (WBS) is not a procurement document, but a project management document. A WBS is a hierarchical decomposition of the project scope into smaller and manageable components. A WBS defines the deliverables, activities, and tasks that are required to complete the project4. A project charter is not a procurement document, but a project management document. A project charter is a document that formally authorizes the initiation of a project. A project charter defines the purpose, objectives, scope, assumptions, constraints, risks, stakeholders, roles, responsibilities, and authority of the project. A vision document is not a procurement document, but a business analysis document. A vision document is a document that describes the desired future state of a solution. A vision document defines the goals, benefits, features, and scope of the solution. References: CBAP® Handbook, CBAP® Exam Prep Study Guide, Project Management Institute, Project Work Breakdown Structure, [Project Charter], [Vision Document]

System thinking is a type of analytical thinking that involves understanding how the components of a system interact with each other and affect the whole. System thinking helps the business analyst to see the big picture, identify the root causes of problems, and design solutions that address the system as a whole. System thinking is essential for conducting requirements elicitation for a process that involves people, processes, and technology, as these are interrelated and interdependent elements of a system. The other options are not types of analytical thinking, but rather techniques or skills that can be used in different situations. References:

• 9.1 Analytical Thinking and Problem Solving, paragraph 1
• Business Analysis Blog | Systems Thinking – An Analyst’s Essential Trait, paragraph 1
• Top 11 Most Effective Business Analysis Techniques | 2024, paragraph 2

A requirements workshop is a type of elicitation technique that involves carefully selected stakeholders and subject matter experts for a short, intensive period (usually for one to a few days) to define and document the requirements for a solution. A requirements workshop is also known as a joint application development (JAD) session or a facilitated workshop. The benefits of a requirements workshop include increased stakeholder collaboration, consensus building, creativity, and productivity. A requirements workshop is facilitated by a business analyst or a professional facilitator, who guides the participants through a structured agenda and ensures that the objectives of the workshop are met. References:

• BABOK Guide, section 4.2.5.1, page 108
• CBAP / CCBA Certified Business Analysis Study Guide, chapter 5, page 173
• Certified Business Analysis Professional™ (CBAP®) | Coursera, course 2, week 3, video 3.1

The conduct elicitation activity is a technique to understand stakeholder needs and identify potential solutions that may meet those needs. It involves guiding stakeholders and collaborating with them through the elicitation activity, doing research or running experiments, and capturing elicitation outcomes1. The inputs for this activity are the following2:

• Requirements management plan: This document defines how requirements will be elicited, analyzed, documented, validated, and managed throughout the project lifecycle. It provides guidance on the elicitation approach, techniques, roles, responsibilities, and deliverables.
• Business need: This is the problem or opportunity that the project intends to address. It provides the context and rationale for the elicitation activity and helps to define the scope and objectives of the project.
• Solution scope: This is the set of capabilities and features that a solution must deliver in order to meet the business need. It defines the boundaries and assumptions of the project and helps to identify the stakeholders and sources of information for the elicitation activity.
• Stakeholder list, roles, and responsibilities: This is the identification and description of the individuals and groups who have an interest or influence in the project. It defines their roles, responsibilities, expectations, and level of involvement in the elicitation activity.
• Business analysis information: This is the collection of information that has been gathered, analyzed, and documented during the business analysis process. It includes the business analysis plan, the business case, the current and future state descriptions, the requirements, the assumptions, the constraints, the risks, the issues, and the change requests. It provides the input and reference for the elicitation activity and helps to avoid duplication or inconsistency of information.
• Elicitation activity plan: This is the plan that describes the specific details of the elicitation activity, such as the purpose, scope, objectives, approach, techniques, participants, agenda, logistics, materials, and expected outcomes. It helps to prepare and organize the elicitation activity and ensure its alignment with the requirements management plan and the business analysis plan.

Documented elicitation results are not an input, but an output of the conduct elicitation activity. They are the records of the information that has been elicited from the stakeholders and other sources during the elicitation activity. They include notes, transcripts, recordings, models, diagrams, sketches, prototypes, surveys, questionnaires, and other artifacts that capture the stakeholder needs, expectations, preferences, assumptions, constraints, and feedback. They are used as an input for the confirm elicitation results activity, where they are checked for accuracy, completeness, and consistency. References: Conduct Elicitation - iiba.org, Exploring the CBAP Knowledge Areas - Institute i4

A feasibility study is a type of document that evaluates the potential solution alternatives and their expected benefits, costs, risks, and impacts on the organization and its stakeholders. A feasibility study also provides data and statistics to support the analysis and recommendations. A feasibility study helps the decision makers to select the most viable and beneficial solution for the business need.

References:

• CBAP Handbook, page 10, section 3.4.2.3
• BABOK Guide, page 100, section 6.1.5.2

Visual learners are the type of learners who learn best through the presentation of models. Models are graphical representations of concepts, processes, systems, or data that help to illustrate and communicate information. Visual learners prefer to see the information rather than hear it or read it. They benefit from the use of colors, shapes, symbols, and spatial arrangements to organize and highlight the information. Models can help visual learners to understand the relationships, patterns, and trends of the information, as well as to compare and contrast different aspects of the information. Some examples of models that can be used in a presentation are diagrams, charts, graphs, maps, tables, and infographics. The other options are not the type of learners who learn best through the presentation of models, although they may also benefit from them. Auditory learners are the type of learners who learn best through listening to the information. They prefer to hear the information rather than see it or read it. They benefit from the use of voice, tone, pitch, and volume to convey and emphasize the information. Auditory learners can also learn from verbal explanations, discussions, debates, and questions. Kinesthetic learners are the type of learners who learn best through doing or experiencing the information. They prefer to interact with the information rather than see it or hear it. They benefit from the use of movement, touch, and physical activities to engage and stimulate the information. Kinesthetic learners can also learn from demonstrations, simulations, experiments, and role-plays. Communication model learners are not a type of learners, but rather a term used to describe a framework that explains how communication works. A communication model consists of elements such as sender, receiver, message, channel, feedback, and noise. A communication model can help the business analyst to understand the factors that affect the effectiveness and efficiency of communication, as well as to identify and overcome the barriers and challenges of communication. References:

• The four different types of learners, and what they mean for your presentations (infographic), paragraph 2
• Presentations for Each Type of Learner – Microsoft 365, paragraph 3
• 8 Types of Learning Styles | The Definitive Guide - Bay Atlantic University, paragraph 1
• Learning styles (power point) | PPT - SlideShare, slide 4

Benchmarking is the process of comparing the performance or quality of a product, service, or process against a standard or best practice. Bob and Susan are benchmarking the materials by testing them and measuring the results to see how they compare to each other. This will help them select the best material for their project.

References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Enterprise Analysis, page 217.
• BABOK® Guide, Version 3, Section 3.4: Strategy Analysis, page 50.

Implementation subject matter experts are the stakeholders who would need detailed technical interface requirements. These are the people who are responsible for designing, developing, and deploying the solution components that interact with other systems or applications. Technical interface requirements specify the format, structure, protocol, and security of the data exchange between the solution and the external entities. Project manager, regulators, and testers are other types of stakeholders who may need different levels of information related to the requirements, but not necessarily the technical interface details. References:

• BABOK® Guide, p. 29, 36, 51, 54
• CBAP / CCBA Certified Business Analysis Study Guide, p. 45, 49, 50, 52
• Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 1, Week 3, Video: “Stakeholder Analysis”

A regulator is a stakeholder who may be responsible to dictate that a specific process or technique be followed during the requirements elicitation activities. A regulator is an external stakeholder who has the authority to enforce laws, rules, standards, or policies that affect the project or the solution. A regulator may impose certain requirements or constraints on the project or the solution, such as compliance, security, privacy, or quality. A regulator may also require the use of specific methods, tools, or documentation for eliciting, analyzing, or validating the requirements. The other options are not necessarily responsible for dictating the process or technique for requirements elicitation, although they may have some influence or preference. A project manager is a stakeholder who is responsible for planning, executing, monitoring, and controlling the project activities and resources. A project manager may collaborate with the business analyst to select the appropriate process or technique for requirements elicitation, but does not have the authority to dictate it. A functional management is a stakeholder who is responsible for the day-to-day operations of a specific function or department within the organization, such as finance, marketing, or human resources. A functional management may provide input or feedback on the requirements elicitation process or technique, but does not have the authority to dictate it. A project sponsor is a stakeholder who is responsible for initiating, funding, and supporting the project or the solution. A project sponsor may approve or endorse the requirements elicitation process or technique, but does not have the authority to dictate it. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Elicitation and Collaboration, page 175-176.
• Engaging Stakeholders in Elicitation and Collaboration, paragraph 4
• Top 10 Most Common Requirements Elicitation Techniques, paragraph 2
• A Review of Fundamental Tasks in Requirements Elicitation, paragraph 1

The conduct elicitation activity is a technique to understand stakeholder needs and identify potential solutions that may meet those needs. It involves guiding stakeholders and collaborating with them through the elicitation activity, doing research or running experiments, and capturing elicitation outcomes1. The captured outcomes should be recorded in a format that is clear, consistent, and accessible for future reference and analysis. Text messages sent via a secured mobile phone are not an acceptable element for requirements documentation, as they are not easily retrievable, traceable, or verifiable. Written documents, visual or audio recordings, and whiteboards are acceptable elements for requirements documentation, as long as they are properly stored, labeled, and managed2. References: Conduct Elicitation - iiba.org, Conducting elicitation activity – The Functional BA

GAP analysis is a technique that involves determining and documenting the variance between business requirements and current capabilities. GAP analysis helps to identify the gaps or discrepancies between the current state and the desired state of a system or a process. GAP analysis can also help to prioritize the requirements, define the scope, and plan the actions needed to close the gaps. GAP analysis is different from risk analysis, which is a technique that involves identifying, assessing, and managing the uncertainties and threats that may affect the project objectives. GAP analysis is also different from schedule analysis, which is a technique that involves estimating, monitoring, and controlling the time and resources needed to complete the project activities. GAP analysis is not a cost benefit analysis, which is a technique that involves comparing the costs and benefits of alternative solutions or courses of action. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Enterprise Analysis, page 215-216.
• Business Capability Analysis: How to analyze capabilities, paragraph 3
• ProjectManagement.com - Variance Analysis, paragraph 1
• Which of the following techniques involves determining and documenting …, paragraph 1

Risk identification is a process that can start with the source of problems or with the problem itself. Risk identification is the process of determining the risks that may affect the project or the solution, and documenting their characteristics. Risk identification can be performed by analyzing the sources of risks, such as the project environment, the stakeholders, the requirements, the assumptions, the constraints, or the dependencies. Risk identification can also be performed by analyzing the problems or issues that may arise during the project or the solution, such as the gaps, conflicts, ambiguities, uncertainties, or changes. Risk identification helps to create a list of potential risks and their causes, impacts, and probabilities for further analysis and response planning12. Risk estimation is a process that follows risk identification. Risk estimation is the process of assessing the likelihood and impact of the identified risks, and prioritizing them according to their severity. Risk estimation helps to quantify the level of risk exposure and the expected value of the risk for decision making12. Risk analysis is a process that follows risk estimation. Risk analysis is the process of evaluating the identified and prioritized risks, and determining the appropriate responses to them. Risk analysis helps to develop strategies and actions to avoid, reduce, transfer, or accept the risks, and to allocate resources and contingency reserves for risk management12. Risk management is a process that encompasses risk identification, risk estimation, risk analysis, and risk monitoring and control. Risk management is the process of planning, identifying, analyzing, responding to, and monitoring and controlling the risks throughout the project or the solution lifecycle. Risk management helps to minimize the negative effects and maximize the positive opportunities of the risks, and to ensure the project or the solution objectives are met12. References: CBAP® Handbook, CBAP® Exam Prep Study Guide

Enterprise analysis is the business analysis knowledge area that involves defining the business need, assessing the capability gaps, determining the solution approach, defining the solution scope, and building the business case. In this scenario, the activity of examining the workflow and internal processes for order fulfillment and identifying the business problems and opportunities is part of the enterprise analysis. The purpose of this activity is to understand the current state of the organization and its environment, and to propose a solution that can address the business need and deliver value to the stakeholders. References:

• BABOK® Guide, p. 16-17
• CBAP / CCBA Certified Business Analysis Study Guide, p. 83-84
• Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 1, Week 4, Video: “Enterprise Analysis”

A data dictionary is a model that defines the name of the data, data aliases, and description of system data. A data dictionary is a collection of metadata that provides information about the data elements and structures in a system or a database. A data dictionary can include the following information for each data element: name, alias, description, data type, size, format, domain, constraints, default value, source, owner, and usage. A data dictionary can help the business analyst to understand the data requirements, design the data model, and ensure the data quality and consistency. A data dictionary is different from a class model, which is a model that defines the classes, attributes, operations, and relationships in an object-oriented system. A data dictionary is also different from an entity relationship model, which is a model that defines the entities, attributes, relationships, and cardinalities in a relational database. A data dictionary is not a CRUD matrix, which is a model that defines the create, read, update, and delete operations for each data element and user role in a system. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 8: Requirements Analysis, page 288-289.
• Data Dictionary - Tutorialspoint, paragraph 1-2
• What is a Data Dictionary? | Definition and How To, paragraph 1-2
• Data Dictionary - Project Management Knowledge, paragraph 1

 A plan-driven approach to business analysis planning and monitoring is one that follows a predefined and detailed plan for the business analysis activities, deliverables, and tasks. A plan-driven approach is usually preferred when the scope, requirements, and solution are well-defined and stable, and when the stakeholders have a high degree of agreement and alignment. A plan-driven approach typically requires a significant amount of formality and detail in the documentation, approval, and communication of the requirements and the business analysis work. A plan-driven approach is also known as a predictive or waterfall approach. References:

• BABOK® Guide, p. 13-14
• CBAP / CCBA Certified Business Analysis Study Guide, p. 27-28
• Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 1, Week 2, Video: “Business Analysis Planning and Monitoring”

Active observation is a technique of observing the behavior and activities of stakeholders while asking questions or participating in the work. Active observation can help to gain a deeper understanding of the work processes and environment of the stakeholders, as well as any issues or challenges they face. Active observation can also help to build rapport and trust with the stakeholders, and to elicit tacit or implicit knowledge that may not be easily expressed. In this case, Martha is using active observation by workingalongside Sarah and helping her complete the work, so that Martha can understand all of the steps Sarah must complete. References: BABOK Guide v3, page 97; CBAP / CCBA Certified Business Analysis Study Guide, page 163.

An independent task is a task that does not rely on other activities, and no other activities rely on this task completing. An independent task can be performed at any time during the project, as long as it meets the project objectives and requirements. An independent task has no dependencies or constraints with other tasks. An analysis task is a task that involves examining, evaluating, and interpreting information to identify and understand the problem, need, or opportunity. An analysis task may rely on other activities, such as elicitation, documentation, or validation, and other activities may rely on this task completing, such as design, development, or testing. An analysis task may have dependencies or constraints with other tasks. A predecessor task is a task that must be completed before another task can start or finish. A predecessor task has a logical or sequential relationship with another task, which is called a successor task. A predecessor task may affect the start or end date, duration, or resources of the successor task. A dependent task is a task that relies on another task to start or finish. A dependent task has a logical or sequential relationship with another task, which is called a predecessor task. A dependent task may be affected by the start or end date, duration, or resources of the predecessor task. References: CBAP® Handbook, CBAP® Exam Prep Study Guide, Project Management Institute

Dependencies between requirements are an important consideration to include in the assessment of the solution, as they may affect the delivery options and the value realization of the solution. Dependencies between requirements are the relationships or interconnections among the requirements that indicate that one requirement is contingent on another requirement. Dependencies may be logical, temporal, or resource-based. Dependencies may influence the order, timing, and feasibility of the solution delivery, as well as the benefits and risks associated with the solution. Therefore, the business analyst should identify, analyze, and manage the dependencies between requirements as part of the solution assessment.

Historical information, experience of the implementation team, and enterprise environmental factors are also relevant factors to consider in the solution assessment, but they are not as specific as dependencies between requirements. Historical information may provide insights into the past performance, lessons learned, and best practices of similar projects or solutions. Experience of the implementation team may affect the quality, efficiency, and effectiveness of the solution delivery. Enterprise environmental factors may include the organizational culture, structure, policies, processes, and systems that may influence the solution design and implementation. However, these factors are more general and may not directly relate to the tradeoffs between delivery options or the value realization of the solution. References:

• BABOK® Guide, p. 123-124, 128-129
• CBAP / CCBA Certified Business Analysis Study Guide, p. 299-300, 304-305
• Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 2, Week 4, Video: “Assess Proposed Solution”

 Decision analysis is a business analysis technique that involves evaluating the feasibility, benefits, risks, and impacts of various options and selecting the best one based on predefined criteria and stakeholder preferences. In this scenario, the business analyst is considering using decision analysis to rate the available methodologies against the organizational needs and objectives, and to choose the most suitable one for the business analysis approach. Decision analysis can help the business analyst to align the business analysis activities with the project and enterprise goals, and to optimize the value delivery of the solution. References:

• BABOK® Guide, p. 66-67
• CBAP / CCBA Certified Business Analysis Study Guide, p. 133
• Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 1, Week 2, Video: “Business Analysis Planning and Monitoring”

 A one-to-one interview is the most common type of interview as part of requirements elicitation. A one-to-one interview is a systematic approach for eliciting information from a single person in an informal or formal setting by asking questions and documenting the responses. A one-to-one interview allows the business analyst to establish rapport with the interviewee, probe deeper into their needs and expectations, observe their non-verbal cues, and clarify any ambiguities or inconsistencies. A one-to-one interview is also easier to schedule and conduct than other types of interviews that involve multiple participants, such as many-to-one, many-to-many, or one-to-many. References:

• Requirements Elicitation: Interview Dos and Don’ts, paragraph 1
• Top 10 Most Common Requirements Elicitation Techniques, paragraph 3
• Types of Elicitation Techniques for the Business Analyst, paragraph 2
• What Questions Do I Ask During Requirements Elicitation?, paragraph 1
• Interviews: Requirements Elicitation Technique, paragraph 1

A class model is a technique to represent the structure and behavior of the entities within a solution domain. It shows the attributes, operations, and relationships of the classes that define the entities. A class is a category or type of entity that has common characteristics and can perform certain functions. A class model helps to identify the entities, their properties, their behaviors, and their interactions for a solution. Entity Relationship is a technique to represent the data and information requirements of a solution. It shows the entities, attributes, and relationships of the data and information. An entity is a thing or object of interest that can be uniquely identified and has attributes that describe its properties. An entity relationship model helps to identify the data and information, their characteristics, their associations, and their constraints for a solution. Data dictionary is a technique to define and document the data and information elements of a solution. It provides a detailed description of each data and information element, such as its name, definition, format, type, source, owner, and usage. A data dictionary helps to standardize and clarify the data and information, their meaning, their structure, and their quality for a solution. CRUD matrix is a technique to analyze the alignment of the data and information elements with the business processes or functions of a solution. It shows the data and information elements and the business processes or functions that create, read, update, or delete them. A CRUD matrix helps to identify the data and information, their lifecycle, their dependencies, and their gaps for a solution. References: Class Model - iiba.org, Entity Relationship - iiba.org, Data Dictionary - iiba.org, CRUD Matrix - iiba.org