CBAP Exam Dumps - IIBA Certified Business Analysis Professional Questions and Answers

 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

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 information management approach is a document that describes how the business analysis information will be stored, accessed, distributed, and maintained throughout the project. It includes the details of the tools, formats, standards, and processes for managing the information. The BA will update the information management approach to reflect the changes in how the user stories will be organized and made more accessible for the next sprint. This will help to ensure that the information is consistent, accurate, and available for the stakeholders. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 3: Business Analysis Planning and Monitoring, Section 3.4: Plan Business Analysis Information Management, p. 101-102
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 3: Business Analysis Planning and Monitoring, Section 3.4: Plan Business Analysis Information Management, p. 64-65

The BA’s first step is to perform a gap analysis to understand the missing capabilities of the COTS tool and the existing manual processes. A gap analysis is a technique that compares the current state and the desired future state of a solution or a process, and identifies the gaps or differences between them. By performing a gap analysis, the BA can determine the feasibility, suitability, and risks of using the COTS tool to automate the existing manual processes, and identify the requirements and changes needed to bridge the gaps. The other options are not the first steps, as they may either be premature, unnecessary, or ineffective without a proper gap analysis. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 5: Strategy Analysis, Section 5.1: Analyze Current State, p. 206
• 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
• Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 3: Strategy Analysis, Week 2: Analyze Current State, video: “Gap Analysis”

The BA should handle the change request by adding the feature to the product backlog for future prioritization. The product backlog is a list of features, functions, and requirements that are desired for the solution, but have not yet been planned or implemented. The product backlog is constantly updated and prioritized by the product owner, who represents the voice of the customer and the stakeholders. The BA should collaborate with the product owner to capture and document the change request and add it to the product backlog. The product owner will then decide when and how to prioritize the feature for the next iteration or release, based on the value and urgency of the feature and the feedback from the stakeholders. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 3: Business Analysis Planning and Monitoring, Section 3.2: Plan Business Analysis Approach, p. 90-91
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 3: Business Analysis Planning and Monitoring, Section 3.2: Plan Business Analysis Approach, p. 58-59
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 4: Elicitation and Collaboration, Section 4.6: Communicate Business Analysis Information, p. 124-125