Free IIBA CBAP Practice Exam with Questions & Answers | Set: 4

 Influence and attitude are two factors that the business analyst must consider when conducting stakeholder analysis. Influence is the stakeholder’s ability to affect the project or the solution, either positively or negatively. Attitude is the stakeholder’s level of support or resistance to the change, either enthusiastic or reluctant. By assessing these two factors, the business analyst can determine the stakeholder’s impact and interest in the project, and plan the appropriate engagement and communication strategies for each stakeholder group. References:

CBAP® Handbook, page 15, section 4.1.2.3

BABOK® Guide, page 32, section 3.2.3

How To Create a Stakeholder Analysis (With Example)

How to Conduct a Thorough Stakeholder Analysis - CloudApp Blog … - Zight

According to the BABOK Guide, textual requirements are one of the forms of specifying and modeling requirements. Textual requirements are written statements that describe the characteristics of the solution in a clear, concise, and consistent manner. Textual requirements typically consist of three components: the capability of the solution, the condition under which the requirement is applicable, and the constraint that may limit the solution. The capability describes what the solution must or should do, the condition describes the situation or scenario in which the requirement is relevant, and the constraint describes the restriction or limitation that may affect the solution’s ability to meet the requirement. For example, a textual requirement for a banking system could be:

The system shall allow customers to withdraw cash from any ATM machine (capability) within the network (condition) up to a maximum of $500 per day (constraint).

References:

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

Textual Requirement Artifacts - Blueprint Online Help - HelpDocs, paragraph 1

How to Model Textual Requirements - Formal Mind GmbH, paragraph 2

Requirements are dynamic and may change throughout the project life cycle due to various factors, such as changing stakeholder needs, new business opportunities, feedback from testing, or regulatory changes. Business analysis planning and monitoring involves defining the process for managing changes to requirements, including identifying the roles and responsibilities, the approval levels, the change control tools, and the communication methods. The business analyst should be prepared to handle changes to requirements at any time and follow the established change control process. References:

CBAP® Handbook, page 6, section 2.4. Review the Exam Blueprint

BABOK® Guide, page 29, section 2.4. Manage Business Analysis Performance

Tips for Earning a Business Analysis Certification, point 3. Understand the BABOK® Guide

 Benchmarking is a technique for comparing the performance or practices of an organization with those of other organizations, usually considered to be the best in the field. It is not a technique for identifying the solution approach, which is the process of defining the most feasible and appropriate way to implement a change that addresses a business need. The other techniques are useful for identifying the solution approach. Decision analysis helps to evaluate multiple options and select the best one based on criteria and trade-offs. Risk analysis helps to identify and assess the uncertainties and potential impacts of the solution approach. Brainstorming helps to generate and explore diverse ideas for the solution approach. References:

BABOK® Guide v3, section 10.17 Benchmarking, section 10.18 Brainstorming, section 10.25 Decision Analysis, section 10.33 Risk Analysis and Management, section 11.2 Define Solution Approach

CBAP® Handbook, section 5. Review the Exam Blueprint

Tips for Earning a Business Analysis Certification, section 4. Leverage a variety of study resources

A capabilities gap assessment is a process of identifying and analyzing the gaps between the current and desired capabilities of an organization. It helps to determine what new capabilities are needed to achieve the business goals and objectives, and to seize the business opportunities1. A business opportunity is the chance to take advantage of an occurrence in the market for business gain. It involves some kind of favourable condition that can be used to create and implement ideas and innovations, solve problems, and maximize profits2.

If an organization does not have the necessary resources and technology to seize a business opportunity, the most likely course of action is to launch a new project. A project is a temporary endeavor undertaken to create a unique product, service, or result3. By launching a new project, the organization can allocate the required resources and technology, define the project scope, schedule, and budget, and deliver the desired outcome. A new project can also help the organization to close the capabilities gap, improve its performance, and gain a competitive advantage in the market.

The other options are less likely or not feasible. Hiring additional resources or contractors may not be enough to close the capabilities gap, as they may not have the relevant skills, knowledge, or experience. Moreover, hiring may incur additional costs and risks for the organization. Moving onto the next opportunity may not be a wise decision, as it may result in losing a valuable chance to grow the business and satisfy the customer needs. Therefore, launching a new project is the best course of action for the organization. References:

Capabilities Based Assessment (CBA) - AcqNotes

What Is Business Opportunity? – Importance, Types … - Feedough

Project Management Basics: What Is a Project? | PMI

A methodology is a set of principles, rules, and processes that guide the business analysis activities and deliverables within a project or organization. A methodology can be based on a standard, such as the BABOK Guide, or a specific framework, such as Waterfall or Agile. A methodology helps the business analyst to plan, execute, monitor, and control the business analysis work in a consistent and effective way. References:

BABOK Guide, Chapter 2: Business Analysis Planning and Monitoring, Section 2.1: Plan Business Analysis Approach, p. 24-25

Business Analysis Methodology | What is this and is it real?

 A change-driven approach to business analysis is one that adapts to the changing needs and priorities of the stakeholders and the business environment. It focuses on delivering business value in short iterations, rather than following a fixed and detailed plan. A change-driven approach is often associated with agile methodologies, such as Scrum, Kanban, or XP, which emphasize collaboration, feedback, and continuous improvement. A change-driven approach can help business analysts respond to uncertainty, complexity, and ambiguity, and deliver solutions that meet the customer’s expectations and satisfaction. References:

Defining Business Analysis, section 1.3.2, page 7

How to Choose the Right Business Analysis Approach, paragraph 4

Business Analysis Approach, paragraph 2

The Agile Business Analysis Approach Means…, paragraph 1

Defining the Business Analysis Approach in 2023, paragraph 2

Quality control is the process of monitoring and measuring the quality of the project deliverables and outputs against the quality standards and criteria established in the quality management plan. Quality control is used to make certain that the project team members are completing the project work according to the project plan and meeting the stakeholder expectations. Quality control involves performing quality audits, inspections, tests, reviews, and validations to identify and correct any defects, errors, or deviations from the specifications. Quality control is one of the key processes in the project quality management knowledge area, which ensures that the project meets the quality requirements1234. References: 1: BABOK® Guide v3, section 11.6.5.9 Quality Management and Control, page 418 2: CBAP® Exam Prep Study Guide, chapter 9, page 340 3: Project Quality Management: Processes & Tools | Villanova University5 4: Quality Control in Project Management | PMI6

 Quality control is not one of the reasons why trace requirements is useful, but a process that monitors and measures the quality of the project deliverables and outputs against the quality standards and criteria established in the quality management plan. Quality control is used to make certain that the project team members are completing the project work according to the project plan and meeting the stakeholder expectations. Quality control involves performing quality audits, inspections, tests, reviews, and validations to identify and correct any defects, errors, or deviations from the specifications1.

The other three options are valid reasons why trace requirements is useful. Trace requirements is a technique that involves establishing and documenting the relationships between requirements and other aspects of the product management process, such as design elements, test cases, releases, and incidents. Trace requirements is useful for the following purposes234:

Impact analysis: Trace requirements helps to evaluate the impact of a potential change or a problem on the requirements and the solution. By tracing the dependencies and links between requirements and other items, the business analyst can quickly and easily assess the scope, cost, time, and risk implications of the change or the problem, and plan the appropriate response actions.

Requirements coverage: Trace requirements helps to ensure that all the requirements are fulfilled by the solution and that all the solution components contribute to the requirements. By tracing the alignment and mapping between requirements and solution components, the business analyst can verify that the solution meets the stakeholder needs and expectations, and that there are no gaps or redundancies in the solution.

Requirements allocation: Trace requirements helps to assign requirements to solution components and to releases. By tracing the distribution and allocation of requirements to different parts of the solution and to different phases of the project, the business analyst can prioritize and schedule the requirements based on their value, risk, dependency, and complexity, and ensure that the solution is delivered incrementally and iteratively. References: 1: Project Quality Management: Processes & Tools | Villanova University5 2: Requirements Traceability - The What, Why and How | Netmind6 3: Requirements traceability – why and how to do it?7 4: Requirements traceability : What, why and how - Modern Analyst8

 Automation is a type of process improvement that can reduce the time, cost, and errors involved in performing tasks. By automating some of the software and activities that the stakeholders use, you can increase the efficiency and effectiveness of the data report generation process. Automation can also enhance the quality and consistency of the outputs, as well as the satisfaction of the customers and the workers. References:

CBAP® Handbook, page 6, section 4. Review the Exam Blueprint, under Business Analysis Planning and Monitoring, task 5.2: Plan Business Analysis Process Improvements.

CBAP / CCBA Certified Business Analysis Study Guide, page 144, section 5.2.2: Plan Business Analysis Process Improvements, under Automation.