Pass the IIBA Certified Business Analysis Professional CBAP Questions and answers with CertsForce

 A work breakdown structure (WBS) is a visual decomposition of the project scope into smaller and manageable components or deliverables. A WBS is a hierarchical representation of the work that needs to be done to complete the project and achieve its objectives. A WBS defines the scope, schedule, cost, and quality of the project, and helps to allocate the resources and assign the responsibilities for the project. A WBS also helps to identify the dependencies, risks, and issues of the project, and to monitor and control the project performance12. A budgeted cost of work scheduled (BCWS) is a measure of the planned value of the project. 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 project, and helps to compare the actual cost and the earned value of the project. A BCWS also helps to identify the cost variance and the cost performance index of the project, and to forecast the cost at completion and the estimate at completion13. A resource breakdown structure (RBS) is a visual decomposition of the resources that are needed to complete the project. An RBS is a hierarchical representation of the human and non-human resources that are required to perform the work packages and activities of the project. An RBS defines the types, categories, and quantities of the resources, and helps to estimate, acquire, and manage the resources for the project. An RBS also helps to identify the availability, utilization, and allocation of the resources, and to optimize the resource efficiency and effectiveness14. A product breakdown structure (PBS) is a visual decomposition of the products that are delivered by the project. A PBS is a hierarchical representation of the components and features that make up the products of the project. A PBS defines the scope, quality, and functionality of the products, and helps to design, develop, and test the products for the project. A PBS also helps to identify the requirements, specifications, and standards of the products, and to verify and validate the products1 . References:

CBAP® Handbook

Work Breakdown Structure - iiba.org

Budgeted Cost of Work Scheduled - iiba.org

Resource Breakdown Structure - iiba.org

[Product Breakdown Structure - iiba.org]

An activity network diagram is a method of displaying the timelines of all the various subtasks that are involved in any project. It shows the sequence and dependencies of the subtasks, as well as their durations and start and finish times. An activity network diagram can help to identify the critical path, which is the longest path of subtasks that determines the minimum time required to complete the project. An activity network diagram can also help to monitor and control the project progress, identify and manage risks, and optimize the use of resources. References:

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

Critical Path Mapping with Activity Network Diagrams

How To Create a Project Timeline in 8 Easy Steps, under Step 4: Choose a project timeline format

 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

Millstones are timeless events that show progress in the project. Millstones are significant points or achievements in the project lifecycle that indicate the completion of a major deliverable, phase, or stage. Millstones are typically achieved at the end of each phase in the project lifecycle, such as initiation, planning, execution, monitoring and control, and closure. Millstones help to measure and communicate the project status, performance, and results, and to ensure the alignment and satisfaction of the project stakeholders12. Achievements are the outcomes or results of the project that fulfill the project objectives and deliver value to the project stakeholders. Achievements are not necessarily timeless events that show progress in the project, as they may occur at any point in the project lifecycle, depending on the nature and scope of the project. Achievements help to evaluate and demonstrate the project success, quality, and benefits, and to justify the project investment and resources34. Phases are the stages or segments of the project lifecycle that divide the project into manageable and logical units. Phases are not timeless events that show progress in the project, as they are the periods of time during which the project activities and tasks are performed and the project deliverables are produced. Phases help to organize and structure the project work, scope, and schedule, and to apply the appropriate methods, tools, and techniques for each phase1 . Templates are the standardized documents or formats that are used to plan, execute, and control the project. Templates are not timeless events that show progress in the project, as they are the tools or aids that facilitate the project management processes and practices. Templates help to ensure the consistency, completeness, and quality of the project documentation, communication, and reporting1 . References:

CBAP® Handbook

Millstone - iiba.org

Achievement - iiba.org

Project Success - iiba.org

[Phase - iiba.org]

[Template - iiba.org]

 The BA is facing a situation where the stakeholders are not cooperating or engaged in the business analysis activities. To resolve this issue, the BA needs to use the competencies of negotiation, conflict resolution, and effective communication. Negotiation is the ability to reach an agreement that is acceptable to all parties involved. Conflict resolution is the ability to manage and resolve disagreements or disputes among stakeholders. Effective communication is the ability to convey information clearly and accurately, and to listen and respond appropriately to the needs and concerns of others. These competencies will help the BA to understand the root causes of the stakeholders’ resistance, address their expectations and interests, and persuade them to participate and collaborate in the business analysis process. References: CBAP Competencies, CBAP Handbook, CBAP Study Guide

 Lessons learned is a technique that involves identifying and documenting the successes, failures, and best practices of a project or initiative, and using them to improve the performance and quality of future work. Lessons learned can help the manager to help the BAs develop their skills and address the corrective actions, because it can provide feedback, insights, and recommendations on how to enhance the business analysis processes, methods, and competencies. Lessons learned can also help to identify the gaps, issues, and opportunities for improvement, and to plan and implement the necessary actions to resolve them. Team restructure, weekly meetings, or team building are not the best options for achieving this goal, because they are either too general, too specific, or not directly related to the business analysis skills and corrective actions. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 8: Solution Evaluation, page 348

Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 8: Solution Evaluation, section 8.5: Assess Enterprise Limitations, page 159

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 348

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?

The marketing department (AAC) is a key stakeholder for launching an existing product in another channel, as they are responsible for defining the requirements, confirming the elicitation results, and validating the solution. Therefore, they have a high influence on the project, as they can affect the decisions and outcomes of the project. They also have a high impact from the project, as they will be directly affected by the changes and benefits of the new channel. According to the stakeholder analysis technique, influence and impact are two dimensions that can be used to categorize and prioritize stakeholders12. A stakeholder with high influence and high impact is considered a primary stakeholder, who should be actively involved and engaged throughout the project

 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.

A resource breakdown structure (RBS) is a type of chart that shows which resources are needed in the project and allows you to group the resources by project phase or other attributes. A resource is anything that is required to perform the project activities, such as human resources, equipment, materials, facilities, etc. A RBS is a hierarchical representation of the resources, where each level represents a category or a subcategory of resources. A RBS helps to plan, allocate, monitor, and control the resources for the project. A RBS also helps to identify the dependencies and constraints among the resources, as well as the potential risks and opportunities related to the resources. References: CBAP / CCBA Certified Business Analysis Study Guide, chapter 6, page 237; CBAP Sample Questions, question 237.