CBAP flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Business Analysis Approach

The planned method for performing business analysis work, selecting predictive, adaptive, or hybrid based on risk, change rate, regulation, and stakeholder availability, and naming deliverables and approval gates.

Stakeholder Engagement Plan

A plan that classifies stakeholders by influence and attitude, sets a target engagement level for each, and defines communication style and frequency matched to that level.

BA Governance

The rules for decision-making, requirement change control, prioritization, and approval authority; it names who approves baselines and how conflicts are escalated.

Requirements Information Management

The approach for storing, versioning, tracing, securing, and reusing business analysis information so it stays consistent and auditable across the life cycle.

BA Performance Measures

Quantitative indicators of business analysis work quality, such as requirement defect rate, rework hours, cycle time, and stakeholder satisfaction, compared against a recorded baseline.

RACI Matrix

A responsibility assignment matrix: one Accountable per activity, Responsible performs the work, Consulted gives two-way input before, Informed receives one-way updates after.

Prepare for Elicitation

The task of defining the objective, selecting techniques, identifying and scheduling participants, and preparing materials before conducting any elicitation activity.

Confirm Elicitation Results

The task of checking elicited information with the source and other stakeholders to verify accuracy and completeness before treating it as requirements input.

Observation vs Job Shadowing

Observation watches a process without interference to see actual work; job shadowing follows one specific worker to capture tacit steps and workarounds.

Elicitation Workshop

A structured group session used to build consensus and resolve conflicting needs; it requires a clear objective, decision-capable participants, an agenda, and documented output.

Manage Stakeholder Collaboration

The ongoing task of communicating with stakeholders, negotiating disagreements, and surfacing conflict early so that it is handled through governance rather than silently assumed away.

Prototyping as Elicitation

Using a preliminary model of a solution to surface hidden or unstated needs; a throwaway prototype is an elicitation aid, not a requirements deliverable.

Bidirectional Traceability

The ability to trace requirements backward to business objectives and stakeholders and forward to design, build, and test artifacts that satisfy them.

Baseline Requirements

A formally reviewed and approved set of requirements that changes only through change control, with impact analysis, approval, and version update recorded.

Change Impact Analysis

Assessment of a proposed requirement change covering affected requirements, designs, tests, and stakeholders, plus effort, cost, schedule, risk, and alternative options.

MoSCoW Prioritization

A ranking scheme grouping requirements as Must have, Should have, Could have, or Won't have for the current delivery, used to bound scope and defer low value.

Requirement States

Life-cycle statuses such as proposed, in progress, approved, deferred, cancelled, rejected, and implemented; each transition is a governance event that should be recorded.

Current State Analysis

Assessment of internal capabilities, processes, technology, and culture plus external market, competitor, and regulatory context to establish the starting point for change.

Future State Definition

The description of desired business goals and objectives, expressed as measurable and time-bound targets, that the change is intended to achieve.

Gap Analysis

The comparison of current state against future state that identifies missing capabilities and their causes, and which drives the change strategy rather than a preselected solution.

Change Strategy

The approach for moving from current to future state, compared across options by cost, benefit, risk, and feasibility, and defined before committing to a specific solution.

Business Need vs Solution

The business need is the problem or opportunity to be addressed; the solution is one option for addressing it, and confusing the two is a common strategy error.

SWOT Analysis

A technique pairing internal strengths and weaknesses with external opportunities and threats to generate strategy options, which are then tested against business goals.

Verify vs Validate Requirements

Verification confirms a requirement is well formed and testable; validation confirms it addresses the real business need and delivers stakeholder value.

Requirements Architecture

The organization of requirements into a coherent whole, showing relationships among them and traceability to business objectives while remaining consistent with standards.

Design Options Analysis

Comparison of alternative solution designs by cost, benefit, risk, and feasibility, leading to a recommendation that maximizes value against the stated objectives.

Business Rule

A statement that governs or constrains business behavior, discovered rather than invented, which requirements must comply with and which is not itself a requirement.

Non-Functional Requirements

Requirements describing quality attributes such as performance, security, usability, and reliability; they are as binding as functional requirements and must be measurable.

Measure Solution Performance

The Solution Evaluation task of collecting performance data against the business objectives and expected benefits defined earlier, using a recorded baseline for comparison.

Solution vs Enterprise Limitation

A solution limitation is a constraint inside the solution such as design or capacity; an enterprise limitation is outside it, such as policy, culture, skills, or incentives.

Recommend Actions to Increase Value

The final Solution Evaluation task: choose among doing nothing, adjusting the solution, adjusting the enterprise, retiring the solution, or revising objectives with approval.

Solution Value

The benefit a solution delivers minus its cost, judged against business objectives; a solution that satisfies requirements but misses objectives delivers low value.