CBAP Certified Business Analysis Professional Questions and Answers

 A scribe is a participant who has to keep the minutes and details of the conversation during interviews. A scribe is a person who records the key points, questions, answers, and action items that are discussed during the interview. A scribe helps to capture the information accurately and completely, as well as to document any assumptions, issues, or risks that arise during the interview. A scribe also helps to prepare and distribute the interview notes and follow-up actions to the relevant stakeholders. A scribe can be a business analyst, a stakeholder, or a third-party facilitator, depending on the availability and suitability of the role. References: IIBA BABOK Guide v3, section 4.2.5.2, page 116; CBAP / CCBA Certified Business Analysis Study Guide, chapter 4, page 178; Free CBAP CBAP® Exam Questions - IIBA CBAP Exam - Study4Exam, question 240.

 Operational assessment is a type of analysis that involves evaluating the current state of the business processes, activities, and performance, and identifying the gaps, issues, and opportunities for improvement. Operational assessment was missed prior to purchasing a solution, because it would have helped to understand the differences and similarities between the Life and Non-Life teams, and to determine the best solution that would meet the needs and expectations of both groups. By skipping the operational assessment, the company bought a solution that did not fit the processes and preferences of the Non-Life team, and resulted in inefficiency and dissatisfaction. Organizational structure, stakeholder impact analysis, or stakeholder location are not the best options for the type of analysis that was missed, because they are either irrelevant, inaccurate, or not the root cause of the problem. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Strategy Analysis, page 248
• Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 5: Strategy Analysis, section 5.2: Analyze Current State, page 95
• Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 6: Strategy Analysis, page 248

 The information architect is the role that helps assess the data requirements of a project, identifies data assets, and helps the project team complete data modeling requirements. The information architect is responsible for designing and organizing the data structures, relationships, and flows that support the business processes and objectives. The information architect also ensures that the data quality, security, and integrity are maintained throughout the project. The information architect works closely with the business analyst, the database analyst, the end user, and the subject matter expert to elicit, analyze, validate, and communicate the data requirements and models. References: CBAP / CCBA Certified Business Analysis Study Guide, chapter 6, page 237; CBAP Sample Questions, question 231.

The critical path method (CPM) is a graphical presentation of a project plan that shows the sequence and duration of the project activities, and the dependencies and constraints among them. The CPM identifies the critical path, which is the longest path of activities that determines the minimum time required to complete the project. The CPM also identifies the float or slack, which is the amount of time that an activity can be delayed without affecting the project completion date. The CPM is most appropriate for presenting to upper management because it provides a clear and concise overview of the project schedule, scope, and risk. It also helps to communicate the project milestones, deliverables, and progress, and to highlight the critical activities and issues that need attention or resolution12. A pie chart is a graphical presentation of a project plan that shows the proportion of each category or segment of data in relation to the whole. A pie chart is useful for presenting to upper management when the project plan involves a simple breakdown of the project budget, resources, or scope into discrete and mutually exclusive categories or segments. A pie chart helps to compare the relative size and distribution of the categories or segments, and to illustrate the percentage or fraction of the whole that each category or segment represents34. A Pareto chart is a graphical presentation of a project plan that shows the frequency or impact of different factors or causes of problems or issues in descending order of importance. A Pareto chart is based on the Pareto principle, also known as the 80-20 rule, which states that 80% of the effects come from 20% of the causes. A Pareto chart is useful for presenting to upper management when the project plan involves a complex analysis of the project quality, performance, or risk. A Pareto chart helps to identify and prioritize the most significant factors or causes of problems or issues, and to focus on the vital few rather than the trivial many5 . A scatter chart is a graphical presentation of a project plan that shows the relationship or correlation between two variables or sets of data. A scatter chart plots the values of the variables or sets of data as points on a coordinate plane, and shows the pattern or trend of the points. A scatter chart is useful for presenting to upper management when the project plan involves a sophisticated evaluation of the project variables, outcomes, or assumptions. A scatter chart helps to explore and test the hypotheses or causal relationships between the variables or sets of data, and to measure the strength and direction of the correlation . References:

• Critical Path Method - iiba.org
• How to Make a Project Plan Presentation for Clients and Stakeholders
• Pie Chart - iiba.org
• How to Use a Schedule Model in Project Management
• Pareto Chart - iiba.org
• [ProjectManagement.com - Certified Business Analysis Professional (CBAP®)]
• [Scatter Chart - iiba.org]
• [CBAP Presentation | PPT - SlideShare]

 A formal approach is suitable for a project that has a high level of complexity, uncertainty, and risk, as well as a high degree of stakeholder involvement and scrutiny. A project to expand into new markets is likely to have these characteristics, especially in the banking industry, which is highly regulated and competitive. A formal approach would help ensure that the project scope, objectives, and requirements are clearly defined, communicated, and approved by the relevant stakeholders, such as the CEO and the CFO. A formal approach would also provide more control and traceability over the project deliverables and changes, as well as more visibility and accountability for the project progress and outcomes. References: CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 2: Business Analysis Planning and Monitoring, page 59; Business Analysis Body of Knowledge (BABOK ®) Guide, Chapter 2: Business Analysis Planning and Monitoring, section 2.1.4: Selecting the Business Analysis Approach, pages 28-29.

 Collaborative games are a technique that can be used to elicit requirements in a workshop setting. They involve engaging the participants in structured activities that encourage creativity, collaboration, and consensus. Collaborative games can help to avoid disrupting the workshop by creating a positive and productive atmosphere, reducing the potential for conflict, and increasing the buy-in and ownership of the requirements. Some examples of collaborative games are brainstorming, affinity diagramming, storyboarding, and prioritization games. References:

• Business Analysis Body of Knowledge (BABOK) Guide, section 10.18, Collaborative Games
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, chapter 6, Elicitation and Collaboration, page 223-224
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, chapter 10, Review Questions, question 10.14, page 440

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

• A business problem or opportunity
• Possible solutions and their benefits and disadvantages
• Risks associated with the main solution
• Costs
• Implementation timeline
• Consequences for implementing a solution and for retaining the status quo

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

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

• How to Write a Business Case (Template Included) - ProjectManager
• How to Write a Business Case | Smartsheet
• Prioritizing Requirements - IIBA®
• How to Prioritize Requirements: Techniques, Tools, and Examples
• Break-Even Analysis - Definition, Formula, Example, and Advantages
• [How to Write a Business Case (with Examples & Template to Help) - Pingboard]
• [Cost-Benefit Analysis: A Quick Guide with Examples and Templates]

A phase gate review is a process that must be performed at the end of each project phase to determine the completeness of the project work and to gain the customer’s acceptance to move the project forward. A phase gate review is also known as a stage gate review, a milestone review, or a toll gate review. The purpose of a phase gate review is to evaluate the project’s performance, risks, issues, deliverables, and alignment with the business objectives and requirements. A phase gate review also provides an opportunity to decide whether to continue, modify, or terminate the project based on the current status and expected outcomes. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, page 47
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, page 47
• CERTIFIED BUSINESS ANALYSIS PROFESSIONAL, page 6
• Business Analysis Professional Resources | IIBA®, under Standards, Regulations, and Best Practices

To calculate the break-even point, we need to compare the total costs of the internal solution and the vendor’s solution over time. The internal solution has a higher initial cost ($78,000) and a higher monthly cost ($8,765) than the vendor’s solution ($61,000 and $7,990 respectively). Therefore, the internal solution will take longer to break even with the vendor’s solution. The formula for the break-even point is:

Break-even point = (Initial cost difference) / (Monthly cost difference)

Plugging in the numbers, we get:

Break-even point = ($78,000 - $61,000) / ($8,765 - $7,990) Break-even point = $17,000 / $775 Break-even point = 21.94 months

Rounding up to the nearest whole month, we get 22 months as the break-even point. References: This question is based on the concept of financial feasibility analysis, which is part of the business analysis planning and monitoring knowledge area in the BABOK® Guide. Financial feasibility analysis is the process of comparing the costs and benefits of different solutions to determine the optimal one for the organization. One of the techniques for financial feasibility analysis is break-even analysis, which calculates the point in time when the costs of a solution equal the benefits of the solution. You can find more information about financial feasibility analysis and break-even analysis in the following sources:

• BABOK® Guide, section 3.4.5.5, pages 76-77
• CBAP / CCBA Certified Business Analysis Study Guide, chapter 3, pages 85-86
• Certified Business Analysis Professional™ (CBAP®) | Coursera, course 2, week 3, video 3.3

A plan-driven approach to business analysis is a methodology that focuses on minimizing up-front uncertainty and ensuring that the solution is fully defined before implementation begins in order to maximize control and minimize risk. This approach tends to be preferred in situations where requirements are stable and clear, and where changes are costly and disruptive. Therefore, a plan-driven approach has the most business analysis work at the beginning of the project or during the start of a project phase, as it involves detailed planning, analysis, and documentation of the requirements and the solution. A plan-driven approach also requires formal approval and sign-off of the requirements and the solution before moving to the next phase123. References: 1: How to Choose the Right Business Analysis Approach1 2: Plan driven projects versus change driven2 3: Business Analysis Methodology3

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

• Business Analysis Approach (BA Planning & Monitoring)
• Adapting Your Requirements Practices | StickyMinds
• Requirements definition and management — English - SFIA

The conduct stakeholder analysis task is one of the tasks in the business analysis planning and monitoring knowledge area. According to the BABOK® Guide1, this task involves identifying and analyzing the stakeholders of a change, assessing their attitudes, expectations, influence, and interests regarding the change, and determining the best ways to engage and communicate with them. The purpose of this task is to ensure that the business analysis activities are aligned with the needs and concerns of the stakeholders, and that the stakeholders are appropriately involved and informed throughout the change.

The other options are not accurate descriptions of the conduct stakeholder analysis task, but rather:

• A. This is a partial description of the define business need task, which identifies the business problem or opportunity that requires analysis.
• C. This is a partial description of the assess capability gaps task, which compares the current and future states to identify the gaps that must be addressed by a solution.
• D. This is a vague and incomplete description of the conduct stakeholder analysis task, as it does not mention the analysis, assessment, and engagement aspects of the task.

References:

• CBAP® Handbook, page 15, section 4.1.2.3
• BABOK® Guide, page 32, section 3.2.3
• CBAP / CCBA Certified Business Analysis Study Guide, page 96, section 3.2.3
• How To Create a Stakeholder Analysis (With Example)
• How to Perform a Stakeholder Analysis | Lucidchart

The number of communication channels in a project is an indicator of the complexity of communication among the stakeholders. It is calculated by using the following formula1:

Number of communication channels = N x (N - 1) / 2

Where N = Number of stakeholders

In this case, N = 65, so the number of communication channels is:

65 x (65 - 1) / 2 = 2080

Therefore, the correct answer is A. 2080. References:

• Number of Communication Channels (+ PMP® Formula & Calculator)

 Regulatory ranking is a type of requirements prioritization that involves ranking the requirements based on the compliance with laws and regulations in the industry. Regulatory ranking can help to ensure that the solution meets the legal and ethical standards and avoids penalties or lawsuits. Regulatory ranking can also help to align the solution with the organizational policies and objectives. Regulatory ranking is one of the factors that influence the requirement prioritization, as it reflects the penalty of not implementing a requirement. Regulatory ranking can be done by identifying the relevant laws and regulations for the solution, assessing the impact and likelihood of non-compliance, and assigning a priority level to each requirement123. References: 1: What AreRequirement Prioritization Techniques?1 2: Prioritizing Legal Requirements2 3: What Is Requirements Prioritization?3

Benchmarking is a business analysis approach that involves comparing one’s own performance, processes, or products with those of other organizations, especially the best performers or industry leaders, to identify gaps and opportunities for improvement. Benchmarking can help business analysts understand the competitive landscape, identify best practices, set realistic goals, and measure progress. In this question, Sally and her business analysis team are using benchmarking to determine what the competition is offering and how they can increase their revenue by remaining competitive. References:

• CBAP® Handbook, page 15, section 4.1.2.3
• BABOK® Guide, page 32, section 3.2.3
• CBAP / CCBA Certified Business Analysis Study Guide, page 96, section 3.2.3
• What is a Competitive Analysis — and How Do You Conduct One?

 Focus groups are a type of requirements elicitation activity that involve gathering a group of stakeholders from different perspectives and backgrounds to discuss a specific topic or issue. Focus groups can help to identify the ideas and attitudes of the stakeholders about the current situation, the desired outcomes, the problems, the solutions, and the actions needed to improve the service. Focus groups can also help to generate new ideas, uncover hidden needs, and reveal conflicting opinions. Focus groups are facilitated by a moderator who guides the discussion, asks open-ended questions, and encourages participation from all members. Focus groups are usually recorded and analyzed to extract the key findings and requirements1234. References: 1: Software Engineering | Requirements Elicitation - GeeksforGeeks 2: A Review of Fundamental Tasks in Requirements Elicitation 3: Top 10 Most Common Requirements Elicitation Techniques 4: 20 Tips for Effective Requirements Elicitation | Inflectra

 A repository is a centralized place where project requirements are stored and managed throughout the project lifecycle. A repository can be a physical or electronic system that allows business analysts to access, update, and track the status of the requirements. A repository can also facilitate the communication, collaboration, and verification of the requirements among the stakeholders. A repository is not the same as a change management system (A), a project scope statement ©, or a requirements register (D), which are different tools or documents that serve different purposes in project management. References:

• IIBA BABOK Guide v3, p. 30, 176, 264
• How to Write Project Requirements | Smartsheet, paragraph 3
• What is Requirements Management? | IBM, paragraph 1

The T in SWOT analysis stands for Threats. These are external factors that may pose risks or challenges to the organization, its projects, or its solutions. Threats can be related to the market, the industry, the technology, the environment, the society, the regulation, or the competition. Business analysts should identify and assess the potential threats and their impact on the organization’s objectives and strategies, and recommend ways to mitigate or avoid them. References:

• CBAP® Handbook, page 15, section 4.1.2.3
• BABOK® Guide, page 32, section 3.2.3
• SWOT Analysis: How To With Table and Example
• SWOT Analysis Threats: Definition & Examples

A business case is a document that clearly identifies the reasoning for initiating a project to justify the resources required. It is written to justify the resources required for the project (money or effort) and align the project objectives to the business needs. It also includes the costs, benefits, and risks of the proposed solution, and compares it with alternative options1. A business case is an important input for the project initiation and approval process, as it helps the decision makers to assess the value and feasibility of the project2.

To write a business case, you need four main inputs: feasibility study, assumptions and constraints, business need, and solution options3. A feasibility study is an analysis that evaluates the technical, economic, social, and environmental aspects of the project, and determines whether it is viable and worth pursuing4. Assumptions and constraints are factors that affect the project scope, cost, schedule, and quality, and that need to be identified and documented in the business case. Assumptions are things that are believed to be true or certain, while constraints are things that limit or restrict the project5. Business need is the problem or opportunity that the project aims to address, and that aligns withthe strategic goals and vision of the organization. Solution options are the different ways of solving the business need, and their respective costs, benefits, and risks.

Stakeholder concerns are not an input for writing a business case, but rather an output of stakeholder analysis. Stakeholder analysis is a process of identifying and prioritizing the people or groups who have an interest or influence in the project, and understanding their needs, expectations, and perspectives. Stakeholder concerns are the issues or challenges that the stakeholders face or anticipate in relation to the project, and that need to be addressed or resolved. Stakeholder concerns are important for defining the requirements, managing the communication, and ensuring the stakeholder satisfaction, but they are not directly used for writing the business case. References:

• How to Write a Business Case (Template Included) - ProjectManager
• How to Write a Business Case | Smartsheet
• Business Case Examples, explained in simple language - Chase Consulting
• Feasibility Study: Definition, Methods, and Examples
• Project Assumptions and Constraints: Examples and Differences
• [Business Need - IIBA®]
• [Solution Options - IIBA®]
• [Stakeholder Analysis: Overview, Tools and Techniques - KnowledgeHut]
• [Stakeholder Concerns - IIBA®]

Functional decomposition is a technique that breaks down a complex solution scope into smaller and manageable work products or deliverables. It helps to understand the scope of work that needs to be completed, and to organize and prioritize the requirements. Functional decomposition can be represented in various ways, such as hierarchical diagrams, tables, or lists. It can also be used to create a work breakdown structure (WBS) for the project management. Functional decomposition is useful for projects that have a large or unclear solution scope, as it helps to reduce ambiguity and complexity, and to identify dependencies and gaps. References:

• Using Scope Models to Manage Solution Scope
• Solution Scope vs. Project Scope
• Solution Scope – An Insight

A change strategy is a plan that outlines how the project team will manage the transition from the current state to the future state of the system, and how they will address the impacts and risks of the change on the organization and the stakeholders. A change strategy is needed when system A is offline for 3 months, as this will affect the claims processing operations and the user experience. A change strategy should include the following elements:

• Change vision and objectives: This defines the purpose and scope of the change, and the expected outcomes and benefits of the system upgrade.
• Change readiness assessment: This evaluates the current level of awareness, willingness, and ability of the organization and the stakeholders to adopt the change, and identifies any gaps or barriers that need to be addressed.
• Change impact analysis: This identifies and analyzes the potential effects of the change on the business processes, roles and responsibilities, policies and procedures, systems and tools, and culture and behavior of the organization and the stakeholders.
• Change communication plan: This specifies the key messages, channels, methods, and frequency of communication with the organization and the stakeholders, and how to solicit and incorporate feedback and input.
• Change training plan: This defines the learning objectives, content, delivery modes, and evaluation methods of the training programs that will help the organization and the stakeholders acquire the necessary knowledge and skills to use the upgraded system.
• Change management roles and responsibilities: This clarifies the roles and expectations of the project team, the sponsors, the champions, the change agents, and the end users in the change process, and how they will collaborate and coordinate with each other.
• Change monitoring and evaluation plan: This establishes the metrics, indicators, and tools that will measure the progress and performance of the change process, and how to report and act on the results.

References:

• IIBA BABOK Guide, Section 5.6, Define Change Strategy
• Change Management Strategy: A Guide with Best Practices, Smartsheet
• How to Develop a Change Management Strategy, Indeed

 A focus group is a technique that helps to elicit the opinions, preferences, and feedback of a group of stakeholders about a specific topic, such as a prototype of a new web-based application. A focus group is facilitated by a moderator who guides the discussion and encourages the participants to share their views and experiences. A focus group can help the BA to understand the stakeholders’ perception, ideas, and attitudes about the prototypes, and to identify any issues, gaps, or improvements. A decision analysis is a technique that helps to evaluate and compare the possible outcomes of different alternatives using criteria such as costs, benefits, risks, and impacts. A decision analysis can help the BA to select the best solution option, but it does not elicit the stakeholders’ perception, ideas, and attitudes about the prototypes. A prioritization is a technique that helps to rank the requirements or solution options based on their relative importance, urgency, value, or dependency. A prioritization can help the BA to determine the optimal scope and sequence of the solution delivery, but it does not elicit the stakeholders’ perception, ideas, and attitudes about the prototypes. A brainstorming is a technique that helps to generate a large number of ideas or solutions in a short time by encouraging the participants to think creatively and freely. A brainstorming can help the BA to explore different possibilities and perspectives, but it does not elicit the stakeholders’ perception, ideas, and attitudes about the prototypes. References: BABOK Guide v3, Chapter 10: Techniques, Section 10.24: Focus Groups, p. 532-533; Section 10.16: Decision Analysis, p. 518-520; Section 10.38: Prioritization, p. 550-552; Section 10.7: Brainstorming, p. 503-504.

 Assessing the capability gaps is the business analysis process that involves comparing the current state and the future state of an organization to identify the gaps or differences that must be addressed by a solution. This process helps to understand the root causes of the problems, the needs and opportunities for improvement, and the feasibility and scope of the solution. In this question, the NGQ Company wants to analyze its ability to meet an identified business need, which implies that there is a gap between its current and desired performance. Therefore, assessing the capability gaps is the appropriate process to complete for the organization. References:

• CBAP® Handbook, page 14, section 4.1.2.2
• BABOK® Guide, page 30, section 3.2.1
• CBAP / CCBA Certified Business Analysis Study Guide, page 94, section 3.2.1
• Business Analysis Process Flow: Step by Step Tutorial, step 3. Analyze all the project relevant documents

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

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

References:

• [A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 402, section 10.31.2.11
• Textual Requirement Artifacts - Blueprint Online Help - HelpDocs, paragraph 1
• How to Model Textual Requirements - Formal Mind GmbH, paragraph 2

Alternative generation is a business analysis element that tries to identify as many potential options as possible to meet the business objectives and fill identified gaps in capabilities. Alternative generation is part of the strategy analysis knowledge area, which involves defining the business need, assessing the current state, defining the future state, identifying solution options, and recommending a solution. Alternative generation helps to explore the possible ways to achieve the desired outcomes, and to evaluate the feasibility, viability, and suitability of each option. Alternative generation can use various techniques, such as brainstorming, benchmarking, market analysis, or SWOT analysis, to generate and compare different solution alternatives. References:

• [A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 100, section 5.41
• [CBAP Certification Study Guide v3.0], Chapter 5: Strategy Analysis, Section 5.4: Identify Solution Options, page 5-152
• What Is Business Analysis and Why Is It Important? - Indeed, paragraph 4
• More CBAP Preparation Questions – The Functional BA, question 4

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

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

The implementation approach is a component of the solution scope that describes how the chosen solution approach will deliver the solution scope. The solution approach is the method or process that will be used to implement the solution, such as a predictive or adaptive approach. The solution scope is the set of capabilities and features that the solution must provide to meet the business need1. The implementation approach explains how the solution approach will be applied to achieve the solution scope, such as the phases, activities, tasks, deliverables, and resources involved. The implementation approach also considers the risks, issues, assumptions, and constraints that may affect the implementation process23.

The other options are not correct. A. The implementation approach is not described in terms of the major features and functions that are to be included, as this is part of the solution scope, not the implementation approach. B. The implementation approach does not define major business and technical dependencies that impose constraints to the effort to deploy the solution, as this is part of the risk analysis, not the implementation approach. C. The implementation approach does not describe the new capabilities required to meet the business need, as this is part of the solution scope, not the implementation approach. References:

• Solution Scope - IIBA®
• Defining the Business Analysis Approach in 2023 | Free Template
• Business Analysis Planning and Monitoring - IIBA®

Prioritizing requirements by the likelihood of success is a technique that can help build confidence and trust among the project stakeholders, especially if the project is complex, risky, or has a long duration. By delivering some of the requirements that have a highchance of success early in the project, the business analyst can demonstrate the value of the project and the effectiveness of the business analysis process. This can also help reduce resistance to change and increase user satisfaction and adoption. Some of the other factors that can be used to prioritize requirements are business value, urgency, dependency, risk, cost, and effort. References:

• Certified Business Analysis Professional (CBAP) Handbook, page 6, section 4. Review the Exam Blueprint.
• BABOK Guide v3, page 34, section 4.2.3. Prioritize Requirements.

The type of project or initiative affects the business analysis duties that need to be performed, as different types of projects may require different approaches, techniques, deliverables, and stakeholders. For example, a software development project may have different business analysis needs than a business process improvement project. The business analyst should plan the business analysis process according to the project type and its characteristics, such as scope, complexity, risk, methodology, and lifecycle. References:

• A Checklist for Business Analysis Planning
• Business Analysis Process Flow: Step by Step Tutorial
• What is Business Analysis? Process & Techniques
• How do you plan a business analysis approach?

The business analysis approach is a plan that describes how the business analysis activities will be performed, including the deliverables, the team roles, the analysis techniques, the communication methods, the change management process, and the stakeholder engagement strategy. The business analysis approach does not define the requirements for solutions acceptance, which are the criteria that the solution must meet to be accepted by the stakeholders. The requirements for solutions acceptance are part of the solution scope, which is an output of the enterprise analysis tasks, not the business analysis approach. References:

• [A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 24, section 2.21
• [CBAP Certification Study Guide v3.0], Chapter 4: Requirements Life Cycle Management, Section 4.1: Plan Business Analysis Approach, page 4-22
• Business Analysis Approach, paragraph 1

A RACI chart is a tool that helps to define and clarify the roles and responsibilities of different stakeholders in a project or a process. It stands for Responsible, Accountable, Consulted, and Informed, which are the four types of tasks or activities that stakeholders can be involved in. A RACI chart is a matrix that lists the tasks or activities in the left column and the stakeholders or roles in the top row. For each task or activity, the RACI chart indicates who is Responsible, Accountable, Consulted, or Informed by using the letters R, A, C, or I. A RACI chart can help to improve communication, collaboration, and accountability among stakeholders, and to avoid confusion, duplication, or conflict of roles. A RACI chart can be used as part of the stakeholder analysis process, which is the process of identifying, categorizing, and assessing the stakeholders of a project or a process, and understanding their needs, expectations, and interests.

References:

• RACI Chart - a how to guide to using RACI, paragraph 1
• How the RACI Matrix Streamlines Stakeholder Engagement, paragraph 1
• Stakeholder Wrangling 101: The RACI Framework, paragraph 1
• [A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 30, section 2.51

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

• CBAP® Handbook, page 6, section 2.4 Review the Exam Blueprint
• BABOK® Guide, page 30, section 3.2 Requirements Analysis and Design Definition
• CBAP / CCBA Certified Business Analysis Study Guide, page 111, chapter 5 Requirements Analysis

A requirements re-use repository is a collection of reusable requirements that can be applied to similar projects or products. It can help streamline the requirements gatheringprocess by reducing the effort and time needed to elicit, analyze, and document requirements. It can also improve the quality and consistency of requirements by leveraging best practices and lessons learned from previous projects. A requirements re-use repository can also facilitate traceability, change management, and communication among stakeholders.

B. Implementing project templates is not the best answer because project templates are more related to project management than requirements gathering. Project templates can help standardize the project planning and execution processes, but they do not necessarily address the specific requirements of each project or product.

C. Implementing a requirements gathering form is not the best answer because a requirements gathering form is a tool for capturing and documenting requirements, not for streamlining the requirements gathering process. A requirements gathering form can help structure and organize the requirements, but it does not reduce the effort and time needed to elicit, analyze, and document requirements.

D. Implementing scope solution models is not the best answer because scope solution models are used to define and communicate the boundaries and features of a solution, not to streamline the requirements gathering process. Scope solution models can help clarify and validate the solution scope, but they do not reduce the effort and time needed to elicit, analyze, and document requirements. References:

• Using Scope Models to Manage Solution Scope - Business Analyst Articles …
• What is requirements gathering? Template and examples
• Top 10 Requirements Gathering Templates with Samples and Examples

 Requirements prioritization is the process of ranking the requirements in the order of their importance or value to the stakeholders and the solution. Requirements prioritization helps to ensure that the most critical and beneficial requirements are implemented first, and that the project focuses on delivering the maximum value to the stakeholders within the available time and resources. Requirements prioritization also helps to manage the scope, schedule, budget, and quality of the project, as well as to handle changes and risks effectively123. References: 1: Five Requirements Prioritization Methods1 2: What is Requirements Prioritization?2 3: The 6 Most Important Requirements Practices3

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

• CBAP® Handbook, page 6, section 4. Review the Exam Blueprint, under Business Analysis Planning and Monitoring, task 5.2: Plan Business Analysis Process Improvements.
• CBAP / CCBA Certified Business Analysis Study Guide, page 144, section 5.2.2: Plan Business Analysis Process Improvements, under Automation.

A model is a representation of a system or a process that helps stakeholders and customers visualize the potential system. Models can use different forms, such as flowcharts, graphs, diagrams, or prototypes, to show the structure, behavior, or functionality of the system. Models are useful for communicating, analyzing, verifying, and validating the requirements.

Models are not slices of the project solution (A), although they may show some aspects of the solution. Models are not meant to simplify the requirements for common stakeholders (B), but rather to help all stakeholders understand the requirements better. Models are not statistics for the return on investment, time saved, and other mathematics ©, although some models may use quantitative data to support the requirements.

The solution approach is the process of defining the most feasible and appropriate way to implement a change that addresses a business need. It involves identifying and evaluating different options for creating or acquiring new capabilities, such as products, services, processes, or systems, that will deliver value to the stakeholders and solve the business problem. The solution approach also considers the constraints, risks, assumptions, and dependencies that may affect the solution. The solution approach provides the basis for defining the solution scope, which specifies the features and functions of the solution, and the project scope, which specifies the work required to deliver the solution123.

The other options are not correct definitions of the solution approach. Option A is the definition of scope change control, which is the process of managing and documenting the changes to the product scope as approved by the project stakeholders. Option C is the definition of a risk, which is an uncertain event or condition that may have a positive or negative impact on the project objectives. Option D is the definition of decomposition, which is a technique that breaks down the project scope into smaller deliverables; each deliverable is subdivided repeatedly until the deliverable cannot or should not be broken down any further4. References: 1: BABOK® Guide v3, section 11.2 Define Solution Approach, page 402 2: CBAP® Exam Prep Study Guide, chapter 9, page 323 3: How toChoose the Right Business Analysis Approach 4: PMBOK® Guide, Sixth Edition, section 5.4.2.1 Decomposition, page 156

According to the BABOK Guide, defining the business needs is the process of identifying the ends that the organization is seeking to achieve. Business goals and objectives are statements of the desired outcomes of the change initiative that align with the organization’s strategy and vision. They provide the context for identifying and evaluating alternative solutions that can satisfy the business needs. Alternative identification, solution assessment, and requirements are parts of other processes that follow defining the business needs. References:

• BABOK Guide, Chapter 5: Strategy Analysis, Section 5.1: Define the Business Need, p. 100-101
• CBAP Certification Study Guide v3.0, Chapter 5: Strategy Analysis, Section 5.1: Define the Business Need, p. 5-3 to 5-4

 The BA needs to compare the value and costs of different design options, such as a customized version of the existing software or a fully made to order solution. The potential value is the benefit that the solution will provide to the bank, such as improved efficiency, accuracy, and security. The design options are the alternative ways of meeting the needs and requirements of the bank, such as modifying the existing software or developing a new one. The BA needs to evaluate the trade-offs between the value and costs of each option and recommend the most feasible and desirable one. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Strategy Analysis, page 217
• Business Analysis Body of Knowledge (BABOK ®) Guide, Version 3, Section 6.4: Define Design Options, pages 142-144
• Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 3: Strategy Analysis, Week 3: Define Design Options

The business analysis approach is the set of processes, activities, tasks, deliverables, and techniques that are used to conduct business analysis. The business analysis approach should be aligned with the needs, preferences, and expectations of the stakeholders, as well as the characteristics and constraints of the project and the organization. The level of formality is one of the factors that influences the business analysis approach. It refers to the degree of rigor, detail, and documentation that is required for the business analysis work. The level of formality may vary depending on the type, size, complexity, and risk of the project, as well as the regulatory and governance requirements, the stakeholder involvement, and the organizational culture. In this scenario, the BA is dealing with two main stakeholders that have different levels of formality. The government agency is highly regulated and may require a formal approach that follows strict standards, policies, and procedures, and produces detailed and comprehensive documentation. The private company is less formal and may prefer a flexible and collaborative approach that allows for rapid changes, feedback, and experimentation, and produces minimal and concise documentation. Therefore, the BA’s strategy should be to develop consensus on a tailored approach for formality that balances the needs and expectations of both stakeholders, and that is suitable for the project context and objectives. The BA should facilitate a meeting with the representatives from each entity and discuss the advantages and disadvantages of different levels of formality, and how they can be adapted and customized to meet the project requirements and deliver value. The BA should also consider the impact of the level of formality on the other aspects of the business analysis approach, such as the planning, elicitation, analysis, validation, and management of the requirements and design specifications. The BA should seek to achieve a common understanding and agreement among the stakeholders on the level of formality and the business analysis approach. Option B is incorrect because using a formal approach to appeal to the government entity’s higher authority may not satisfy the needs and preferences of the private company, and may create conflict and dissatisfaction among the stakeholders. Option C is incorrect because employing the standard business analysis level of formality may not be appropriate or effective for the project and the organization, and may not address the specific needs and expectations of the stakeholders. Option D is incorrect because asking the government entity to accept a flexible collaborative approach may not comply with the regulatory and governance requirements, and may create resistance and distrust among the stakeholders. References: BABOK Guide v3, Chapter 2: Business Analysis Planning and Monitoring, Section 2.2: Plan Business Analysis Approach, p. 28-32; Chapter 10: Techniques, Section 10.6: Business Analysis Approach, p. 501-502.

The BA should approach the solution limitation by assessing the impact on the business operations. This means that the BA should analyze how the inability to meet the SLA in one out of five scenarios would affect the business goals, objectives, performance, value, and risks. The BA should also consider the frequency, severity, and likelihood of the scenarios, and the expectations and needs of the stakeholders. Based on the impact assessment, the BA can then recommend the best course of action, such as modifying the SLA, changing the business process, increasing the scope, or deferring the requirement to a future release. The other options are not the best approaches, as they may either be unrealistic, unnecessary, or ineffective without a proper impact assessment. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 7: Solution Evaluation, Section 7.2: Analyze Performance Measures, p. 311-312
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 7: Solution Evaluation, Section 7.2: Analyze Performance Measures, p. 269-270

 In order to gain consensus between the CFO and other management, the BA could estimate the potential value delivered by each option and present the results to the stakeholders. This would involve assessing the benefits, costs, and risks of each option, as well as the alignment with the strategic objectives and customer needs. By estimating the value, the BA could help the stakeholders understand the trade-offs and implications of each option, and facilitate a rational and informed decision-making process. References:

• IIBA BABOK Guide, Section 9.4, Evaluate Solution Options
• How to Estimate the Value of a Business Analysis Solution, Bridging the Gap
• Business Analysis Techniques: Estimating Value, Business Analyst Learnings

 A cultural assessment is a process of evaluating the current state of the enterprise culture and how well it aligns with the goals and values of the organization. It can help the BA understand the expectations, experiences, philosophies, and behaviors that guide the stakeholders in the organization. By conducting a cultural assessment, the BA can identify the potential impacts of the solution change on the organizational culture and vice versa. The BA can also use the assessment results to plan for effective change management and stakeholder engagement strategies. References:

• IIBA BABOK Guide, Section 3.5.2, Enterprise Culture Assessment
• Cultural Assessments: What They Are and How To Conduct One, Indeed.com
• Culture Assessment: Definition, Framework, Types of Culture and Questions, QuestionPro.com

 A risk-averse organization is one that prefers to minimize or eliminate the exposure to risks, even if it means sacrificing some potential benefits or opportunities. A risk avoidance strategy is one that involves changing the project plan, scope, schedule, or budget to avoid the risk or its impact. A risk avoidance strategy is suitable for a risk-averse organization, as it reduces the uncertainty and the potential negative consequences of the risk. In this scenario, the BA has identified an assumption that has a high degree of uncertainty and may affect the validity of the requirements. The BA has added the assumption to the risk register and performed a risk analysis to handle this situation. If the organization is risk-averse, the BA may use a risk avoidance strategy to modify the requirements or the solution design to eliminate the dependency on the assumption, or to seek more information or evidence to validate the assumption. A risk acceptance strategy is one that involves acknowledging the risk and its impact, but not taking any action to prevent or reduce it. A risk acceptance strategy is suitable for a risk-seeking or risk-neutral organization, or for risks that have low probability or impact. A risk transfer strategy is one that involves shifting the responsibility or ownership of the risk or its impact to a third party, such as a vendor, a partner, or an insurer. A risk transfer strategy is suitable for risks that have high impact but low probability, or for risks that require specialized skills or resources to manage. A risk mitigation strategy is one that involves taking actions to reduce the probability or impact of the risk, such as implementing contingency plans, preventive measures, or backup solutions. A risk mitigation strategy is suitable for risks that have high probability and impact, or for risks that can be controlled or influenced by the project team. References: BABOK Guide v3, Chapter 10: Techniques, Section 10.51: Risk Analysis and Management, p. 567-569; Free CBAP IIBA Actual Exam Questions & Answers, Question 467.

Ad images are a strong candidate to be addressed while planning for requirements reuse, because they are likely to change frequently and have common elements that can be reused across different weeks. Requirements reuse is a technique that involves identifying, storing, and reusing requirements or requirement components for future projects or initiatives. It can help to reduce duplication, improve consistency, and save time and effort. Ad images can benefit from requirements reuse, because they can use a standard template, format, and style, and only change the specific image and text for each new topping. Dough preparation, toppings preparation, and topping recipes are not good candidates for requirements reuse, because they are either stable or unique for each week. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 3: Requirements Life Cycle Management, page 124
• Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 3: Requirements Life Cycle Management, section 3.7: Reuse Requirements, page 66
• Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 3: Requirements Life Cycle Management, page 124

 A formal review with the stakeholders is a way to validate the elicitation results and ensure that nothing is missed or misunderstood. The review can also help to build trust and confidence among the stakeholders and the BA. The other options are not directly related to addressing the sponsor’s concerns. References: CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 5: Elicitation and Collaboration, p. 173-174; [A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3], Chapter 4: Elicitation and Collaboration, Section 4.4: Confirm Elicitation Results, p. 107-108.

 A RACI chart is a graphical representation of roles and responsibilities of different project team members. It is a matrix that shows the relationship between the project activities and the project roles. RACI stands for Responsible, Accountable, Consulted, and Informed. These are the four levels of involvement that a project team member can have in a project activity. A RACI chart can help to clarify the expectations, avoid confusion, and improve communication among the project team and stakeholders. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, page 343
• Business Analysis Professional Resources | IIBA®, under Business Analysis Body of Knowledge (BABOK ®) Guide
• What is a RACI Chart? | RACI Chart Definition & Example | ASQ

 A focus group is a technique for eliciting information from a group of stakeholders who have knowledge or experience on a specific topic. It involves asking open-ended questions, facilitating discussions, and capturing feedback. A focus group can help the BA to gather information about the decision making authorities within the company by engaging with the relevant stakeholders, such as project sponsors, managers, directors, or board members. The BA can use the focus group to understand the roles, responsibilities, and expectations of the decision makers, as well as the criteria, methods, and processes they use to make decisions. The other options are not suitable techniques for gathering this information. A market analysis is a technique for researching and analyzing the external factors that affect the demand, supply, and opportunities for a product, service, or solution. A survey is a technique for collecting quantitative or qualitative data from a large number of respondents using a predefined set of questions. A cost benefit analysis is a technique for comparing the costs and benefits of alternative solutions or courses of action. References: CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 5: Elicitation and Collaboration, p. 164-165, 168-169, 171-172; A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3, Chapter 4: Elicitation and Collaboration, Section 4.2: Prepare for Elicitation, p. 94-95; Chapter 10: Techniques, Section 10.15: Focus Groups, p. 378-379.

The project scope statement, an output of the define scope process, does document the process and criteria for accepting completed products. The project scope statement is a detailed description of the project scope, which includes the project objectives, deliverables, requirements, boundaries, assumptions, and constraints. The project scope statement also defines the acceptance criteria, which are the standards or measures that must be met or satisfied by the products, services, or results of the project. The acceptance criteria help to ensure that the customer’s needs and expectations are met and that the project quality is achieved. The project scope statement is a key input for developing the work breakdown structure, the project schedule, the project budget, and the project quality plan. References: [IIBA BABOK Guide v3], section 5.1.2, page 162; [CBAP / CCBA Certified Business Analysis Study Guide], chapter 6, page 233; CBAP Sample Questions, question 253.

The BA needs to consider metrics and key performance indicators (KPIs) when using basic statistical sampling concepts to measure the objective of a solution implemented. Metrics and KPIs are quantitative measures that are used to evaluate the performance, progress, and value of a solution, process, or activity. They can help the BA to determine if the solution is meeting the expected outcomes and benefits, and to identify any gaps, issues, or opportunities for improvement. Metrics and KPIs can also help the BA to communicate the results and impact of the solution to the stakeholders and the organization. Some examples of metrics and KPIs that can be used to measure the objective of increasing the number of customer calls resolved per hour are: average call duration, first call resolution rate, customer satisfaction score, and call resolution efficiency. Frequency and timing, financial analysis, and benchmarking and market analysis are not the best options to consider when using basic statistical sampling concepts, because they are either too general, too specific, or not directly related to the objective of the solution. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 8: Solution Evaluation, page 337
• Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 8: Solution Evaluation, section 8.2: Analyze Performance Measures, page 153
• Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 8: Solution Evaluation, page 337

The project charter is the document that is created first after the project is awarded and the statement of work is handed over to the project manager. The project charter is a high-level document that formally authorizes the initiation of the project and defines the project vision, objectives, scope, deliverables, stakeholders, roles and responsibilities, assumptions, constraints, risks, and success criteria. The project charter also identifies the project sponsor, the project manager, and the project budget and schedule. The project charter provides the direction and guidance for the project and serves as a reference point for future decisions and changes. The project charter is usually created by the project sponsor or the customer, in collaboration with the project manager and the business analyst, and approved by the key stakeholders. References: [IIBA BABOK Guide v3], section 5.1.1, page 161; CBAP / CCBA Certified Business Analysis Study Guide, chapter 6, page 233; CBAP Sample Questions, question 243.

 The user interface is the part of a system that allows the actual users to interact with one another, the system, or data moved between two users. The user interface is the means by which the users can input, view, manipulate, or output information through the system. The user interface can be graphical, textual, auditory, tactile, or a combination of these. The user interface is an important aspect of the user experience and usability of the system. The user interface should be designed to meet the user needs, preferences, and expectations, as well as the system requirements and constraints. References: IIBA BABOK Guide v3, section 9.1.2, page 326; CBAP / CCBA Certified Business Analysis Study Guide, chapter 7, page 251; CBAP Exam Questions - Institute i4, question 241.

 Quantitative risk analysis is a technique that involves attempting to make and numerically determine the probability of various adverse events and measuring the likely extent of the losses. It uses numerical methods, such as expected monetary value analysis, Monte Carlo simulation, decision tree analysis, and sensitivity analysis, to estimate the likelihood and impact of risk events, and to evaluate the overall risk exposure of the project. Quantitative risk analysis can help to prioritize risks, allocate resources, optimize contingency reserves, and support decision making. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, page 47
• Risk Analysis- Open Courses by Atlantic International University - AIU, paragraph 1
• Which of the following techniques involves attempting to make and numerically determine the probability of various adverse events and measuring the likely extent of the losses?, answer D

The BA should use a sequence diagram to elicit information about the other client applications that will interface with the new system and provide the information graphically. A sequence diagram is a type of interaction diagram that depicts the interactions between objects or components in a time-ordered sequence. A sequence diagram can help the BA and the technical staff to understand the message interaction within the systems for key business transactions, as it shows the chronological order of interactions and the messages exchanged between objects. A sequence diagram can also help the BA to model the behavior of a single use case or scenario, and to identify the dependencies and constraints among the objects. Process, activity, or context diagrams are not the best options for this purpose, because they are either too general, too abstract, or not directly related to the message interaction within the systems. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 7: Requirements Analysis and Design Definition, page 279
• Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 7: Requirements Analysis and Design Definition, section 7.5: Specify and Model Requirements, page 133
• Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 7: Requirements Analysis and Design Definition, page 279
• Interaction Diagram Tutorial, Lucidchart, What is an interaction diagram?

One of the possible reasons for the disagreement among the stakeholders is that they have different interpretations of the requirements, which may lead to conflicting expectations, assumptions, and preferences. The BA should use various techniques to elicit, analyze, validate, and communicate the requirements clearly and consistently to all the stakeholders, and to resolve any ambiguities or discrepancies. The BA should also ensure that the requirements align with the business need and the solution scope that were formally approved by the stakeholders at the beginning of the project.

An enterprise readiness assessment is a process of evaluating the current state of an organization and its readiness to adopt a new system or change12. It helps to identify the gaps, risks, and opportunities that may affect the success of the project3. Before eliciting requirements for a new system, the BA needs to understand the current situation, thestakeholders, the culture, the processes, and the potential impacts of the change4. This will help the BA to define the scope, objectives, and approach for the requirements elicitation. 

A work breakdown structure (WBS) is a visual decomposition of the program scope and the resources needed in order to create the things defined within the program scope. A WBS is a hierarchical representation of the deliverables, activities, and tasks that are required to complete the program. A WBS defines the scope, schedule, cost, and quality of the program, and helps to allocate the resources and assign the responsibilities for the program. A WBS also helps to identify the dependencies, risks, and issues of the program, and to monitor and control the program performance12. A resource breakdown structure (RBS) is a visual decomposition of the resources that are needed to complete the program. An RBS is a hierarchical representation of the human and non-human resources that are required to perform the activities and tasks of the program. An RBS defines the types, categories, and quantities of the resources, and helps to estimate, acquire, and manage the resources for the program. An RBS also helps to identify the availability, utilization, and allocation of the resources, and to optimize the resource efficiency and effectiveness13. A product breakdown structure (PBS) is a visual decomposition of the products that are delivered by the program. A PBS is a hierarchical representation of the components and features that make up the products of the program. A PBS defines the scope, quality, and functionality of the products, and helps to design, develop, and test the products for the program. A PBS also helps to identify the requirements, specifications, and standards of the products, and to verify and validate the products14. A budgeted cost of work scheduled (BCWS) is a measure of the planned value of the program. A BCWS is the sum of the budgets for all the work packages and activities that are scheduled to be completed by a given date. A BCWS defines the expected cost of the program, and helps to compare the actual cost and the earned value of the program. A BCWS also helps to identify the cost variance and the cost performance index of the program, and to forecast the cost at completion and the estimate at completion1 . References:

• CBAP® Handbook
• Work Breakdown Structure - iiba.org
• Resource Breakdown Structure - iiba.org
• Product Breakdown Structure - iiba.org
• [Budgeted Cost of Work Scheduled - iiba.org]

The stakeholders and the BA need to measure benefits, penalties, and costs to determine if the solution is providing expected value and ensure the accuracy of the measurements. Benefits are the positive outcomes or value that the solution delivers to the stakeholders or the organization. Penalties are the negative consequences or costs that the solution may incur if it fails to meet the requirements or expectations. Costs are the resources or expenses that are required to implement, operate, and maintain the solution. By measuring benefits, penalties, and costs, the stakeholders and the BA can assess the return on investment (ROI), the net present value (NPV), and the break-even point (BEP) of the solution, and compare them with the expected or planned values. This can help to evaluate the effectiveness, efficiency, and feasibility of the solution, and to identify any gaps, issues, or opportunities for improvement. Strategy, solution, and scope are not the best options to measure, because they are either too general, too abstract, or not directly related to the value of the solution. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 8: Solution Evaluation, page 337
• Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 8: Solution Evaluation, section 8.2: Analyze Performance Measures, page 153
• Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 8: Solution Evaluation, page 337

Time boxing is a technique that involves allocating a fixed amount of time for a specific activity or deliverable. It is often used in agile and iterative approaches to prioritize and manage requirements based on the amount of work that the project team can complete within a given time frame, such as a sprint or an iteration. Time boxing helps to focus on the most important and valuable requirements, deliver frequent and incremental value, and reduce scope creep and rework. Negotiation, grouping, and budgeting are not techniques that are based on the amount of work that the project team is capable of delivering in a given period of time. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 3: Requirements Life Cycle Management, page 121
• Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 3: Requirements Life Cycle Management, section 3.5: Prioritize Requirements, page 62
• Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 3: Requirements Life Cycle Management, page 121

 A requirement attribute is a characteristic or property of a requirement that provides additional information about it. Requirement attributes can help to manage, prioritize, trace, and verify the requirements. Some common requirement attributes are source, priority, status, owner, version, etc. One of the qualities of a good requirement is that it should be unambiguous, which means that it should have only one possible interpretation and avoid any confusion or misunderstanding. An unambiguous requirement is clear, precise, and consistent, and it can be easily verified and validated. An ambiguous requirement, on the other hand, can lead to errors, defects, rework, and conflicts among the stakeholders. References:

• Characteristics of Effective Software Requirements and Software Requirements Specifications (SRS) - Jama Software, under Qualities of Good Requirements
• The Four Attributes of High-Quality Requirements - ArgonDigital, paragraph 1
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, page 47

Information architecture is the structure and organization of information within a system or process1. It helps to ensure that the process models relate to each other by defining the relationships, dependencies, and interactions among the data, information, and knowledge that are used or produced by the processes2. Information architecture also helps to align the process models with the business goals, objectives, and requirements3. 

 The level of decomposition needed for the requirements depends on the complexity of the system, the level of detail required by the stakeholders, and the level of architecture decomposition that is necessary to specify the system being developed. The BA must take into account the stakeholder perspectives when decomposing the requirements, as different stakeholders may have different needs and expectations for the granularity and clarity of the requirements. The BA must also ensure that the decomposed requirements are consistent, feasible, verifiable, and traceable to the higher-level requirements. References:

• BABOK Guide v3, Section 5.2.3: Decompose Requirements - Guidelines and Tools1
• Step 4: Analyze, Refine & Decompose Requirements - AcqNotes2
• MDRE: Developer Derived/Decomposed Requirements | SpringerLink3
• Requirements Decomposition - ArgonDigital | Making Technology a …4
• Requirements decomposition - No Magic Product Documentation

A trigger for re-prioritization is an event or a change that affects the relative importance or urgency of the project’s requirements or deliverables1. A new initial public offering (IPO) in the stock market is an example of such an event, as it may create new opportunities or threats for the online stock trading system and its stakeholders. The project team may need to re-prioritize the requirements or deliverables to align with the new market conditions and stakeholder expectations. The other options are not triggers for re-prioritization, but rather project issues or risks that need to be managed or mitigated. References: 1

The BA should trace the requirements to the business needs, because the business needs are the high-level goals or objectives that the organization or stakeholders want to achieve. By tracing the requirements to the business needs, the BA can ensure that the requirements are aligned with the strategic direction and value proposition of the organization or stakeholders, and that they do not conflict with each other or with the business needs. Tracing the requirements to the business needs can also help to prioritize, validate, and verify the requirements, as well as to manage changes and dependencies. Stakeholder tasks, organizational functions, and solution components are not the best options for tracing the requirements, because they are either too specific or too abstract, and they do not directly measure the value or benefit of the requirements. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 5: Requirements Traceability and Monitoring, page 197
• Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 6: Requirements Analysis and Design Definition, section 6.1: Trace Requirements, page 121
• Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 5: Requirements Traceability and Monitoring, page 197

A BA should identify any potential constraints that may affect the requirements or the solution and communicate them to the relevant stakeholders for resolution. In this case, the policies are a constraint that may prevent the implementation of the requirement or require a change to the policies. The BA should review the constraint with management and seek their guidance on how to proceed. The BA should not modify the policies or the requirements without proper approval or justification. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 5: Requirements Analysis and Design Definition, page 214
• Business Analysis Body of Knowledge (BABOK ®) Guide, Version 3, Section 5.2: Analyze Current State, page 112
• Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 3: Requirements Analysis and Design Definition, Week 2: Analyze Current State, video: “Identify Constraints”

The stakeholders that were missed in the requirements are the end users. End users are the people who will use the solution or be affected by its outcomes. They are a key source of requirements, as they can provide valuable insights into the needs, expectations, preferences, and pain points of the solution. The BA should elicit requirements from the end users, as well as validate and verify them with their feedback. The BA should also ensure that the end users are involved throughout the project lifecycle, from planning to testing to implementation. The other options are not the stakeholders that were missed, as they are either not directly related to the solution or not the primary source of requirements. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 2: Business Analysis Key Concepts, Section 2.3: Stakeholders, p. 59-60
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 2: Business Analysis Key Concepts, Section 2.3: Stakeholders, p. 28-29
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 4: Elicitation and Collaboration, Section 4.1: Prepare for Elicitation, p. 97-98

An elicitation activity plan is a technique that helps to plan and prepare the activities and tasks that are required to elicit the information and requirements from the stakeholders. An elicitation activity plan defines the objectives, scope, approach, methods, techniques, tools, resources, schedule, and deliverables of the elicitation process. An elicitation activity plan can help the BA to create an output of the initial meeting with experts, as it can help to identify the stakeholders, their roles and responsibilities, their information and communication needs, their availability and preferences, and their expectations and constraints. An elicitation activity plan can also help the BA to select the most appropriate and effective elicitation techniques, such as interviews, workshops, observation, or document analysis, to obtain the relevant and reliable information and requirements from the experts. An entity relationship diagram is a technique that helps to represent the data and information needs of an organization or a solution using graphical or textual symbols and relationships. An entity relationship diagram shows the entities that are relevant to the domain, the attributes that describe the entities, and the relationships that exist between the entities. An entity relationship diagram can help the BA to define and analyze the data requirements, but it is not an output of the initial meeting with experts. A current state flowchart is a technique that helps to create a graphical representation of the activities and tasks that are performed to achieve a specific goal or outcome in the current state of the organization or the solution. A current state flowchart shows the sequence and flow of the activities and tasks, the roles and responsibilities of the performers, the inputs and outputs of each activity or task, and the rules and conditions that govern the process. A current state flowchart can help the BA to understand and document the current state of the delivery process, but it is not an output of the initial meeting with experts. An information management approach is a technique that helps to plan and manage the storage, access, distribution, and retention of the information and requirements throughout the project lifecycle. An information management approach defines the format, structure, level of detail, and quality of the information and requirements, the tools and techniques to be used, the roles and responsibilities of the information and requirements owners and users, and the policies and procedures to be followed. An information management approach can help the BA to ensure the consistency, accuracy, completeness, and security of the information and requirements, but it is not an output of the initial meeting with experts. References: BABOK Guide v3, Chapter 10: Techniques, Section 10.12: Elicitation Activity Plan, p. 513-514; Section 10.19: Data Modeling, p. 525-527; Section 10.43: Process Modeling, p. 557-559; Section 10.14: Information Management Approach, p. 516-517.

According to the BABOK® Guide1, the business analysis approach is the set of processes, tools, deliverables, techniques, and standards that will be used to perform business analysis work on a project. The approach can be either plan-driven, adaptive, or a hybrid of both. A plan-driven approach is more suitable for projects that have stable and well-defined requirements, low levels of change, and clear acceptance criteria. An adaptive approach is more suitable for projects that have uncertain or evolving requirements, high levels of change, and emergent outcomes. Therefore, one of the factors that would drive the decision towards an adaptive approach is the organization’s tolerance for uncertainty, which means the degree to which the organization is willing to accept ambiguity and risk in the project. An organization with a high tolerance for uncertainty can benefit from an adaptive approach that allows for frequent feedback, experimentation, and learning. References:

• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 3: Business Analysis Planning and Monitoring, Section 3.2: Plan Business Analysis Approach, p. 57-59
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 3: Business Analysis Planning and Monitoring, Section 3.2: Plan Business Analysis Approach, p. 89-91

 Before meeting with the project sponsor, the BA must ensure that the requirements are atomic, feasible and testable. These are some of the characteristics of good requirements, as defined by the BABOK® Guide1. Atomic means that each requirement is concise and has a single meaning. Feasible means that each requirement can be implemented within the constraints and resources of the project. Testable means that each requirement can be verified and validated using objective criteria. These characteristics help to ensure that the requirements are clear, realistic, and measurable, and that they align with the objective of the project. References:

• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 4: Elicitation and Collaboration, Section 4.5: Confirm Elicitation Results, p. 122-123
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Requirements Analysis and Design Definition, Section 6.2: Specify and Model Requirements, p. 253-254

A communication plan should consider the preferences of the stakeholders, such as how they like to receive information, how often, and in what format. E-mail may not be the best choice for all stakeholders, especially if they prefer face-to-face meetings, phone calls, or other methods of communication. The BA should also consider the impact, urgency, and confidentiality of the information when choosing the communication channel. The business objectives, retention, and presentation materials are not directly related to the stakeholder analysis, but rather to the communication requirements and strategy. References:

• CBAP Handbook, page 6, section 2.4.4
• [BABOK Guide], page 417, section 10.3.2.3

Based on the table in the image, the total cost of upgrading system A with the first 8 features is $3.5 million, which is equal to the budget for the initiative. This option would also allow the company to retain the system that is preferred by the claim processors and has more flexibility to be modified. The other options would either exceed the budget or compromise the functionality and usability of the system. Therefore, upgrading system A with the first 8 features is a feasible solution to make sure the project stays within budget. References:

• IIBA BABOK Guide, Section 10.23, Decision Analysis
• Cost Benefit Analysis: An Expert Guide, Smartsheet
• How to Choose the Right Software Vendor, CIO