CBAP Exam Dumps : Certified Business Analysis Professional

The conduct stakeholder analysis task is one of the tasks in the business analysis planning and monitoring knowledge area. According to the BABOK® Guide1, this task involves identifying and analyzing the stakeholders of a change, assessing their attitudes, expectations, influence, and interests regarding the change, and determining the best ways to engage and communicate with them. The purpose of this task is to ensure that the business analysis activities are aligned with the needs and concerns of the stakeholders, and that the stakeholders are appropriately involved and informed throughout the change.

The other options are not accurate descriptions of the conduct stakeholder analysis task, but rather:

A. This is a partial description of the define business need task, which identifies the business problem or opportunity that requires analysis.

C. This is a partial description of the assess capability gaps task, which compares the current and future states to identify the gaps that must be addressed by a solution.

D. This is a vague and incomplete description of the conduct stakeholder analysis task, as it does not mention the analysis, assessment, and engagement aspects of the task.

References:

CBAP® Handbook, page 15, section 4.1.2.3

BABOK® Guide, page 32, section 3.2.3

CBAP / CCBA Certified Business Analysis Study Guide, page 96, section 3.2.3

How To Create a Stakeholder Analysis (With Example)

How to Perform a Stakeholder Analysis | Lucidchart

A regulator is a stakeholder who may be responsible to dictate that a specific process or technique be followed during the requirements elicitation activities. A regulator is an external stakeholder who has the authority to enforce laws, rules, standards, or policies that affect the project or the solution. A regulator may impose certain requirements or constraints on the project or the solution, such as compliance, security, privacy, or quality. A regulator may also require the use of specific methods, tools, or documentation for eliciting, analyzing, or validating the requirements. The other options are not necessarily responsible for dictating the process or technique for requirements elicitation, although they may have some influence or preference. A project manager is a stakeholder who is responsible for planning, executing, monitoring, and controlling the project activities and resources. A project manager may collaborate with the business analyst to select the appropriate process or technique for requirements elicitation, but does not have the authority to dictate it. A functional management is a stakeholder who is responsible for the day-to-day operations of a specific function or department within the organization, such as finance, marketing, or human resources. A functional management may provide input or feedback on the requirements elicitation process or technique, but does not have the authority to dictate it. A project sponsor is a stakeholder who is responsible for initiating, funding, and supporting the project or the solution. A project sponsor may approve or endorse the requirements elicitation process or technique, but does not have the authority to dictate it. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Elicitation and Collaboration, page 175-176.

Engaging Stakeholders in Elicitation and Collaboration, paragraph 4

Top 10 Most Common Requirements Elicitation Techniques, paragraph 2

A Review of Fundamental Tasks in Requirements Elicitation, paragraph 1

Prioritizing requirements is a process that helps business analysts and stakeholders to rank the requirements according to their importance, value, urgency, and dependency. Prioritizing requirements helps to ensure that the most critical requirements are addressed first, and that the available resources are allocated effectively. Prioritizing requirements also helps to manage the scope, schedule, and budget of the project, and to deal with changes and uncertainties. Prioritizing requirements is not only about determining the cost or the schedule of each requirement, but also about understanding the impact and the benefit of each requirement on the business need and the solution. Prioritizing requirements is not only about identifying the risks associated with each requirement, but also about mitigating or avoiding those risks by choosing the best solution option. References:

[A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 402, section 10.31.3.11

Why Prioritise Requirements – How to do it and Why it is Critical to Project Success – BusinessAnalystMentor.com, paragraph 1

Why You Should Prioritize Requirements - ArgonDigital, paragraph 1

What Is Requirements Prioritization? Definition & Examples - airfocus, paragraph 1

Business analysts : How to prioritize requirements - Adaptive US, paragraph 1