IIBA CBAP - Certified Business Analysis Professional

 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

 According to the BABOK® Guide, one of the tasks of defining the business need is to review the requirements stated documentation and ensure that it reflects the actual business requirements, not a description of the solutions. This is important because the business need should be based on the underlying problem or opportunity, not on a predetermined solution. The other options are not relevant to this task. References: BABOK® Guide, v3, p. 30; CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, p. 36.

System thinking is a type of analytical thinking that involves understanding how the components of a system interact with each other and affect the whole. System thinking helps the business analyst to see the big picture, identify the root causes of problems, and design solutions that address the system as a whole. System thinking is essential for conducting requirements elicitation for a process that involves people, processes, and technology, as these are interrelated and interdependent elements of a system. The other options are not types of analytical thinking, but rather techniques or skills that can be used in different situations. References:

9.1 Analytical Thinking and Problem Solving, paragraph 1

Business Analysis Blog | Systems Thinking – An Analyst’s Essential Trait, paragraph 1

Top 11 Most Effective Business Analysis Techniques | 2024, paragraph 2

A schedule variance report is a report that shows the difference between the planned and actual schedule of a project. It indicates whether the project is ahead of, on, or behind schedule, and by how much. It also identifies the causes of the schedule variance and the corrective actions needed to bring the project back on track. A status report is a report that provides an overview of the current state of the project, including the scope, schedule, cost, quality, risks, issues, and deliverables. A delay report is a report that documents the reasons for a delay in the project, the impact of the delay, and the mitigation strategies to minimize the delay. A cost variance report is a report that shows the difference between the planned and actual cost of a project. It indicates whether the project is under or over budget, and by how much. It also identifies the causes of the cost variance and the corrective actions needed to control the project cost. References: CBAP® Handbook, CBAP® Exam Prep Study Guide, Project Management Institute

The requirements management plan is a document that describes how the requirements will be elicited, analyzed, documented, validated, and managed throughout the project. The requirements management plan also defines the criteria and process for prioritizing the requirements, based on factors such as value, risk, urgency, dependency, and stakeholder preference. The requirements management plan guides the business analyst through the process of prioritizing the requirements and ensuring that they are aligned with the project objectives and the stakeholder needs. References: BABOK Guide v3, page 36; CBAP / CCBA Certified Business Analysis Study Guide, page 74.

A change log is a tool that helps to manage and monitor the changes that affect the requirements, the solution, or the project. A change log tracks all characteristics and status of changes that have been received, such as the source, description, priority, impact, approval, and resolution of the changes. A change log can help to ensure that the changes are properly documented, communicated, and controlled, and that they are aligned with the stakeholder needs and expectations. References: BABOK Guide v3, page 54; CBAP / CCBA Certified Business Analysis Study Guide, page 161.

 Voting is a technique of requirements prioritization that involves asking the stakeholders to express their preferences for the requirements using various methods, such as ranking, rating, or allocating points or money. Voting helps to achieve consensus and alignment among the stakeholders and to identify the most important and valuable requirements. In this scenario, the business analyst is using a voting method that assigns play money to the requirements, which reflects the relative importance and benefit of each requirement. The requirements with the highest amount of play money are prioritized over the ones with lower amounts.

References:

BABOK® Guide, p. 55, 376-377

CBAP / CCBA Certified Business Analysis Study Guide, p. 165-166

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

 Decision analysis is a technique of evaluating the possible outcomes of different alternatives and choosing the best one based on the criteria and preferences of the stakeholders. Decision analysis can be used to assess potential risks that may impact the solution and the cost and benefits associated with it, by using methods such as decision trees, decision tables, or expected value analysis. Decision analysis can help to select the optimal solution that maximizes the value and minimizes the risk for the organization. References: BABOK Guide v3, page 130; CBAP / CCBA Certified Business Analysis Study Guide, page 185.

Risky requirements are those that have a high probability of causing problems or failures in the project. By addressing them early in the prioritization, the project team can identify and resolve any issues before they affect the rest of the requirements or the project deliverables. This way, the project can avoid rework, delays, and cost overruns that may result from risky requirements. References: CBAP / CCBA Certified Business Analysis Study Guide, Chapter 6: Requirements Analysis, page 203. Certified Business Analysis Professional (CBAP®) Handbook, page 6.

 A desired outcome is a statement of what the organization wants to achieve as a result of the business analysis work. A desired outcome should be specific, measurable, achievable, relevant, and time-bound (SMART). A desired outcome should also be aligned with the organizational goals and objectives, and provide value to the stakeholders. Examples of desired outcomes are increase sales, reduce costs, and reduce time to deliver a product or service. Implement new machinery to complete the work processes faster is not an example of a desired outcome, but rather a possible solution or requirement that may help to achieve a desired outcome. References: BABOK Guide v3, page 97; CBAP / CCBA Certified Business Analysis Study Guide, page 217.