Assign features to feature teams in time-boxed iterations. Who: Project Manager, Chief Programmers. Duration: 1–2 days per iteration planning.
In the crowded landscape of Agile methodologies—Scrum, Kanban, XP, Lean—one framework consistently delivers for large-scale, long-term enterprise projects, yet remains under-discussed: .
FDD operates on a rigid but highly effective sequential lifecycle consisting of five core processes. The first three processes establish the foundational framework, while the final two processes repeat iteratively until project completion.
Decompose the domain model into client-valued features. Who: Chief Programmer, Project Manager. Duration: 1–3 days. a practical guide to feature driven development pdf
FDD defines distinct roles to ensure clear accountability and eliminate bottlenecks in large-scale projects.
This is where the "rubber meets the road." You assign ownership of features to specific developers (called ), establish dependencies, and schedule them for sequential iteration. Jeff De Luca is famously anti-collective ownership, stating, "Collective ownership is code for 'no ownership'." FDD relies on individual class ownership to maintain integrity as the codebase scales.
Strict version control tracks changes across all classes and ensures that completed features can be built cleanly. Assign features to feature teams in time-boxed iterations
Prevents the "tragedy of the commons" in code. Because every class has a designated owner, code quality, consistency, and refactoring are fiercely guarded.
If you are compiling this information into a downloadable corporate PDF guide, use the following layout standard: Executive Summary & FDD Manifesto.
FDD provides a highly structured approach to agility, making it an excellent choice for organizations that require rigorous tracking, clear ownership, and scalable architecture without sacrificing the speed of iterative delivery. Decompose the domain model into client-valued features
In this stage, the project manager and chief programmers assign features to developers. Unlike other Agile methods where teams are cross-functional, FDD utilizes —developers responsible for specific pieces of code—and Feature Teams —temporary groups formed to complete a specific feature. 4. Design by Feature
A fully tested, functional piece of software promoted to the master system build. 3. Roles and Responsibilities in FDD