This chapter is from the book
This chapter is from the book
This chapter is from the book
Summary
FDD blends a number of industry-recognized best practices into a cohesive whole. The best practices used in FDD are:
Domain Object Modeling—a thorough exploration and explanation of the domain of the problem to be solved, resulting in a framework within which to add features.
Developing by Feature—driving and tracking development through a functionally decomposed list of small, client-valued functions.
Individual Class Ownership—having a single person who is responsible for the consistency, performance, and conceptual integrity of each class.
Feature Teams—doing design activities in small, dynamically formed teams so that multiple minds are always applied to each design decision, and multiple design options are always evaluated before one is chosen.
Inspections—applying the best-known defect-detection technique and leveraging the opportunities it provides to propagate good practice, conventions, and development culture.
Regular Builds—ensuring that there is always a demonstrable system available and flushing out any integration issues that manage to get past the design and code inspections. Regular builds provide a known baseline to which to add more function and against which a quality assurance team can test.
Version Control—identifying the latest versions of completed source code files and providing historical tracking of all information artifacts in the project.
Progress Reporting—frequent, appropriate, and accurate progress reporting at all levels, inside and outside the project, based on completed work.