Once the design is approved, class owners write the actual code and develop unit tests for their respective classes. After the code passes a peer inspection and successfully integrates into the main build, the feature is marked complete, and the temporary feature team disbands. Tracking Progress in FDD
The FDD life cycle consists of five sequential steps. The first three steps establish the project foundation. The final two steps repeat for every feature.
Prioritize and assign work. The Project Manager and Chief Architects determine the order of operations. a practical guide to feature driven development pdf
Start small: Pick one major module, build a feature list, and deliver one feature every 2 days.
"Design first, code second, inspect frequently." Once the design is approved, class owners write
: Assigning specific code components to individual "Class Owners".
The feature team conducts rigorous peer code reviews. The first three steps establish the project foundation
This structured breakdown eliminates subjective status updates like "the task is 90% done." A feature is either explicitly at a milestone or it is not. FDD vs. Scrum: Key Differences