Changed CCBA Exam Questions

According to the Capability in Business Analysis™ (CCBA®) Learning documents, a stakeholder is anyone who has an interest or influence in the project or its outcome1. Stakeholders can have different levels of power, interest, impact, and influence on the project, and they can be internal or external to the organization2. However, no stakeholder group is more important than another, as they all contribute to the project’s success in different ways. The project manager’s role is to identify, analyze, engage, and manage the stakeholders throughout the project lifecycle, and to balance their needs, expectations, and interests3. The project manager should also communicate effectively with the stakeholders, and ensure that their feedback, input, and approval are obtained at the appropriate stages of the project4.

References:

• Business Analysis Expert Certification, CCBA® | IIBA®, section “BABOK® Guide v3”, chapter 2, section 2.1
• Stakeholder in Project Management - Techcanvass, section “Types of Stakeholders”
• Stakeholder Management | Its Importance | Institute of Project Management, section “What is Stakeholder Management?”
• What Is a Stakeholder? Definitions, Types & Examples, section “How to Manage Stakeholders”
• Who are Project Stakeholders and Why They are Important? - KnowledgeHut, section “How to manage project stakeholders?”

• A. It defines the nature of a solution that meets that need: This is a correct activity of enterprise analysis, as it involves defining the scope, objectives, and requirements of the solution that will address the business problem or opportunity.
• B. It identifies business needs, problems, or opportunities: This is a correct activity of enterprise analysis, as it involves understanding the current state of the organization, its goals, and the external and internal factors that affect its performance.
• C. It justifies the investment necessary to deliver that solution: This is a correct activity of enterprise analysis, as it involves assessing the costs, benefits, risks, and feasibility of the proposed solution and presenting a business case that supports the decision to implement it.
• D. It manages and expresses requirements to a broad and diverse audience: This is an incorrect activity of enterprise analysis, as it belongs to another knowledge area, which is requirements communication and management. This knowledge area involves ensuring that the requirements are understood, agreed upon, and controlled by all the stakeholders throughout the project lifecycle.

 According to the web search results, requirements envisioning is “a technique used in change-driven approaches to elicit and document a high-level overview of the scope and objectives of a project or initiative” 1. Requirements envisioning involves creating a list of high-level requirements that describe the features and capabilities of the desired solution, as well as the business value and benefits that it will deliver. Requirements envisioning helps to establish a common vision and understanding among stakeholders, as well as to prioritize and plan the requirements in short iterations. The other options are not correct because:

• B. Requirements foundation is not a term used in change-driven approaches, but rather in plan-driven approaches. It refers to the “set of requirements that provide the basis for planning, managing, and delivering a project” 2.
• C. Product scope is “the features and functions that characterize a product, service, or result” 3. It is not the same as the initial high-level listing of requirements, as it may include more detailed and specific information about the product specifications and quality attributes.
• D. Project scope is “the work performed to deliver a product, service, or result with the specified features and functions” 3. It is not the same as the initial high-level listing of requirements, as it may include more detailed and specific information about the project activities, resources, and deliverables. References:
• 1: What Are High-Level Requirements in Project Management?, section “What are High-Level Requirements in Project Management?”
• 2: BABOK® Guide, p. 35
• 3: [A Guide to the Project Management Body of Knowledge (PMBOK® Guide)], p. 705

The high-level requirements list that the business analyst may create when using a change-driven approach is also known as requirements envisioning. This is a technique for eliciting and documenting the high-level features and characteristics of the solution, and defining the scope and boundaries of the initiative12. Requirements envisioning helps to establish a common understanding and vision among the stakeholders, and to guide the iterative and incremental delivery of the solution. The other options are not terms that are equivalent to the high-level requirements list, but rather terms that describe different aspects of the solution or the project, such as project scope (B), which is the work that must be performed to deliver the solution3, product scope ©, which is the features and functions that characterize the solution3, or requirements foundation (D), which is a term that refers to the core set of requirements that are essential for the solution4. References: Business Analysis Expert Certification, CCBA® | IIBA®, Certification of Capability in Business Analysis™ (CCBA®), Business Analysis Certification Competencies, CCBA® | IIBA®, The Ultimate Guide to Business Capability Analysis