Skip to main content
Bluecoders
← Tech glossary

FDD

Methodology

FDD = development one feature at a time

FDD (Feature-Driven Development) is an iterative software development method that organizes all work around small features with visible value for the customer, each deliverable within a few days. It was designed in the late 1990s by Jeff De Luca, with Peter Coad, on a large banking project.

The method follows five steps: build an overall domain model, draw up the list of features (phrased like "calculate the total of an order"), plan by feature, design by feature, then build by feature. The last two repeat in a short loop.

FDD belongs to the agile family, but it is more structured than Scrum: it emphasizes upfront modeling, code ownership by developer and precise progress tracking. It is rarely practiced as such today, but its central idea, splitting work into customer-valued features, can be found in most product teams.

Why it matters when hiring

Little direct hiring impact: few teams apply FDD to the letter. What matters in a candidate is the ability to break a need down into small, useful deliveries, whatever method they cite.

A recruitment need?

Describe what you need. A recruiter from your sector will call you back within 24 business hours.