Business Analysis (CBAP) Question bank

Short Description: Introduction to BABOK

This lesson introduces BABOK, which means Business Analysis Body of Knowledge. BABOK is a globally recognized guide that explains the standard practices, tasks, techniques, competencies, and concepts used in business analysis.

The lesson explains that business analysis is not just about writing requirements. It is about helping an organization understand its needs, analyze change, recommend valuable solutions, and deliver business value. Learners will understand the role of a business analyst, the structure of the BABOK Guide, the importance of tasks, techniques, underlying competencies, and how business analysis can be applied in different contexts such as Agile, Business Intelligence, Information Technology, Business Architecture, and Business Process Management.

This lesson explains the key concepts that guide professional business analysis work. It introduces the Business Analysis Core Concept Model (BACCM), which helps business analysts think clearly and holistically about every change initiative.

The lesson also explains important business analysis terms such as business analysis information, design, enterprise, organization, plan, requirement, and risk. It further introduces the requirements classification schema, stakeholder roles, and the relationship between requirements and designs. The main idea is that business analysis is not only about collecting requirements; it is about understanding change, need, solution, stakeholders, value, and context so that the right solution can deliver meaningful business value.

This lesson explains how business analysis work is planned, organized, coordinated, monitored, and improved. It helps the business analyst decide how business analysis activities will be carried out, who will be involved, how stakeholders will be engaged, how requirements and designs will be governed, how information will be managed, and how performance will be assessed.

The lesson also introduces the five major tasks in Business Analysis Planning and Monitoring: Plan Business Analysis Approach, Plan Stakeholder Engagement, Plan Business Analysis Governance, Plan Business Analysis Information Management, and Identify Business Analysis Performance Improvements. The main purpose is to ensure that business analysis work is structured, controlled, stakeholder-focused, and aligned with the objectives of the initiative.

This lesson explains how the business analyst decides the best method for conducting business analysis activities. It defines how the work will be done, what activities will be performed, what deliverables will be produced, what techniques will be used, when tasks will happen, who will perform them, and how formal the work should be.

The lesson also explains the difference between predictive and adaptive approaches. A predictive approach works well when requirements are stable, documentation is required, and sign-off is mandatory. An adaptive approach works well when requirements may change, feedback is needed quickly, and the best solution is still being discovered.

This lesson explains how decisions about business analysis information, especially requirements and designs, will be made, reviewed, approved, changed, prioritized, and escalated.

The purpose of Business Analysis Governance is to create clarity around authority and accountability. It answers important questions such as: Who can approve requirements? Who can request changes? Who performs impact analysis? Who decides priority? Who gives final approval? What happens when stakeholders disagree?

In simple terms, this lesson teaches that requirements and designs must not be managed casually. They need a clear governance process so that decisions are controlled, changes are managed, and business value is protected.

This lesson explains how business analysis information should be stored, accessed, organized, reused, and maintained throughout an initiative.

The purpose is to ensure that important information such as requirements, designs, decisions, business rules, assumptions, approvals, and stakeholder inputs are properly managed. When business analysis information is well managed, it becomes easier for stakeholders, developers, testers, regulators, and decision-makers to find the right information at the right time.

In simple terms, this task prevents business analysis information from being lost, duplicated, misunderstood, misused, or mismanaged.

This lesson explains how business analysts review the quality, effectiveness, and value of business analysis work. The purpose is to check whether business analysis activities are helping the project or organization achieve the desired outcome.

It focuses on comparing planned performance with actual performance, identifying gaps, and recommending actions that improve future business analysis work. The lesson teaches that business analysis should not only produce deliverables; it should produce useful, accurate, timely, and decision-supporting outputs that help stakeholders deliver value.