IIBA Updated CBAP Exam Questions and Answers by azlan

 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 number of communication channels in a project is calculated by the formula:

n(n−1)/2

, where

n

is the number of stakeholders. Therefore, if there are 50 stakeholders in the current project, the number of communication channels is:

50(50−1)/2=1225

Communication channels are the pathways or mediums through which information is exchanged among the stakeholders. The more stakeholders involved in a project, the more communication channels are needed, and the more complex the communication management becomes. References: CBAP / CCBA Certified Business Analysis Study Guide, chapter 6, page 236; CBAP Sample Questions, question 248.

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 elicitation scope defines the boundaries of the elicitation activity and ensures that the BA and the stakeholders focus on the relevant information and avoid unnecessary details or tangential points. The elicitation scope helps the BA to communicate the purpose, objectives, and expected outcomes of the elicitation activity to the stakeholders, and to manage their expectations and participation. The elicitation scope is influenced by the business domain, corporate culture, group dynamics, and expected outputs, as these factors affect the type and level of information that is needed and available for the project. References:

BABOK Guide v3, Section 4.1.1: Prepare for Elicitation - Inputs1

Preparing for elicitation – The Functional BA2

What Is Elicitation: Top Requirement Elicitation Techniques for 20243