IIBA CBAP Based on Real Exam Environment

The elicitation technique that the BA should select to enable the customer and the key stakeholders to visualize the final product is prototyping. Prototyping is a technique that involves creating a simplified or partial version of the solution that can demonstrate its features, functions, and appearance. Prototyping can help to elicit, validate, and verify the requirements, as well as to obtain feedback and approval from the stakeholders. Prototyping can also help to reduce the risks, costs, and time of the project by identifying and resolving any issues or gaps before the final implementation of the solution. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Elicitation and Collaboration, Section 4.2: Conduct Elicitation, p. 167-168
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 4: Elicitation and Collaboration, Section 4.2: Conduct Elicitation, p. 103-104
• 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

 Prototyping is an elicitation technique that involves creating a mock-up or a simulation of the final product to demonstrate its functionality and design to the customer and the stakeholder. Prototyping can help the BA to obtain feedback, validate requirements, and resolve ambiguities or conflicts early in the development process. Prototyping can also help the customer and the stakeholder to visualize the final product and confirm that it meets their expectations and needs. References:

• IIBA BABOK Guide, Section 10.25, Prototyping
• Top 9 Requirements Elicitation Techniques Used by Business Analysts, Software Testing Help
• Prototyping Use as a Software Requirements Elicitation Technique: A Case Study, Springer Link

Reviews and workshops are effective techniques for validating and negotiating requirements with stakeholders. They can help the BA to identify and resolve any conflicting or contradictory requirements, as well as to gain consensus and agreement among the stakeholders. Reviews can be done in various forms, such as walkthroughs, inspections, or peer reviews. Workshops can be used to facilitate collaborative discussions, brainstorming, and decision making among the stakeholders. Both techniques can help the BA to safeguard against conflicting requirements by ensuring that the requirements are clear, accurate, complete, and aligned with the business goals and needs123. References:

• 1: BABOK Guide v3, Chapter 4: Elicitation and Collaboration, Section 4.5: Validate Requirements
• 2: BABOK Guide v3, Chapter 5: Requirements Life Cycle Management, Section 5.5: Approve Requirements
• 3: BABOK Guide v3, Chapter 10: Techniques, Section 10.32: Reviews, Section 10.50: Workshops