IIBA Certified Business Analysis Professional CBAP New Questions

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

 According to the BABOK® Guide, a risk is “an uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project objectives such as scope, schedule, cost, and quality” (p. 10). A risk can have both positive and negative impacts, depending on the perspective of the stakeholders and the objectives of the solution. For example, a risk of adopting a new technology may be that it increases the productivity of the employees (positive) but also requires more training and maintenance (negative). A risk analysis in the business case should consider both the probability and the impact of the risks, as well as the strategies to mitigate or exploit them. References: BABOK®Guide, p. 10, 114-115; Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 3, Week 2, Video: “Risk Analysis and Management”

The Delphi technique is a type of requirements elicitation technique that is based on a survey method. The Delphi technique involves sending a series of questionnaires to a group of experts who have knowledge or experience in the domain of the project or the solution. The questionnaires are designed to elicit opinions, ideas, or feedback on the requirements or the issues related to the project or the solution. The responses from the experts are collected and analyzed by a facilitator, who then provides a summary of the results and the areas of agreement or disagreement to the experts. The facilitator also prepares a new questionnaire based on the feedback and sends it back to the experts for another round of responses. This process is repeated until a consensus is reached or a sufficient level of information is obtained. The Delphi technique is useful for gathering requirements from a large and diverse group of stakeholders who are geographically dispersed or have conflicting views. The Delphi technique also helps to reduce the influence of dominant or biased individuals and to encourage honest and independent opinions. The Delphi technique is different from a workshop, which is a type of requirements elicitation technique that involves bringing together a group of stakeholders in a face-to-face or virtual setting to collaborate and exchange information on the requirements or the issues related to the project or the solution. The workshop is facilitated by a moderator, who guides the discussion and ensures the participation and contribution of all the attendees. The workshop is useful for generating a large number of ideas and finding solutions for a specific problem in a short time. The workshop also helps to build rapport and trust among the stakeholders and to resolve conflicts or misunderstandings. The Delphi technique is also different from a round table, which is a type of requirements elicitation technique that involves inviting a group of stakeholders to a formal or informal meeting to share their perspectives and insights on the requirements or the issues related to the project or the solution. The round table is moderated by a leader, who introduces the topic and encourages the dialogue and debate among the participants. The round table is useful for exploring different viewpoints and opinions and for gaining a deeper understanding of the problem and the context. The round table also helps to foster a sense of involvement and ownership among the stakeholders and to identify the areas of agreement or disagreement. The Delphi technique is not a prototyping, which is a type of requirements elicitation technique that involves creating a simplified or partial version of the solution or a component of the solution and presenting it to the stakeholders for feedback. The prototype can be either low-fidelity or high-fidelity, depending on the level of detail and functionality. The prototype is useful for validating and verifying the requirements and for demonstrating the feasibility and usability of the solution. The prototype also helps to reduce the ambiguity and uncertainty of the requirements and to increase the satisfaction and acceptance of the solution. 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
• Delphi Method Forecasting Definition and How It’s Used - Investopedia, paragraph 1
• The Delphi Technique - Students 4 Best Evidence, paragraph 1

 A business analysis communications plan is a document that describes how the business analysis information will be communicated to the stakeholders, including the format, frequency, content, and recipients of the communication. A business analysiscommunications plan can help to ensure that the stakeholders are informed, engaged, and satisfied with the business analysis work, and that the business analysis deliverables are validated and approved. A business analysis communications plan is part of the business analysis plan, which is a comprehensive document that covers all aspects of the business analysis approach, activities, and deliverables. References: BABOK Guide v3, page 37; CBAP / CCBA Certified Business Analysis Study Guide, page 75.