Feature-Driven Development
Feature-Driven Development organizes model-informed software delivery around small, client-valued features designed and built in short cycles.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/feature-driven-development/
01What 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.[1][2][3]
- 01Develop overall modelDomain experts and developers build shared understanding
- 02Build feature listSmall client-valued functions grouped by area
- 03Plan by featureSequence, ownership, dependencies, and milestones
- 04Design by featureInspect the model and prepare a small feature set
- 05Build by featureImplement, inspect, test, and integrate
- 06Update progressCompleted features inform the next plan
FDD provides a structured feature cadence; it still needs real customer evidence, modern engineering controls, and adaptation to product uncertainty.
02Why 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.
03When 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.
04How it works
- Develop an overall object or domain model collaboratively to establish the shape and vocabulary of the system.
- Build a hierarchical feature list using small descriptions of client-valued functions.
- Plan by feature, considering business priority, dependencies, effort, ownership, and delivery sequence.
- Form a feature team to design a selected set of features, inspect the design, and prepare the work.
- Build by feature, inspect code, test it, and promote the completed feature into the regular build.
05A 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.
06Where 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.
07Sources
- An Interview with FDD Creator Jeff De Lucait-agile · Primary author interviewAn Interview with FDD Creator Jeff De Luca
- Feature-Driven Development—PracticesNortheastern University · Book chapter archiveFeature-Driven Development—Practices
- What Is Feature-Driven Development?TechTarget · Professional referenceWhat Is Feature-Driven Development?