[IIBA] CCBA - Capability in Business Analysis Exam Dumps & Study Guide

Free [IIBA] CCBA - Capability in Business Analysis Practice Questions Preview

• Question 1

  You are currently working on creating the activity list for an initiative in your organization. What characteristic must be assigned to each task in your task list?
  

  • A. Procurement needs
  • B. Risk level
  • C. Unique number
  • D. Roles and responsibilities

  Correct Answer: Answer: B is incorrect. The risk level is not associated with the task list.

  Explanation:

  The AI assistant recommends Answer D.
  
  Reasoning for choosing Answer D:
  When creating an activity list for a business analysis initiative, it is crucial to assign Roles and responsibilities to each task. This practice is fundamental for effective planning, execution, and monitoring of business analysis activities. The BABOK Guide, particularly within the "Business Analysis Planning and Monitoring" Knowledge Area (Chapter 3), emphasizes the importance of defining and allocating responsibilities. Assigning clear roles and responsibilities for each task ensures that:
  

  • There is clarity regarding who is accountable for performing, reviewing, and approving each specific task.
  • Confusion is minimized, preventing tasks from being overlooked or duplicated.
  • Stakeholders are appropriately involved in the relevant activities, fostering collaboration and ensuring that the right expertise is applied.
  • Overall accountability is improved, leading to more efficient and effective execution of the business analysis work.

  This aligns perfectly with the discussion summary's conclusion, which highlighted that assigning roles and responsibilities is consistent with the BABOK Guide's principles for smooth execution and improved accountability.
  
  Reasoning for not choosing other answers:
  

  • A. Procurement needs: While procurement may be a task within a larger initiative, "procurement needs" is not a universal characteristic that *must* be assigned to *each* task in a general activity list. Most business analysis tasks do not involve procurement as a direct characteristic for their definition.
  • B. Risk level: While identifying and managing risks is vital to any project or initiative, assigning a specific "risk level" to *each individual task* in a granular activity list is not a universally mandated characteristic. Risk assessments are typically done at a higher level (e.g., for the project, specific deliverables, or major phases) rather than as a mandatory attribute for every single detailed task. The original "Suggested Answer" within the question content also correctly identified B as incorrect.
  • C. Unique number: While assigning a unique number or identifier to each task is an excellent practice for tracking, sequencing, and referencing tasks, it is primarily an *identification mechanism* rather than a substantive *characteristic* of the task's content or execution requirement. The question asks what characteristic *must be assigned* to define the task for its successful completion and management in a business analysis context. Roles and responsibilities directly address the "who" and accountability aspects essential for task execution, which is a more fundamental characteristic from a BABOK perspective than merely a numerical ID. The discussion also noted a lack of supporting reasoning for choosing C.

  Citations

  • International Institute of Business Analysis (IIBA) - BABOK Guide V3.0
    https://www.iiba.org/standards-and-resources/babok/

• Question 2

  Shelly is the business analyst for her organization and she's working with Thomas to review the business requirements. They are discussing the identified requirements, how the requirements will transition to the operations, and the longevity of the solution. Thomas is concerned that the identified requirements may not map to the desired future state of the organization. What business analysis task is Shelly facilitating in this scenario?
  

  • A. Acceptance evaluation criteria definition
  • B. Requirements quality assurance
  • C. Validate requirements
  • D. Stakeholder management

  Correct Answer: C

  Explanation:

  The AI assistant agrees with the suggested answer, C: Validate requirements.
  
  Reason for choosing this answer:
  The scenario describes Shelly and Thomas reviewing business requirements, discussing their transition to operations, longevity, and critically, Thomas's concern that "the identified requirements may not map to the desired future state of the organization." This directly aligns with the purpose of the Business Analysis task "Validate Requirements" as defined in the BABOK® Guide.
  
  According to the BABOK® Guide v3, "Validate Requirements" (Task 7.4 within the Requirements Analysis and Design Definition Knowledge Area) is performed to ensure that all requirements and designs align to the business requirements and support the delivery of value. A key aspect of this task is to confirm that requirements support the achievement of business objectives and align with the desired future state of the organization. Thomas's concern about the requirements mapping to the desired future state precisely reflects the core objective of validating requirements. The discussion about the transition to operations and longevity also falls under validation, as it considers the overall fit and long-term viability of the solution derived from these requirements.
  
  Reasons for not choosing the other answers:
  

  • A. Acceptance evaluation criteria definition: While related to ensuring a solution meets needs, this task (BABOK® Guide v3, Task 8.1.5: Define Acceptance Criteria) focuses on defining the standards and conditions that must be met for a solution to be accepted by stakeholders. In the given scenario, the focus is on assessing the requirements themselves against the future state, not yet defining the criteria for the solution's acceptance.
  • B. Requirements quality assurance: This task, often referred to as "Verify Requirements" (BABOK® Guide v3, Task 7.2.5), focuses on ensuring that requirements are well-formed. This includes checking for characteristics like clarity, completeness, consistency, feasibility, and atomicity. While important for overall quality, Thomas's specific concern is about the strategic alignment and mapping to the future state, which goes beyond mere quality attributes to the strategic fit and value delivery—the domain of validation.
  • D. Stakeholder management: This is a broad knowledge area (BABOK® Guide v3, Chapter 3) that encompasses identifying, analyzing, and engaging with stakeholders. While Thomas is a stakeholder, and Shelly is engaging with him, the specific activity described—reviewing and discussing the *content* of requirements in relation to business objectives and future state—is a specific requirements analysis task, not just a general stakeholder management activity. The scenario describes a specific activity involving requirements, not just how to manage stakeholder expectations or communication.

  
  Citations:

  • A Guide to the Business Analysis Body of Knowledge (BABOK® Guide) v3, International Institute of Business Analysis (IIBA)
  • https://www.iiba.org/standards-and-resources/babok/

• Question 3

  Which of the following are documented approaches to the business analysis work? Each correct answer represents a complete solution.
  

  • A. Deming's Quality Circle
  • B. Lean
  • C. Six Sigma
  • D. Waterfall approach

  Correct Answer: Answer: A is incorrect. Deming's Quality Circle describes the quality management approach of plan, do, check, and act. This isn't a business analysis approach.

  Explanation:

  The AI assistant agrees with the suggested answer, which identifies B (Lean), C (Six Sigma), and D (Waterfall approach) as documented approaches to business analysis work.
  
  Reason for choosing Lean (B), Six Sigma (C), and Waterfall approach (D):
  These three are widely recognized and documented approaches or methodologies that heavily involve business analysis activities.

  • Lean: Lean principles focus on maximizing customer value while minimizing waste. Business analysts apply Lean thinking to identify and eliminate non-value-added activities in processes, improve efficiency, and streamline workflows. This is a fundamental aspect of process analysis and improvement within the scope of business analysis. The BABOK® Guide v3 often references Lean principles as relevant to various knowledge areas, including Strategy Analysis, Requirements Analysis and Design, and Solution Evaluation.
  • Six Sigma: Six Sigma is a data-driven methodology used to eliminate defects and improve processes. Business analysts frequently participate in or lead Six Sigma projects, utilizing its structured phases (e.g., DMAIC - Define, Measure, Analyze, Improve, Control) to rigorously analyze problems, gather data, identify root causes, and design effective solutions. Its focus on process capability, quality, and variation reduction directly aligns with business analysis objectives for improving business performance.
  • Waterfall Approach: The Waterfall approach is a traditional, predictive project management methodology characterized by sequential phases (e.g., Requirements, Design, Implementation, Verification, Maintenance). Business analysis is a critical component of the early phases, particularly the "Requirements" phase, where detailed requirements elicitation, analysis, documentation, and validation are performed. While it's a project lifecycle approach, it significantly dictates how business analysis activities are structured, managed, and executed within a project context. Therefore, it is a documented approach *to* how business analysis work is performed within a specific project management paradigm.
  
  The discussion content incorrectly states that the conclusion is only 'D. Waterfall approach' despite claiming to agree with the suggested answer of B, C, and D. It also misinterprets the question by suggesting it implicitly asks for an option that is *not* a process analysis and improvement method. The question explicitly asks what *are* documented approaches to business analysis work, and all three (Lean, Six Sigma, Waterfall) fit this description from different perspectives (process improvement frameworks, and a project lifecycle methodology guiding BA activities).
  
  Reason for not choosing Deming's Quality Circle (A):
  Deming's Quality Circle, while related to quality improvement and involving analysis, is primarily a specific quality management technique or a participative management structure where small groups of employees identify and solve workplace problems. It is a valuable tool, but it is not considered a broad "approach to business analysis work" in the same overarching sense as Lean, Six Sigma, or the Waterfall project methodology that frames significant business analysis efforts. It is more of a technique or a team-based problem-solving mechanism within a larger quality management or continuous improvement program, rather than a comprehensive methodology for performing business analysis across its various knowledge areas.

  
  

  Citations:

  • A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) v3.0, IIBA.
  • Lean Software Development - Wikipedia, https://en.wikipedia.org/wiki/Lean_software_development
  • Six Sigma - Wikipedia, https://en.wikipedia.org/wiki/Six_Sigma
  • Waterfall model - Wikipedia, https://en.wikipedia.org/wiki/Waterfall_model
  • Quality circle - Wikipedia, https://en.wikipedia.org/wiki/Quality_circle

• Question 4

  You are the business analyst for your organization and working with the stakeholders to prioritize the requirements. The stakeholders are concerned about the financial impact of the requirements should some of them fail during the implementation. You would like to rank the risk tolerance of the stakeholders based on their comments about the solution and the requirements. The following are the three categories of risk tolerance associated with the stakeholders except for which one?
  

  • A. Neutrality
  • B. Mitigation
  • C. Risk-seeking
  • D. Risk-aversion

  Correct Answer: B

  Explanation:

  The AI assistant agrees with the suggested answer, B. Mitigation.
  
  Reason for choosing this answer:
  The question asks to identify the option that is *not* a category of risk tolerance associated with stakeholders when prioritizing requirements. In business analysis, particularly as described in the BABOK® Guide, stakeholders exhibit different levels of inherent risk tolerance. These categories define how stakeholders perceive and react to uncertainty and potential losses or gains.
  
  The commonly recognized categories of stakeholder risk tolerance are:

  • Risk-Aversion: Stakeholders prefer to avoid risk and often choose options with lower uncertainty, even if potential returns are also lower.
  • Risk-Seeking: Stakeholders are willing to accept higher levels of risk for the potential of greater rewards.
  • Risk-Neutrality (or Neutrality): Stakeholders are indifferent to risk and make decisions based purely on expected value, without factoring in their personal comfort with risk.

  Mitigation, on the other hand, is not a category describing how stakeholders tolerate risk. Instead, it is a risk response strategy. Risk mitigation involves taking actions to reduce the probability of a risk occurring or to lessen its impact if it does occur. For example, implementing a robust testing strategy or developing contingency plans are forms of risk mitigation. Since the question specifically asks for the option that is *not* a category of risk tolerance, B. Mitigation is the correct choice as it describes an action rather than a characteristic of tolerance.
  
  Reason for not choosing the other answers:
  The other options represent actual categories of stakeholder risk tolerance:

  • A. Neutrality: This refers to being risk-neutral, a recognized category of risk tolerance where decisions are based purely on expected value, with no preference for or aversion to risk.
  • C. Risk-seeking: This is a recognized category of risk tolerance, where stakeholders are inclined to take on higher risks for the possibility of greater rewards.
  • D. Risk-aversion: This is a recognized category of risk tolerance, where stakeholders prefer lower risk and certainty, even if it means foregoing potentially higher returns.

  All three (Neutrality, Risk-seeking, and Risk-aversion) describe how stakeholders inherently perceive and react to risk, making them valid categories of risk tolerance discussed in business analysis practices, particularly in the context of prioritizing requirements based on associated risks.
  
  

  Citations:

  • A Guide to the Business Analysis Body of Knowledge (BABOK® Guide) v3, Chapter 5: Requirements Life Cycle Management, Task 5.2: Prioritize Requirements (discusses risk as a prioritization criterion and stakeholder risk tolerance).
    https://www.iiba.org/standards-and-resources/babok/

• Question 5

  Tracy is a business analyst for her organization and she's gathered and identified the needed requirements for the solution scope. What must Tracy do before she can begin managing the requirements? Choose the best answer.
  

  • A. Tracy must decompose the requirements in WBS.
  • B. Tracy must create cost-benefits analysis of each requirement to manage the benefits first.
  • C. Tracy must identify roles, responsibilities, and owners of the requirements to fully manage the requirements.
  • D. Tracy must communicate the requirements to the stakeholders for their consent and approval.

  Correct Answer: D

  Explanation:

  The AI assistant agrees with the suggested answer, which is D.

  The reason for choosing option D, "Tracy must communicate the requirements to the stakeholders for their consent and approval," is that it represents a crucial prerequisite before commencing comprehensive requirements management activities.
  Before requirements can be effectively managed—which includes tasks such as prioritization, traceability, change management, and eventual implementation—they must first gain formal review, agreement, and approval from the relevant stakeholders. This step ensures that the gathered requirements accurately reflect the business needs and objectives, are complete, clear, and acceptable to those who will use or be impacted by the solution. Obtaining stakeholder consent and approval establishes a baseline for the requirements, providing the necessary authority and commitment to proceed. Without this approval, any subsequent management activities lack a ratified foundation, risking rework, misdirection, and project delays. This principle is directly aligned with the Requirements Life Cycle Management knowledge area of the BABOK® Guide, specifically the 'Approve Requirements' task, which emphasizes the necessity of obtaining stakeholder agreement and formal approval as a critical step in the requirements lifecycle.
  
  The reasons for not choosing the other options are as follows:

  • Option A, "Tracy must decompose the requirements in WBS," is incorrect. While decomposing requirements (e.g., using a Work Breakdown Structure or other methods) is an important part of requirements analysis and definition, it is typically done to refine and organize requirements for implementation. Formal approval of the requirements, or at least the scope, is generally a prerequisite before committing to a detailed decomposition for execution. Decomposition helps in *understanding* and *organizing* requirements, but approval grants them legitimacy for *management* and *development*.
  • Option B, "Tracy must create cost-benefits analysis of each requirement to manage the benefits first," is incorrect. Cost-benefit analysis is an evaluation technique used for justifying and prioritizing requirements or solutions, often performed *after* requirements have been initially understood and captured. It informs decisions about which requirements to pursue or how to prioritize them, rather than being a universal initial step *before* managing the requirements themselves. Managing benefits is a continuous process throughout the solution lifecycle, but it doesn't preclude the initial approval of the requirements baseline.
  • Option C, "Tracy must identify roles, responsibilities, and owners of the requirements to fully manage the requirements," is incorrect. Identifying roles and responsibilities is indeed essential for effective requirements management and is typically part of planning the requirements management approach. However, defining *who* manages the requirements (roles) and *how* they are managed (responsibilities) is a procedural step that often comes concurrently with or slightly after ensuring that the requirements themselves are approved and ready to be managed. The fundamental action that enables all subsequent management activities concerning the *content* of the requirements is stakeholder agreement and approval on those requirements.

  Citations:

  • International Institute of Business Analysis (IIBA) - BABOK® Guide v3.0, https://www.iiba.org/standards-and-resources/babok-guide/

• Question 6

  Ben is the business analyst for his organization. Ben is currently working on a solution to improve a laser printer. He has taken the laser printer apart, identified each component, and documented each component's purpose. What type of requirements organization is Ben doing in this scenario?
  

  • A. Functional decomposition
  • B. Process modeling
  • C. Scope modeling
  • D. Data modeling

  Correct Answer: A

  Explanation:

  The AI assistant agrees with the suggested answer A. Functional decomposition.
  
  Reason for choosing A. Functional decomposition: The scenario describes Ben taking a laser printer apart, identifying each component, and documenting each component's purpose. This activity perfectly aligns with the definition of functional decomposition. Functional decomposition is a requirements organization technique used to break down a system, process, or solution into its constituent parts to understand how each part contributes to the overall functionality. By identifying individual components and their purposes, Ben is essentially dissecting the system's functionality into smaller, more manageable pieces, which is the core principle of functional decomposition.
  
  Reasons for not choosing the other answers:

  • B. Process modeling: Process modeling focuses on representing the flow of activities, tasks, and events within a process. It describes *how* something is done, often using techniques like swimlanes, flowcharts, or Business Process Model and Notation (BPMN). Ben's activity of identifying components and their individual purposes is not about the sequence of operations or the flow of work, but rather about the structural breakdown and individual functions of parts.
  • C. Scope modeling: Scope modeling defines the boundaries of the solution, system, or project. It helps to clarify what is included within the scope and what is excluded. While understanding components can contribute to defining scope, Ben's primary activity described (disassembling and documenting individual components and their purposes) is a deeper dive into the internal structure and functionality, rather than merely setting boundaries or defining the high-level extent of the solution. Techniques like context diagrams or feature trees are more typical for scope modeling.
  • D. Data modeling: Data modeling is concerned with organizing and structuring data elements and their relationships within a system. It involves identifying entities, attributes, and relationships to represent information. Ben is analyzing physical components and their operational functions, not the data they process or store, nor the relationships between data elements.

  Citations:

  • A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3.0, International Institute of Business Analysis (IIBA)
  • https://www.iiba.org/standards-and-resources/babok/

• Question 7

  You are the business analyst for your organization and you're working with Fran on business analysis processes. Fran is a stakeholder who wants to ensure that your business analysis approach and activities are compatible with the project activities. Of the following, what type of business analysis stakeholder is Fran?
  

  • A. Regulator
  • B. Project manager
  • C. Sponsor
  • D. Domain subject matter expert

  Correct Answer: B

  Explanation:

  The AI assistant agrees with the suggested answer B. Project Manager.

  The reason for choosing this answer is that Fran's objective – to ensure business analysis approaches and activities are compatible with project activities – precisely aligns with the core responsibilities of a Project Manager. The Project Manager is explicitly accountable for the overall planning, execution, and closing of a project, which includes integrating all project components and ensuring that various work streams, such as business analysis, are synchronized with the project's timeline, budget, and scope. They serve as the primary liaison between the business analysis team and other project stakeholders, facilitating communication and ensuring alignment.
  
  As per the BABOK® Guide, the Project Manager is a key stakeholder who is responsible for managing the project work and for achieving the project objectives. This involves coordinating business analysis activities with the overall project plan, managing dependencies, and ensuring that the business analysis scope and schedule are integrated effectively into the project. Fran's concern about compatibility directly reflects this responsibility.

  The reasons for not choosing the other answers are as follows:
  

  • A. Regulator: Regulators are stakeholders who define and enforce standards or rules that a project or solution must comply with. While they are crucial for legal and ethical compliance, their primary role is not to ensure the compatibility of business analysis processes with project activities. Their focus is on adherence to external guidelines, not internal project workflow integration.
  • C. Sponsor: The Sponsor is the individual or group who provides the financial resources, in-kind support, or both for the project. They are primarily responsible for the project's overall success, providing direction, and ensuring the project delivers business value. While interested in the project's smooth operation, they typically delegate the detailed operational compatibility of business analysis activities with project activities to the Project Manager.
  • D. Domain subject matter expert (SME): A Domain Subject Matter Expert is any person with in-depth knowledge of a topic relevant to the business need or solution scope. Their role is to provide expertise on the business domain, processes, or systems. They are concerned with the 'what' of the solution (the functional and non-functional requirements) rather than the 'how' the business analysis process integrates with the project management process.

  Citations:
  

  • BABOK® Guide (A Guide to the Business Analysis Body of Knowledge®), International Institute of Business Analysis (IIBA®)
    https://www.iiba.org/standards-and-resources/babok/

• Question 8

  You are a business analyst for your organization and you're working with Mary. Mary wants to know what you need to complete the process of planning the business analysis approach if you're already the business analyst for your organization. Which of the following statements is true regarding the plan business analysis approach?
  

  • A. The plan business analysis approach describes the amount of budget needed for the requirements elicitation.
  • B. The plan business analysis approach is required to select an approach that will perform business analysis.
  • C. The plan business analysis approach describes the processes the business analyst will or will not do, based on the time and budget available.
  • D. The plan business analysis approach describes the amount of time needed for the business analysis approach.

  Correct Answer: B

  Explanation:

  The AI assistant agrees with the suggested answer, which is B.

  Reasoning for choosing this answer (B):
  The task "Plan Business Analysis Approach" is a foundational activity within the Business Analysis Planning and Monitoring Knowledge Area, as defined in the BABOK® Guide. Its primary purpose is to define the methodology, techniques, and activities that will be used to perform business analysis for a given initiative. This involves selecting an appropriate approach (e.g., predictive, adaptive, or hybrid) that aligns with the project context, organizational standards, and stakeholder needs. By selecting an approach, the business analyst ensures consistency and effectiveness in subsequent business analysis activities. Therefore, stating that the plan is "required to select an approach that will perform business analysis" is entirely accurate and captures the core essence of this planning task.

  Reasoning for not choosing other answers:
  

  • A. The plan business analysis approach describes the amount of budget needed for the requirements elicitation.
    While budget is a critical consideration in overall project planning, the "Plan Business Analysis Approach" primarily focuses on *how* business analysis will be performed, not the specific budget allocation for individual activities like requirements elicitation. Budget estimation for business analysis activities is a subsequent or concurrent step (often part of overall project resource planning or a more detailed activity planning), influenced by the chosen approach, but it is not the direct output described by this specific planning task itself.
  • C. The plan business analysis approach describes the processes the business analyst will or will not do, based on the time and budget available.
    This statement is partially misleading. The "Plan Business Analysis Approach" defines *which* business analysis activities and techniques *will* be performed and *how*. While time and budget are significant constraints that influence the selection of the approach and techniques, the plan is not merely a list of what the business analyst *will not* do. It proactively defines the chosen processes, methods, and deliverables to achieve the initiative's objectives effectively within given constraints, rather than just listing exclusions.
  • D. The plan business analysis approach describes the amount of time needed for the business analysis approach.
    Similar to option A, this statement misrepresents the primary purpose. The "Plan Business Analysis Approach" defines the *methodology* and *activities*. Estimating the *amount of time* (effort estimation) required for these activities is a subsequent step, typically covered in "Plan Business Analysis Activities" or broader project planning, once the approach has been defined. The approach influences the time estimates, but it does not *describe the amount of time needed* as its direct output.

  Citations:

  • A Guide to the Business Analysis Body of Knowledge (BABOK® Guide) v3, Chapter 3: Business Analysis Planning and Monitoring, Task 3.1: Plan Business Analysis Approach, https://www.iiba.org/standards-and-resources/babok/
  • CCBA Certification FAQs, https://www.iiba.org/certification/iiba-certifications/ccba/ccba-faqs/

• Question 9

  You are the business analyst for a large software development project. There are several issues that must be resolved by certain dates or the problem will prevent the project from advancing. What technique can you use to track problems with the requirements?
  

  • A. Issue tracking
  • B. RTM
  • C. Problem tracking
  • D. Baselining

  Correct Answer: Answer: D is incorrect. Baselining the requirements does not track problems but creates a standard set of requirements that deliverables may be compared

  Explanation:

  The AI assistant agrees with the suggested answer. The recommended technique is Problem tracking (Option C).

  
  

  Reasoning for choosing this answer:
  The question describes a scenario where issues with requirements must be resolved by certain dates to prevent project advancement. Problem tracking, also referred to as Item Tracking in the BABOK® Guide, is a business analysis technique specifically designed to identify, record, track, and manage all issues, concerns, and problems that arise during business analysis activities, including those related to requirements. It provides an organized approach to ensure these issues are addressed and resolved in a timely manner.
  
  According to the BABOK® Guide v3, under Technique 10.26: Item Tracking, this technique involves capturing and assigning responsibility for issues and concerns, prioritizing them, and ensuring their timely resolution to prevent project delays. This directly aligns with the need to track and resolve problems by specific deadlines to ensure the project can advance. It enables the business analyst to maintain control over the resolution process, ensuring that critical impediments to the project's progress are systematically addressed.

  
  

  Reasoning for not choosing the other answers:
  

  • A. Issue tracking: While conceptually similar and often used interchangeably with problem tracking, "Problem tracking" is explicitly stated and detailed as the correct answer in the provided context and aligns directly with the BABOK's "Item Tracking" which covers problems, defects, and issues. Therefore, "Problem tracking" is the more precise choice given the options.
  • B. RTM (Requirements Traceability Matrix): A Requirements Traceability Matrix is used to trace requirements throughout the project lifecycle, linking them to other related artifacts such as design components, test cases, or business objectives. Its primary purpose is to ensure that all requirements are covered, to manage changes, and to assess the impact of changes. However, an RTM does not directly function as a tool for actively managing and resolving issues or problems with the requirements themselves by specific deadlines. While it can help identify *which* requirements are affected by a problem, it does not provide the mechanism for tracking and resolving the problem itself.
  • D. Baselining: Baselining involves creating a stable, approved version of requirements or other project artifacts. Once baselined, changes to these artifacts typically require a formal change control process. While crucial for managing scope and controlling changes, baselining is not a technique for tracking or resolving ongoing problems or issues. It establishes a fixed point of reference, rather than a dynamic system for managing open issues that need resolution.

  
  Citations:

  • IIBA BABOK Guide Version 3.0, Chapter 5: Requirements Life Cycle Management – Maintain Requirements, Technique 10.26: Item Tracking.
  • https://www.iiba.org/standards-and-resources/babok/

• Question 10

  Which one of the following statements is most true about changing requirements in a change-driven approach to business analysis and requirements management?
  

  • A. Change-driven approaches must use a change control system with a change control board.
  • B. Change-driven approaches only use a change control system for approved changes.
  • C. Change-driven approaches don't use a formal change control process.
  • D. Change-driven approaches are driven by change control processes.

  Correct Answer: C

  Explanation:

  The AI assistant agrees with the suggested answer C.
  
  Reason for choosing C:
  The statement "Change-driven approaches don't use a formal change control process" is the most accurate description of how change is managed in change-driven methodologies, such as Agile. These approaches are inherently designed to embrace and accommodate frequent changes to requirements throughout the development lifecycle, rather than resisting them or subjecting them to rigid, formal approval processes. In a change-driven context, requirements are expected to evolve, and changes are managed through continuous collaboration with stakeholders, iterative development cycles, and adaptive planning. The emphasis is on flexibility, rapid feedback, and delivering value incrementally, which contrasts sharply with the need for a formal Change Control Board (CCB) or a highly structured change control system typical of predictive (plan-driven) approaches. This approach is consistent with the principles of the BABOK Guide when discussing requirements life cycle management in adaptive environments.
  
  Reason for not choosing other answers:
  

  • A. Change-driven approaches must use a change control system with a change control board. This statement is incorrect. Change-driven approaches specifically aim to minimize or eliminate the need for a formal change control system and a Change Control Board (CCB). The very essence of these approaches is to respond to change without bureaucratic hurdles, allowing requirements to emerge and adapt throughout the project.
  • B. Change-driven approaches only use a change control system for approved changes. This is also incorrect for the same reasons as A. If a change-driven approach were to use a formal change control system, it would contradict its core principles of agility and adaptability. Changes are typically integrated and managed continuously, not held for "approval" in a rigid sense.
  • D. Change-driven approaches are driven by change control processes. This statement is misleading and generally incorrect. While changes certainly occur and are managed in change-driven environments, they are not "driven by" *formal* change control processes in the traditional sense. Instead, they are driven by the iterative development cycle, continuous stakeholder collaboration, and the need to deliver evolving value. Formal change control processes are characteristic of predictive methodologies, not adaptive ones. The discussion explicitly highlights that this view is contrary to the consensus and BABOK Guide principles regarding adaptive approaches.

  
  Citations:

  • A Guide to the Business Analysis Body of Knowledge (BABOK Guide) v3.0, Chapter 5: Requirements Life Cycle Management - Assess Requirements Changes https://www.iiba.org/standards-and-resources/babok/ (General BABOK Guide information)
  • Agile Manifesto Principles (emphasizes responding to change over following a plan) https://agilemanifesto.org/principles.html