CBAP Exam Dumps - Certified Business Analysis Professional

 This question is based on a case study that compares two scenarios for Company C, a software development firm. In Scenario 1, Company C uses a traditional waterfall approach to develop a software product for a client. In Scenario 2, Company C uses an agile approach to develop the same product. The question asks for the increased cost in Scenario 2, which is the difference between the total cost of Scenario 2 and the total cost of Scenario 1. According to the case study, the total cost of Scenario 1 is $1,236,210 and the total cost of Scenario 2 is $1,444,000. Therefore, the increased cost in Scenario 2 is $1,444,000 - $1,236,210 = $207,790. References: The case study is available in the CBAP® Exam Sample Questions and Exam Blueprint document1. The answer is also verified by the CBAP® Exam Answer Key document2. Both documents are accessible from the IIBA® website3.

 A purchase solution approach is one that involves acquiring a COTS software package from an external vendor or provider, rather than developing a custom solution in-house. A purchase solution approach can offer several benefits, such as faster delivery, lower cost, higher quality, and reduced risk. However, a purchase solution approach also has some drawbacks, such as limited customization, dependency on the vendor, compatibility issues, and licensing fees. A BA should evaluate the pros and cons of a purchase solution approach against the business needs and requirements, and compare it with other possible solution approaches, such as outsource, exploit, or create. References:

Evaluating Candidate COTS Packages, ArgonDigital

Seven Insights: Agile and Custom Off The Shelf (COTS) packaged software, Kenny & Company

COTS Software Procurement Methodology, IGI Global

The waterfall model is a linear and sequential process model that needs to complete each set of tasks in one phase before moving into the next phase in a project development life cycle. The phases are typically requirements, design, implementation, verification, and maintenance. The waterfall model is suitable for projects with well-defined and stable requirements, clear objectives, and minimal risks of changes. References:

Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 1, Week 2, Video: “Waterfall Model”

CERTIFIED BUSINESS ANALYSIS PROFESSIONAL, Page 9, Section: “Review the Exam Blueprint”

 Videoconferencing is a communication technique that allows business analysts to interact with stakeholders who are not collocated. It enables real-time audio and visual communication, which can facilitate collaboration, feedback, and decision making. Videoconferencing can also help build rapport and trust among stakeholders, as well as reduce travel costs and time. Videoconferencing is one of the many communication techniques that business analysts can use to elicit information and collaborate with stakeholders in different geographical locations1234. References: 1: How to create a business analysis communication plan - Lucidchart 2: Business Analysis Techniques: Eliciting Information and Collaborating with Stakeholders 3: Key sets of BA: analysis and communication techniques - Exposit 4: Communication strategy for stakeholder engagement – SustaiNet

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

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

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

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

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

 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.

Creative thinking is a type of analytical thinking that involves generating new ideas and innovative concepts to approach problems, solve problems, and generate alternative solutions. Creative thinking helps the business analyst to find novel and original ways to address the needs and expectations of the stakeholders, overcome the challenges and constraints of the project, and add value to the solution. Creative thinking also helps the business analyst to explore different perspectives, challenge assumptions, and experiment with different possibilities. The other options are not types of analytical thinking, but rather techniques or skills that can be used to enhance creative thinking. Lateral thinking is a technique that involves using logic and reasoning to find unconventional or unexpected solutions. Brainstorming is a technique that involves generating a large number of ideas in a group setting. Decision making is a skill that involves choosing the best option among several alternatives based on criteria and evidence. References:

9.1 Analytical Thinking and Problem Solving, paragraph 1

Top 11 Most Effective Business Analysis Techniques | 2024, paragraph 2

6 business analysis techniques to use in your strategic plans, paragraph 2

What is analytical thinking ? – The Functional BA, paragraph 2

Business Analysis Blog | Systems Thinking – An Analyst’s Essential …, paragraph 2

 A fishbone diagram, also known as an Ishikawa diagram or a cause-and-effect diagram, is a tool that can be used in root cause analysis. It helps to identify, explore, and display the possible causes of a specific problem or quality issue. A fishbone diagram has a main branch that represents the problem, and several sub-branches that represent the categories of causes. Each category can have further sub-causes that are linked to the main causes. The diagram resembles the skeleton of a fish, hence the name. A fishbone diagram can help to organize and analyze the causes of a problem, and to find the root cause that needs to be addressed. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, page 47

Root Cause Analysis: Definition, Examples & Methods | Tableau, under Approaches to Root Cause Analysis

What is Root Cause Analysis (RCA)? | ASQ, under Approaches to Root Cause Analysis