Certified Business Analysis Professional CBAP Release Date

 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

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

The BA can alleviate the concerns of the stakeholders in domain 2 by presenting a model applicable for them. A model is a representation of a concept or system that is used to communicate, analyze, or design. A model can help the BA to convey complex or abstract information in a clear and concise way, using the appropriate level of detail, notation, and terminology for the audience. A model can also help the BA to elicit feedback, validate understanding, and resolve issues or conflicts. A survey, an estimation, or a backlog are not the best options to alleviate the concerns of the stakeholders in domain 2, because they are either too general, too specific, or too technical, and they do not address the root cause of the problem, which is the lack of clarity and relevance of the presentation. 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

 A baseline schedule is derived from a schedule model to meet the project execution plan and achieve management approval for use as a baseline. A schedule model is a representation of the project activities, durations, dependencies, and resources that shows how the project will be executed over time. A baseline schedule is a specific version of the schedule model that is approved and frozen as a reference point for measuring and controlling the project progress and performance. A baseline schedule reflects the agreed-upon scope, cost, and schedule of the project and serves as a basis for comparison and change management. References: CBAP / CCBA Certified Business Analysis Study Guide, chapter 6, page 234; CBAP Sample Questions, question 252.