A Practical Guide - To Feature Driven Development Pdf
A Practical Guide to Feature-Driven Development (FDD)
Version: 1.0
Audience: Project Managers, Chief Architects, and Development Teams
Practical Guide to Feature-Driven Development (FDD)
Process 5: Build by Feature (The Iteration End)
- Goal: Write the code and test it.
- Method:
- Developers write the actual code for their classes.
- Unit tests are written and executed.
- Code is inspected.
- The feature is promoted to the "Build" (integration).
- Result: A tangible, working piece of functionality is delivered.
4. Tracking Progress: The "Progress" Chart
FDD uses a unique reporting method that provides high visibility to stakeholders. It moves away from abstract "story points" and focuses on binary completion. a practical guide to feature driven development pdf
- The Metric: Percentage of features completed.
- The Chart: A "Burn-up" chart (not a Burn-down chart).
- The X-axis is time.
- The Y-axis is the number of features.
- It shows total scope vs. completed features.
- Why it works: Management can see exactly how many features are done. Since features are client-valued, "50 features completed" is a meaningful statement to a business owner.
5. Roles in FDD
| Role | Responsibility | Number per team |
|------|----------------|------------------|
| Project Manager | Track progress, coordinate | 1 |
| Chief Architect | Overall model, feature list | 1–2 |
| Chief Programmer | Design & build by feature, class ownership | 1 per 5–10 devs |
| Domain Expert | Validate model & features | 1–2 |
| Developer | Code, unit test, inspect | Many |
| Release Manager | Build & deployment | 1 | Goal: Write the code and test it
Blog Post Title: From Chaos to Clarity: A Practical Guide to Feature-Driven Development (FDD)