: Stephen R. Palmer & John M. Felsing Published : February 2002 | Pages : 304 | ISBN : 0130676152 This is the definitive book on FDD. It combines the speed and flexibility of Agile with model-driven techniques that scale to the largest teams and projects. The book includes practical, hands-on coverage of all five key FDD activities: developing an overall model, building a feature list, plan by feature, design by feature, and build by feature. It also offers specific guidance on adapting FDD to many different types of projects. PDF versions of this title are available through various academic and technical book platforms.
FDD is for the team that wants to spend less time talking about work and more time shipping it. It is a discipline of clarity, where the code serves the feature, and the feature serves the user.
Every practical guide to FDD has hidden warnings. Here are the top three ways to fail at FDD:
The lifecycle of an FDD project is divided into five highly structured, sequential processes. While the first three processes occur upfront to establish structure, the final two processes repeat iteratively for every single feature. a practical guide to feature driven development pdf
Deconstruct the domain model into distinct functional areas.
“Apply discount code to an order.”
The Chief Programmer forms a temporary "Feature Team" composed of the class owners required to implement these features. The team designs sequence diagrams, refines the object model, and conducts a formal design review. : Stephen R
After design approval, the feature is built, unit tested, inspected, and integrated into the main build. Any issues are fed back into the design. Once a feature successfully passes its inspection and testing, it is promoted to the main build.
: The feature is implemented, tested, and promoted to the main build. Integrated Best Practices
The project manager and Chief Programmers assign features to development waves. This planning phase accounts for feature dependencies, system complexity, and team workload. It also assigns class ownership to specific developers. 4. Design by Feature It combines the speed and flexibility of Agile
Benefits:
+-----------------------------------------------------------------+ | 1. Develop an Overall Model | +-----------------------------------------------------------------+ | v +-----------------------------------------------------------------+ | 2. Build a Features List | +-----------------------------------------------------------------+ | v +-----------------------------------------------------------------+ | 3. Plan by Feature | +-----------------------------------------------------------------+ | +-----------------------+-----------------------+ | | v v +-------------------------------+ +-------------------------------+ | 4. Design by Feature | <----------> | 5. Build by Feature | +-------------------------------+ +-------------------------------+ 1. Develop an Overall Model
In FDD, a feature is not a massive epic or a vague user story. It is a small, piece of client-valued work expressed in a strict grammatical format: