How to Easily Pass the IIBA CBAP Exam: Expert Advice

 Cost-benefit analysis is a technique that compares two or more systems, states, services, products, or things to determine the best viable choice. It involves estimating and comparing the total costs and benefits of each alternative over a specified period of time. The costs and benefits can be expressed in monetary or non-monetary terms, depending on the nature and scope of the analysis. Cost-benefit analysis can help to identify the most efficient and effective solution that maximizes the net benefit or minimizes the net cost. Cost-benefit analysis can also help to evaluate the feasibility, desirability, and sustainability of a project or initiative. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, page 47
• Business Analysis Professional Resources | IIBA®, under Standards, Regulations, and Best Practices
• Cost-Benefit Analysis Definition

Ad images are a strong candidate to be addressed while planning for requirements reuse, because they are likely to change frequently and have common elements that can be reused across different weeks. Requirements reuse is a technique that involves identifying, storing, and reusing requirements or requirement components for future projects or initiatives. It can help to reduce duplication, improve consistency, and save time and effort. Ad images can benefit from requirements reuse, because they can use a standard template, format, and style, and only change the specific image and text for each new topping. Dough preparation, toppings preparation, and topping recipes are not good candidates for requirements reuse, because they are either stable or unique for each week. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 3: Requirements Life Cycle Management, page 124
• Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 3: Requirements Life Cycle Management, section 3.7: Reuse Requirements, page 66
• Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 3: Requirements Life Cycle Management, page 124

The business analysis approach is used by the BA Professional to guide which sources of information and which results are to be compared when confirming the elicitation results. The business analysis approach is a description of the methodology, techniques, tools, and deliverables that will be used to conduct the business analysis work. The business analysis approach can help the BA Professional to determine the best way to compare and validate the elicitation results, and to ensure that they are consistent, complete, and accurate. The business analysis approach can also help the BA Professional to identify and resolve any conflicts, gaps, or issues that may arise from the elicitation results. Information management approach, business analysis plan, or elicitation activity plan are not the best options for guiding which sources of information and which results are to be compared, because they are either too specific, too general, or not directly related to the confirmation of the elicitation results. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Elicitation and Collaboration, page 165
• Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 4: Elicitation and Collaboration, section 4.3: Confirm Elicitation Results, page 81
• Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 4: Elicitation and Collaboration, page 165

The plan business analysis activities process involves defining the tasks and resources needed to perform the business analysis work. The inputs to this process are the business analysis approach, the organizational process assets, the stakeholder list, roles, and responsibilities, and the business analysis performance assessment. The list of identified risks is not an input to this process, but rather an output of the identify risks process, which is part of the business analysis planning and monitoring knowledge area. References: BABOK Guide v3, page 37; CBAP / CCBA Certified Business Analysis Study Guide, page 75.

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 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 desired outcome is a statement of what the organization wants to achieve as a result of the business analysis work. A desired outcome should be specific, measurable, achievable, relevant, and time-bound (SMART). A desired outcome should also be aligned with the organizational goals and objectives, and provide value to the stakeholders. Examples of desired outcomes are increase sales, reduce costs, and reduce time to deliver a product or service. Implement new machinery to complete the work processes faster is not an example of a desired outcome, but rather a possible solution or requirement that may help to achieve a desired outcome. References: BABOK Guide v3, page 97; CBAP / CCBA Certified Business Analysis Study Guide, page 217.

 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.

Recording the dependencies and relationships for the requirements is a technique of identifying and documenting how the requirements are linked or influenced by each other or by external factors. Recording the dependencies and relationships can help to determine the sequence in which requirements are to be addressed, by showing which requirements must be implemented before, after, or in parallel with other requirements. This can help to plan and manage the requirements implementation, and to avoid any conflicts or gaps in the requirements. References: BABOK Guide v3, page 52; CBAP / CCBA Certified Business Analysis Study Guide, page 160.

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