Before the BA can proceed with any analysis of the features, t hey 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 inconsist ent 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.”

According to the BABOK® Guide 1 , the business analysis approach is the set of processes, tools, deliverables, techniques, and standards that will be used to perform business analysis work on a project. The approach can be either plan-driven, adaptive, or a hybrid of both. A plan-driven approach is more suitable for projects that have stable and well-defined requirements, low leve ls of change, and clear acceptance criteria. An adaptive approach is more suitable for projects that have uncertain or evolving requirements, high levels of change, and emergent outcomes. Therefore, one of the factors that would drive the decision towards an adaptive approach is the organization’s tolerance for uncertainty, which means the degree to which the organization is willing to accept ambiguity and risk in the project. An organization with a high tolerance for uncertainty can benefit from an adaptiv e approach that allows for frequent feedback, experimentation, and learning.  References :

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. 57-59

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 3: Business Analysis Planning and Monitoring, Section 3.2: Plan Business Analysis Approach, p. 89-91

The BA should approach the solution limitation by assessing the impact on t he business operations. This means that the BA should analyze how the inability to meet the SLA in one out of five scenarios would affect the business goals, objectives, performance, value, and risks. The BA should also consider the frequency, severity, an d likelihood of the scenarios, and the expectations and needs of the stakeholders. Based on the impact assessment, the BA can then recommend the best course of action, such as modifying the SLA, changing the business process, increasing the scope, or defer ring the requirement to a future release. The other options are not the best approaches, as they may either be unrealistic, unnecessary, or ineffective without a proper impact assessment.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 7: Solution Evaluation, Section 7.2: Analyze Performance Measures, p. 311-312

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 7: Solution Evaluation, Section 7.2: Analyze Performance Measures, p. 269-270

According to the BABOK® Guide, eliciting requirements is not a compartmentalized activity that can be completed in a single phase of the project. Rather, it is an ongoing process that occurs throughout the project life cycle, as new information is discovered, new stakeholders are identified, and changes are requested. Therefore, the duration o f the requirements elicitation process is not determined by the schedule, the size, or the stakeholder involvement of the project, but by the evolving nature of the requirements themselves.  References :  BABOK® Guide v3 , section 4.1, page 50;  CBAP® Handbook , page 6.

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 thei r 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 he lps to create a list of potential risks and their causes, impacts, and probabilities for further analysis and response planning 1 2 . 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 making 1 2 . Risk analysis is a process that follows risk estimation. Risk analysis is the process of evaluating the identified and prioritized risks, and dete rmining 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 con tingency reserves for risk management 1 2 . Risk management is a process that encompasse s 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 lifec ycle.  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 met 1 2 .  References :  CBAP® Handbook ,  CBAP® Exam Prep Study Guide

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 dissatisfac tion, 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 rapp ort 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 examini ng 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 scenario s, 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 p roblem, 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 owners hip.  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

The prepare for elicitation process is a technique to understand the scope of the elicitation activity, select appropriate techniques, and plan for (or procure) appropriate supporting materials and resources.  The inputs for this process are the following 1 2 :

Stakeholder list: 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 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 concerns are not an input, but an output of the prepare for elicitation process. They are the issues or questions that the stakeholders have regarding the project or the solution. They are used as an input for the conduct elicitation process, where they are addressed or answered during the elicitation activity.  References :  Prepare for Elicitation - iiba.org ,  Preparing for elicitation – The Functional BA

 Passive observation is a technique of observing the behavior and activities of stakeholders without asking questions or influencing them in any way. Passive observation can help to capture the actual work processes and environment of the stakeholders, as well as any issues or challenges they face. Passive observation can also reduce the bias or distortion that may arise from direct interaction with the stakeholders.  References :  BABOK Guide v3 , page 97;  CBAP / CCBA Certified Business Analysis Study Guide , page 163.

 A regulator is not a stakeholder that is considered when completing the business analysis planning and monitoring task to determine a business analysis approach. A regulator is an external entity that imposes rules, standards, or guidelines that the organization and the solution must comply with. A regulator is not directly involved in the business analysis process, but rather in the governance and validation of the solution. Therefore, a regulator does not influence the choice of the business analysis approach, which is based on the characteristics and needs of the project and the organization.

The other options are stakeholders that are considered when completing the business analysis planning and monitoring task to determine a business analysis approach. A tester is a stakeholder who verifies and vali dates the quality and functionality of the solution. A project manager is a stakeholder who oversees and coordinates the project activities, resources, and deliverables. A functional manager is a stakeholder who manages a specific business function or depa rtment, such as finance, marketing, or human resources. These stakeholders have different roles, responsibilities, expectations, and interests in the business analysis process, and they may affect or be affected by the choice of the business analysis appro ach.  References :

BABOK® Guide , p. 29, 32, 66

CBAP / CCBA Certified Business Analysis Study Guide , p. 45, 48, 133

Certified Business Analysis Professional™ (CBAP®) | Coursera , Course 1, Week 2, Video: “Business Analysis Planning and Monitoring”

Prioritizing requirements is a process of determining the relative importance and urgency of the requirements based on the criteria and preferences of the stakeholders. Prioritizing requirements can help to allocate resources, manage scope, and resolve conflicts. One of the factors that can affect the prioritization of requirements is the dependency, which means that one requirement must be implemented before another requirement can be implemented. In this case, you are correct to move one of the requirements higher in the prioritization because it is needed to be implemented before some of the more important requirements are done. This way, you can ensure that the dependency is satisfied and that the project can deliver the expected value. Ra lph is incorrect to rank the requirements based on their level of difficulty, as this is not a relevant criterion for prioritization. The level of difficulty can be considered in the estimation and planning of the project, but not in the prioritization of the requirements.  References :  BABOK Guide v3 , page 52;  CBAP / CCBA Certified Business Analysis Study Guide , page 160.