CPIT BA key terms

The knowledge area that determines which activities the business analyst will perform, who will be involved, and how progress and quality will be governed throughout an initiative.

The agreed plan describing how analysis work will be performed, including deliverables, timing, formality, prioritization method, and techniques to be used on a given initiative.

Identifying the people and groups affected by or influencing a change, then assessing their authority, attitude, and information needs so engagement can be tailored appropriately.

A documented schedule of who will be involved, when, in what form, and for what purpose, used to keep communication and participation predictable across the initiative.

A responsibility assignment grid marking each activity as Responsible, Accountable, Consulted, or Informed, clarifying decision rights and avoiding duplicated or unowned work.

An approach that defines most requirements and design up front, with formal approvals and documentation, suited to stable scope, regulatory constraints, or contractual milestones.

An approach that elaborates requirements incrementally through short cycles and frequent feedback, suited to uncertain or evolving needs where early delivery reduces risk.

The component of the approach that defines how requirements will be traced, baselined, versioned, prioritized, and changed, including approval authority and tooling.

Drawing out information from stakeholders and other sources through interviews, workshops, observation, and document analysis, then confirming that what was captured is accurate.

A short plan setting out the purpose, participants, technique, logistics, and supporting materials for a specific elicitation session, prepared so time with stakeholders is used efficiently.

A facilitated group session used to elicit requirements, resolve conflicts, or reach agreement, relying on clear objectives, ground rules, and documented outcomes.

Guiding a group through discussion so that all relevant voices contribute, disagreements surface productively, and the session ends with agreed, recorded decisions.

Watching stakeholders perform real work to capture tacit knowledge and actual behavior, useful where people cannot fully articulate what they do or where process detail matters.

A focused form of observation in which the analyst follows one worker through a full cycle of tasks, noting workarounds, inputs, handoffs, and pain points.

The knowledge area covering how requirements are traced, maintained, prioritized, approved, and changed from first capture through to retirement.

The recorded relationships between requirements and their sources, designs, tests, and other requirements, enabling impact analysis and evidence that each need is addressed.

A table linking each requirement to its origin, related design components, and verification tests, used to demonstrate coverage and assess the effect of changes.

An approved, versioned set of requirements that serves as the reference point for further change, so modifications are deliberate rather than silent drift.

A defined process for submitting, assessing, approving, or rejecting proposed requirement changes, ensuring decisions are recorded and affected parties are informed.

Assessing what a proposed change affects, including other requirements, designs, systems, costs, schedules, and stakeholders, before a decision to accept or reject it.

Ranking requirements by value, risk, urgency, or effort so that limited resources go first to what matters most, using an agreed and consistently applied method.

A prioritization scheme classifying items as Must have, Should have, Could have, or Will not have this time, making the consequences of constrained delivery explicit to stakeholders.

The knowledge area concerned with understanding the current state, defining a desired future state, and identifying the changes needed to move the organization between them.

Examining existing processes, systems, capabilities, and problems to establish a factual baseline against which future-state options and their value can be judged.

Describing the goals, capabilities, and conditions the organization intends to reach, expressed clearly enough to guide design decisions and measure progress.

Comparing current and desired states to identify missing capabilities, process differences, and the changes required to close the distance between them.

Measurable statements of what the organization wants to achieve within a timeframe, providing the yardstick against which proposed solutions are evaluated.

The knowledge area covering how elicited information is structured, refined, verified, and translated into designs that satisfy the stated need.

Checking that requirements are complete, consistent, unambiguous, testable, and within scope, so defects are found before design and build commit resources.

Confirming with stakeholders that documented requirements represent their real need and will deliver the intended value, rather than merely being internally well written.

A constraint on how a solution must behave, such as performance, security, availability, usability, or compliance, rather than a specific function it must perform.

Specifying how requirements will be met through components, interfaces, data, and process flows, at whatever level of detail the delivery approach requires.

Measuring how well a delivered or partial solution performs against business objectives, identifying limitations, and recommending action to increase realized value.

A structured review of what worked and what did not during an initiative, captured so future work benefits from the experience rather than repeating known mistakes.

The fundamental ideas underlying the discipline: need, change, solution, stakeholder, value, and context, which together frame every analysis activity regardless of domain.

The behavioral, communication, analytical, and technical abilities a business analyst applies, such as negotiation, critical thinking, and tool proficiency, alongside knowledge of techniques.

Addressing disagreement among stakeholders about needs or priorities by surfacing underlying interests and guiding the group toward a decision that can be supported.

An ordered list of work items such as features or requirements awaiting delivery, continuously refined and reprioritized so the highest-value items are addressed first.