# Feature-Driven Development

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

- Type: method
- Domain: Delivery & agility
- Level: Intermediate
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/feature-driven-development/>)

## What it means

Feature-Driven Development \(FDD\) is an iterative software-development method created from the work of Jeff De Luca and Peter Coad. It begins with an overall domain model and a structured feature list, then plans, designs, and builds in small units of client-valued functionality, typically intended to fit within short time spans.

## Why it matters

Large development efforts can lose a clear view of progress when reporting centers on documents, activities, or partially complete components. FDD defines progress through completed features and uses domain modeling to create shared structure. Feature teams, inspections, regular builds, and ownership conventions support coordinated delivery.

## When to use it

Use FDD when a sizeable software effort has a rich business domain, benefits from upfront modeling, and needs fine-grained progress visibility. It fits organizations comfortable with explicit technical roles and standards. Smaller exploratory products may find the modeling and role structure heavier than necessary.

## How it works

1. Develop an overall object or domain model collaboratively to establish the shape and vocabulary of the system.
2. Build a hierarchical feature list using small descriptions of client-valued functions.
3. Plan by feature, considering business priority, dependencies, effort, ownership, and delivery sequence.
4. Form a feature team to design a selected set of features, inspect the design, and prepare the work.
5. Build by feature, inspect code, test it, and promote the completed feature into the regular build.

## A practical example

An insurance platform team models policies, claims, parties, and payments. Its feature list includes “calculate a claimant’s deductible” and “record an adjuster’s decision.” A temporary feature team designs the deductible behavior across relevant classes, inspects the design and code, runs tests, and adds the completed feature to the shared build.

## Where it breaks

FDD’s role model, domain-model emphasis, and individual class ownership can conflict with collective ownership or rapidly changing product discovery. A feature list may fragment end-to-end customer outcomes into technical slices. Progress reporting is only trustworthy when “complete” includes integration and testing, and the method offers less guidance for continuous discovery and organizational change.

## Common mistakes

- Writing features as technical tasks rather than observable client-valued functions.
- Reporting partially designed or coded features as completed progress.
- Treating the initial model as fixed instead of evolving it with learning.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/feature-driven-development/#visualization-feature-driven-development>)

## Sources

1. [An Interview with FDD Creator Jeff De Luca](<https://www.it-agile.de/fileadmin/docs/FDD-Interview_en_final.pdf>) — it-agile · Primary author interview
2. [Feature-Driven Development—Practices](<https://www.khoury.northeastern.edu/home/lieber/courses/csg260/f06/materials/papers/fdd/pg2fddch03.pdf>) — Northeastern University · Book chapter archive
3. [What Is Feature-Driven Development?](<https://www.techtarget.com/it-infrastructure/definition/feature-driven-development-FDD>) — TechTarget · Professional reference

## Related topics

- [Extreme Programming](<https://wiki.soroush.uk/topic/extreme-programming/>)
- [Dynamic Systems Development Method](<https://wiki.soroush.uk/topic/dynamic-systems-development-method/>)
- [Agile Product Development](<https://wiki.soroush.uk/topic/agile-product-development/>)
