Explore a product domain

Delivery & agility

Planning, requirements, agile methods, and predictable delivery.

89matching
entries
DomainDelivery & agility
TypeAll types
LevelAll levels

89 topics shown

A
practiceFoundational

Acceptance Criteria

Specific, testable conditions that describe the behavior and outcomes a work item must satisfy to be accepted by product and delivery collaborators.

Read the entry
principleFoundational

Agile Product Development

An adaptive approach to creating products through short feedback loops, close collaboration, frequent delivery, and learning-led changes to plans.

Read the entry
B
practiceIntermediate

Backlog Management

The ongoing practice of maintaining an ordered, transparent, and strategically aligned set of potential product work so teams can make sound delivery choices.

Read the entry
practiceIntermediate

Backlog Refinement

An ongoing collaborative activity that adds appropriate detail, order, and size to near-term backlog items as the team learns more about the work.

Read the entry
artifactFoundational

Burndown Chart

A burndown chart plots work remaining over time, often against a reference line that reaches zero at the end of a sprint or delivery horizon.

Read the entry
artifactFoundational

Burnup Chart

A burnup chart plots completed work against total scope over time, making progress and scope change visible as separate lines.

Read the entry
C
practiceIntermediate

Change Control

A governed process for capturing, evaluating, deciding, implementing, and recording proposed changes to approved project baselines or controlled items.

Read the entry
methodIntermediate

Change Impact Analysis

A structured assessment of how a proposed change affects value, people, processes, requirements, designs, systems, plans, risks, and obligations.

Read the entry
practiceAdvanced

Continuous Delivery

The capability to keep software in a releasable state so changes can be deployed safely, quickly, and sustainably whenever the organization chooses.

Read the entry
methodAdvanced

Critical Path Method

A network-scheduling method that identifies the sequence of dependent activities governing the earliest possible project completion date.

Read the entry
methodIntermediate

Crystal Methods

Crystal is a family of people-centered Agile methods tailored to team size, system criticality, communication needs, and local context.

Read the entry
artifactIntermediate

Cumulative Flow Diagram

A cumulative flow diagram is a stacked area chart showing how the cumulative count of work items in each workflow state changes over time.

Read the entry
metricFoundational

Cycle Time

Cycle time measures elapsed time from the defined start of work on an item until that item reaches the workflow's defined finished point.

Read the entry
D
artifactFoundational

Definition of Done

A shared quality standard that defines when an increment is complete and usable.

Read the entry
artifactIntermediate

Definition of Ready

A team-defined set of conditions indicating that a work item is sufficiently understood to be considered for selection.

Read the entry
practiceIntermediate

Dependency Management

The practice of identifying, reducing, sequencing, and monitoring relationships that constrain independent product delivery.

Read the entry
frameworkAdvanced

Disciplined Agile

Disciplined Agile is a context-sensitive toolkit for choosing and continuously improving ways of working across teams and value streams.

Read the entry
frameworkIntermediate

Dual-Track Agile

A product-development pattern in which discovery reduces value, usability, feasibility, and viability risks while delivery builds dependable solutions.

Read the entry
methodAdvanced

Dynamic Systems Development Method

DSDM is a full-lifecycle Agile project-delivery method that fixes time, cost, and quality while varying lower-priority scope.

Read the entry
E
methodAdvanced

Earned Value Management

An integrated project-control method that compares planned value, earned value, and actual cost to assess cost and schedule performance against a baseline.

Read the entry
artifactFoundational

Epic

A large, coherent body of product work that is too broad for one delivery interval and is progressively split into smaller items.

Read the entry
methodIntermediate

Extreme Programming

Extreme Programming combines rapid customer feedback with disciplined engineering practices such as pairing, testing, refactoring, and continuous integration.

Read the entry
F
practiceIntermediate

Feature Flags

Runtime controls that change product behavior for selected contexts, allowing teams to separate code deployment from user-facing release decisions.

Read the entry
methodIntermediate

Feature-Driven Development

Feature-Driven Development organizes model-informed software delivery around small, client-valued features designed and built in short cycles.

Read the entry
frameworkAdvanced

Flight Levels

Flight Levels improves the flow of work across teams by connecting operational delivery, cross-team coordination, and strategy.

Read the entry
metricIntermediate

Flow Efficiency

Flow efficiency compares active working time with total elapsed flow time to show how much of an item's journey is spent being worked rather than waiting.

Read the entry
artifactFoundational

Functional Requirement

A requirement describing a capability or behavior a product must provide in response to defined conditions.

Read the entry
G
artifactFoundational

Gantt Chart

A time-scaled visual schedule that represents project activities as horizontal bars and can show dates, durations, milestones, dependencies, and progress.

Read the entry
frameworkIntermediate

Growth–Share Matrix

A portfolio framework that compares relative market share with market growth to prompt investment, harvesting, repositioning, or exit discussions.

Read the entry
I
artifactFoundational

Increment

A usable, verified addition to a product that meets the Definition of Done and advances its Product Goal.

Read the entry
frameworkIntermediate

INVEST Criteria

Six diagnostic qualities—Independent, Negotiable, Valuable, Estimable, Small, and Testable—for improving user stories and backlog items.

Read the entry
artifactFoundational

Issue Log

A controlled record of current problems, questions, or decisions affecting delivery, with ownership, priority, actions, due dates, and resolution evidence.

Read the entry
J
K
L
frameworkAdvanced

Large-Scale Scrum

Large-Scale Scrum applies Scrum to multiple teams working on one product while deliberately minimizing added roles, artifacts, and coordination layers.

Read the entry
metricFoundational

Lead Time

Lead time measures elapsed time from a request or commitment point until delivery, capturing both queue time and time spent actively completing the work.

Read the entry
M
principleIntermediate

Minimum Lovable Product

The smallest coherent product release designed to create an intentionally satisfying experience, not merely functional tolerance, for a focused early audience.

Read the entry
principleIntermediate

Minimum Viable Product

The smallest product experiment that can deliver a meaningful experience to early users and generate validated learning about a critical business assumption.

Read the entry
methodAdvanced

Monte Carlo Forecasting

Monte Carlo forecasting repeatedly samples historical delivery data to estimate probability ranges for how much work may finish or when a body of work may complete.

Read the entry
N
frameworkAdvanced

Nexus Framework

Nexus minimally extends Scrum so several teams can manage dependencies and produce one integrated, valuable product increment every Sprint.

Read the entry
frameworkFoundational

Now–Next–Later Roadmap

A roadmap format that groups priorities into three confidence horizons instead of assigning speculative dates to distant work.

Read the entry
O
artifactIntermediate

Outcome-Based Roadmap

A roadmap organized around measurable changes in customer or business behavior rather than predetermined feature output.

Read the entry
P
methodAdvanced

PERT Estimation

A three-point estimation method that combines optimistic, most likely, and pessimistic durations to represent uncertainty in project activities.

Read the entry
artifactFoundational

Product Backlog

An emergent, ordered list of work that may improve a product and serves as the Scrum Team’s single source of planned work.

Read the entry
artifactFoundational

Product Backlog Item

A single, ordered unit of work or value recorded in a product backlog.

Read the entry
artifactFoundational

Product Brief

A short, problem-focused document that frames a product opportunity, its intended users, strategic value, evidence, assumptions, constraints, and success signals.

Read the entry
artifactIntermediate

Product Initiative

A coordinated, strategic body of product work that groups multiple efforts toward a shared objective or outcome.

Read the entry
practiceAdvanced

Product Portfolio Management

The ongoing practice of selecting, balancing, funding, and reviewing products and major investments as one strategic system.

Read the entry
artifactFoundational

Product Requirement

A documented condition, capability, or constraint a product must satisfy to address a need or objective.

Read the entry
artifactIntermediate

Product Requirements Document

A living document that aligns a cross-functional team on a product initiative’s purpose, users, scope, requirements, constraints, and measures of success.

Read the entry
artifactFoundational

Product Roadmap

A strategic communication artifact that connects product direction and desired outcomes to a changing sequence of investments.

Read the entry
artifactFoundational

Product Scope

The agreed boundary of the capabilities, qualities, users, contexts, and exclusions that characterize a product or product change.

Read the entry
artifactFoundational

Project Charter

A concise authorization document that establishes why a project exists, who sponsors it, what success means, and what authority the project manager holds.

Read the entry
methodFoundational

Project Premortem

A project premortem imagines that an initiative has already failed and works backward to expose plausible causes while preventive action is still possible.

Read the entry
Q
R
artifactFoundational

RAID Log

A consolidated control log for tracking risks, assumptions, issues, and dependencies that can affect project or programme delivery.

Read the entry
practiceIntermediate

Release Planning

The collaborative practice of defining a release goal, viable scope, forecast, dependencies, readiness criteria, and learning plan.

Read the entry
frameworkIntermediate

Requirement Types

A classification of business, stakeholder, solution, and transition requirements that connects the reason for change to needs, product behavior, and adoption.

Read the entry
practiceIntermediate

Requirements Analysis

The iterative examination and modeling of needs and requirements to make them coherent, feasible, valuable, and decision-ready.

Read the entry
artifactAdvanced

Requirements Baseline

An approved, version-controlled set of requirements used as a reference for design, verification, contracts, and controlled change.

Read the entry
practiceIntermediate

Requirements Elicitation

The collaborative practice of drawing out and confirming needs, constraints, rules, and knowledge relevant to a proposed change.

Read the entry
practiceIntermediate

Requirements Management

The ongoing practice of organizing, maintaining, tracing, prioritizing, and governing requirements as needs and solutions evolve.

Read the entry
practiceIntermediate

Requirements Prioritization

The ongoing practice of ordering requirements using value, urgency, risk, dependencies, cost, and stakeholder consequences.

Read the entry
practiceAdvanced

Requirements Traceability

The ability to follow relationships from needs and requirements through designs, implementation, tests, releases, and outcomes in both directions.

Read the entry
practiceIntermediate

Requirements Verification and Validation

Complementary checks that requirements are well formed and usable for development, and that they represent the right stakeholder and business needs.

Read the entry
practiceFoundational

Retrospective

A recurring team reflection that examines how work happened, identifies a meaningful improvement, and turns learning into a concrete experiment or action.

Read the entry
artifactIntermediate

Risk Register

A maintained record of identified uncertainties, their potential effects, assessments, owners, planned responses, actions, and residual exposure.

Read the entry
S
frameworkAdvanced

Scaled Agile Framework

SAFe coordinates strategy, portfolio decisions, and multi-team product delivery through a structured Lean-Agile operating model.

Read the entry
methodAdvanced

Scenario Planning

A structured method for exploring several plausible futures and testing whether strategy remains useful across uncertainty.

Read the entry
termFoundational

Scope Creep

The uncontrolled expansion of product or project scope without corresponding decisions about value, cost, time, capacity, or risk.

Read the entry
frameworkFoundational

Scrum

A lightweight framework in which a small, self-managing team delivers usable increments, inspects results, and adapts its plan around a Product Goal.

Read the entry
frameworkAdvanced

Scrum@Scale

Scrum@Scale uses modular Scrum-based coordination cycles to align networks of teams while aiming for a minimum viable bureaucracy.

Read the entry
methodIntermediate

Shape Up

A product-development method that shapes bounded pitches, bets on selected work, and gives small teams fixed time with flexible scope to deliver.

Read the entry
methodIntermediate

Spike

A short, timeboxed investigation or prototype used to answer a specific question and reduce uncertainty before a delivery decision.

Read the entry
artifactFoundational

Sprint Backlog

The Sprint Goal, selected Product Backlog Items, and actionable delivery plan maintained by Developers during a Sprint.

Read the entry
artifactFoundational

Sprint Goal

A single objective for a Scrum Sprint that gives selected work coherence while preserving flexibility in how the team achieves it.

Read the entry
practiceFoundational

Sprint Planning

The Scrum event in which the whole team establishes why the Sprint is valuable, what it can accomplish, and an initial plan for doing the work.

Read the entry
practiceFoundational

Sprint Review

A collaborative Scrum event where the team and stakeholders inspect the Sprint’s outcome, discuss changing conditions, and adapt what to do next.

Read the entry
frameworkIntermediate

Stage-Gate Process

A product-innovation process that separates cross-functional development stages with evidence-based investment gates and go, hold, recycle, or stop decisions.

Read the entry
methodIntermediate

Story Splitting

A method for dividing a large user story into smaller, independently useful slices that preserve observable value and learning.

Read the entry
frameworkAdvanced

Strategic Bets

Explicit, consequential investment choices based on a theory of advantage, named assumptions, and evidence-based commitment stages.

Read the entry
T
metricFoundational

Team Velocity

Team velocity is the amount of estimated or counted work one team completes within an iteration, interpreted from that team's recent history.

Read the entry
artifactIntermediate

Theme-Based Roadmap

A roadmap structured around a small set of strategic themes that connect related investments to broader product intent.

Read the entry
frameworkAdvanced

Three Horizons Framework

A portfolio lens for managing current core performance, emerging growth businesses, and future options concurrently.

Read the entry
metricFoundational

Throughput

Throughput is the exact count of work items finished during a defined unit of time, such as a day, week, sprint, or month.

Read the entry
U
artifactFoundational

User Story

A concise statement of a desired outcome from a user’s perspective that acts as a prompt for collaborative requirements and delivery conversations.

Read the entry
methodIntermediate

User Story Mapping

A collaborative method for arranging user activities and stories into a journey-shaped map, then slicing that map into coherent releases and learning steps.

Read the entry
W
artifactIntermediate

Work Breakdown Structure

A hierarchical decomposition of the project’s total scope into manageable deliverables and work packages that can be estimated, assigned, scheduled, and controlled.

Read the entry
metricFoundational

Work in Progress

Work in progress is the number of work items that have crossed the workflow's start point but have not yet crossed its finished point.

Read the entry

Start typing to search titles, definitions, categories, and frameworks.