A Practical Guide to Feature Driven Development (FDD): From Theory to Application (PDF Resource Included)

Every credible "Feature Driven Development PDF" structures its content around these five collaborative processes. Here is the practical, condensed version.

  • Who: Developer + code inspector
  • Output: Working, tested feature + code inspection report
  • Timebox: ≤ 6 hours coding + 1 hour inspection

| 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 | a practical guide to feature driven development pdf

a practical guide to feature driven development pdf

Please rotate your device!

a practical guide to feature driven development pdf

PLEASE MAKE YOUR BROWSER WINDOW TALLER!

  • Please use your browsers view preferences and either choose “Actual Size” or “Zoom Out” or “100%”
  • Click and drag your browser window’s bottom
    edge to make it taller