CBAP Exam Dumps : Certified Business Analysis Professional

 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.

 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.

The waterfall software development life cycle is a methodology that divides the project into phases, and the project manager focuses on control of time, cost, and scope. The waterfall model is a linear and sequential approach that follows a predefined set of steps from the initiation to the closure of the project. The waterfall model assumes that the requirements, scope, and design of the project are clear and stable, and that each phase can be completed before moving to the next one. The waterfall model helps to ensure that the project deliverables meet the quality standards and specifications, and that the project is completed within the budget and schedule12. The spiral software development life cycle is a methodology that combines the iterative and incremental approach with the risk management and prototyping techniques. The spiral model is a cyclical and evolutionary approach that follows a series of loops or iterations from the planning to the deployment of the project. The spiral model assumes that the requirements, scope, and design of the project are dynamic and complex, and that each iteration can be refined and improved based on the feedback and learning from the previous ones. The spiral model helps to identify and mitigate the risks and uncertainties of the project, and to deliver a functional and adaptable product13. The agile software development life cycle is a methodology that emphasizes the collaboration, communication, and flexibility among the project stakeholders. The agile model is an adaptive and iterative approach that follows a series of short and frequent cycles or sprints from the conception to the delivery of the project. The agile model assumes that the requirements, scope, and design of the project are emergent and changing, and that each sprint can deliver a working and valuable product increment. The agile model helps to respond to the changes and feedback of the project, and to maximize the customer satisfaction and value14. The incremental software development life cycle is a methodology that breaks down the project into smaller and manageable chunks or modules. The incremental model is a progressive and modular approach that follows a series of steps from the analysis to the implementation of each module of the project. The incremental model assumes that the requirements, scope, and design of the project are partially known and defined, and that each module can be developed and delivered independently. The incremental model helps to reduce the complexity and risk of the project, and to provide a gradual and continuous delivery of the product15. References:

CBAP® Handbook

Waterfall Model - iiba.org

Spiral Model - iiba.org

Agile Model - iiba.org

Incremental Model - iiba.org