Pass the IIBA Certified Business Analysis Professional CBAP Questions and answers with ExamsMirror

Enterprise analysis is a knowledge area that describes the business analysis activities that take place for an enterprise to identify business opportunities, build a business architecture, determine the optimal project investment path for the enterprise and implement new business and technical solutions1. Enterprise analysis can be triggered by different need generation approaches, such as bottom-up, external drivers, middle management, or top-down2. In this case, the business need stems from external drivers, which are factors outside the organization that influence its performance, such as customers, competitors, regulations, or market trends3. A customer requesting new software for collecting customer information is an example of an external driver that creates a business need for the organization. The organization should conduct enterprise analysis to understand the customer’s requirements, assess the current capabilities and gaps, evaluate the feasibility and risks of the proposed solution, and define the business case and scope for the project. References:

What is Enterprise Analysis: does it differ from Enterprise Architecture?

[Enterprise Analysis - Business Analyst Training]

[External Drivers: Definition & Examples - Video & Lesson Transcript | Study.com]

A non-negotiable demand by a stakeholder during the requirements prioritization session is one that does not allow for any trade-offs, compromises, or alternatives. It is a demand that must be met regardless of the impact on other requirements, the feasibility of the solution, or the value to the organization. A stakeholder who insists that all requirements are ranked as high is making a non-negotiable demand, as this would prevent any meaningful prioritization and allocation of resources. Communication, cost-benefits ratio, and cost are not non-negotiable demands, as they can be negotiated, adjusted, or balanced with other factors during the requirements prioritization session. References: BABOK Guide v3, section 10.25 Requirements Prioritization; 1

The change-driven approach is an agile method that focuses on delivering value to the customer in short iterations and adapting to changing requirements. The change-driven approach favors defining requirements through team interaction, as this allows for more collaboration, feedback, and learning among the stakeholders. The change-driven approach also uses minimal documentation and relies on working software as the primary measure of progress. The change-driven approach is suitable for projects that have high uncertainty, complexity, and volatility. References:

Business Analysis Approach (BA Planning & Monitoring)

Adapting Your Requirements Practices | StickyMinds

Requirements definition and management — English - SFIA

 Customer-facing activities are those that directly involve or affect the customers, such as sales, service, support, or marketing. These activities should be consistent across the organization, as consistency is a key factor for customer satisfaction and loyalty12. Customers expect to have the same level of service and quality every time they interact with a business, regardless of the channel, location, or employee. If some employees perform customer-facing activities in a different format than the others, it can create confusion, frustration, or distrust among the customers, and potentially damage the business reputation and revenue34. Therefore, this is a problem that can be addressed as part of an improvement opportunity. Jane, as a business analyst, can use passive observation to identify the variations in the customer-facing activities, and then analyze the root causes, impacts, and possible solutions. She can also use other techniques, such as interviews, surveys, or focus groups, to gather feedback from the customers and the employees, and understand their needs and expectations. She can then propose recommendations to standardize the customer-facing activities, and ensure that they align with the business goals, values, and policies5. References:

The three Cs of customer satisfaction: Consistency, consistency, consistency | McKinsey

How to create consistency in customer service | Zapier

How To Improve Customer Focus Using 8 Key Strategies

Consistent Communication: A Must-Have For Your Customer Service Team - Forbes

Important Client-Facing Skills: Definition and Examples

Opportunities to prioritize requirements is not something that Rachel should include in her business case, as it is not relevant for the decision-making process. A business case is a document that clearly identifies the reasoning for initiating a project to justify the resources required. It includes the following items12:

A business problem or opportunity

Possible solutions and their benefits and disadvantages

Risks associated with the main solution

Costs

Implementation timeline

Consequences for implementing a solution and for retaining the status quo

Opportunities to prioritize requirements is not one of these items, as it is part of the business analysis process, not the business case. Prioritizing requirements is a technique that helps to rank the requirements in order of importance, urgency, or value for the stakeholders. It helps to determine which requirements should be implemented first, and which ones can be deferred or excluded. Prioritizing requirements is useful for managing the scope, schedule, and budget of the project, but it is not a factor that influences the approval or rejection of the project34.

The other options are things that Rachel should include in her business case, as they are relevant for the decision-making process. A. Time to break even is the period of time required for the project to recover its initial investment. It is a measure of the profitability and feasibility of the project, and it helps to compare different solution options5. C. Follow-on opportunities are the potential benefits or outcomes that can be achieved after the completion of the project, such as new markets, customers, products, or services. They are part of the qualitative and quantitative benefits of the project, and they help to demonstrate the value and alignment of the project with the business vision and strategy. D. Qualitative and quantitative benefits are the positive impacts or results that the project will deliver to the organization and the stakeholders, such as increased revenue, customer satisfaction, efficiency, or quality. They are expressed in both non-numerical and numerical terms, and they help to justify the costs and risks of the project. References:

How to Write a Business Case (Template Included) - ProjectManager

How to Write a Business Case | Smartsheet

Prioritizing Requirements - IIBA®

How to Prioritize Requirements: Techniques, Tools, and Examples

Break-Even Analysis - Definition, Formula, Example, and Advantages

[How to Write a Business Case (with Examples & Template to Help) - Pingboard]

[Cost-Benefit Analysis: A Quick Guide with Examples and Templates]

 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

 According to the BABOK® Guide, conflicts among stakeholders are inevitable and must be resolved before formal approval of the requirements can be obtained. The business analyst is responsible for facilitating the resolution of conflicts by using various techniques such as problem-solving, negotiation, or escalation. The business analyst should not make the decision for the stakeholders, nor should the decision be based on seniority or deferred until later. References: BABOK® Guide v3, section 4.5.5, page 142; CBAP® Handbook, section 4.4, page 6.

 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

 Process modeling is a technique that can be used to define and document the business analysis approach, as it describes the activities, tasks, inputs, outputs, and roles involved in the business analysis work. Process modeling can help to identify the scope, objectives, deliverables, dependencies, assumptions, constraints, and risks of the business analysis work. Process modeling can also help to communicate and validate the business analysis approach with stakeholders and ensure alignment with the project management approach. References: BABOK Guide v3, section 4.1.1.1, page 110; Business Analysis Techniques: Planning and Monitoring Business Analysis Work by Milena Pajic, section Using Process Modeling for Planning and Monitoring, page 171

The requirements analysis processes are the activities that prioritize, organize, specify, model, verify, and validate the requirements for the solution. They ensure that analysis and implementation efforts focus on the most critical requirements that deliver the most value to the stakeholders and the organization. They also help to resolve any conflicts or inconsistencies among the requirements and the stakeholders. References:

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

BABOK® Guide, page 30, section 3.2 Requirements Analysis and Design Definition

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