Complete CBAP IIBA Materials

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

Business rules analysis is a business analysis technique that involves identifying, analyzing, and documenting the rules that govern how an organization operates and makes decisions. Business rules analysis can help an organization to adapt to the change economy, new technologies, and an increase in competition by ensuring that the rules are aligned with the organizational goals and objectives, and that they are consistent, transparent, and flexible. Business rules analysis can also help to identify any gaps, conflicts, or redundancies in the existing rules, and to propose new or revised rules that can improve the organizational performance and efficiency. References: BABOK Guide v3, page 142; CBAP / CCBA Certified Business Analysis Study Guide, page 191.

 Problem tracking is a document elicitation technique that can help in this scenario. Problem tracking is the process of identifying, documenting, and resolving issues that arise during the business analysis process. Problem tracking helps to ensure the quality and validity of the requirements and the solutions. Problem tracking also provides an opportunity for stakeholders to rank the importance of issues affecting them. Problem tracking can be done using various tools, such as spreadsheets, databases, or software applications. Problem tracking can help the business analyst to monitor the status of the issues, communicate the progress and outcomes to the stakeholders, and improve the business analysis performance and practices. The other options are not document elicitation techniques, but rather information elicitation techniques. Brainstorming is a technique that involves generating new ideas and finding solutions for a specific problem. Observation is a technique that involves watching how people perform their tasks or interact with a system. Interviews are a technique that involves asking questions and documenting the responses from a single person or a group of people. References:

Problem/Issue Tracking Technique — Business Analyst Learnings, paragraph 1

Elicitation Methods | SpringerLink, paragraph 1

Understanding the Document Analysis Technique - Business Analyst Learnings, paragraph 1

A requirements workshop is a type of elicitation technique that involves carefully selected stakeholders and subject matter experts for a short, intensive period (usually for one to a few days) to define and document the requirements for a solution. A requirements workshop is also known as a joint application development (JAD) session or a facilitated workshop. The benefits of a requirements workshop include increased stakeholder collaboration, consensus building, creativity, and productivity. A requirements workshop is facilitated by a business analyst or a professional facilitator, who guides the participants through a structured agenda and ensures that the objectives of the workshop are met. References:

BABOK Guide, section 4.2.5.1, page 108

CBAP / CCBA Certified Business Analysis Study Guide, chapter 5, page 173

Certified Business Analysis Professional™ (CBAP®) | Coursera, course 2, week 3, video 3.1