IIBA CPOA key terms

The set of analysis activities a product owner performs to understand customer needs, shape solutions, and guide delivery decisions across a product's life, distinct from project-scoped business analysis.

The accountable role that maximizes product value by ordering the backlog, clarifying intent, and making trade-off decisions on scope, priority, and acceptance.

A concise statement of the benefit a product delivers to a specific customer segment and why that benefit beats the alternatives available to them.

A group of users or buyers who share needs, behaviors, or constraints closely enough that one product offering can serve them well.

A research-based archetype describing a representative user's goals, context, and pain points, used to keep design and priority decisions customer-centered.

A lightweight canvas capturing what a user says, thinks, does, and feels, helping a team build shared understanding of customer context before proposing solutions.

A short, conversation-oriented statement of a need expressed from the user's perspective, typically paired with acceptance criteria that make completion verifiable.

The conditions a backlog item must satisfy to be accepted by the product owner, written to be testable and agreed before development begins.

A shared team agreement describing the quality attributes every increment must meet before it counts as complete, applied uniformly across backlog items.

An ordered, evolving list of product needs, ideas, and work items that the product owner continuously prioritizes to reflect current value and risk.

The recurring activity of clarifying, splitting, estimating, and reordering backlog items so upcoming work is understood well enough to plan confidently.

The deliberate ranking of competing needs based on value, risk, cost, and dependencies, producing a sequence the delivery team can act on.

A prioritization technique sorting items into Must have, Should have, Could have, and Will not have this time, useful for negotiating scope under a fixed constraint.

An economic prioritization method that ranks items by cost of delay divided by job duration, favoring high-value, short-effort work when capacity is limited.

The economic value lost per unit of time a product capability is not delivered, used to compare competing investments objectively.

The smallest release that lets a team test key assumptions with real users and learn whether to invest further, not merely a reduced-scope product.

The smallest coherent capability that delivers standalone value a customer would notice, pay for, or adopt, used to slice releases meaningfully.

A measurable change in customer or business behavior resulting from a product change, distinguished from the output of work delivered.

A tangible deliverable such as a feature, release, or document produced by the team, which matters only insofar as it drives intended outcomes.

A quantified measure chosen to track progress toward a specific product or business objective over time, with a defined baseline and target.

A metric that changes before the final result and therefore helps a product owner predict and steer future performance rather than only report history.

A time-boxed test of a stated hypothesis with defined success measures, run to reduce uncertainty before committing larger investment.

A testable statement linking a proposed change to an expected outcome and measure, forming the basis for experiments and learning loops.

A belief treated as true without evidence, which a product owner should surface, rank by risk, and validate before relying on it.

A visual model of the people and groups affected by or influencing a product, showing their interests, influence, and preferred engagement approach.

Explicit agreement about who is authorized to make which product decisions, reducing delays and conflicts between product, business, and technical roles.

The structures, policies, and decision pathways an organization uses to guide and constrain product investment, balancing autonomy with accountability and compliance.

The sequence of stages a product passes through from concept and introduction to growth, maturity, and retirement, each requiring different ownership emphasis.

A communication artifact showing intended product direction, sequencing, and expected outcomes over time, ideally framed around goals rather than fixed feature promises.

The end-to-end sequence of activities and handoffs required to move an idea to a customer, analyzed to expose delays and waste.

A usable, potentially releasable addition to the product produced within a timebox, meeting the team's agreed definition of done.

The accumulated future cost of shortcuts in design or code that slow later change, which a product owner must weigh against feature investment.

The boundary of what a product change will and will not include, actively negotiated rather than fixed when time, cost, or quality constraints bind.

An uncertain event or condition that could affect product value, delivery, or compliance, assessed by likelihood and impact to guide mitigation and sequencing.

A legal, regulatory, or policy requirement that limits product design choices and must be identified early and traced through delivery.

An agreed approach describing which stakeholders receive what product information, in which format, and how often, to sustain alignment.

A disposition emphasizing customer value, evidence-based learning, ownership of outcomes, and willingness to say no, rather than merely administering requirements.

A visual timeline of a customer's end-to-end experience with a product or service, highlighting pain points and moments that shape satisfaction.