CCBA Certification of Capability in Business Analysis (CCBA) Question and Answers

The course of action that would resolve the situation of missing information is to conduct elicitation activities. Elicitation is the process of obtaining information from stakeholders or other sources to understand the needs, expectations, and context of the project. Elicitation activities can include interviews, workshops, surveys, observation, document analysis, and prototyping. By conducting elicitation activities, the BA can fill in the gaps, clarify the ambiguities, and confirm the accuracy of the information collected during the previous elicitation sessions. Elicitation activities are different from verifying the requirements results, which is the process of checking that the requirements are correctly and completely documented; conducting traceability analysis, which is the process of tracking the relationships and dependencies among the requirements and other project artifacts; and validating the requirements, which is the process of ensuring that the requirements are aligned with the business objectives, stakeholder needs, and solution scope.

References: The answer is verified and explained using the principles found in the CCBA® certification learning documents, specifically the Business Analysis Body of Knowledge (BABOK®) guide, which outlines the knowledge areas and skills required for effective business analysis and the handling of such situations123.

 The scenario describes a situation where there is a discrepancy between the system users’ perception and the system performance statistics regarding the new payments system. The BA needs to demonstrate to the users how the new system is performing and address their complaint. The best way to do this is to collect system metrics and communicate the results in an understandable format. System metrics are quantitative measures that indicate the performance, quality, and efficiency of the system. Communicating the results in an understandable format means using clear and simple language, charts, graphs, or tables to present the data and explain the benefits of the new system.

References: The answer and explanation are consistent with the CCBA® Handbook and the IIBA® website, which provide the details and best practices for the solution evaluation knowledge area, including the task of measure solution performance12. The CCBA® resources also describe the techniques and tools that can be used to perform each task in the business analysis process, such as system metrics and communication

According to the BABOK Guide, maintaining requirements is the process of ensuring that the requirements and designs remain aligned to and fulfill the business need1. One of the benefits of maintaining requirements is that they can easily be traced and reused for future projects or initiatives2. This can save time, effort, and resources for the organization. Therefore, the BA should communicate this benefit to the PM to help him or her understand the value of this task. References: BABOK Guide, CCBA Exam Prep

The pair of requirements fail to meet the characteristic of consistency, which means that the requirements do not contradict or conflict with each other or with other requirements. The first requirement states that comments should not be deleted by the users, while the second requirement states that users with super administrator privileges should be able to delete every page/section in the application. This implies that super administrators can also delete comments, which contradicts the first requirement. The BA should resolve this inconsistency by clarifying the scope and definition of the terms “users” and “comments”, and by specifying the exceptions or conditions for the deletion of comments.

References: The answer is verified and explained using the principles found in the CCBA® certification learning documents, specifically the Business Analysis Body of Knowledge (BABOK®) guide, which outlines the knowledge areas and skills required for effective business analysis and the handling of such situations

The scenario describes a task that involves verifying requirements for a software solution. The verification process is a part of the requirements life cycle management knowledge area, which is one of the six knowledge areas covered by the CCBA® certification. According to the CCBA® Handbook and the IIBA® website, checklists are one of the techniques that can be used to verify requirements, as they provide a structured way of ensuring that all important items are included and accounted for in the final requirements deliverable12. Checklists can also help to identify any gaps, inconsistencies, or errors in the requirements12.

References: The answer and explanation are consistent with the CCBA® Handbook and the IIBA® website, which provide the details and best practices for the requirements life cycle management knowledge area, including the task of verify requirements12. The CCBA® resources also describe the techniques and tools that can be used to perform each task in the business analysis process12.

According to the BABOK® Guide, gap analysis is a technique that is used to compare the current state and the future state of an organization, and identify the differences or gaps between them. Gap analysis can help to determine the changes needed in the new application by identifying the existing functionality, the desired functionality, and the gaps that need to be addressed. Gap analysis can also help to estimate the complexity of the project by assessing the size and impact of the gaps, and the effort and resources required to close them. References: BABOK® Guide, Version 3, Chapter 10, Section 10.17; Business Analysis Expert Certification, CCBA® | IIBA®, Section “What Should I know to be CCBA Certified?”

 According to the BABOK® Guide, a requirement attribute is a piece of information that describes or qualifies a requirement. Requirement attributes can be used to organize, rank, and manage requirements throughout the requirements lifecycle. One of the common requirement attributes is priority, which indicates the relative importance or urgency of a requirement. By including priority as a requirement attribute, the business analyst (BA) can allocate the requirements to the proper phase based on their value and dependency. References: BABOK® Guide, Version 3, Chapter 7, Section 7.3.2; Business Analysis Expert Certification, CCBA® | IIBA®, Section “What Should I know to be CCBA Certified?”

According to the CCBA® certification, one of the main objectives of business analysis is to identify and evaluate opportunities for better business outcomes12. One of the ways to achieve this is to increase efficiencies by streamlining business processes, eliminating waste, and enhancing productivity34. By automating repetitive tasks that require multiple staff touchpoints, the BA can reduce human errors, save time, and improve quality, which are all indicators of increased efficiency.

References: CCBA Career Guide, Business Analysis Expert Certification, CCBA® | IIBA®, About Certification of Capability in Business Analysis (CCBA), Certification of Capability in Business Analysis™ (CCBA®)

The scenario describes a situation where the bank has discovered a major security loophole that could compromise customer information. This is a critical issue that needs to be resolved as soon as possible to avoid potential losses, reputational damage, and legal consequences. Therefore, the BA should use urgency as the main factor to convince the bank to move forward with the emergency fix, as it demonstrates the importance and priority of the issue. Urgency also implies that the fix is a temporary solution that will be replaced by a more robust and permanent one in the future.

References: The answer and explanation are consistent with the CCBA® Handbook and the IIBA® website, which state that business analysts should consider urgency as one of the criteria for evaluating and prioritizing requirements12. The CCBA® resources also emphasize the role of business analysts in ensuring the security and confidentiality of information12.

A plan-driven approach to business analysis is an approach that plans upfront with maximum control of what the expected implementation would be. The waterfall project methodology supports a predictive approach in planning. In this approach, the business analyst defines the requirements at a high level and then seeks formal approval from the stakeholders before proceeding to the next phase of the project. This ensures that the scope and objectives of the project are clear and agreed upon by all parties involved. The initial requirements are also known as the business requirements or the scope statement. They provide a broad overview of the problem or opportunity, the desired outcomes, the assumptions, constraints, and risks1.

When it comes to communication in a plan-driven approach, the type of communication that is likely required is formal. Formal communication is communication that follows a predefined structure, format, and protocol. It is usually documented, approved, and distributed through official channels. Formal communication is suitable for a plan-driven approach, as it helps to ensure clarity, consistency, accuracy, and traceability of the information. Formal communication also helps to manage expectations, reduce ambiguity, and avoid conflicts or misunderstandings2.

The other options are not correct types of communication that are likely required in a plan-driven approach:

• A. Face-to-face: Face-to-face communication is communication that occurs when the participants are physically present and interact directly with each other. It is usually informal, spontaneous, and dynamic. Face-to-face communication is more suitable for an adaptive or agile approach, as it helps to foster collaboration, feedback, and trust among the stakeholders2.
• B. Ad hoc: Ad hoc communication is communication that occurs without any prior planning or preparation. It is usually informal, flexible, and responsive. Ad hoc communication is more suitable for an adaptive or agile approach, as it helps to accommodate changes, uncertainties, and emergent issues2.
• C. Chain of command: Chain of command communication is communication that follows the hierarchical structure of the organization. It is usually formal, authoritative, and controlled. Chain of command communication is not a type of communication that is specific to a plan-driven approach, as it can be used in any organizational context. However, it may not be the most effective or efficient way of communicating, as it may create delays, distortions, or barriers in the information flow2. References:
• 1: How to Choose the Right Business Analysis Approach2, section Waterfall Approach, page 1-2
• 2: How to create a business analysis communication plan1, section Types of communication, page 2-3

The previous task that could assist the BA in performing the impact analysis is to create requirement relationships. This is because creating requirement relationships is the process of identifying and documenting the connections or associations between different requirements or other elements. Creating requirement relationships can help to understand the dependencies, traceability, composition, generalization, or other types of relationships among the requirements. This can facilitate the impact analysis of a change by showing how it affects other related requirements or elements. The other options are not as helpful or relevant as creating requirement relationships. References:

• BABOK Guide, section 4.3.2: Validate Requirements
• CCBA Practice Test, question 107

 The business analyst will use the solution scope as a guideline to define the relationships between business requirements and solution components. The solution scope describes the boundaries of the solution, including what is in scope and what is out of scope, as well as the key assumptions and constraints that affect the solution1. By using the solution scope, the BA can ensure that the requirements and the solution components are aligned with the business needs and the stakeholder expectations, and that they do not conflict with each other or introduce unnecessary complexity or risk.

References: The answer is based on the BABOK® Guide, which is a key resource for the CCBA® certification. Specifically, it relates to the Strategy Analysis knowledge area, where defining solution scope and business case is a key task for the BA12. It also relates to the Requirements Analysis and Design Definition knowledge area, where the BA should specify and model requirements and designs, and allocate requirements to solution components

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, a textual requirement is a requirement that is expressed in natural language, such as English, French, or Arabic. A textual requirement should describe the capabilities of the solution, any conditions that must exist for the requirement to operate, and any constraints that may prevent the solution from fulfilling the requirement. A constraint is a restriction or limitation that affects the solution, such as a technical, legal, regulatory, or business rule. Therefore, option A is the correct answer. The other options are not components of the textual requirement, but rather guidelines or techniques for writing effective textual requirements. References: BABOK® Guide, page 115; Business Analysis Expert Certification, CCBA® | IIBA®, section “What Should I know to be CCBA Certified?”

Diagram Description automatically generated

A process model is a visual representation of the activities, events, and outcomes that describe a business process. Process models can be used to verify and validate the requirements by showing how the current and future states of the process operate and interact. A single process model on automation for all stakeholders (option A) may not capture the specific needs and concerns of each stakeholder group, and may not reflect the complexity and variability of the process. A database structure in the viewpoint of the selected stakeholders (option B) may not be relevant or understandable for all stakeholders, and may not address the process flow and logic. A list of requirements in a spreadsheet for all stakeholders (option C) may not provide enough detail or clarity for the stakeholders to verify and validate the requirements, and may not show the relationships and dependencies among the requirements. A set of process models in the viewpoint of the selected stakeholders (option D) is the best option, as it allows the BA to tailor the process models to the level of detail and perspective that each stakeholder group needs, and to show how the process works and changes in different scenarios and situations. References: BABOK® Guide v3, section 10.25 Process Modeling; Business Analysis for Practitioners: A Practice Guide, section 5.3.2 Process Modeling.

Stability is the factor that describes the affected requirement, as it indicates the likelihood of the requirement remaining constant and static. Requirements that are not stable or whose definition changes frequently are given a lower priority to minimize recurrence, rework, and time and resource waste. References: Please refer to the CCBA® guide and other official IIBA resources for specific references and detailed explanations. You can also check out the following web search results for more guidance:

• Five Requirements Prioritization Methods - Business Analyst Articles …
• What Are Requirement Prioritization Techniques? - Techcanvass
• 5 Popular Requirements Prioritisation Techniques - The Business Analyst …
• How to prioritize requirements – The Functional BA
• An Overview of Requirements Prioritization > Business Analyst Community …

 This is because performance metrics are measurable indicators that help to evaluate the effectiveness and efficiency of the business analysis work. By identifying the performance metrics before starting the project, the consulting company can set clear expectations, monitor progress, and demonstrate value to the client. Recommending a new methodology (A) is not a valid option, as it does not address the feedback about the technical jargon in the documents. Assigning a different BA to the project (B) is not a good option, as it may disrupt the rapport and trust that the assigned BA has built with the stakeholders. Discussing the feedback during the brainstorming sessions after project completion © is a good practice, but it is too late to improve the current project outcome. References: CCBA Practice Test, CCBA Mock Test

According to the BABOK® Guide, abstraction is the process of removing or suppressing details to focus on essential characteristics. Abstraction helps to make the requirements as re-usable as possible by avoiding unnecessary or specific details that may vary across different contexts or situations. For a pharmaceutical distribution company with an expansion plan across many states, each with their own tools and methods, the BA should describe the requirements at a high level of abstraction to capture the common and essential features and functions that are applicable to all states. References: BABOK® Guide, Version 3, Chapter 10: Techniques, Section 10.2: Abstraction, Page 370; Chapter 6: Requirements Life Cycle Management, Section 6.4: Approve Requirements, Page 154.

This is because when it is not possible to implement all the requirements at once, the BA should prioritize the requirements based on their value, urgency, and dependency, and assign them to different releases or iterations. This way, the most important requirements can be delivered first, and the feedback from the stakeholders can be incorporated in the subsequent releases. Redefining the business requirements (A) is not necessary, as they have already been signed off. Recommending a reduction in the project scope (B) is not a good option, as it may compromise the value and quality of the solution. Ensuring all requirements are traceable using a matrix (D) is a good practice, but it does not address the issue of technical constraints. References: CCBA Practice Test, CCBA Mock Test

This is because the BA should respect the scope and objectives of the project, and consult with the owner before making any changes to the existing processes. The owner may or may not agree to incorporate the improvements, depending on the cost, benefit, and risk involved. Creating documentation based on the observed processes (B) is not a good option, as it may miss the opportunities for improvement that could enhance the quality and efficiency of the restaurant operations. Providing documentation of improved procedures © is not a valid option, as it may violate the scope and expectations of the project, and create confusion and resistance among the stakeholders. Performing benchmarking and market analysis (D) is not a relevant option, as it may be beyond the scope and budget of the project, and may not reflect the unique value proposition of the restaurant. References: CCBA Practice Test, CCBA Mock Test

Organizational modelling is used to represent the roles, structures, and hierarchies within an organization, which includes understanding the formal relationships between different people working in the enterprise. It helps in identifying how individuals interact with each other and with the systems and processes of the organization.

 According to the Capability in Business Analysis™ (CCBA®) guidelines, one of the tasks that business analysts perform in the requirement elicitation activity is to conduct elicitation sessions, which involves facilitating workshops and other techniques to elicit the requirements from the stakeholders12. During the elicitation sessions, the business analyst should be prepared to handle any issues that may arise, such as scope creep, conflicting opinions, or unclear requirements34. If a stakeholder raises an issue that is outside of the project’s scope, the business analyst should consider the issue’s impact on the project and gain agreement with stakeholders on the next step, such as deferring the issue to a later stage, escalating the issue to the project manager, or revising the scope statement5.

References: The CCBA® learning documents, which can be found on the IIBA website12, describe the various tasks and techniques that a business analyst can use to elicit the requirements from the stakeholders, including the conduct of elicitation sessions and the handling of issues. Additionally, the IIBA Bookstore offers resources that provide further insights into the objectives and best practices for business analysis, including the facilitation of workshops and the management of scope3

 An internal enterprise asset that the BA must include in the analysis of the current state is the organizational structure. The organizational structure is the way that the enterprise is arranged and governed, including its roles, responsibilities, reporting relationships, and authority levels. The organizational structure influences the business processes, culture, communication, and decision-making of the enterprise. The BA should include the organizational structure in the analysis of the current state to understand the existing capabilities, constraints, and opportunities of the enterprise, as well as to identify the stakeholders and their needs, expectations, and influence.

References: The answer is verified and explained using the principles found in the CCBA® certification learning documents, specifically the Business Analysis Body of Knowledge (BABOK®) guide, which outlines the knowledge areas and skills required for effective business analysis and the handling of such situations12.

Stakeholder analysis is a technique to identify the stakeholders who have an interest or influence on the project, and to determine their needs, expectations, and level of involvement. Stakeholder analysis is critical for communications planning, as it helps to tailor the communication content, frequency, and format to suit the preferences and requirements of each stakeholder group. Stakeholder analysis also helps to identify potential risks, issues, and conflicts that may arise from different stakeholder perspectives and expectations. Stakeholder analysis is usually performed at the beginning of the project and updated throughout the project lifecycle as new stakeholders emerge or existing ones change their roles or interests. References:

• CCBA Handbook, page 16
• [BABOK Guide], page 30
• [Business Analysis for Practitioners: A Practice Guide], page 39
• [Business Analysis: The Question and Answer Book], page 25

 The BA was attempting to achieve the effect of stimulating teamwork in a fun situation by using a collaborative game to elicit requirements. A collaborative game is a technique that uses game elements, such as rules, goals, challenges, rewards, and feedback, to engage the stakeholders in a creative and interactive way. A collaborative game can help to overcome the challenges of a stalled project, such as low motivation, poor communication, lack of trust, or resistance to change, by fostering a positive and collaborative atmosphere, enhancing stakeholder participation and involvement, generating new ideas and insights, and building consensus and commitment. A collaborative game can also help to elicit requirements that are more complete, accurate, and aligned with the stakeholder needs and expectations.

References: The answer is verified and explained using the principles found in the CCBA® certification learning documents, specifically the Business Analysis Body of Knowledge (BABOK®) guide, which outlines the knowledge areas and skills required for effective business analysis and the handling of such situations123.

MoSCoW prioritization is a technique that helps to classify requirements or user stories based on their relative importance and urgency. The acronym stands for Must have, Should have, Could have, and Won’t have. This technique enables the business analyst (BA) and the stakeholders to agree on the minimum viable product (MVP) and the order of delivery for the project scope. MoSCoW prioritization also supports incremental and iterative approaches, as it allows for frequent feedback and validation of the product value. References: BABOK® Guide, Version 3, Chapter 10, Section 10.46; Business Analysis Expert Certification, CCBA® | IIBA®, Section “What Should I know to be CCBA Certified?”

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?”

If you’re a business analyst and using an event-based elicitation task, such as a requirements workshop, the purpose of the workshop can be considered as essential to establish with the participants. The purpose of the workshop is the clear and concise statement of what the workshop intends to achieve, such as identifying, analyzing, validating, or prioritizing the requirements. The purpose of the workshop helps to set the expectations and focus of the participants, as well as to guide the agenda, activities, and facilitation techniques of the workshop. The purpose of the workshop is different from cost management, which is the process of planning, estimating, budgeting, and controlling the costs of the project; deadlines, which are the specific dates or times by which the tasks or deliverables must be completed; and ground rules, which are the agreed-upon norms of behavior and interaction for the workshop participants. References:

• CCBA Handbook, page 19
• [BABOK Guide], page 63
• [Business Analysis for Practitioners: A Practice Guide], page 69
• [Business Analysis: The Question and Answer Book], page 31

 Consulted is a RACI designation that indicates the stakeholders who need to be consulted before a decision or action is taken1. Consulted can help the BA to improve the communication of the business analysis information from the elicitation phase by involving the testing and training teams in the review and validation of the requirements and designs. By consulting the testing and training teams, the BA can ensure that the requirements and designs are feasible, testable, and aligned with the business needs and objectives2. The other options are not the best RACI designations for the training and testing teams, as they may not reflect their roles and responsibilities in the project. Responsible is a RACI designation that indicates the stakeholders who are assigned to do the work or complete the task3. Accountable is a RACI designation that indicates the stakeholders who have the authority and accountability for the work or task, and who approve the final outcome4. Informed is a RACI designation that indicates the stakeholders who need to be kept informed of the progress or results of the work or task. References:

• 1: RACI Matrix: Definition, Benefits and Examples
• 2: How to Consult Stakeholders Effectively
• 3: RACI Matrix: Definition, Benefits and Examples
• 4: RACI Matrix: Definition, Benefits and Examples
• : RACI Matrix: Definition, Benefits and Examples

A constraint is a restriction or limitation that affects the performance or value of a solution1. Constraints can be related to time, cost, quality, scope, resources, or technology2. In this question, option A is a valid constraint because it specifies a time limit for the solution implementation. Options B, C, and D are not constraints, but rather objectives or goals that the solution should achieve or support.

References: The answer is based on the BABOK® Guide, which is a key resource for the CCBA® certification. Specifically, it relates to the Strategy Analysis knowledge area, where defining solution scope and business case is a key task for the BA13. It also relates to the Requirements Analysis and Design Definition knowledge area, where the BA should define design options and recommend a solution14.

1: Certification of Capability in Business Analysis™ (CCBA®) Handbook 2: Business Analysis Expert Certification, CCBA® | IIBA® 3: Certification of Capability in Business Analysis™ (CCBA®) 4: The Ultimate Guide to Business Capability Analysis

The quality criteria that must be satisfied when the BA is defining requirements relationships is necessary. This means that the BA should ensure that each requirement has a clear and valid reason or purpose for being included in the solution scope. A necessary requirement is one that supports a business goal or objective, addresses a problem or opportunity, or satisfies a stakeholder need or expectation.

The other options are incorrect because:

• Option A is incorrect because priority is not a quality criteria that must be satisfied when the BA is defining requirements relationships, but a factor that the BA should consider when prioritizing requirements. Priority is the relative importance or urgency of a requirement based on its value, feasibility, risk, or dependency.
• Option B is incorrect because complexity is not a quality criteria that must be satisfied when the BA is defining requirements relationships, but a factor that the BA should consider when analyzing requirements. Complexity is the degree of difficulty or uncertainty involved in implementing or maintaining a requirement based on its scope, scale, or interdependencies.
• Option D is incorrect because source is not a quality criteria that must be satisfied when the BA is defining requirements relationships, but an attribute that the BA should document when managing requirements. Source is the origin or reference of a requirement such as a stakeholder, document, regulation, standard, etc.

References:

• BABOK Guide v3, section 6.2: Requirements Analysis and Design Definition
• CCBA Exam Questions, question 31

The business policies will help the BA because they define the limits within which decisions must be made in accordance with contracts, agreements, warranties, or certifications. This means that the business policies specify the rules or constraints that govern or regulate the decisions or actions of stakeholders or an organization. The business policies can help the BA to identify and prioritize the requirements that are mandatory, essential, or desirable for a solution.

The other options are incorrect because:

• Option A is incorrect because business policies do not provide lessons learned from previous projects that should be incorporated into planning approach for current projects. Lessons learned are insights or knowledge gained from experience or feedback that can be used to improve future performance or outcomes. Lessons learned can help the BA to identify and avoid potential risks or issues in planning approach for current projects.
• Option B is incorrect because business policies do not outline the organizational roles and responsibilities in an effort to define a prioritization approach that involves the correct stakeholders. Organizational roles and responsibilities are descriptions of the functions or duties that stakeholders or groups perform within an organization. Organizational roles and responsibilities can help the BA to identify and engage the relevant stakeholders in a prioritization approach.
• Option C is incorrect because business policies do not describe industry regulations and are used to develop a framework for sound business decision making. Industry regulations are standards or rules that are imposed by external authorities or bodies on an industry or sector. Industry regulations can help the BA to ensure compliance and alignment of a solution with legal or ethical requirements.

References:

• BABOK Guide v3, section 10.1: Business Policies
• CCBA Exam Questions, question 18

This answer is correct because keeping separate records for customers who are also vendors is a duplicate task that can be eliminated by using the new software module. This would improve efficiency and accuracy of data. The other options are not opportunities identified by the BA in this scenario. References: BABOK Guide v3, page 15; CCBA Mock Test, question 9

“The solution will report the average number of days an account payment is outstanding” is an example of a key performance indicator (KPI). A KPI is a measurable value that demonstrates how effectively an organization or a solution is achieving its key business objectives or goals. KPIs can help to monitor and evaluate the performance of a solution or an organization over time, identify areas of improvement, and support decision making. The average number of days an account payment is outstanding is a KPI that measures how well the AP solution supports the goal of timely payment processing. References: : Key Performance Indicator (KPI)

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

According to the BABOK® Guide, the level of complexity of a solution is influenced by the number and nature of the relationships among the requirements, as well as the requirements themselves. The more interdependent, conflicting, or ambiguous the requirements are, the more complex the solution will be. Therefore, option A is the correct answer. The other options are not directly related to the complexity of the requirements, but rather to the complexity of the project environment or the project management. References: BABOK® Guide, page 11; Business Analysis Expert Certification, CCBA® | IIBA®, section “What Should I know to be CCBA Certified?”

 The performance of all requirements management and communication activities is governed by the business analysis plans. The business analysis plans are the outputs of the plan business analysis approach and plan business analysis governance tasks. They describe how the business analysis work will be performed, monitored, and controlled throughout the project lifecycle. The business analysis plans include the business analysis approach, the business analysis performance and communication plans, the requirements management plan, the traceability and change management plans, and the business analysis process assets. The business analysis plans are different from the business analyst, who is the person responsible for performing the business analysis work; the project manager, who is the person responsible for leading the project team and delivering the project objectives; and the project sponsor, who is the person who provides the funding and support for the project. References:

• CCBA Handbook, page 15
• [BABOK Guide], page 38
• [Business Analysis for Practitioners: A Practice Guide], page 41
• [Business Analysis: The Question and Answer Book], page 27

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 BA should engage with the technical team to understand their concerns and resistance. By meeting with them, the BA can clarify any misunderstandings, provide additional information, and work collaboratively to address any issues. This approach aligns with the CCBA®’s emphasis on effective stakeholder engagement and communication to ensure that all parties are aligned and that project deliverables are accepted.

References: The CCBA® Handbook and the Business Analysis Competency Model from IIBA outline the importance of stakeholder collaboration and the BA’s role in facilitating communication between business and technical teams to achieve project success

 Job shadowing is not a business analysis planning & monitoring activity, but an elicitation technique. Job shadowing involves following and observing a stakeholder as they perform their work tasks. It helps to elicit information about the current state of the business processes, the roles and responsibilities of the stakeholders, the problems and issues they face, and the opportunities for improvement. Job shadowing is part of the elicitation and collaboration knowledge area in the CCBA certification12

The business analysis planning & monitoring activities are the tasks and steps that are performed to plan, monitor, and control the business analysis work and deliver the business analysis outputs. They include:

• Defining and determining business analysis processes: This is the activity of establishing and documenting the business analysis approach, activities, tasks, deliverables, roles, responsibilities, and governance. It helps to plan, monitor, and control the business analysis work, and to align it with the project objectives and stakeholder preferences.
• Planning how requirements will be approached, traced, and prioritized: This is the activity of defining and documenting the requirements management plan, which specifies how the requirements will be elicited, analyzed, documented, validated, verified, approved, communicated, traced, prioritized, changed, and maintained. It helps to ensure the quality, consistency, and alignment of the requirements with the stakeholder needs and expectations.
• Identifying stakeholders: This is the activity of determining who are the individuals or groups that have an interest or influence on the project or the solution, and what are their needs, expectations, and level of involvement. It helps to plan and execute the stakeholder engagement and communication strategies, and to manage the stakeholder relationships.

References:

• 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.
• Business Analysis Certification Competencies, CCBA® | IIBA®, section “Plan Business Analysis Work”
• CCBA Step-by-Step Application Process Guide - IIBA®, page 6, section “4. Review the Exam Blueprint”
• CCBA® and CBAP® Certifications Study Guide - Google Books, Chapter 2: Business Analysis Planning and Monitoring
• [CCBA® and CBAP® Certifications Study Guide - Packt Subscription], Chapter 2: Business Analysis Planning and Monitoring

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?”

SMART goals are objectives that are designed to be Specific, Measurable, Achievable, Relevant, and Time-bound. The element of ‘Relevant’ in SMART goals refers to ensuring that the goal aligns with broader business strategies, visions, missions, and values. In the context of the facilities management company’s objective to double the revenue of their office waste recycling service, the goal would need to be relevant to the enterprise’s overall direction and purpose to ensure it contributes meaningfully to the organization’s success.

References: The information is based on the SMART goals framework as understood in business analysis practices up to the year 2021. For the most current and detailed explanations, please refer to the latest resources provided by the International Institute of Business Analysis (IIBA) or the specific learning documents for the Capability in Business Analysis™ (CCBA®) certification.

 A terminology register is a document that defines the terms, acronyms, and nomenclature used in a specific domain or context. It helps to ensure consistency and clarity in communication and documentation. A terminology register is one of the outputs of the Plan Business Analysis Approach task, which is part of the Business Analysis Planning and Monitoring knowledge area. A terminology register is different from a data dictionary, which describes the attributes and relationships of data elements in a solution. A WBS is a work breakdown structure, which is a hierarchical decomposition of the project scope and deliverables. A business analysis register is a tool that tracks the status and ownership of business analysis deliverables and issues. References: Business Analysis Expert Certification, CCBA® | IIBA®, Business Analysis Certification Competencies, CCBA® | IIBA®, CERTIFICATION OF CAPABILITY IN BUSINESS ANALYSIS

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]

Job observation is a technique that involves observing and documenting the tasks, activities, and behaviors of a stakeholder or a group of stakeholders in their work environment. It helps to elicit information about the current state of the business processes, the roles and responsibilities of the stakeholders, the problems and issues they face, and the opportunities for improvement. Job observation can be done in different ways, such as:

• Job shadowing: This is a process of following and observing a stakeholder as they perform their work tasks. It allows the business analyst to gain a firsthand and detailed understanding of the stakeholder’s perspective, needs, challenges, and expectations. Job shadowing can also facilitate rapport and trust building between the business analyst and the stakeholder12
• Video or audio recording: This is a process of capturing the work tasks and activities of a stakeholder or a group of stakeholders using a video or audio device. It allows the business analyst to review and analyze the recorded data at a later time, and to identify patterns, trends, gaps, and inconsistencies. Video or audio recording can also provide a visual or auditory evidence of the current state of the business processes3
• Work sampling: This is a process of observing and recording the work tasks and activities of a stakeholder or a group of stakeholders at random intervals over a period of time. It allows the business analyst to estimate the frequency, duration, and variability of the work tasks and activities, and to measure the productivity, efficiency, and quality of the work performance. Work sampling can also provide a statistical representation of the current state of the business processes.

The other options are not elicitation processes that are part of job observation, but they are related to other business analysis knowledge areas or techniques:

• Identifying stakeholders: This is a process of determining who are the individuals or groups that have an interest or influence on the project or the solution, and what are their needs, expectations, and level of involvement. It helps to plan and execute the stakeholder engagement and communication strategies, and to manage the stakeholder relationships. Identifying stakeholders is part of the business analysis planning and monitoring knowledge area.
• Defining and determining business analysis processes: This is a process of establishing and documenting the business analysis approach, activities, tasks, deliverables, roles, responsibilities, and governance. It helps to plan, monitor, and control the business analysis work, and to align it with the project objectives and stakeholder preferences. Defining and determining business analysis processes is part of the business analysis planning and monitoring knowledge area.
• Planning how requirements will be approached, traced, and prioritized: This is a process of defining and documenting the requirements management plan, which specifies how the requirements will be elicited, analyzed, documented, validated, verified, approved, communicated, traced, prioritized, changed, and maintained. It helps to ensure the quality, consistency, and alignment of the requirements with the stakeholder needs and expectations. Planning how requirements will be approached, traced, and prioritized is part of the business analysis planning and monitoring knowledge area.

References:

• 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.
• Business Analysis Body of Knowledge (BABOK® Guide), Version 3, Chapter 4: Elicitation and Collaboration, Section 4.2: Elicitation Techniques, p. 70-71.
• [Certification of Capability in Business Analysis (CCBA®) - Simplilearn], Module 6: Elicitation and Collaboration, Lesson 6.3: Conduct Elicitation, p. 8-9.
• [Business Analysis Body of Knowledge (BABOK® Guide)], Version 3, Chapter 4: Elicitation and Collaboration, Section 4.2: Elicitation Techniques, p. 71-72.
• [Certification of Capability in Business Analysis (CCBA®) - Simplilearn], Module 6: Elicitation and Collaboration, Lesson 6.3: Conduct Elicitation, p. 10-11.
• [Business Analysis Body of Knowledge (BABOK® Guide)], Version 3, Chapter 2: Business Analysis Planning and Monitoring, Section 2.2: Plan Stakeholder Engagement, p. 34-35.
• [Certification of Capability in Business Analysis (CCBA®) - Simplilearn], Module 5: Planning and Monitoring, Lesson 5.2: Conduct Stakeholder Analysis, p. 6-7.
• [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-33.
• [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 2: Business Analysis Planning and Monitoring, Section 2.3: Plan Business Analysis Governance, p. 36-37.
• [Certification of Capability in Business Analysis (CCBA®) - Simplilearn], Module 5: Planning and Monitoring, Lesson 5.3: Plan Business Analysis Governance, p. 6-7.

Business analysis planning and monitoring includes tasks that organize and coordinate the efforts of business analysis professionals and stakeholders. These tasks produce outputs that are used as guidance for the other tasks1. Some of the activities involved in this knowledge area are:

• Planning how requirements will be approached, traced, and prioritized. This involves defining the requirements life cycle, the level of detail and quality of the requirements, the traceability approach, and the prioritization methods2.
• Identifying stakeholders. This involves determining who are the key individuals or groups that have an interest or influence on the solution or the business need, and analyzing their needs, expectations, and level of involvement2.
• Defining and determining business analysis processes. This involves selecting the appropriate business analysis approach (such as predictive, adaptive, or hybrid), defining the deliverables and activities, and estimating the effort and resources needed for the business analysis work2.

Job shadowing, on the other hand, is not a business analysis planning and monitoring activity, but an elicitation technique. It involves observing a stakeholder performing their work tasks to gain a better understanding of their needs and challenges2. References:

• 2: CBAP/CCBA Certified Business Analysis Study Guide, 2nd Edition, by Susan Weese and Terri Wagner, Wiley, 2011.
• 1: A) Business Analysis Planning and Monitoring | The International Institute of Business Analysisâ„¢.

According to the IIBA, a data flow diagram is a technique that shows where data comes from, which activities process the data, and if the output results are stored or utilized by another activity or external entity1. A data flow diagram consists of four basic elements2:

• Data flow: A data flow is a line that represents the movement of data from one point to another. It can be labeled with the name or description of the data.
• External entities: External entities are rectangles that represent the sources or destinations of data outside the system boundary. They can be people, organizations, systems, or devices that interact with the system.
• Data process: A data process is a circle that represents a process that transforms data by performing some operation on it. It can be labeled with the name or description of the process.
• Data store: A data store is an open-ended rectangle that represents a place where data is stored or retrieved. It can be a database, a file, a queue, or a memory.

Among these elements, the one that represents a process that transforms data by combining it with other data is concatenation. Concatenation is a type of data process that joins two or more data flows into one data flow. For example, a concatenation process can combine the first name and last name data flows into a full name data flow3. References:

• 1: BABOK Guide, section 10.13 Data Flow Diagrams, page 402
• 2: CCBA® and CBAP® Certifications Study Guide, section Data flow diagrams, page 1
• 3: Data Flow Diagram Symbols, Types, and Tips, section Data Flow Diagram Symbols, page 1

Benchmarking is a technique that involves comparing the performance, practices, or processes of one organization with those of another organization or industry leader. Benchmarking can help identify areas of improvement, best practices, and realistic goals. However, benchmarking also has some disadvantages, such as:

• Time consumption: Benchmarking can be a time-consuming process that requires collecting, analyzing, and interpreting large amounts of data from multiple sources. It may also involve visiting other organizations or conducting interviews with their staff. Benchmarking may divert resources and attention from other important tasks or activities.
• Requirement of expertise of the person conducting the study: Benchmarking requires a high level of expertise and skill from the person conducting the study. The person must be able to select appropriate benchmarks, measure performance accurately, interpret results correctly, and communicate findings effectively. The person must also be aware of the potential biases, limitations, and challenges of benchmarking, such as data availability, validity, reliability, and comparability.
• Inability to produce innovative solutions: Benchmarking can limit the creativity and innovation of the organization by focusing on existing practices and processes of other organizations. Benchmarking may create a tendency to imitate or copy others, rather than to develop original or novel solutions. Benchmarking may also discourage risk-taking or experimentation, as the organization may become complacent or satisfied with matching or exceeding the benchmarks.

Discovery of new approaches, on the other hand, is not a disadvantage of benchmarking, but rather a potential benefit. Benchmarking can help the organization learn from the best practices and experiences of other organizations, and discover new or alternative ways of doing things. Benchmarking can expose the organization to different perspectives, ideas, and methods that can enhance its performance and competitiveness. References: Capability in Business Analysis™ (CCBA®) Certification, Business Analysis Driving Business Success, A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide)

The business analyst should consider the business relevance of the requirements while tracing them to the business needs, goals, and objectives. This will help the BA to ensure that the requirements are aligned with the business value and provide a clear rationale for their inclusion in the solution scope. By tracing the requirements, the BA can also identify and eliminate any unnecessary or redundant features that do not contribute to the business value.

References: The answer is based on the BABOK® Guide, which is a key resource for the CCBA® certification. Specifically, it relates to the Requirements Life Cycle Management knowledge area, where tracing requirements is a key task for the BA12. It also relates to the Business Analysis Planning and Monitoring knowledge area, where the BA should define the business analysis approach and the requirements prioritization process

 The element of stakeholder management that the BA is performing when negotiating and resolving conflict with stakeholders to ensure they participate in required BA activities is gaining agreement on commitments. This means that the BA is establishing consensus or acceptance among stakeholders regarding their roles, responsibilities, expectations, deliverables, and timelines for a project or a solution. The BA is also addressing any differences or disputes among stakeholders that may hinder their participation or collaboration.

The other options are incorrect because:

• Option A is incorrect because confirming elicitation results is not an element of stakeholder management, but an element of elicitation. Confirming elicitation results means verifying and validating that the information gathered from stakeholders during elicitation activities is accurate, complete, clear, and consistent.
• Option C is incorrect because monitoring stakeholder engagement is not an element of stakeholder management, but an element of stakeholder analysis. Monitoring stakeholder engagement means assessing and tracking the level of involvement, interest, influence, and impact of stakeholders throughout a project or a solution.
• Option D is incorrect because planning stakeholder engagement is not an element of stakeholder management, but an element of stakeholder analysis. Planning stakeholder engagement means defining and documenting the strategies, methods, and activities for engaging and communicating with stakeholders.

References:

• BABOK Guide v3, section 2.5: Manage Stakeholder Collaboration
• CCBA Exam Questions, question 19

The requirement classification schema that this requirement belongs to is nonfunctional requirements. Nonfunctional requirements are statements of conditions or restrictions on a solution or its components that affect its quality, performance, usability, reliability, security, etc. Nonfunctional requirements specify how well a solution should perform or behave.

The other options are incorrect because:

• Option B is incorrect because stakeholder requirements are not a requirement classification schema, but a requirement type. Stakeholder requirements are statements of needs, expectations, preferences, or problems of stakeholders or an organization.
• Option C is incorrect because transitional requirements are not a requirement classification schema, but a requirement type. Transitional requirements are statements of capabilities or conditions that enable a solution to transition from its current state to its desired future state.
• Option D is incorrect because functional requirements are not a requirement classification schema, but a requirement type. Functional requirements are statements of features, functions, or behaviors of a solution or its components that enable it to provide value to stakeholders.

References:

• BABOK Guide v3, section 6.1: Specify and Model Requirements
• CCBA Exam Questions, question 35

 Sharing the requirements document with the development team immediately may lead to a lack of proper review and validation of the requirements by relevant stakeholders. This can result in rework if errors are found later, impacting the project timeline and potentially leading to delays in other project activities.

References: The CCBA® Handbook and the BABOK® Guide emphasize the importance of requirements review and validation to ensure that they align with business needs and stakeholder expectations12. It is crucial for the BA to facilitate a thorough review process before proceeding with development

According to the BABOK® Guide, the plan business analysis activities process is the process of defining the tasks, dependencies, effort, and schedule for the business analysis work. The four inputs to this process are:

• Business analysis approach: This input provides information about the selected method and level of detail for performing the business analysis work, such as the plan-driven, change-driven, or hybrid approach, and the level of abstraction, formality, and rigor of the requirements and designs.
• Stakeholder list, roles, and responsibilities: This input provides information about the stakeholders who are involved in or affected by the business analysis work, their roles and responsibilities, their communication preferences, and their availability.
• Organizational process assets: This input provides information about the policies, procedures, standards, guidelines, and templates that are relevant to the business analysis work, such as the project management methodology, the business analysis methodology, the requirements management plan, and the change management plan.
• Business analysis performance assessment: This input provides information about the current state and desired state of the business analysis performance, such as the strengths, weaknesses, opportunities, and threats of the business analysis work, the performance indicators and measures, and the improvement actions and recommendations.

Stakeholder tolerance for risk is not an input to the plan business analysis activities process, but rather an input to the identify risks process, which is a sub-process of the plan business analysis approach process. Stakeholder tolerance for risk provides information about the degree of uncertainty and potential impact that the stakeholders are willing to accept for the business analysis work and the solution. References: BABOK® Guide, page 25; Business Analysis Expert Certification, CCBA® | IIBA®, section “What Should I know to be CCBA Certified?”

 The scenario describes a task that involves preparing a business analysis information package to discuss the changes in the online customer experience. The information package is a part of the solution evaluation knowledge area, which is one of the six knowledge areas covered by the CCBA® certification. According to the CCBA® Handbook and the IIBA® website, a visual prototype is one of the tools that can assist the BA in this discussion, as it provides a realistic representation of the solution and its features, functions, and interfaces12. A visual prototype can also help to elicit feedback, validate requirements, and assess the value and usability of the solution12.

References: The answer and explanation are consistent with the CCBA® Handbook and the IIBA® website, which provide the details and best practices for the solution evaluation knowledge area, including the task of communicate business analysis information12. The CCBA® resources also describe the tools and techniques that can be used to perform each task in the business analysis process12.

 This is because classifying requirements helps to ensure that they are fully understood and traceable by grouping them into categories based on their type, source, priority, or other criteria. Classifying requirements also helps to avoid duplication, ambiguity, and inconsistency among the requirements. Extracting requirements for review (A) is not a valid option, as it implies that the requirements are already documented and ready for approval. Validating requirements © is a good practice, but it does not ensure traceability, which is the ability to link the requirements to the business needs, solution components, and test cases. Meeting regulatory standards (D) is a quality criterion, but it does not ensure that the requirements are fully understood and traceable. References: CCBA Practice Test, CCBA Mock Test

The business analyst (BA) should observe customer interaction with the system before distributing the survey to assess its usability. According to the BABOK Guide, observation is “a technique used to elicit information by viewing and understanding activities and their context” 4. By observing the customer interaction with the system, the BA can gain insights into the actual usage, behavior, problems, and preferences of the customers, which can help the BA design a more effective and relevant survey. Validating the survey with the project sponsor, reviewing the risk register with the project sponsor, and updating the project plan to include the survey are important steps, but they should be done after observing the customer interaction with the system. References: 4: BABOK Guide, Version 3, Section 10.24 Observation

The BA team is evaluating the technology and infrastructure of the new COTS application and how it will interact with the existing legacy systems. Technology and infrastructure are the hardware, software, networks, and platforms that support the solution and enable its functionality. Evaluating the technology and infrastructure is an important aspect of assessing the feasibility, compatibility, and performance of the solution, as well as identifying any integration challenges, risks, or gaps. The BA team should consider the technical requirements, constraints, and dependencies of the solution, as well as the current and future state of the technology and infrastructure of the organization.

References: The answer is verified and explained using the principles found in the CCBA® certification learning documents, specifically the Business Analysis Body of Knowledge (BABOK®) guide, which outlines the knowledge areas and skills required for effective business analysis and the handling of such situations123.

A classification schema is a technique that helps to organize and categorize requirements based on common characteristics or attributes. A classification schema can facilitate effectively understanding the different types of requirements by providing a clear and consistent way to communicate, prioritize, analyze, and manage them. A classification schema can also help to identify gaps, overlaps, and dependencies among requirements. References: BABOK® Guide, Version 3, Chapter 10: Techniques, Section 10.6: Classification Schema, Page 387; Chapter 6: Requirements Life Cycle Management, Section 6.2: Prioritize Requirements, Page 146.

The scenario describes a task that involves reviewing and determining the inclusion of requirements for each release of the solution. The task requires the BA to consider the different needs and preferences of the business areas that will use the new system, as well as the effort, cost, business impact and risk of each requirement. This is an example of prioritization, which is a technique used by business analysts to rank and select the most important or valuable requirements for the solution. Prioritization helps to ensure that the solution meets the business objectives and delivers the expected benefits.

References: The answer and explanation are consistent with the CCBA® Handbook and the IIBA® website, which provide the details and best practices for the prioritization technique as part of the business analysis process12. The CCBA® resources also describe the factors and criteria that can be used to prioritize requirements, such as effort, cost, business impact, and risk12.

 In the context of project risks, particularly for the implementation of a new web portal, the potential inadequacy of the current infrastructure to support increased performance is a significant concern. This is because if the infrastructure is not capable of handling the enhanced demands of the new system, it could lead to performance issues, system downtime, or even failure, which would negatively impact the project’s success.

References: The CCBA® certification emphasizes the importance of identifying and evaluating opportunities for better business outcomes, which includes assessing risks that could hinder these outcomes123. The IIBA’s BABOK® Guide is a key resource for understanding the tasks and techniques associated with business analysis, including risk assessment4.

 The first thing that the BA should do is perform a root cause analysis. Root cause analysis is a technique for identifying and analyzing the underlying causes of a problem or an issue2. By performing a root cause analysis, the BA can find out why the solution that was implemented several years ago is causing problems and inefficiencies for the end users, and what factors are contributing to them. This will help the BA to define the problem statement, determine the scope of the analysis, and identify potential solutions. References: 2: BABOK Guide v3, Section 10.25

 The BA must create merged viewpoints of the requirements to address the concerns of the CEO. This is because a merged viewpoint is a way of combining the perspectives of different stakeholders into a coherent and consistent set of requirements. A merged viewpoint can help to resolve conflicts, identify gaps, and ensure alignment among the stakeholders. Creating merged viewpoints can also help to integrate and service the two client bases in the newly formed company after a merger. The other options are not sufficient or relevant to address the CEO’s concerns. References:

• BABOK Guide, section 4.3.2: Validate Requirements
• CCBA Practice Test, question 100

 The BA should resolve the conflict between two stakeholders over which model to use for describing requirements by explaining that the models are complementary to each other. A model is a representation of a concept or system that is used to communicate or analyze it. Different models can be used for different purposes or audiences depending on their strengths and limitations. For example, an activity diagram can show the sequence and conditions of actions performed by actors or objects in a system, while a state diagram can show how an object changes its state in response to events. The BA should demonstrate how both models can be useful and relevant for describing different aspects of the requirements. References: : BABOK Guide v3, Section 4.5 : Activity Diagram vs State Diagram

 The correct answer is D. The BA will be ensuring that the performance measures align with other measures within the broader context of the solution. This means that the performance measures are consistent with the business goals, objectives, and strategies of the organization and the stakeholders. The performance measures should also be aligned with the expected benefits and outcomes of the solution. This will help to evaluate the effectiveness and efficiency of the solution and its impact on the business value.

The other options are incorrect because:

• Option A is incorrect because performance measures can be both qualitative and quantitative, depending on the nature and scope of the solution and the stakeholder needs. Qualitative measures are based on subjective judgments, opinions, or perceptions, while quantitative measures are based on numerical data, statistics, or calculations.
• Option B is incorrect because aligning performance measures to industry benchmarks is not a validation technique, but a comparison technique. Industry benchmarks are standards or best practices that can be used to compare or evaluate the performance of a solution against similar solutions in the same domain or sector. However, industry benchmarks may not reflect the specific needs and expectations of the stakeholders or the organization.
• Option C is incorrect because writing performance measures in the correct format, using the agreed standards and terminology, is not a validation technique, but a documentation technique. The format and language of performance measures should be clear, concise, and consistent, but they do not guarantee that the performance measures are relevant, feasible, or reliable.

References:

• BABOK Guide v3, section 7.6: Validate Requirements
• CCBA Practice Test, question 9

The BA should model the elicited requirements in a review meeting to resolve the variation in results among stakeholders after completing multiple workshops involving them. Modeling the elicited requirements means creating graphical or textual representations of the requirements to communicate their meaning, structure, relationships, or behavior. Modeling the elicited requirements in a review meeting can help to resolve any inconsistencies, conflicts, gaps, or ambiguities among stakeholder perspectives.

The other options are incorrect because:

• Option A is incorrect because letting the project manager decide which requirement is relevant is not a way to resolve the variation in results among stakeholders after completing multiple workshops involving them. This is an authoritative technique that is based on the power or influence of a single person or group over others. Authoritative techniques can expedite or simplify the decision-making process, but they may not reflect the consensus or agreement of all stakeholders.
• Option B is incorrect because letting the BA select which requirements are correct is not a way to resolve the variation in results among stakeholders after completing multiple workshops involving them. This is an authoritative technique that is based on the power or influence of a single person or group over others. Authoritative techniques can expedite or simplify the decision-making process, but they may not reflect the consensus or agreement of all stakeholders.
• Option C is incorrect because letting the project manager model requirements in a review meeting is not a way to resolve the variation in results among stakeholders after completing multiple workshops involving them. This is an authoritative technique that is based on the power or influence of a single person or group over others. Authoritative techniques can expedite or simplify the decision-making process, but they may not reflect the consensus or agreement of all stakeholders.

References:

• BABOK Guide v3, section 10.30: Data Modeling
• CCBA Exam Questions, question 23

 The project manager must be consulted regarding the changes to the business analysis approach before they are implemented in this project. The project manager is responsible for planning, executing, monitoring, controlling, and closing the project activities within the constraints of scope, time, cost, quality, resources, and risk. The project manager also coordinates with other roles such as business analysts, developers, testers, sponsors, and end users. Therefore, any changes to the business analysis approach must be discussed with the project manager to ensure alignment with the project objectives and plan. References: : Project Manager Role : Project Manager Responsibilities

According to the BABOK® Guide, a business analyst (BA) should collaborate with stakeholders throughout the business analysis process to ensure their needs and expectations are understood and met. Collaboration involves establishing and maintaining relationships, communicating effectively, resolving conflicts, and facilitating decision making. In this scenario, the BA should have engaged in consistent collaboration with the project SMEs to keep them involved and interested in the project, and to address any issues or concerns they may have. This way, the BA could have ensured the SMEs’ participation and contribution to the project, and avoided the delay to the project build phase. References:

• [BABOK® Guide], section 3.1: Collaboration
• CCBA Exam Questions & Answers with Explanations, question 417

The user story “As a customer service representative, I need to enter my time on the mobile application so that I can leave work to pick up my sick daughter from school” is not aligned with the existing scope of the project, which is to support external customers and broaden the organization’s brand and increase customer engagement. This user story is focused on the internal staff and their convenience, rather than the external customers and their needs. Therefore, the BA must suggest that the story be included with a change to solution scope or be removed, as it may not add value to the project or the stakeholders. The BA should evaluate the alignment of the user stories with the existing scope by using the scope statement, the business case, and the business objectives as the reference points1. The other options are not the best techniques that the BA should use to evaluate the alignment of the user stories with the existing scope, as they may not address the issue of scope creep or misalignment. Adding the functionality to the list of requirements may increase the complexity, cost, and risk of the project, without delivering the expected benefits. Asking the product owner to rank the user story against the existing product backlog may not resolve the conflict or inconsistency between the user story and the scope statement. Reviewing the business objectives and determining the potential value may not be sufficient to justify the inclusion of the user story, as it may still contradict the scope statement or the business case. References:

• 1: Scope Statement: Definition, Benefits and Examples
• : Business Case: Definition, Benefits and Examples
• : Business Objectives: Definition, Benefits and Examples

According to the BABOK® Guide, a waterfall approach is a sequential project life cycle that consists of distinct phases, such as initiation, planning, analysis, design, construction, testing, implementation, and maintenance. Each phase has a defined set of activities, deliverables, and exit criteria that must be completed before moving to the next phase. A waterfall approach is suitable for projects that have a clear and stable scope, well-defined requirements, and minimal changes or uncertainty. In this scenario, a new contract requires a thorough level of documentation to be developed and maintained with planned phases of reviews and authorized sign offs. This implies that the project has a high degree of formality, control, and documentation, which fits the characteristics of a waterfall approach. References:

• [BABOK® Guide], section 2.5: Plan Business Analysis Approach
• CCBA Exam Questions & Answers with Explanations, question 418

The BA should review the use case scenarios after eliciting requirements from end users for a new application, and then completing a set of use cases and use case scenarios. Reviewing the use case scenarios means verifying and validating that they are accurate, complete, clear, consistent, and aligned with the stakeholder needs and expectations. Reviewing the use case scenarios can help to ensure the quality and correctness of the requirements.

The other options are incorrect because:

• Option A is incorrect because identifying all the roles and responsibilities is not an action that the BA takes after eliciting requirements from end users for a new application, and then completing a set of use cases and use case scenarios. Identifying all the roles and responsibilities means defining and documenting the functions or duties that stakeholders perform within an organization or a project. Identifying all the roles and responsibilities can help to engage and collaborate with the relevant stakeholders.
• Option C is incorrect because conducting a requirements workshop is not an action that the BA takes after eliciting requirements from end users for a new application, and then completing a set of use cases and use case scenarios. Conducting a requirements workshop means facilitating a structured session with stakeholders to elicit, analyze, communicate, or validate requirements. Conducting a requirements workshop can help to gather information from multiple stakeholders in an interactive way.
• Option D is incorrect because creating acceptance criteria is not an action that the BA takes after eliciting requirements from end users for a new application, and then completing a set of use cases and use case scenarios. Creating acceptance criteria means defining and documenting the conditions or standards that must be met by a solution to be accepted by stakeholders. Creating acceptance criteria can help to evaluate the performance and value of the solution.

References:

• BABOK Guide v3, section 10.46: Use Cases
• CCBA Exam Questions, question 22

According to the BABOK® Guide, a requirements repository is a tool that stores and manages the requirements and designs of a project or an organization. A requirements repository can facilitate the re-use of requirements by providing a centralized and accessible location for storing, retrieving, and updating the requirements. A requirements repository can also help to maintain the traceability, quality, and consistency of the requirements. Therefore, option B is the correct answer. The other options are not suitable places for keeping the defined requirements for re-use, as they are either documents or scopes that may not be easily accessible, searchable, or modifiable. References: BABOK® Guide, page 40; Business Analysis Expert Certification, CCBA® | IIBA®, section “What Should I know to be CCBA Certified?”

 MoSCoW is a prioritization technique used in business analysis and project management to categorize requirements into four levels of priority: Must have, Should have, Could have, and Won’t have. This method helps teams focus on the most critical requirements that need to be satisfied for a project to be successful, while also identifying which requirements can be deferred or excluded if necessary.

• Must have: These are non-negotiable requirements that are essential for the project’s success. If these are not met, the project is considered a failure.
• Should have: These are important but not critical requirements. They are high-priority items that can be scheduled for a future release without impacting the current one.
• Could have: These are desirable requirements that do not affect the overall success of the project. They can be included if time and resources permit.
• Won’t have: These are the lowest priority requirements or those that are not necessary for the current delivery cycle. They are recognized but not planned for the current project timeline.

References: The MoSCoW method is detailed in the Dynamic System Development Method (DSDM) handbook and is widely used across various industries for effective project management

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 scenario describes a task that involves interviewing an industry thought leader who predicted that many of the regulations currently imposed by the government will change very soon. The task requires the BA to document the inputs from the thought leader and consider how they will impact the strategic initiatives of the insurance company. This is an example of identifying assumptions, which is an element of requirement validation. Assumptions are statements that are believed to be true or certain without proof or evidence. Identifying assumptions helps to clarify the uncertainties and risks that may affect the requirements and the solution.

References: The answer and explanation are consistent with the CCBA® Handbook and the IIBA® website, which provide the details and best practices for the requirement validation technique as part of the business analysis process12. The CCBA® resources also describe the elements and criteria of requirement validation, such as identifying assumptions12.

The scenario describes a task that involves recommending a phased rollout of a new application. The phased rollout is a technique used by business analysts to deliver the solution incrementally, in stages or iterations, rather than all at once. The BA expects to achieve several benefits by this approach, such as:

• Reducing the risk and complexity of the project by breaking it down into smaller and manageable chunks
• Increasing the quality and usability of the solution by incorporating feedback and testing at each stage
• Enhancing the value and satisfaction of the stakeholders by delivering the most important or urgent features first
• Improving the alignment and adaptation of the solution to the changing business needs and environment

References: The answer and explanation are consistent with the CCBA® Handbook and the IIBA® website, which provide the details and best practices for the phased rollout technique as part of the business analysis process12. The CCBA® resources also describe the benefits and challenges of using different delivery approaches, such as phased rollout12.

 Impact Analysis is a technique used by business analysts to assess the potential consequences of a change, such as the introduction of a new regulation, on a project. It helps in understanding how the change will affect different aspects of the project, including project scope, timelines, costs, and resources. The BA will evaluate the change by analyzing its impact on existing requirements, business processes, and systems to ensure the project remains competitive and industry compliant.

References: The information is verified as per the Capability in Business Analysis™ (CCBA®) Learning documents and resources available on the IIBA website and the IIBA Bookstore.

 Identifying assumptions is crucial in managing risks because assumptions are statements about the current or future state that are believed to be true without proof. In the context of a product launch, assumptions about the benefits of the new product may include expected market demand, customer satisfaction, or revenue generation. These assumptions, if incorrect, can pose risks to the project’s success. By identifying and examining these assumptions, the BA can assess their validity and prepare mitigation strategies for potential risks that may arise if the assumptions prove to be false.

References: The information is aligned with the principles outlined in the Certification of Capability in Business Analysis™ (CCBA®) resources, which emphasize the importance of risk management in business analysis activities

 According to the BABOK® Guide, elicitation is the process of drawing out, exploring, and identifying information relevant to the change. Elicitation helps the business analyst (BA) to obtain the information needed to understand the current state, define the future state, and determine the requirements for the change. If the BA needs to identify additional information after verifying the accuracy and consistency of the information obtained from the stakeholders, the BA should conduct elicitation activities to gather more information from the appropriate sources. Some of the elicitation techniques are brainstorming, document analysis, interviews, observation, prototyping, and workshops. References: BABOK® Guide, Version 3, Chapter 4: Elicitation and Collaboration, Section 4.2: Conduct Elicitation, Page 82; Chapter 10: Techniques, Section 10.9: Elicitation Techniques, Page 394.

 According to the BABOK® Guide, one of the tasks of the business analyst (BA) during requirements elicitation and collaboration is to prepare for elicitation. This involves defining the purpose, scope, and approach for elicitation activities, as well as identifying and engaging the relevant stakeholders. One of the aspects that the BA should consider when preparing for elicitation is the logistics, which are the practical arrangements and resources required to conduct elicitation activities. For interviewing, a common elicitation technique, the logistics include the participants and their roles, the location and time of the interviews, the interview questions and agenda, and the recording and documentation methods. References: BABOK® Guide, Version 3, Chapter 4, Section 4.1; Business Analysis Expert Certification, CCBA® | IIBA®, Section “What Should I know to be CCBA Certified?”

Tracing the requirements for the interaction between a customer and the new online ordering system will enable the business analyst (BA) to illustrate the relationships between relevant requirements. According to the BABOK Guide, requirement traceability is “the ability to track the origin and evolution of a requirement and its relationship to other requirements” 3. By tracing the requirements, the BA can show how the requirements are aligned with the business objectives, how they support each other, and how they affect the scope, quality, and risk of the solution. Showing all of the decision points in the business process, capturing all users that will be impacted by the project, and detailing the inner workings of the system being changed are possible outcomes of tracing the requirements, but they are not the primary purpose of the technique. References: 3: BABOK Guide, Version 3, Section 7.6 Trace Requirements

According to the BABOK® Guide, one of the tasks of the business analyst (BA) during solution evaluation is to measure solution performance. This involves collecting and analyzing data to assess how well the solution meets the business needs and delivers value to stakeholders. One of the factors that the BA should consider to avoid skewed results and an inaccurate conclusion is the timing of the measurement, which is the point in time or the duration when the data is collected. The timing of the measurement should be consistent and appropriate for the type and purpose of the data, as well as the expected outcomes and benefits of the solution. For example, the BA should avoid measuring the solution performance during peak or off-peak hours, or before or after a major change, as these may affect the validity and reliability of the data. References: BABOK® Guide, Version 3, Chapter 8, Section 8.2; Business Analysis Expert Certification, CCBA® | IIBA®, Section “What Should I know to be CCBA Certified?”

According to the Capability in Business Analysis™ (CCBA®) guidelines, one of the techniques that a business analyst can use to develop a plan for the business analysis activities is to review the lessons learned from previous initiatives. This technique helps the business analyst to identify the best practices, challenges, risks, and opportunities that were encountered in similar projects, and to apply them to the current initiative. By learning from the past experiences, the business analyst can improve the quality and efficiency of the business analysis plan and avoid potential pitfalls.

References: The CCBA® learning documents, which can be found on the IIBA website12, describe the various techniques that a business analyst can use to plan the business analysis approach, scope, activities, and deliverables. Additionally, the IIBA Bookstore offers resources that provide further insights into the objectives and best practices for business analysis, including the use of lessons learned technique

The communication method was inappropriate because the BA sent a 600-page document without any summary or explanation to all stakeholders, which is likely to overwhelm and confuse them. The BA should have chosen a more suitable format and level of detail to communicate the status of the requirements management process, such as a dashboard or a report. The business rules, the distribution, and the models were not the main issues in this situation. References: BABOK Guide v3, page 50; CCBA Mock Test, question 17

The BA and the stakeholders should review the priorities when they receive detailed estimates of time required to develop each report based on business requirements. This means that they should reassess and adjust the relative importance or urgency of each report based on its value, feasibility, risk, and dependency. They should also consider factors such as stakeholder expectations, resource availability, schedule constraints, and quality standards.

The other options are incorrect because:

• Option A is incorrect because revising business requirements is not an action that the BA and stakeholders take when they receive detailed estimates of time required to develop each report based on business requirements. Business requirements are high-level statements of goals, objectives, needs, or problems of stakeholders or an organization. Business requirements are not revised based on estimates, but based on changes in stakeholder needs or expectations.
• Option B is incorrect because writing functional report specifications is not an action that the BA and stakeholders take when they receive detailed estimates of time required to develop each report based on business requirements. Functional report specifications are detailed descriptions of how each report should look and behave in terms of layout, content, format, functionality, etc. Functional report specifications are written based on business requirements, not based on estimates.
• Option D is incorrect because analyzing technical constraints is not an action that the BA and stakeholders take when they receive detailed estimates of time required to develop each report based on business requirements. Technical constraints are limitations or restrictions imposed by the technology, system, or solution that affect its design, development, or implementation. Technical constraints are analyzed based on solution requirements, not based on estimates.

References:

• BABOK Guide v3, section 10.43: Prioritization
• CCBA Exam Questions, question 12

 A predictive development process is a type of approach that follows a predefined and detailed plan for delivering the solution, with minimal changes and uncertainties1. A predictive development process is suitable for the initiative that has a short deadline and a regulatory mandate, as it can help the BA and the stakeholders to ensure that the solution meets the compliance requirements and the schedule constraints. A predictive development process can also help to manage the risks and expectations of the stakeholders, as it provides clear and consistent scope, requirements, and deliverables2. The other options are not the best approaches for the initiative, as they may not be able to handle the complexity and urgency of the project. A crystal clear development process is a type of agile approach that focuses on collaboration, communication, and feedback, with frequent iterations and adjustments3. A Kanban development process is a type of lean approach that visualizes the workflow, limits the work in progress, and optimizes the flow of value. An adaptive development process is a type of approach that responds to changes and uncertainties, with flexible and iterative planning and delivery. References:

• 1: Predictive Development Process: Definition, Characteristics and Examples
• 2: Why Use a Predictive Development Process?
• 3: Crystal Clear Development Process: Definition, Principles and Practices
• : [Kanban Development Process: Definition, Principles and Practices]
• : [Adaptive Development Process: Definition, Characteristics and Examples]

The BA should investigate the business process to uncover inefficiencies and failing control points first. This is because the problem statement given by the finance manager indicates that there are issues with the current process that need to be resolved before replacing the system. The BA should analyze the current state of the process, identify the root causes of the problems, and recommend improvements that can address them. The other options are not relevant at this stage of the project. References:

• BABOK Guide, section 5.1: Plan Business Analysis Approach
• CCBA Practice Test, question 98

Requirement attributes are additional pieces of information that provide more details about each requirement1. They can include information such as priority, source, status, owner, risk, complexity, etc1. When the product roadmap is modified due to changing market conditions, the BA should modify the requirement attribute values to reflect the new situation and communicate the impact to the stakeholders2. For example, the priority of some requirements may change, the status of some requirements may be deferred or cancelled, the risk of some requirements may increase or decrease, etc2. Modifying the requirement attribute values helps the BA to manage the requirements effectively and ensure alignment with the business objectives and stakeholder needs3.

Requirement description is the statement that captures what the requirement is about and what it intends to achieve1. It should be clear, concise, consistent, and testable1. Requirement description does not need to be modified unless the requirement itself changes or is clarified4.

Requirement performance measures are the criteria that are used to evaluate the degree to which the requirement meets the stakeholder expectations and the business value1. They can include metrics such as quality, timeliness, cost, customer satisfaction, etc1. Requirement performance measures do not need to be modified unless the stakeholder expectations or the business value change5.

Scope model is a graphical representation of the boundaries and relationships of the solution and its components1. It can include diagrams such as context diagram, scope diagram, feature model, use case diagram, etc1. Scope model does not need to be modified unless the scope of the solution changes or is refined6. References: 1(https://www.iiba.org/business-analysis-certifications/ccba/),  2(https://www.iiba.org/business-analysis-certifications/ccba/ccba/),  3(https://www.techno-pm.com/blogs/project-management-concepts/ccba),  4(https://www.simplilearn.com/project-management/ccba-certification-training),  5(https://www.oreilly.com/library/view/ccba-and-cbap/9781838825263/),  6(https://www.apm.org.uk/blog/how-to-engage-stakeholders-who-keep-changing-project-requirements/)

 The predictive approach provides the appropriate level of formality for this project. The predictive approach is a method of planning and managing projects that follows a predefined and sequential process. The predictive approach aims to define the scope, requirements, and deliverables of the project upfront and minimize changes during the implementation. The predictive approach is suitable for projects that have a clear and stable vision, well-understood requirements, and low uncertainty or risk.

The other options are incorrect because:

• Option B is incorrect because the reactive approach does not provide the appropriate level of formality for this project. The reactive approach is a method of planning and managing projects that responds to changes and issues as they arise. The reactive approach does not follow a predefined or sequential process, but adapts to the changing needs and expectations of the stakeholders. The reactive approach is suitable for projects that have a vague or evolving vision, unclear or changing requirements, and high uncertainty or risk.
• Option C is incorrect because the proactive approach does not provide the appropriate level of formality for this project. The proactive approach is a method of planning and managing projects that anticipates and prevents potential problems or opportunities before they occur. The proactive approach involves identifying, analyzing, and mitigating risks, as well as enhancing benefits and value. The proactive approach is suitable for projects that have a complex or dynamic environment, multiple or conflicting stakeholder interests, and significant impacts or dependencies.
• Option D is incorrect because the adaptive approach does not provide the appropriate level of formality for this project. The adaptive approach is a method of planning and managing projects that delivers the solution in increments or iterations. The adaptive approach involves frequent feedback, collaboration, and testing to ensure that the solution meets the stakeholder needs and expectations. The adaptive approach is suitable for projects that have an emergent or innovative vision, flexible or variable requirements, and moderate uncertainty or risk.

References:

• BABOK Guide v3, section 3.2: Plan Business Analysis Approach
• CCBA Exam Questions, question 21

The project team should consult with the business owner to discuss possible trade-offs when prioritizing requirements. Trade-offs are compromises or concessions that are made to balance conflicting or competing factors or criteria. Trade-offs can help to resolve disagreements or disputes among stakeholders regarding the relative importance or urgency of requirements. Requirements are conditions or capabilities that a stakeholder needs or wants from a solution.

The other options are incorrect because:

• Option A is incorrect because changing the priority of the requirements by performing a ranking is not a collaborative technique, but an analytical technique. Ranking is a method of assigning scores or values to requirements based on predefined criteria or scales. Ranking can help to compare and order requirements according to their significance or relevance for a solution, but it does not involve stakeholder input or feedback.
• Option C is incorrect because implementing the requirements that the project team considers important is not a collaborative technique, but an authoritative technique. Authoritative techniques are based on the power or influence of a single person or group over others. Authoritative techniques can help to expedite or simplify the decision-making process, but they may not reflect the consensus or agreement of all stakeholders.
• Option D is incorrect because executing the requirements that the business owner identified is not a collaborative technique, but an authoritative technique. Authoritative techniques are based on the power or influence of a single person or group over others. Authoritative techniques can help to expedite or simplify the decision-making process, but they may not reflect the consensus or agreement of all stakeholders.

References:

• BABOK Guide v3, section 10.43: Prioritization
• CCBA Exam Questions, question 6

Providing information to staff so they can answer customer inquiries directly themselves is an opportunity for improvement that the BA could recommend. This would improve the efficiency and effectiveness of the business operations, as well as the customer satisfaction and loyalty. By empowering the staff with the relevant information, the BA can reduce the dependency on other departments or systems, streamline the communication process, and enhance the quality of service.

References: The answer is based on the BABOK® Guide, which is a key resource for the CCBA® certification. Specifically, it relates to the Solution Evaluation knowledge area, where identifying opportunities for improvement is a key task for the BA12. It also relates to the Strategy Analysis knowledge area, where the BA should assess the current state of the business and define the desired future state13.

Item tracking methods are techniques to monitor and control the status of items such as issues, defects, changes, or action items. They help to manage and resolve the outstanding issues that have been logged in an issues register. Requirements documentation, requirements analysis, and metrics and KPIs are not techniques for managing and resolving issues. References: BABOK Guide v3, page 387; CCBA Mock Test, question 13

Standard templates and syntax help to ensure that the correct information about the requirements is provided to the participants of a requirements elicitation workshop. Standard templates and syntax are used to document and communicate requirements in a consistent and clear manner, avoiding ambiguity and confusion. They also help to organize and structure the requirements according to their type, priority, and relationship1. Standard templates and syntax are also a technique for specifying and modelling requirements2. References: 1: BABOK Guide v3, Section 4.3 2: BABOK Guide v3, Section 4.5.6

The top priority for the BA in assessing the solution approach is the trade-off and value to stakeholders. This means that the BA should evaluate how each solution approach balances the costs, benefits, risks, and impacts for the stakeholders. The BA should also determine how each solution approach delivers value to the stakeholders in terms of meeting their needs, expectations, and preferences.

The other options are incorrect because:

• Option B is incorrect because the strategy alignment with the balanced scorecard is not the top priority for the BA in assessing the solution approach, but a factor that the BA should consider in assessing the solution approach. The strategy alignment with the balanced scorecard means how each solution approach supports or contributes to the strategic goals or objectives of an organization. The balanced scorecard is a framework that measures and monitors the performance of an organization based on four perspectives: financial, customer, internal process, and learning and growth.
• Option C is incorrect because the total cost of ownership of the project is not the top priority for the BA in assessing the solution approach, but a factor that the BA should consider in assessing the solution approach. The total cost of ownership of the project means the sum of all direct and indirect costs associated with acquiring, developing, implementing, operating, and maintaining a project or a solution.
• Option D is incorrect because the strategy design options are not the top priority for the BA in assessing the solution approach, but a factor that the BA should consider in assessing the solution approach. The strategy design options are alternative ways of designing or developing a solution to address a problem or an opportunity.

References:

• BABOK Guide v3, section 6.3: Solution Evaluation
• CCBA Exam Questions, question 26

 The BA should use a quality control checklist to address the project manager’s concern about incomplete requirements. This is because a quality control checklist is a tool that helps to verify that the requirements meet the quality criteria and standards defined for the project. A quality control checklist can help to identify and correct any errors, omissions, inconsistencies, or ambiguities in the requirements. Using a quality control checklist can also help to avoid schedule delays caused by incomplete requirements. The other options are not directly related to checking the completeness of the requirements. References:

• BABOK Guide, section 4.2.3: Verify Requirements
• CCBA Practice Test, question 102

Creating an agenda is a useful activity to ensure a productive and focused workshop, as it helps to define the purpose, scope, objectives, participants, roles, and expected outcomes of the workshop. It also helps to manage time and expectations, and to avoid distractions and conflicts. Documenting feedback, facilitating the workshop, and reserving a location are also important activities, but they are not done in advance of the workshop. References: BABOK Guide v3, page 54; CCBA Mock Test, question 18

 To ensure a shared understanding of requirements, the BA must determine the format to present the requirements to the SMEs attending the workshop. The format of presenting requirements refers to how the requirements are expressed and communicated to different stakeholders. The format can be textual, graphical, tabular, or a combination of these3. The BA should choose a format that is appropriate for the type, level, and complexity of the requirements, as well as the preferences and expectations of the SMEs. The format should also facilitate feedback, validation, and verification of the requirements. References: 3: BABOK Guide v3, Section 4.5

 Logistics setup is a technique that defines the physical and technical arrangements for conducting elicitation activities, such as location, time, equipment, and materials1. Logistics setup can help the BA to handle the situation where not everyone could attend the meeting because of their individual dispersed locations, by adjusting the arrangements to accommodate the remote participants, such as using online conferencing tools, sending the agenda and materials in advance, and recording the session for later review2. The other options are not the things that the BA needs to adjust to handle the situation, but rather the things that the BA may have already defined or planned before the elicitation activities. Project stakeholders are the people or groups who have an interest or influence in the project or the solution3. Elicitation scope is a technique that defines the boundaries and sources of information for the elicitation activities. Elicitation technique is a technique that defines the methods and practices for obtaining information from the stakeholders. References:

• 1: BABOK® Guide v3, p. 50
• 2: Logistics Setup: Definition, Elements and Examples
• 3: BABOK® Guide v3, p. 13
• : BABOK® Guide v3, p. 51
• : BABOK® Guide v3, p. 52

Dependencies are the relationships between requirements that indicate that one requirement is contingent on another requirement. Dependencies can affect the feasibility, value, and risk of the requirements, and therefore, they should be taken into account when prioritizing the requirements. The business analyst should identify and document the dependencies between the requirements, and analyze how they impact the project scope, schedule, and budget. The business analyst should also communicate the dependencies to the business owner and other stakeholders, and help them to prioritize the requirements based on the dependencies and the business objectives. References: BABOK Guide v3, page 156; CCBA Mock Test, question 7

Quantitative performance measure is being practiced by the software development company that evaluates solutions against the number of defects reported in the testing phase. Quantitative performance measures are those that use numerical values or statistics to assess the performance of a solution or an organization. They can help to measure aspects such as quality, efficiency, productivity, profitability, customer satisfaction, etc. The number of defects is a quantitative measure of quality that indicates how well a solution meets its specifications and expectations. References: : Quantitative Performance Measures

 The deliverable that will facilitate understanding between IT and the business stakeholders is a data dictionary. This is because a data dictionary is a document that defines and describes the data elements, attributes, properties, formats, relationships, rules, etc. of a data-centric solution. A data dictionary can help to facilitate understanding between IT and the business stakeholders by providing a common language and reference for the data requirements and specifications. The other options are not as effective or suitable as a data dictionary. References:

• BABOK Guide, section 10.9: Data Dictionary
• CCBA Practice Test, question 119

A weighted scoring model is a technique that assigns weights to different criteria and rates each vendor’s performance against them. The total score for each vendor is calculated by multiplying the weight and the rating for each criterion and summing them up. The vendor with the highest score is selected as the best option. A weighted scoring model is one of the tools and techniques of the Evaluate Potential Value and Recommend Solution task, which is part of the Strategy Analysis knowledge area. A weighted scoring model is different from a scoring model, which does not assign weights to the criteria and uses a simple sum of the ratings. A vendor profile assessment scale is a tool that defines the characteristics and requirements of a vendor and assigns a score based on how well they match them. A screening system is a process that filters out vendors that do not meet the minimum requirements or standards. References: Business Analysis Expert Certification, CCBA® | IIBA®, CERTIFICATION OF CAPABILITY IN BUSINESS ANALYSIS

A tester is the stakeholder who is responsible for verifying released and solution components. A tester is a person who performs testing activities to ensure that the solution meets the quality standards and the requirements. A tester is involved in the allocated requirements to design, execute, and report test cases, as well as to identify and document defects and issues. A tester is different from the project team, which is the group of people who work together to deliver the project objectives; the project manager, who is the person who leads the project team and manages the project scope, schedule, budget, and risks; and the operational support, which is the function that provides the maintenance and support for the solution after it is deployed. References:

• CCBA Handbook, page 11
• [BABOK Guide], page 13
• [Business Analysis for Practitioners: A Practice Guide], page 17
• [Business Analysis: The Question and Answer Book], page 11

 Effective business analysis practices aim to minimize the amount of change to requirements in a stable business environment by ensuring that the requirements are well-understood, properly documented, and agreed upon by all stakeholders. While it is not possible to eliminate changes entirely due to the evolving nature of business and technology, good business analysis can significantly reduce the frequency and impact of these changes.

References: The BABOK® Guide emphasizes the importance of assessing requirements changes to maintain a stable baseline for the requirements. It also highlights the need for approval of requirements to ensure stakeholder support and buy-in123.

Requirements elicitation is not a business analysis planning and monitoring approach, but a business analysis elicitation and collaboration approach. Requirements elicitation is the process of identifying and obtaining the information needed from the stakeholders and other sources to define and validate the requirements. It involves using various techniques, such as interviews, workshops, surveys, observation, prototyping, etc., to elicit the needs, expectations, assumptions, and constraints of the stakeholders12

The business analysis planning and monitoring approach is the methodology and process that will be used to conduct business analysis activities and deliver business analysis outputs. It involves defining the scope, objectives, deliverables, roles, responsibilities, tasks, schedule, budget, quality, risk, and communication of the business analysis work. It also involves monitoring and controlling the business analysis performance and reporting the progress and issues to the stakeholders34

The other options are examples of business analysis planning and monitoring approaches:

• Structured walkthroughs: This is a technique that is used to validate and verify the business analysis approach, not to define and document it. Structured walkthroughs involve presenting and reviewing the business analysis approach with the stakeholders, and soliciting their feedback and approval. It helps to ensure the quality, completeness, and alignment of the business analysis approach with the stakeholder needs and expectations.
• Decision analysis: This is a technique that is used to evaluate and select the business analysis approach, not to define and document it. Decision analysis involves comparing the costs, benefits, risks, and impacts of the alternative business analysis approaches, and choosing the one that best meets the project objectives and stakeholder preferences. It helps to justify and rationalize the business analysis approach to the stakeholders, and to document the decision criteria and rationale.
• Process modeling: This is a technique that is used to define and document the business analysis approach. Process modeling involves creating a graphical representation of the business analysis activities, tasks, inputs, outputs, roles, and responsibilities. It helps to communicate and visualize the business analysis approach to the stakeholders, and to identify and manage the dependencies, risks, and issues. Process modeling can be done using various tools and notations, such as flowcharts, swimlane diagrams, BPMN, UML, etc.

References:

• Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed, Section 7.4: Requirements Elicitation
• Certification of Capability in Business Analysis (CCBA®) - Simplilearn, Module 6: Elicitation and Collaboration, Lesson 6.1: Prepare for Elicitation
• Business Analysis Expert Certification, CCBA® | IIBA®, section “Plan Business Analysis Work”
• CERTIFICATION OF CAPABILITY IN BUSINESS ANALYSIS, page 6, section “4. Review the Exam Blueprint”
• [Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed], Section 7.3: Structured Walkthrough
• [Certification of Capability in Business Analysis (CCBA®) - Simplilearn], Module 5: Planning and Monitoring, Lesson 5.5: Validate Requirements
• [Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed], Section 8.6: Decision Analysis
• [Certification of Capability in Business Analysis (CCBA®) - Simplilearn], Module 5: Planning and Monitoring, Lesson 5.6: Manage Business Analysis Performance
• [Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed], Section 7.2: Process Modeling
• [Certification of Capability in Business Analysis (CCBA®) - Simplilearn], Module 5: Planning and Monitoring, Lesson 5.1: Plan Business Analysis Approach

 In this scenario, the stakeholders are actually defining solutions, not business requirements. Solutions are the specific ways of satisfying one or more business needs in the context of a specific project or initiative. Solutions include the products, services, or results that are delivered to the stakeholders, as well as the changes to the organization, processes, and capabilities that are required to enable the delivery. Solutions are different from business requirements, which are the higher-level statements of the goals, objectives, or needs of the enterprise. Business requirements are not solution-specific and do not include any details of how the needs will be met. Business requirements are also different from perceived problems, which are the negative aspects of the current state that the stakeholders want to resolve; perceived needs, which are the positive aspects of the desired state that the stakeholders want to achieve; and longevity, which is the expected lifespan of the solution or the business need. References:

• CCBA Handbook, page 10
• [BABOK Guide], page 10
• [Business Analysis for Practitioners: A Practice Guide], page 14
• [Business Analysis: The Question and Answer Book], page 9

 According to the BABOK Guide, the task of prioritizing requirements assesses the value, urgency, dependencies, and risks associated with requirements and designs to ensure that analysis and delivery work is done on the most important ones at any given time1. Prioritization is an ongoing process, with priorities changing as the context changes. The task of prioritizing requirements creates just one output, which is requirements (prioritized). This output is a list or a model of requirements and designs that have been assigned a level of importance or urgency relative to other requirements and designs2. The output of requirements (prioritized) is used as an input for other tasks, such as managing solution scope and requirements, assessing proposed solutions, allocating requirements, and validating requirements3.

The other options are not correct outputs of the task of prioritizing requirements:

• Validated requirements are an output of the task of validating requirements, which ensures that the requirements and designs support the delivery of value, fulfill the stakeholder needs, and meet the quality standards3.
• Requirements rankings are not a formal output of the task of prioritizing requirements, but rather a possible technique to assign a numerical value to each requirement or design based on a set of criteria2.
• Requirements assessment is not an output of the task of prioritizing requirements, but rather a possible technique to evaluate the impact, feasibility, and value of requirements and designs2. References:
• 2: CCBA® and CBAP® Certifications Study Guide, section Task: Prioritize Requirements, page 1
• 3: BABOK Guide, section 4.5 Prioritize Requirements, page 72
• 1: Prioritize Requirements and Designs1, page 1

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”

The decomposition of activities and tasks based on the work breakdown structure creates an activity list for the business analyst. An activity list is a document that identifies the activities and tasks needed to produce the business analysis deliverables. It also includes information such as activity name, description, duration, resource requirements, and dependencies. An activity list is an input to the business analysis planning process, where the business analyst determines the sequence, schedule, and budget of the activities and tasks. References:

• Business Analysis Expert Certification, CCBA® | IIBA®, section “Plan Business Analysis Work”
• CERTIFICATION OF CAPABILITY IN BUSINESS ANALYSIS, page 6, section “4. Review the Exam Blueprint”

According to the BABOK® Guide, opportunity cost is the value of the next best alternative that is forgone as a result of making a decision. In this case, the opportunity cost of choosing the second project for $565,000 is the value of the first project that is not chosen, which is $375,000. This means that the organization is giving up the potential benefit of $375,000 by selecting the second project over the first one. References: BABOK® Guide, page 32; Business Analysis Expert Certification, CCBA® | IIBA®, section “What Should I know to be CCBA Certified?”

 According to the BABOK® Guide, the plan business analysis approach is the task of defining the most appropriate method and level of detail for performing business analysis activities, based on the characteristics of the project, the solution, and the stakeholders. This task is important because it helps the business analyst (BA) to determine the scope, complexity, and risk of the business analysis work, as well as the deliverables, tasks, techniques, and stakeholders involved. The plan business analysis approach also provides guidance and direction for the BA throughout the project lifecycle. References: BABOK® Guide, page 24; Business Analysis Expert Certification, CCBA® | IIBA®, section “What Should I know to be CCBA Certified?”

 The BA should ensure buy-in from key stakeholders before using “Product Box” as a collaboration game to prioritize the list of features. Buy-in is the agreement and support of the stakeholders for a proposed solution, approach, or decision. Buy-in is important for the success of any business analysis activity, as it helps to build trust, commitment, and collaboration among the stakeholders. Buy-in can be achieved by involving the stakeholders in the planning, elicitation, analysis, and validation of the requirements, as well as by addressing their needs, expectations, and concerns. The BA should ensure buy-in from key stakeholders for using “Product Box” as a collaboration game, as it may be a new or unfamiliar technique for some stakeholders, or they may have different preferences or opinions on how to prioritize the features. The BA should explain the benefits and purpose of the game, as well as the rules and expectations, and seek feedback and agreement from the stakeholders before conducting the game. The BA should also ensure that the game is aligned with the business objectives and the stakeholder requirements.

References:

• CCBA Handbook, page 16
• [BABOK Guide], page 30
• [Business Analysis for Practitioners: A Practice Guide], page 39
• [Business Analysis: The Question and Answer Book], page 25

A work breakdown structure (WBS) is a tool that decomposes the project scope into smaller, manageable components. A WBS is useful for identifying activities in the business analysis approach, as it helps to define the tasks, dependencies, and resources required for each deliverable. A WBS also helps to estimate the effort, duration, and cost of the business analysis work, as well as to monitor and control the progress and quality of the deliverables. A WBS is different from project management input, which is an input to the business analysis approach, not a tool for identifying activities; BABOK, which is a guide that provides the best practices and standards for business analysis, not a tool for identifying activities; and a list of deliverables, which is an output of the business analysis approach, not a tool for identifying activities. References:

• CCBA Handbook, page 15
• [BABOK Guide], page 38
• [Business Analysis for Practitioners: A Practice Guide], page 42
• [Business Analysis: The Question and Answer Book], page 28

 A financial constraint is a limitation on the amount of money that can be spent on a project. It is one of the common types of constraints that affect project management, along with scope, time, quality, and risk constraints. A financial constraint can affect the feasibility, scope, and quality of a project, as well as the resources and activities involved in it. A business analyst needs to identify and document the financial constraints of a project, as well as the assumptions and dependencies related to them. A business analyst also needs to monitor and control the project budget, and communicate any changes or issues to the stakeholders.

References: The concept of financial constraint is discussed in the BABOK Guide, version 3, under the section 4.1 Plan Business Analysis Approach1. The CCBA Certification Study Guide, version 3, also covers this topic under the chapter 4 Business Analysis Planning and Monitoring2. Additionally, the Guidelines on Gender-Responsive and Socially Inclusive Climate Cost-Benefit Analysis (CCBA) provide a framework for analyzing projects with financial constraints, among other factors3.

A constraint is a restriction or limitation on the solution that is imposed by an external factor, such as a regulation, standard, or policy. Constraints must be identified and analyzed during the business analysis process, as they may affect the feasibility, desirability, or viability of the solution. Compliance officers are responsible for ensuring that the solution meets the relevant constraints and does not violate any laws or rules. References:

• Certification of Capability in Business Analysis (CCBA) Handbook, page 6
• [A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], page 30

According to the BABOK® Guide, rolling wave planning is a technique that involves creating a high-level plan for the overall business analysis approach, and then creating detailed plans for the activities that are most imminent or have the highest priority or risk. Rolling wave planning allows the business analyst to adapt to changing circumstances and stakeholder needs, and to incorporate feedback and learning from previous activities into the subsequent plans1. References: 1: BABOK® Guide, version 3, section 4.2.5, page 76.

Planning the business analysis approach involves defining the level of formality, the activities, the timing, and the deliverables of the business analysis work1. It also involves identifying the stakeholders who will be involved in the decision making, consulted, and informed about the approach, as well as the rationale for using it2. Job shadowing is a technique for eliciting requirements, not a factor for planning the business analysis approach3. References:

• 1: BABOK® Guide, Version 3.0, p. 34
• 2: CCBA® Handbook, p. 18
• 3: BABOK® Guide, Version 3.0, p. 123

Visual learners are those who learn best through the presentation of models, diagrams, charts, graphs, and other visual aids. They prefer to see the information rather than hear it or do it. Visual learners can benefit from the use of models in business analysis, as they can help them to understand the problem, the solution, and the requirements in a clear and concise way.

References: The information is verified as per the CCBA Learning documents and resources, which outline the standards and practices for business analysis. You can find more information about the types of learners and the use of models in business analysis in the CCBA guide1 and the BABOK Guide2 available through the IIBA website and bookstore3. You can also find some useful resources and sample questions from other sources45.

 A requirements signoff process is a process of obtaining formal approval from the stakeholders that the requirements are clear, complete, consistent, and aligned with the business needs and objectives. A requirements signoff process is important because it helps to ensure that the stakeholders are satisfied with the requirements and that they agree to move forward with the solution development based on the requirements. A requirements signoff process also helps to avoid scope creep, rework, and conflicts that may arise from unclear or changing requirements12.

The other options are not correct because:

• Option B is incorrect. A requirements signoff process does not confirm that the project sponsor and the project manager are in agreement with the business analyst about the accuracy and completeness of the requirements. A requirements signoff process involves all the stakeholders who have an interest or influence in the project or its outcome, not just the project sponsor and the project manager. The business analyst’s role is to facilitate the communication and collaboration among the stakeholders, not to impose their own views on the requirements3.
• Option C is incorrect. A requirements signoff process does not hold stakeholders accountable for the cost and schedule of the requirements. A requirements signoff process is focused on the quality and validity of the requirements, not on the budget and timeline of the project. The cost and schedule of the requirements are determined by the project manager, who is responsible for planning, executing, monitoring, and controlling the project activities and resources4.
• Option D is incorrect. A requirements signoff process does not allow the project manager to begin the project. A requirements signoff process is usually done after the project has been initiated and the business analysis activities have been conducted. The project manager can begin the project after the project charter has been authorized, which defines the project purpose, objectives, scope, deliverables, milestones, roles and responsibilities, budget, and risks5.

References:

• 3 Quick Tips for Requirements Sign-off - Business Analyst Learnings, section “3 Quick Tips for Requirements Sign-off”
• How to Get Meaningful Sign-Off on Requirements - Bridging the Gap, section “How to Get Meaningful Sign-Off on Requirements”
• Business Analysis Expert Certification, CCBA® | IIBA®, section “BABOK® Guide v3”, chapter 3, section 3.1
• What is Project Management | PMI, first paragraph
• Project Charter, section “Description of Change”

A constraint is a restriction or limitation that affects the performance or value of a solution. Constraints can be related to time, cost, quality, scope, resources, or other factors. In this scenario, the customer’s demand that the solution should not cost more than $300,000 to implement and support for one year is a constraint that limits the possible options and trade-offs for the solution.

References: The information is aligned with the competencies and knowledge areas defined in the Business Analysis Body of Knowledge® (BABOK® Guide) and the Certification of Capability in Business Analysis™ (CCBA®) as provided by the International Institute of Business Analysis (IIBA®). For detailed references, please consult the CCBA® guide1 and the BABOK® Guide2 available through the IIBA® website and bookstore3. You can also find some useful resources and sample questions from other sources4.

Enterprise architecture is an input for stakeholder analysis that describes the organizational units that exist and their interactions with one another. It provides a holistic view of the organization’s structure, processes, systems, and goals, and how they are aligned and integrated. Enterprise architecture helps to identify the stakeholders who are involved in or affected by the business analysis activities and the solution.

References: The information is verified as per the BABOK® Guide and related IIBA resources, which outline the standards and practices for business analysis. The BABOK® Guide is a key resource for understanding business analysis inputs and outputs

The business need is the input that will help you understand the type of information that should be elicited from stakeholders. The business need is the problem or opportunity that the project is intended to address, and it provides the context and scope for the elicitation process. By understanding the business need, you can focus on eliciting the requirements that are relevant, feasible, and valuable for the project.

The other options are not correct because:

• Roles and responsibilities are an input that will help you identify who should be involved in the elicitation process, but not what type of information should be elicited.
• Stakeholder list is an input that will help you determine who are the sources of requirements, but not what type of information should be elicited.
• Risk assessment is an input that will help you identify the potential uncertainties and threats that may affect the elicitation process, but not what type of information should be elicited.

Defining the business problem is the task of identifying and describing the root cause or causes of a situation that prevents the organization from achieving its desired goals1. As part of this analysis, the business analyst should consider the following elements2:

• The adverse impacts of the problem, such as reduced revenue, increased costs, customer dissatisfaction, or regulatory non-compliance.
• The benefits from a potential solution, such as increased efficiency, improved quality, enhanced customer loyalty, or competitive advantage.
• The urgency of the problem, such as how quickly the problem needs to be solved, what are the consequences of delaying the solution, and what are the dependencies or constraints that affect the timing of the solution.
• The underlying source of the problem, such as the gap between the current and desired state, the root cause or causes of the gap, the assumptions or constraints that influence the problem, and the stakeholders who are affected by or can influence the problem.

The other options are not elements that should be considered when defining the business problem, but rather factors that may be relevant for other tasks, such as evaluating solution options, conducting market research, or analyzing requirements. References:

• 1: BABOK® Guide, Version 3.0, p. 30
• 2: Business Analysis Expert Certification, CCBA® | IIBA®

Before requirements can be approved to be managed, they must be verified and validated to ensure that they are aligned with the solution scope, which is the set of capabilities and conditions that the solution must satisfy to meet the business need12. Requirements that do not support the solution scope may introduce unnecessary complexity, cost, or risk to the project, or may not deliver the expected value to the stakeholders. Therefore, it is important to check that the requirements are consistent, complete, correct, feasible, and testable before approving them to be managed3. References:

• 1: BABOK® Guide, Version 3.0, p. 33
• 2: Business Analysis Expert Certification, CCBA® | IIBA®
• 3: BABOK® Guide, Version 3.0, p. 41

According to the CCBA® Handbook, stakeholder impact analysis is “a technique used to identify the effects of a change on the stakeholders of a solution” (p. 22). Stakeholder impact analysis can help the business analyst understand the functions of stakeholders, the location of stakeholders, the tasks stakeholders complete, and the stakeholders’ concerns about the solution. Stakeholder impact analysis can also help the business analyst identify the stakeholder needs, expectations, preferences, and risks, as well as the communication and engagement strategies for each stakeholder group. The other options are not correct because:

• A. Technical assessment is “a technique used to evaluate the technical feasibility and suitability of a solution” (p. 23). Technical assessment can help the business analyst understand the technical requirements, constraints, and capabilities of the solution, but not the stakeholder aspects.
• C. Organizational assessment is “a technique used to evaluate the current state of an organization and its alignment with the desired future state” (p. 22). Organizational assessment can help the business analyst understand the organizational structure, culture, processes, and performance of the organization, but not the stakeholder aspects.
• D. Operational analysis is “a technique used to analyze the efficiency and effectiveness of the current operations of an organization” (p. 22). Operational analysis can help the business analyst understand the operational requirements, problems, and opportunities of the organization, but not the stakeholder aspects. References:
• CCBA® Handbook, p. 22-23
• Stakeholder Impact Analysis - Modern Analyst, section “What is Stakeholder Impact Analysis?”

Interviews are a technique for eliciting requirements by engaging stakeholders in a dialogue to obtain information about their needs, expectations, and preferences. Interviews can also be used to identify stakeholders by asking existing stakeholders to recommend other potential stakeholders or sources of information. Interviews can help to establish rapport and trust with stakeholders, as well as to clarify issues and resolve conflicts. References:

• BABOK® Guide, section 4.2.1, page 99
• CCBA® and CBAP® Certifications Study Guide, chapter 4, page 113

 Product scope is the features and functions that characterize a product, service, or result1. It defines what the product or service will do and how it will meet the customer needs and expectations2. Product scope is different from project scope, which is all the work needed to deliver a product, service, or result as defined in product scope1. Requirements envisioning is a technique to collaboratively identify and define the high-level features and scope of a solution3. Requirements foundation is a term used by IIBA to describe the core concepts of business analysis, such as requirements, stakeholders, and business analysis planning and monitoring4. References:

• Certification of Capability in Business Analysis (CCBA®) Handbook, page 5, section “4. Review the Exam Blueprint”
• Business Analysis Expert Certification, CCBA® | IIBA®, section “BABOK® Guide v3”
• Requirements Envisioning: An Agile Best Practice
• Business Analysis Core Concept Modelâ„¢ (BACCMâ„¢)

Parametric modeling is an estimation technique that uses historical data and mathematical formulas to calculate estimates based on the relationship between variables. In this case, the variables are the number of servers and clients, and the hours required to install them. By multiplying the number of servers by 15 hours, and the number of clients by 10 hours, you can get an estimate of the total hours needed for the project. This technique is useful when the project has a high level of similarity to past projects, and the data is reliable and scalable. References: Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed, Section 8.2: Estimation Techniques; Certification of Capability in Business Analysis (CCBA®) - Simplilearn, Module 5: Planning and Monitoring, Lesson 5.3: Estimation; Intro to the Certification of Capability in Business Analysis (CCBA®) - Pluralsight, Course Overview, 1:40-2:00.

According to the PMBOK Guide, change requests are more likely to occur in the early phases of a project, when the project scope is not well defined and the uncertainty is high. As the project progresses, the scope becomes clearer and the changes are more controlled. Therefore, option A is the best answer.

Option B is incorrect because the project scope management processes are not a specific time period in the project, but rather a set of activities that can occur throughout the project. Option C is incorrect because the project’s launch is not a phase of the project, but rather a milestone that marks the start of the project execution. Option D is incorrect because change requests tend to decrease towards the end of the project, when the project is close to completion and the scope is well established.

 Deming’s Quality Circle is a model of continuous improvement, not a documented approach to business analysis work. The other options are examples of documented approaches that describe how business analysis work is planned, conducted, and delivered. References:

• Business Analysis Expert Certification, CCBA® | IIBA®, section “3.1 Plan Business Analysis Approach”
• [Business Analysis Driving Business Success | IIBA®], section “Business Analysis Methodologies”

Risk analysis is a technique that identifies and assesses the uncertainties and potential negative impacts that may affect the project or the solution. It is not a technique for identifying the solution approach, which is the method or process for solving the identified problem and delivering the desired outcomes12. The other techniques, such as benchmarking, brainstorming, and decision analysis, are acceptable for identifying the solution approach, as they can help to generate, compare, and evaluate different alternatives and criteria for the solution3. References:

• 1: BABOK® Guide, Version 3.0, p. 33
• 2: Business Analysis Expert Certification, CCBA® | IIBA®
• 3: Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed

A structured walkthrough is a technique that involves presenting a business analysis deliverable to a group of stakeholders for review and feedback. The purpose of a structured walkthrough is to validate the quality, accuracy, and completeness of the deliverable, as well as to ensure that it meets the stakeholder needs and expectations. A structured walkthrough can be used to validate a created, selected, or tailored business analysis approach, as it allows the business analyst to explain the rationale behind the approach and to obtain the agreement and approval of the stakeholders.

References: The information is aligned with the competencies and knowledge areas defined in the Business Analysis Body of Knowledge® (BABOK® Guide) and the Certification of Capability in Business Analysis™ (CCBA®) as provided by the International Institute of Business Analysis (IIBA®). For detailed references, please consult the CCBA® guide1 and the BABOK® Guide2 available through the IIBA® website and bookstore3. You can also find some useful resources and sample questions from other sources45.

Networking topology mapping is a business analysis process that involves creating a visual representation of the physical and logical connections between the various devices and systems in an organization. It helps to understand how information flows, how systems interact, and what are the potential points of failure or vulnerability12. Data flow diagram, data dictionary and glossary creation, and prototype are other business analysis processes, but they do not focus on the networking aspects as much as networking topology mapping does3. References:

• 1: Network Topology Mapping | IIBA® BABOK Extended
• 2: Business Analysis Expert Certification, CCBA® | IIBA®
• 3: Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed

The RACI matrix is a technique that helps to define and communicate the roles and responsibilities of the stakeholders involved in a process or a project. It uses the legend of Responsible, Accountable, Consulted, and Informed to indicate the level of participation and authority of each stakeholder for each task or deliverable. The RACI matrix helps to clarify expectations, avoid conflicts, and ensure accountability and collaboration among the stakeholders.

References: The information is verified as per the BABOK® Guide and related IIBA resources, which outline the standards and practices for business analysis. The BABOK® Guide is a key resource for understanding business analysis techniques and their applications across different contexts123. You can also find some useful resources and sample questions from other sources.

• A. Absolute reference: This is an incorrect answer, as it is not a requirement attribute, but a term used in spreadsheet software to refer to a cell address that does not change when copied or moved to another cell.
• B. Ownership: This is a correct answer, as it is a requirement attribute that indicates who is responsible for the creation, approval, and maintenance of the requirement. Ownership helps to ensure the accountability, traceability, and quality of the requirement.
• C. Requirements sponsor: This is an incorrect answer, as it is not a requirement attribute, but a role that provides the funding and support for the project or the solution. The requirements sponsor may or may not be the same person as the owner of the requirement.
• D. Author of the requirement: This is a correct answer, as it is a requirement attribute that identifies the person who wrote the requirement. Authorship helps to provide the source and context of the requirement.

An assumption is a factor that is considered to be true, real, or certain without proof or demonstration. Assumptions are made to reduce uncertainty and complexity in business analysis activities. However, assumptions also introduce risks if they turn out to be false or inaccurate. Therefore, assumptions should be identified, documented, validated, and managed throughout the business analysis process. References:

• Certification of Capability in Business Analysis (CCBA) Handbook, page 7
• [A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], page 31

The Delphi technique is a type of requirements elicitation technique that uses a survey method to gather the opinions of a group of experts on a specific topic or problem. The Delphi technique is an iterative process in which the survey questions are refined and repeated until a consensus is reached among the experts. The Delphi technique is useful for eliciting requirements when the experts are geographically dispersed, have different backgrounds or perspectives, or need to remain anonymous. The Delphi technique helps to reduce the bias, influence, or conflict that may arise from direct communication among the experts. The other options are not types of requirements elicitation techniques that can achieve the same goal as the Delphi technique. A workshop is a technique that involves bringing together a group of stakeholders in a structured and facilitated session to elicit, analyze, or validate the requirements. A prototyping is a technique that involves creating a simplified or partial version of the solution to test its functionality, usability, or design. A round table is a technique that involves having a group discussion among the stakeholders to share their views, ideas, or feedback on the requirements or the solution. References:

• What is the Delphi technique used for in requirements elicitation?
• Top 10 Most Common Requirements Elicitation Techniques
• The Delphi Technique - Students 4 Best Evidence
• Delphi Method - Overview, Process, and Applications

Because the stakeholders are dispersed, what are likely to increase in this endeavor as opposed to a collocated group of stakeholders are communication needs and risks. Communication needs are the requirements and expectations of the stakeholders regarding the frequency, format, content, and quality of the information exchange during the business analysis work12. Risks are the uncertain events or conditions that may have a positive or negative effect on the business analysis work or the solution34. When the stakeholders are dispersed, the communication needs and risks tend to increase, as there may be challenges or barriers related to the time zones, languages, cultures, technologies, or processes that affect the collaboration and coordination among the stakeholders. The other options are not likely to increase in this endeavor, as they depend on other factors, such as the project scope, budget, schedule, or quality, such as face-to-face meetings (A), which may not be feasible or necessary for dispersed stakeholders, or costs (D), which may not be directly related to the stakeholder dispersion. References: Business Analysis Expert Certification, CCBA® | IIBA®, Certification of Capability in Business Analysis™ (CCBA®), Business Analysis Certification Competencies, CCBA® | IIBA®, The Ultimate Guide to Business Capability Analysis, [Certification of Capability in Business Analysis (CCBA®) - Simplilearn]

Constraint ranking is a type of requirements prioritization that considers the limitations or restrictions that affect the solution. Laws and regulations are examples of constraints that must be met by the solution. Therefore, ranking the requirements according to the relevant laws is a constraint ranking method.

References:

• Business Analysis Expert Certification, CCBA® | IIBA®, section “CCBA Competencies”
• Certification of Capability in Business Analysis (CCBA®) Handbook, page 5, section “4. Review the Exam Blueprint”

According to the BABOK® Guide, an assumption is a factor that is considered to be true for the purposes of planning and analysis, but has not been confirmed or proven. Assumptions are used to fill in the gaps of knowledge or uncertainty, and may affect the outcome of the project if they turn out to be false. An example of an assumption is the project manager’s belief that her project team members can program in COBOL, which may or may not be true, and may impact the project’s feasibility, scope, cost, and schedule1. References: 1: BABOK® Guide, version 3, section 10.25, page 336.

Benchmarking is an elicitation technique that is best described as a study to compare the strengths and weaknesses of an organization against its peers and competitors. Benchmarking involves measuring and evaluating the performance, processes, or practices of an organization or a system with those of other organizations or systems that are considered to be the best in the industry or the domain. Benchmarking helps to identify the gaps, opportunities, and best practices for improvement and innovation. Benchmarking can be done at various levels, such as strategic, operational, functional, or technical. The other options are not elicitation techniques that can achieve the same goal as benchmarking. Brainstorming is a technique for generating a large number of ideas or options for solutions in a creative and collaborative way. Market analysis is a technique for researching and analyzing the market trends, demands, and preferences of the customers or the users. Comparative analysis is a technique for comparing and contrasting the similarities and differences between two or more items, such as concepts, theories, models, etc. References:

• Top 10 Most Common Requirements Elicitation Techniques
• What elicitation technique is best described as a study to compare the strengths and weaknesses of an organization against its peers and competitors?
• Types of Elicitation Techniques for the Business Analyst

The business analysis task that Shelly is facilitating in this scenario is validate requirements. This task involves ensuring that the requirements align with the business objectives, goals, and vision of the organization, and that they support the delivery of value. Shelly and Thomas are reviewing the requirements to verify that they are consistent, feasible, and acceptable for the stakeholders. The other options are not relevant to this scenario, as they involve defining the criteria for accepting the solution (A), ensuring the quality of the requirements documentation (B), or managing the relationships and expectations of the stakeholders (D). References: CERTIFICATION OF CAPABILITY IN BUSINESS ANALYSIS, Certification of Capability in Business Analysis (CCBA®) - Simplilearn

According to the BABOK® Guide, high quality requirements should have the following characteristics: atomic, complete, consistent, concise, feasible, unambiguous, testable, prioritized, and traceable. Cohesive, consistent, and complete are among these characteristics, while constrained is not. Constrained means that the requirements are limited by some factors, such as budget, time, or resources, which may affect their quality negatively. References: BABOK® Guide, section 4.2.5, page 98; CCBA Handbook, section 4.4, page 6.

The stakeholder register is the key output of the Identify Stakeholders process. It not only contains the names of the project stakeholders but also their goals, expectations, concerns, and other such details. The stakeholder register helps to plan, manage, and communicate with the stakeholders effectively and efficiently. The other options are not outputs of the Identify Stakeholders process, but inputs or outputs of other processes. The scope baseline, the project charter, and the project scope statement are all inputs or outputs of the Project Scope Management knowledge area, not the Project Stakeholder Management knowledge area. References:

• Identify Stakeholders Process and Stakeholder Register
• Chapter 13 - Stakeholder Management Flashcards
• How to Identify Stakeholders in Project Management?

A current state model is a representation of how the organization operates or performs its functions at the present time. It can be created using various techniques, such as process modeling, data modeling, organizational modeling, or business rules analysis12. A current state model can be useful for several reasons, such as:

• Analyzing the current state of the organization to look for opportunities for improvement, such as identifying gaps, inefficiencies, redundancies, or pain points3.
• Assessing the positive and negative risks that may exist within the current state, such as threats, opportunities, strengths, or weaknesses4.
• Assisting stakeholders to understand the current state, such as clarifying the roles, responsibilities, interactions, and dependencies of different actors and components.

However, validating the solution scope with businesses and technical stakeholders is not a good reason to create a current state model, because the solution scope defines the boundaries and characteristics of the desired future state, not the current state. The solution scope should be validated by comparing it with the business need, the business case, and the stakeholder expectations, not with the current state model. References:

• 1: BABOK® Guide, Version 3.0, p. 130
• 2: Business Analysis Expert Certification, CCBA® | IIBA®
• 3: Business Capability Analysis: How to analyze capabilities - Capstera
• 4: BABOK® Guide, Version 3.0, p. 133
• : Certification of Capability in Business Analysisâ„¢ (CCBA®), page 9
• : BABOK® Guide, Version 3.0, p. 33
• : BABOK® Guide, Version 3.0, p. 36

Managing requirements traceability is a business analysis task that involves creating and maintaining relationships among business objectives, requirements, team deliverables, and solution components to support business analysis activities. It helps to ensure that the requirements are aligned with the business needs and objectives, that the solution meets the requirements, and that the changes to the requirements are tracked and communicated throughout the project lifecycle.

References: The information is verified as per the BABOK® Guide and related IIBA resources, which outline the standards and practices for business analysis. The BABOK® Guide is a key resource for understanding business analysis tasks and techniques123. You can also find some useful resources and sample questions from other sources

Requirements traceability is the ability to describe and follow the life of a requirement in both a forward and backward direction, from its origin, through its development and specification, to its subsequent deployment and use, and through periods of ongoing refinement and iteration in any of these phases1. Requirements traceability helps to ensure that the requirements are aligned with the business need, the solution scope, and the project objectives, and that they are verified and validated throughout the project lifecycle2. Requirements traceability also supports change management, impact analysis, risk management, and quality assurance3. To trace a requirement, one needs to look at the requirement and the others to which it is related, and document the relationships among them. These relationships can be horizontal (between requirements at the same level of detail) or vertical (between requirements at different levels of detail). The most common types of relationships are derivation, satisfaction, verification, and refinement4. A requirement can be traced to other artifacts created by the team, such as design documents, test cases, models, and code, as well as to solution components, such as features, functions, and interfaces5. Therefore, option D is the correct answer, as it captures the essence of requirements traceability.

References:

• Requirements traceability - Wikipedia, first paragraph
• Business Analysis Expert Certification, CCBA® | IIBA®, section “BABOK® Guide v3”, chapter 6, section 6.1.4
• A Guide to Understanding the Requirements Traceability Matrix, section “Why Is Requirements Traceability Important?”
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), version 3, chapter 6, section 6.1.4.1
• What Is Traceability? | Perforce, first paragraph

 According to the CCBA® Handbook, one of the tasks of the business analyst is to “assess proposed solution” (p. 12). This task involves evaluating the potential value and benefits of each solution option, comparing them to the costs and risks, and recommending the best option or no option at all. The inputs to this task are solution options, requirements, and risk assessments. The other options are not correct because:

• A. Solution options are an input to the assess proposed solution task, as they are the possible ways to address the business need and meet the requirements (p. 12).
• B. Requirements are an input to the assess proposed solution task, as they are the capabilities and conditions that the solution must have and meet to address the business need (p. 12).
• C. Risk assessments are an input to the assess proposed solution task, as they are the analysis of the uncertainties and potential negative impacts of each solution option (p. 12). References:
• CCBA® Handbook, p. 12
• BABOK® Guide, p. 106

• A. The communications management plan will dictate what will happen to the business analysis communications: This is a correct answer, as the communications management plan is a document that describes how the communication needs and expectations of the stakeholders will be met, including the methods, frequency, format, and distribution of the business analysis communications. The communications management plan should also specify how the communications will be stored, retrieved, and disposed of at the end of the project.
• B. All formal communication must be destroyed once the project is completed: This is an incorrect answer, as it contradicts the principle of traceability, which is the ability to link the requirements and other business analysis deliverables to their sources and to the solution components that satisfy them. Traceability helps to ensure the quality, completeness, and alignment of the business analysis work. Destroying the communication documents would make it impossible to trace the rationale, assumptions, decisions, and changes that occurred during the project.
• C. All communications must be archived and will become part of the organizational process assets: This is a correct answer, as the organizational process assets are the plans, processes, policies, procedures, and knowledge bases that are specific to and used by the performing organization. They include any artifact, practice, or knowledge that can help the organization to perform its business analysis activities more effectively and efficiently. Archiving the communication documents would enable the organization to reuse, update, or improve them for future projects or initiatives.
• D. All communications must be documented and passed onto the solution’s project manager for analysis and to serve as supporting detail: This is an incorrect answer, as it implies that the business analyst is not responsible for analyzing the communication documents or providing supporting detail for the solution. The business analyst is the primary role that performs the business analysis activities, such as eliciting, analyzing, validating, and managing the requirements and other business analysis deliverables. The project manager is the primary role that performs the project management activities, such as initiating, planning, executing, monitoring, controlling, and closing the project. The business analyst and the project manager should collaborate and communicate effectively throughout the project, but they have different roles and responsibilities.

The signoff on the requirements represents the formal acceptance and approval of the requirements by the stakeholders. It indicates that the stakeholders agree that the requirements are accurate and complete, and that they meet the business need and the solution scope12. The signoff does not imply that the requirements are constrained by time, cost, and quality, or that the project can now be launched, or that the business analyst’s work is done. These are other aspects of the project management and business analysis processes that are not directly related to the signoff on the requirements. References:

• 1: BABOK® Guide, Version 3.0, p. 41
• 2: Business Analysis Expert Certification, CCBA® | IIBA®

The high-level requirements list that the business analyst may create when using a change-driven approach is also known as requirements envisioning. This is a technique for eliciting and documenting the high-level features and characteristics of the solution, and defining the scope and boundaries of the initiative12. Requirements envisioning helps to establish a common understanding and vision among the stakeholders, and to guide the iterative and incremental delivery of the solution. The other options are not terms that are equivalent to the high-level requirements list, but rather terms that describe different aspects of the solution or the project, such as project scope (B), which is the work that must be performed to deliver the solution3, product scope ©, which is the features and functions that characterize the solution3, or requirements foundation (D), which is a term that refers to the core set of requirements that are essential for the solution4. References: Business Analysis Expert Certification, CCBA® | IIBA®, Certification of Capability in Business Analysis™ (CCBA®), Business Analysis Certification Competencies, CCBA® | IIBA®, The Ultimate Guide to Business Capability Analysis

 A request for quote (RFQ) is a document that invites vendors to provide a price quote for their products or services based on a detailed statement of work (SOW). The SOW describes the scope, specifications, deliverables, and acceptance criteria of the solution that the organization needs. The RFQ allows the organization to compare different vendors based on their prices and capabilities, and to select the best one for the project.

References: The information is verified as per the CCBA Learning documents and resources, which outline the standards and practices for business analysis. You can find more information about the RFQ and the SOW in the CCBA guide1 and the BABOK Guide2 available through the IIBA website and bookstore3. You can also find some useful resources and sample questions from other sources.

The project communications management plan is a document that describes how the project information will be generated, collected, distributed, stored, retrieved, and disposed of. It also defines the communication requirements, methods, frequency, and responsibilities for each stakeholder group based on the stakeholder analysis. The project communications management plan helps to ensure that the project stakeholders are kept informed, engaged, and satisfied with the project progress and outcomes12.

The other options are not correct because:

• Option A is incorrect. The project schedule is a document that shows the planned start and finish dates, durations, dependencies, and resources of the project activities. It does not record the communication requirements based on the stakeholder analysis3.
• Option B is incorrect. The project scope management plan is a document that describes how the project scope will be defined, validated, and controlled. It does not record the communication requirements based on the stakeholder analysis4.
• Option C is incorrect. The project reporting structure is not a standard term in project management or business analysis. It may refer to the organizational structure of the project team or the format and content of the project reports. However, it does not record the communication requirements based on the stakeholder analysis.

References:

• Project Communication Management - Five Steps | PMI, section “Project communication management applies the general management skill of communication within the boundaries of the project being managed and the responsibilities of the project manager.”
• What is Project Communication Management? | Wrike, section “What Is Project Communication Management?”
• Project Schedule, section “Description of Change”
• Project Scope Management - A Quick Guide | Simplilearn, section “What is Project Scope Management?”