Feature-Driven Development

Any good process is the cohesive blend of a number of industry best practices, techniques, strategies and patterns. FDD is no exception. FDD includes the use of the following best practices:
Most, if not all, of the best practices in the list have had whole books written on them. Chapter 3 in A Practical Guide... is intended to very briefly introduce each practice and explain just a little why that practice is part of the FDD processes. It is also the first really contentious chapter in the book because it advocates upfront domain object modeling and class ownership; practices that eXtreme Programmers reject, sometimes vehemently. Use case fans may also be disturbed by the lack of a mandatory use case writing activity and the emphasis instead on a hierarchical list of tiny client-valued functional requirements (features).

An early draft of part of this chapter was published as an issue of the old CoadLetter newsletter.