Value Delivery
Working Product
Quality Practices
Flow & Delivery
Vocab
100

Delivering small, usable portions of functionality over time rather than all at once.

What is Incremental Delivery?

100

The primary measure of progress in agile.

What is Working Product (or Working Software)?

100

Writing tests before creating functionality.

What is Test-Driven Development (TDD)?

100

The amount of work currently being developed but not yet completed.

What is Work in Progress (WIP)?

100

A small demonstration or experiment used to reduce uncertainty.

What is a Spike?

200

The agile principle of producing the most benefit possible for the customer.

What is Delivering Customer Value?

200

A product state that meets agreed quality criteria and is potentially releasable.

What is Done / Definition of Done?

200

Frequently combining code changes into a shared repository.

What is Continuous Integration?

200

he amount of time required to complete work once active development begins.

What is Cycle Time?

200

Functionality intentionally postponed because it delivers lower value than other work.

What is Deferred Work (or Lower Priority Backlog)?

300

Ordering work based on business benefit, risk, dependencies, or customer need.

What is Prioritization?

300

Delivering product functionality frequently, often in short cycles.

What is Iterative Delivery?

300

Improving internal code structure without changing system behavior.

What is Refactoring?

300

A constraint slowing movement of work through a process.

What is a bottleneck

300

A delivery approach that makes completed work available to users as soon as feasible.

What is Continuous Delivery?

400

Gathering stakeholder or customer reactions to improve future deliveries.

What is Feedback?

400

A product version released to a limited audience for evaluation and feedback.

What is a Beta Release?

400

A development practice where two programmers work together at one workstation.

What is Pair Programming?

400

The total elapsed time from work request to completed delivery.

What is Lead Time?

400

Accumulated shortcuts or postponed quality work that may create future problems.

What is Technical Debt?

500

A method of validating whether delivered functionality actually meets business needs.

What is Customer Validation?

500

The practice of confirming a product increment is usable before broader deployment.

What is Validation?

500

Embedding quality activities throughout development instead of inspecting quality at the end.

What is Building Quality In?

500

The measurement of completed work units moving through a system.

What is Throughput?

500

An approach where teams adjust product direction based on learning and feedback.

What is Adaptive Delivery?