Knowledge · Rules · Process
Fdd Eight Best Practices
The eight best practices that form the foundation of Feature-Driven Development
Tags
rule
Overview
Purpose
The eight best practices that form the foundation of Feature-Driven Development
Rules
FEBP-001: 1. Domain Object Modeling - class diagrams of problem domain objects
Derived from Fdd eight best practices
Verification: Code review
FEBP-002: 2. Developing by Feature - small, client-valued increments
Derived from Fdd eight best practices
Verification: Code review
FEBP-003: 3. Individual Class (Code) Ownership - one developer responsible per class
Derived from Fdd eight best practices
Verification: Code review
FEBP-004: 4. Feature Teams - dynamic teams formed around features
Derived from Fdd eight best practices
Verification: Code review
FEBP-005: 5. Inspections - design and code reviews for quality
Derived from Fdd eight best practices
Verification: Code review
FEBP-006: 6. Regular Builds - frequent integration to main build
Derived from Fdd eight best practices
Verification: Code review
FEBP-007: 7. Configuration Management - source control and versioning
Derived from Fdd eight best practices
Verification: Code review
FEBP-008: 8. Reporting/Visibility of Results - progress tracking and transparency
Derived from Fdd eight best practices
Verification: Code review