Feature Driven Development: Five Steps That Ship Software
Feature driven development runs software projects through five processes, shipping each client-valued feature in 2 to 10 days.
§
Feature driven development delivers working software by organizing a project around small features clients value. Planview, consulted November 16, 2026, traces the method to a 1997 Singapore bank project where a 50-person team shipped in 15 months, followed by an 18-month effort with 250 people. Each feature ships in 2 to 10 days, so progress stays visible while work proceeds. Up-front domain modeling pairs with agile iteration, which suits large teams working in complex domains where requirements stay stable enough to model.
Feature Driven Development Runs on Five Defined Processes
Feature driven development runs a project through five processes covering the overall model, the feature list, planning, design, and build. The table below follows the five-process account on developer Kieran Potts’s site, consulted November 16, 2026.
| Process | What the team produces |
|---|---|
| Develop an overall model | Shared domain model built in a workshop |
| Build a features list | Hierarchy of feature sets grouped into business activities |
| Plan by feature | Sequenced work with owners assigned to each set |
| Design by feature | Sequence diagrams plus a refined model for the batch |
| Build by feature | Tested code inspected and merged into the main build |
The first three processes run once at project start, and the last two repeat for every batch of features. Planview, consulted November 16, 2026, puts roughly 75 percent of effort on design and build. Potts’s account dates the first print treatment to Palmer and Felsing’s book of 2002.
How Does the Team Model the Domain Before Coding?
The team builds a shared object model of the domain in a workshop before delivery planning starts. Domain experts and developers shape the model together, using Peter Coad’s modeling in color to separate classes by role. Color categories keep business objects, roles, and momentary interactions distinct on one wall. The model then breaks down into the feature list that drives the rest of the project. Teams new to the workshop format can rehearse it with hands-on programming tutorials.
Who Owns Each Feature on a Large Team?
A chief programmer owns each feature set while individual developers own the classes inside it. The chief programmer leads design and integration for the set and mentors the team doing the work. Small feature teams form for one batch of features and disband after integration, which keeps knowledge moving instead of siloed. No single developer bottlenecks a feature set, because teams re-form around the next batch. Teams that persist object state often pair this ownership with Java object persistence.
When Does This Method Beat Scrum?
This method beats Scrum on large projects in complex, well-understood domains that need coordination. It prescribes both a planning unit, the feature, and an up-front modeling step, where Scrum sets time boxes without engineering practice. Planview, consulted November 16, 2026, contrasts this with Scrum sprints of two weeks and sometimes four, and notes FDD leans on documentation over daily meetings. A chief programmer still reviews each design before the batch moves to build. TechTarget reporter Chris Tozzi laid out the trade-offs on April 17, 2024: cross-cutting rewrites, unclear user priorities, and teams too small for parallel groups all blunt the method. Field notes in lessons learned echo the same warning about cross-cutting work.
Feature Driven Development FAQs
What is Feature Driven Development best used for?
Feature Driven Development fits large teams building complex systems in reasonably well-understood domains. The shared model built up front cuts integration risk across parallel feature teams. Smaller teams gain less, since the coordination overhead outweighs the gains. Use it when the domain stays stable enough to model and the team runs big enough to split.
How fast does Feature Driven Development deliver a feature?
Feature Driven Development delivers each feature in 2 to 10 days, per Planview. Any feature needing more than two weeks of design and build gets split until it fits the rule. That cadence makes progress countable, since finished features form the main metric. Short batches also surface design errors before they spread across the codebase.
What roles does Feature Driven Development define?
Feature Driven Development defines chief programmers, class owners, and short-lived feature teams. A chief programmer leads design and integration for a feature set and mentors the team. Each class belongs to one developer, so changes across classes force owner-to-owner talks. Feature teams assemble for one batch and disband after integration, which spreads knowledge.
What are the limits of Feature Driven Development?
Feature Driven Development struggles with work that cuts across features, such as monolith-to-microservices rewrites or app-wide security hardening. It also stalls when user priorities stay unclear or the team runs too small to staff parallel groups. TechTarget reporter Chris Tozzi described these limits on April 17, 2024. Pick a lighter method when the domain keeps shifting.