OBA key terms

The discipline of identifying business needs and recommending solutions that deliver value to stakeholders, using structured techniques to understand problems, opportunities, and the changes required to address them.

The set of responsibilities a practitioner holds, such as eliciting requirements, facilitating communication between business and technical groups, and supporting solution delivery, which vary by organization and project context.

The foundational ideas underlying the discipline: change, need, solution, stakeholder, value, and context. These concepts frame how practitioners interpret situations and justify recommended actions.

A statement of a need or capability that a solution must provide, expressed in a form useful for analysis, design, and verification, and traceable to its source.

Grouping requirements by type, such as business, stakeholder, solution functional, and non-functional categories, so that each kind receives appropriate analysis and treatment throughout the lifecycle.

A requirement describing a quality or constraint the solution must satisfy, such as performance, security, usability, or availability, rather than a specific behavior or feature.

A person or group with an interest in, influence over, or dependence on a change or solution, whose needs and expectations must be identified and managed.

The worth or benefit that a change or solution delivers to an organization and its stakeholders, which may be financial or non-financial and is assessed relative to cost and risk.

The environment surrounding a change effort, including organizational structure, culture, processes, technology, and external factors, that shapes how analysis and solutions must be approached.

Examining the whole organization to understand its structure, capabilities, and strategy so that proposed changes align with broader goals rather than isolated departmental needs.

A documented justification for an initiative that compares expected benefits with estimated costs, risks, and alternatives, used to support a go, no-go, or defer decision.

An assessment of whether a proposed solution is viable across technical, economic, operational, legal, and schedule dimensions, conducted before significant investment is committed.

Identifying stakeholders and assessing their influence, interest, and impact so that engagement and communication efforts can be tailored and prioritized appropriately.

Selecting appropriate techniques, participants, and logistics for gathering requirements, matched to the context, available time, and the nature of the information sought.

A structured method for drawing out information from stakeholders, such as interviews, workshops, observation, surveys, document analysis, or prototyping, each suited to different situations.

A facilitated group session in which stakeholders collaborate to identify, clarify, and prioritize requirements, often producing faster consensus than separate interviews.

A visual or structured representation of the boundaries of a solution, showing what is included and excluded, used to align stakeholders and control changes.

The set of capabilities and boundaries that a proposed solution will and will not deliver, agreed with stakeholders and used as a baseline for planning and change control.

Uncontrolled expansion of solution boundaries through unmanaged additions and changes, which erodes schedules and budgets unless changes are formally evaluated and approved.

The activity of drawing out requirements and other information from stakeholders and sources, using planned techniques rather than simply collecting what people volunteer.

Guiding a group through structured discussion toward agreed outcomes, managing participation, conflict, and process so that the group, not the facilitator, owns the content.

Recording requirements in a clear, consistent, and accessible form, such as specifications, models, or user stories, suited to the audience and the delivery approach.

Confirming that documented requirements are complete, consistent, unambiguous, and correctly written, typically through review or inspection rather than testing a built solution.

Confirming that requirements accurately represent stakeholder needs and will deliver the intended value, ensuring the right solution is being described before building it.

The ability to link requirements backward to their sources and forward to design, build, and test artifacts, supporting impact analysis and demonstrating that needs are met.

A documented approach specifying what information will be shared with which stakeholders, in what format, and how often, to keep engagement consistent and expectations aligned.

A formal process for submitting, evaluating, approving, and recording changes to baselined requirements or scope, preventing unmanaged drift and preserving decision history.

An approved and frozen set of requirements against which subsequent changes are compared, providing a stable reference for planning, delivery, and verification.

Assessing a delivered or partially delivered solution to determine how well it meets needs, delivers value, and whether corrective action or further change is warranted.

Confirming that a solution or work product was built correctly according to its specifications, often through testing, inspection, or demonstration against stated requirements.

Identifying potential threats to a change effort, estimating their likelihood and impact, and defining responses so that significant exposures are managed rather than ignored.

Tracking defined indicators against targets to judge whether a solution or process is achieving intended outcomes, enabling timely corrective action.

Comparing the estimated costs of an option with its expected benefits, often over time, to support selection among alternatives or to justify continued investment.

The principles guiding practitioner conduct, including honesty, integrity, confidentiality, avoiding conflicts of interest, and reporting information accurately even when inconvenient.

A situation where a practitioner's personal, financial, or other interests could improperly influence professional judgment, requiring disclosure and appropriate mitigation.

The obligation to protect sensitive organizational and stakeholder information from unauthorized disclosure, using it only for legitimate purposes related to the work.

The structures, decision rights, and accountability mechanisms that direct and oversee change efforts, ensuring decisions are made at appropriate levels and are documented.

Addressing disagreements among stakeholders through structured approaches such as negotiation or mediation, aiming for outcomes that preserve relationships and serve project goals.