Acceptance criteria
Specific, testable conditions that describe what must be true for a requirement or piece of work to be accepted.
OmniSmith Learning Center·Dictionary
OmniSmith Learning CenterReference
Digital Product Dictionary
Common digital product and Agile delivery terms explained in clear language. Search the definitions or filter them by the part of the work they help describe.59 terms
59 dictionary terms shown.
Adoption
The extent to which intended users understand, begin using, and continue receiving value from a digital product.
Agile
An approach to working that uses short learning and delivery cycles, frequent feedback, and adaptation instead of relying on one fixed plan.
AI-enabled digital product
A digital product that uses artificial intelligence as part of the value it provides and is supported by clear ownership, evaluation, governance, experience, adoption, and operations.
Backlog
An ordered collection of potential product work, including needs, improvements, research, defects, and technical work.
Backlog refinement
The ongoing work of reviewing, clarifying, splitting, estimating, and reordering upcoming backlog items so they can support informed delivery decisions.
Burndown chart
A chart showing how much planned work remains over time, often within a sprint, to help a team see whether completion is trending as expected.
Business analysis
The work of connecting business intent, user needs, processes, data, rules, and constraints to clear product decisions and requirements.
Customer experience (CX)
The overall experience a person has across their interactions and relationship with an organization, including but not limited to a single product.
Daily Scrum (daily stand-up)
A brief daily coordination session where team members inspect progress toward the current goal, surface obstacles, and adjust the immediate plan.
Definition of done
A shared standard describing the quality and completion conditions that work must meet before a team considers it finished.
Dependency
A person, decision, system, team, vendor, or piece of work that another part of the product relies on.
Digital product
An intentionally managed digital capability that delivers continuing value to defined users, supported by ownership, experience, measurement, operations, and evolution.
Digital product lifecycle
The connected decisions and responsibilities through which an organization evaluates an opportunity and discovers, defines, designs, develops, validates, launches, supports adoption of, operates, evolves, and eventually retires a digital product.
Digital product management
The continuing discipline of directing a digital product across outcomes, priorities, decisions, delivery, adoption, performance, and evolution.
Digital productization
The work required to turn a functioning digital solution into a dependable product with ownership, experience, adoption, measurement, governance, support, and an operating model.
Digital solution
A digital response to a defined need or problem. A solution may work technically without yet having the conditions required to operate as a sustainable product.
Discovery
The work of understanding users, needs, problems, context, evidence, constraints, possibilities, and potential value before committing to a direction.
Epic
A large product need or body of work that is too broad for one delivery cycle and is typically divided into smaller stories or backlog items.
Governance
The decision rights, controls, evidence, reviews, and accountability used to guide a product responsibly.
Human-in-the-loop
A design in which people review, guide, approve, correct, or override decisions or outputs produced by an automated or AI-enabled system.
Impediment (blocker)
A condition that slows or prevents progress and requires attention, removal, or a change in plan.
Increment
The usable, integrated product value added during a delivery cycle and combined with everything completed previously.
Iteration
A fixed or repeatable cycle of planning, delivery, review, and learning used to advance a product in manageable steps.
Kanban
A flow-based way of managing work by making it visible, limiting work in progress, and improving how items move from start to finish.
Key performance indicator (KPI)
A defined measure used to track whether a product, outcome, or operating objective is performing as intended.
Minimum viable product (MVP)
The smallest coherent product experience that can deliver meaningful value and produce useful evidence for future decisions.
Model evaluation
The structured assessment of how an AI or machine-learning model performs against defined quality, accuracy, safety, fairness, and use-case expectations.
Operating model
The roles, responsibilities, decisions, processes, tools, and working rhythms through which a digital product is managed and sustained.
Outcome
A meaningful change in user behavior, organizational performance, or another condition that the product is intended to influence.
Product acceptance
Validation that the delivered product meets defined requirements, intended outcomes, and relevant user and organizational expectations.
Product analytics
The use of product data and evidence to understand behavior, adoption, performance, value, and opportunities for improvement.
Product backlog
The ordered source of potential product work that guides what a team may learn, improve, fix, or deliver next.
Product governance
The decisions, controls, reviews, evidence, and accountability used to guide a product throughout its lifecycle.
Product management
The continuing direction of a product across user needs, outcomes, priorities, investment, decisions, adoption, performance, and evolution.
Product operations
The practices, tools, evidence, governance, and working systems that help products and product teams operate consistently.
Product Owner
The person accountable in Scrum for maximizing product value and making Product Backlog priorities clear and usable.
Product ownership
The team-facing responsibility for turning product direction into prioritized, clear, and actionable delivery decisions.
Product roadmap
A communication and decision tool that connects product outcomes, priorities, planned learning, and potential work over time.
Product strategy
The choices that define whom the product serves, what value it should create, where to invest, and how success will be evaluated.
Release readiness
Confirmation that the product, users, support, operations, communications, measurement, and relevant controls are prepared for release.
Requirement
A documented need, condition, rule, behavior, constraint, or quality that a product must address.
Scrum
An Agile framework for complex product work that uses a self-managing team, short sprints, defined accountabilities, regular events, and repeated inspection and adaptation.
Scrum Master
The person accountable for helping a Scrum Team understand and use Scrum effectively while addressing organizational obstacles and supporting improvement.
Sprint
A fixed-length Scrum cycle, usually one month or less, in which a team works toward a single Sprint Goal and creates usable product value.
Sprint backlog
The Sprint Goal, selected Product Backlog items, and the team's evolving plan for delivering the Increment during the Sprint.
Sprint goal
The single outcome a Scrum Team intends to achieve during a Sprint, providing focus while allowing flexibility in the exact work.
Sprint planning
The Scrum event where the team establishes the Sprint Goal, selects work, and forms an initial delivery plan.
Sprint retrospective
The Scrum event where the team examines how it worked during the Sprint and agrees on improvements for the next cycle.
Sprint review
The Scrum event where the team and stakeholders inspect the latest product results, discuss what changed, and adapt future priorities.
Stakeholder
A person or group affected by, responsible for, funding, governing, delivering, supporting, or making decisions about a product.
Story points
Relative units some Agile teams use to compare the overall effort, complexity, and uncertainty of backlog items.
Technical debt
The future cost and constraint created when technical choices favor short-term speed over maintainability, quality, or sustainability.
User acceptance testing (UAT)
Validation performed with business representatives or intended users to confirm that a product supports agreed needs and real-world use.
User experience (UX)
How a person understands, interacts with, and experiences a product, including usefulness, usability, accessibility, and confidence.
User story
A concise expression of a user need that helps a team understand who needs something, what they need, and why it matters.
Value proposition
A clear explanation of the value a product is intended to provide to defined users or the organization.
Velocity
The amount of estimated work a team completes during a delivery cycle, used cautiously for that team's planning rather than as a cross-team productivity measure.
Work in progress limit (WIP limit)
A policy that caps how many work items may be active at one time or in one workflow stage to reduce overload and improve flow.
Build shared understanding
Common language makes better product decisions possible.
OmniSmith provides tailored education and practical enablement that helps leaders and teams understand digital product work and strengthen how the organization performs it.
Explore product management education