CBAP Exam Dumps : Certified Business Analysis Professional

Overlooking a key set of stakeholders can have serious consequences for the project, as they may have different needs, expectations, and perspectives than the existing stakeholders. Their requirements may conflict with or invalidate the ones that have been already elicited and analyzed, leading to rework, delays, and increased costs. Alternatively, they may introduce new requirements that require changes to the project scope, schedule, budget, or quality. Therefore, it is important to identify all relevant stakeholders as early as possible in the business analysis process and to engage them throughout the project lifecycle. References:

CBAP Handbook, page 12, section 2.0 Nine-Steps to Certification, step 3. Enter Your Eligibility Details into the BA Development Log

[BABOK Guide], page 30, section 2.2 Conduct Stakeholder Analysis, task description and output

CBAP/CCBA Study Guide, page 55, section 2.2.3 Stakeholder Analysis, stakeholder identification and analysis techniques

 Lessons learned is a technique that involves identifying and documenting the successes, failures, and best practices of a project or initiative, and using them to improve the performance and quality of future work. Lessons learned can help the manager to help the BAs develop their skills and address the corrective actions, because it can provide feedback, insights, and recommendations on how to enhance the business analysis processes, methods, and competencies. Lessons learned can also help to identify the gaps, issues, and opportunities for improvement, and to plan and implement the necessary actions to resolve them. Team restructure, weekly meetings, or team building are not the best options for achieving this goal, because they are either too general, too specific, or not directly related to the business analysis skills and corrective actions. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 8: Solution Evaluation, page 348

Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 8: Solution Evaluation, section 8.5: Assess Enterprise Limitations, page 159

Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 8: Solution Evaluation, page 348

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