IIBA CCBA - Certification of Capability in Business Analysis (CCBA)

According to the BABOK Guide, the process of defining the business need involves identifying and describing the problem or opportunity that requires a change in the current state of the organization, and articulating the value proposition for the change1. The process of defining the business need uses one output, which is business need. Business need is a statement that describes the problem or opportunity, the desired outcome, the assumptions, constraints, and risks, and the impact on the organization and its stakeholders2. Business need is used as an input for other tasks, such as defining the solution scope, assessing the current state, and conducting stakeholder analysis1.

The other options are not correct outputs of the process of defining the business need:

Feasibility study: A feasibility study is an analysis that evaluates the viability and suitability of a proposed solution based on various criteria, such as technical, operational, economic, legal, and social factors3. A feasibility study is not an output of the process of defining the business need, but rather an output of the task of assessing proposed solutions1.

Solution scope: Solution scope is a description of the boundaries of the solution, including what is in and out of scope, the key assumptions and constraints, and the major features and functions2. Solution scope is not an output of the process of defining the business need, but rather an output of the task of defining the solution scope1.

Capability gaps: Capability gaps are the differences between the current and desired capabilities of the organization, such as processes, skills, systems, or resources2. Capability gaps are not an output of the process of defining the business need, but rather an output of the task of assessing the current state1. References:

1: BABOK Guide, section 5.1 Define the Business Need, page 94

2: BABOK Guide, section 3.8 Glossary, page 516-524

3: CBAP/CCBA Certified Business Analysis Study Guide, 2nd Edition, by Susan Weese and Terri Wagner, Wiley, 2011, page 297

Defining the business need is the activity that Henry is asking Janet to complete. Defining the business need is the process of identifying and describing the problem or opportunity that the organization faces and how it aligns with the organizational goals and objectives. It helps to set the direction and scope for the rest of the business analysis activities and to justify the initiation of a project or an initiative. Defining the business need is part of the strategy analysis knowledge area in the CCBA certification12

Option A is incorrect because brainstorming the business need is not an activity, but a technique. Brainstorming is a technique that involves generating and evaluating new and original ideas to address a problem or an opportunity. It can be used as part of defining the business need, but it is not the same as defining the business need34

Option B is incorrect because creating a data diagram for the service is not an activity, but a deliverable. A data diagram is a graphical representation of the data and information that are relevant to the solution. It can be used as an output of defining the business need, but it is not the same as defining the business need.

Option D is incorrect because eliciting the requirements of the proposal is not an activity, but a process. Eliciting the requirements is the process of identifying and obtaining the information needed from the stakeholders and other sources to define and validate the requirements. It can be used as an input to defining the business need, but it is not the same as defining the business need.

References:

Business Analysis Body of Knowledge (BABOK® Guide), Version 3, Chapter 6: Strategy Analysis, Section 6.1: Define Current State, p. 133-134.

Certification of Capability in Business Analysis (CCBA®) - Simplilearn, Module 7: Requirements Analysis and Design Definition, Lesson 7.1: Define Design Options, p. 6-7.

Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed, Section 7.5: Creative Thinking, p. 83-84.

Certification of Capability in Business Analysis (CCBA®) - Simplilearn, Module 7: Requirements Analysis and Design Definition, Lesson 7.3: Define Design Options, p. 6-7.

[Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed], Section 7.2: Process Modeling, p. 75-76.

[Certification of Capability in Business Analysis (CCBA®) - Simplilearn], Module 7: Requirements Analysis and Design Definition, Lesson 7.2: Analyze Potential Value and Recommend Solution, p. 6-7.

[Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed], Section 7.4: Requirements Elicitation, p. 79-80.

[Certification of Capability in Business Analysis (CCBA®) - Simplilearn], Module 6: Elicitation and Collaboration, Lesson 6.3: Conduct Elicitation, p. 6-7.

Expert judgment is a technique that involves consulting with individuals or groups who have specialized knowledge, skills, or experience in a relevant domain or discipline. Henry can use expert judgment to determine the optimal business analysis approach, which is the set of processes, activities, tasks, deliverables, roles, responsibilities, and governance that will be used to conduct the business analysis work. By asking an expert to help him define the business analysis duties, Henry can benefit from the expert’s insights, opinions, recommendations, and best practices, and apply them to his specific project context and objectives. Expert judgment can help Henry to select themost suitable and effective business analysis approach for his project, and to ensure the quality and alignment of the business analysis outputs and outcomes12

Option A is incorrect because Henry being a new business analyst is not the reason why he would ask an expert to help him define the business analysis duties. While being a new business analyst may imply that Henry has less experience or confidence in defining the business analysis duties, it does not necessarily mean that he needs to consult with an expert. Henry may have other sources of information or guidance, such as the Business Analysis Body of Knowledge (BABOK® Guide), the organizational standards and policies, or the project manager and sponsor. Moreover, even if Henry is an experienced business analyst, he may still benefit from using expert judgment, as each project may have different challenges, complexities, and uncertainties that require expert input3

Option B is incorrect because Henry should not always use expert judgment to confer on the business analysis approach, but only when it is appropriate and feasible. Expert judgment is not the only technique that Henry can use to define the business analysis approach, but one of the many techniques that are available and applicable. Henry should consider the advantages and disadvantages of using expert judgment, such as the availability, reliability, and credibility of the experts, the cost and time of consulting with them, and the potential bias or conflict of interest that may arise from their involvement. Henry should also consider the other factors that may influence the business analysis approach, such as the stakeholder needs and expectations, the project objectives and constraints, and the organizational culture and environment4

Option C is incorrect because Henry using an expert to help save time is not the reason why he would ask an expert to help him define the business analysis duties. While using an expert may help Henry to save time by providing him with quick and ready answers, it may also introduce some risks or challenges, such as the accuracy, validity, and applicability of the expert’s advice, the dependency and accountability of Henry on the expert’s input, and the communication and coordination issues that may occur between Henry and the expert. Henry should not use expert judgment as a shortcut or a substitute for his own analysis and judgment, but as a supplement or a support for his decision making5

References:

Business Analysis Body of Knowledge (BABOK® Guide), Version 3, Chapter 2: Business Analysis Planning and Monitoring, Section 2.1: Plan Business Analysis Approach, p. 31-32.

Certification of Capability in Business Analysis (CCBA®) - Simplilearn, Module 5: Planning and Monitoring, Lesson 5.1: Plan Business Analysis Approach, p. 6-7.

Business Analysis Body of Knowledge (BABOK® Guide), Version 3, Chapter 1: Introduction, Section 1.2: What is Business Analysis?, p. 5-6.

Business Analysis Body of Knowledge (BABOK® Guide), Version 3, Chapter 10: Techniques, Section 10.14: Expert Judgment, p. 347-348.

Certification of Capability in Business Analysis (CCBA®) - Simplilearn, Module 5: Planning and Monitoring, Lesson 5.2: Plan Stakeholder Engagement, p. 6-7.

According to the BABOK® Guide, an implementation constraint is a restriction or limitation that affects the execution or operation of a solution. Examples of implementation constraints include freeze periods, company policies, business cycle timings, regulatory requirements, and technical standards. Weather is not an implementation constraint because it does not affect the solution itself, but rather the external environment in which the solution operates. References: BABOK® Guide, page 31; Business Analysis Expert Certification, CCBA® | IIBA®, section “What Should I know to be CCBA Certified?”

According to the BABOK® Guide, the level of abstraction is the degree to which a requirement or design statement is general or specific. Requirements need to say what needs to be done, not how to do it. This means that requirements should focus on the desired outcome or value, not the implementation details or solution design. How to do it is the responsibility of the solution provider, not the business analyst. Therefore, option C completes the sentence correctly. References: BABOK® Guide, page 11; Business Analysis Expert Certification, CCBA® | IIBA®, section “What Should I know to be CCBA Certified?”

SWOT analysis is a technique that evaluates an organization’s strengths, weaknesses, opportunities, and threats to both internal and external conditions. It helps to identify the current state of the organization and the factors that may affect its future performance. SWOT analysis can be used for strategic planning, problem-solving, decision-making, and innovation. References:

Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed

CCBA® and CBAP® Certifications Study Guide

SWOT analysis - CCBA® and CBAP® Certifications Study Guide

Allocating requirements is the process of assigning stakeholder and solution requirements to solution components, releases, and organizational areas. The purpose of this process is to maximize the business value delivered by the solution, by ensuring that each requirement is addressed by the most appropriate component, release, or area. Allocating requirements also helps to manage dependencies, risks, and priorities among requirements. References:

Business Analysis Expert Certification, CCBA® | IIBA®, section “Who can Become a CCBA?”

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), version 3, section 6.4 “Allocate Requirements”

A plan-driven business analysis approach is a methodology that follows a predefined and structured process, where the requirements and the solution are fully defined and agreed upon before implementation begins. A plan-driven approach is suitable for projects that have low complexity, uncertainty, or volatility, and that require stability and predictability of the scope, schedule, and budget. A plan-driven approach is characterized by its formal and rigid nature, where each project phase must be completed before moving on to the next one. Therefore, the following are not appropriate for a plan-driven business analysis approach:

Informal: This means that the communication, documentation, and validation of the requirements and the solution are done in a casual and flexible manner, without following any standards or rules. Informal methods may lead to ambiguity, inconsistency, and misunderstanding of the requirements and the solution, which can cause delays, errors, and rework in a plan-driven approach.

Face-to-face: This means that the interaction and collaboration among the stakeholders are done in person, rather than through electronic or written means. Face-to-face methods may enhance rapport and trust among the stakeholders, but they may also introduce challenges such as scheduling, availability, and travel costs in a plan-driven approach.

Ad hoc: This means that the business analysis activities and tasks are done in a spontaneous and unplanned manner, without following any methodology or process. Ad hoc methods may allow for creativity and innovation, but they may also result in chaos, confusion, and waste in a plan-driven approach.

Option D is incorrect because formal is appropriate for a plan-driven business analysis approach. Formal means that the communication, documentation, and validation of the requirements and the solution are done in a systematic and rigorous manner, following established standards and rules. Formal methods ensure the quality, completeness, and alignment of the requirements and the solution, which are essential for a plan-driven approach.

References:

Business Analysis Body of Knowledge (BABOK® Guide), Version 3, Chapter 2: Business Analysis Planning and Monitoring, Section 2.1: Plan Business Analysis Approach, p. 31-32.

Certification of Capability in Business Analysis (CCBA®) - Simplilearn, Module 5: Planning and Monitoring, Lesson 5.1: Plan Business Analysis Approach, p. 6-7.

Business Analysis Approach | Do you need one?

How to Choose the Right Business Analysis Approach

Planning Business Analysis Approach and Monitoring

[Defining the Business Analysis Approach in 2023 | Free Template]

According to the BABOK® Guide, from the top down is one of the methods to generate the business need in an organization. This method is described as the need to achieve a strategic goal that is defined by senior management or the governing body of the organization. The business need is derived from the vision, mission, values, and objectives of the organization. This method helps to align the solution with the organizational strategy and direction. References: BABOK® Guide, page 28; Business Analysis Expert Certification, CCBA® | IIBA®, section “What Should I know to be CCBA Certified?”

The requirements management and communication knowledge area consists of four tasks: manage solution scope and requirements, manage requirements traceability, maintain requirements for reuse, and prepare requirements package. The outputs of these tasks are:

Traced requirements: These are requirements that are linked to other requirements, design elements, test cases, or other artifacts to ensure alignment and consistency.

Maintained requirements: These are requirements that are updated and stored in a repository for future reference and reuse.

Requirements package: This is a document or a set of documents that contains the requirements and related information for a specific audience, purpose, or point in time.

Communicated requirements: These are requirements that are shared with the relevant stakeholders in an appropriate format and level of detail.

The requirement management plan, on the other hand, is not an output of the requirements management and communication tasks, but an input. The requirement management plan is a document that describes how the requirements will be elicited, analyzed, documented, validated, and managed throughout the project. The requirement management plan is created as part of the business analysis planning and monitoring knowledge area.

References: While I cannot reference specific documents, the principles mentioned are in line with the general practices of business analysis as outlined in the Business Analysis Body of Knowledge (BABOK) and other business analysis resources. You can find some relevant web search results for CCBA requirements management and communication outputs below:

Overarching Tasks: Requirements Management and Communication

CERTIFICATION OF CAPABILITY IN BUSINESS ANALYSIS

CCBA Certification | Complete Guide on CCBA Certification - HKR Trainings

CCBA® and CBAP® Certifications Study Guide - Packt Subscription

CCBA Step-by-Step Application Process Guide - IIBA®

Project scope defines all of the required work to satisfy the requirements of the project, including the deliverables, activities, tasks, and resources needed. Project scope is usually documented in a project scope statement or a project charter. Project scope is different from product scope, which defines the features and functions of the product, service, or result that the project intends to deliver. Requirements envisioning is a technique to create a shared vision of the desired outcome among the stakeholders. Requirements foundation is a term used by some authors to describe the core concepts and principles of business analysis. References:

CCBA Handbook, page 11

[BABOK Guide], page 28

[Business Analysis for Practitioners: A Practice Guide], page 36

[Business Analysis: The Question and Answer Book], page 23

The best way to communicate the results of an impact analysis and a change approval to the project sponsor is to present the requirements at a high-level. This means that the BA should provide a summary of the main changes, the rationale behind them, the expected benefits and costs, and the impact on the solution scope and quality. A high-level presentation can be done verbally or in writing, depending on the preference and availability of the project sponsor. A high-level presentation is different from scheduling a requirements workshop, which is a technique to elicit, analyze, or validate requirements with a group of stakeholders; emailing the requirements package, which is a document that organizes and presents the requirements for a specific purpose, audience, or time frame; and creating use case scenarios, which are examples of how the solution will be used by the actors to achieve their goals. References:

CCBA Handbook, page 17

[BABOK Guide], page 50

[Business Analysis for Practitioners: A Practice Guide], page 59

[Business Analysis: The Question and Answer Book], page 29

The project scope statement is not an input to the qualitative risk analysis process, but an output of the project scope management process. The project scope statement defines and documents the project objectives, deliverables, requirements, assumptions, constraints, and boundaries. It helps to establish the baseline for the project scope, schedule, and cost. The project scope statement is not directly related to the qualitative risk analysis process, which focuses on prioritizing the identified risks based on their probability and impact12

The inputs to the qualitative risk analysis process are the following:

Risk management plan: This is a document that describes how the risk management activities will be planned, executed, and controlled throughout the project life cycle. It includes information such as the risk management methodology, roles and responsibilities, budget, schedule, risk categories, risk appetite, risk thresholds, risk scoring and ranking methods, risk reporting and communication formats, and risk audit and review processes. The risk management plan provides the guidance and direction for the qualitative risk analysis process34

Stakeholder register: This is a document that identifies and records the information about the project stakeholders, such as their names, roles, interests, influence, expectations, communication preferences, and engagement levels. The stakeholder register helps to determinethe relevant and appropriate stakeholders to involve in the qualitative risk analysis process, and to tailor the risk analysis and communication methods to suit their needs and preferences5

Risk register: This is a document that records the information about the project risks, such as their identification, description, causes, sources, categories, owners, responses, status, and updates. The risk register is the main input and output of the risk management processes, as it captures the results of the risk identification, analysis, response, and monitoring activities. The risk register provides the list of risks to be prioritized in the qualitative risk analysis process.

References:

A Guide to the Project Management Body of Knowledge (PMBOK® Guide), Sixth Edition, Chapter 5: Project Scope Management, Section 5.3: Define Scope, p. 154-155.

Certification of Capability in Business Analysis (CCBA®) - Simplilearn, Module 7: Requirements Analysis and Design Definition, Lesson 7.4: Define Solution Scope, p. 6-7.

A Guide to the Project Management Body of Knowledge (PMBOK® Guide), Sixth Edition, Chapter 11: Project Risk Management, Section 11.1: Plan Risk Management, p. 397-398.

Certification of Capability in Business Analysis (CCBA®) - Simplilearn, Module 8: Solution Evaluation, Lesson 8.2: Assess Enterprise Limitations, p. 6-7.

A Guide to the Project Management Body of Knowledge (PMBOK® Guide), Sixth Edition, Chapter 13: Project Stakeholder Management, Section 13.1: Identify Stakeholders, p. 513-514.

[Certification of Capability in Business Analysis (CCBA®) - Simplilearn], Module 6: Elicitation and Collaboration, Lesson 6.2: Prepare for Elicitation, p. 6-7.

[A Guide to the Project Management Body of Knowledge (PMBOK® Guide)], Sixth Edition, Chapter 11: Project Risk Management, Section 11.2: Identify Risks, p. 414-415.

[Certification of Capability in Business Analysis (CCBA®) - Simplilearn], Module 8: Solution Evaluation, Lesson 8.3: Recommend Actions to Increase Solution Value, p. 6-7.

According to the BABOK® Guide, alternative generation is a technique that involves identifying and exploring different ways to achieve the desired outcomes. One of the outputs of this technique is the option of doing nothing, which means maintaining the current state without implementing any changes. This option should always be included as a baseline for comparison with other alternatives and to assess the value of change. References: BABOK® Guide, page 72; Business Analysis Expert Certification, CCBA® | IIBA®, section “What Should I know to be CCBA Certified?”

Enterprise analysis is not a business analysis approach activity, but a business analysis knowledge area. Enterprise analysis is the process of defining the business need, assessing the capability gaps, determining the solution approach, defining the solution scope, and building the business case. It helps to align the business analysis work with the strategic goals and objectives of the organization12

The business analysis approach activities are the tasks and steps that will be performed to conduct the business analysis work and deliver the business analysis outputs. They include:

Requirements analysis: This is the process of defining, structuring, prioritizing, and verifying the requirements. It helps to ensure that the requirements are clear, complete, consistent, and aligned with the stakeholder needs and expectations34

Solution assessment: This is the process of evaluating the proposed or implemented solutions, assessing their value and performance, and recommending improvements or changes. It helps to ensure that the solutions meet the business need and objectives, and deliver the expected benefits and outcomes5

Business analysis governance: This is the process of establishing and maintaining the policies, standards, roles, responsibilities, and decision-making authority for the business analysis work. It helps to ensure that the business analysis work is planned, monitored, controlled, and reported effectively and efficiently.

References:

Business Analysis Body of Knowledge (BABOK® Guide), Version 3, Chapter 6: Strategy Analysis, p. 133-134.

Certification of Capability in Business Analysis (CCBA®) - Simplilearn, Module 7: Requirements Analysis and Design Definition, Lesson 7.1: Define Design Options

Business Analysis Body of Knowledge (BABOK® Guide), Version 3, Chapter 4: Requirements Analysis and Design Definition, p. 97-98.

Certification of Capability in Business Analysis (CCBA®) - Simplilearn, Module 7: Requirements Analysis and Design Definition, Lesson 7.2: Analyze Potential Value and Recommend Solution

Business Analysis Body of Knowledge (BABOK® Guide), Version 3, Chapter 7: Solution Evaluation, p. 157-158.

[Certification of Capability in Business Analysis (CCBA®) - Simplilearn], Module 8: Solution Evaluation, Lesson 8.1: Measure Solution Performance

[Business Analysis Body of Knowledge (BABOK® Guide)], Version 3, Chapter 2: Business Analysis Planning and Monitoring, p. 31-32.

[Certification of Capability in Business Analysis (CCBA®) - Simplilearn], Module 5: Planning and Monitoring, Lesson 5.3: Plan Business Analysis Governance