Model → Cart , Order , Payment , Inventory . Week 2: Feature list (42 features). Example: Calculate shipping cost , Apply discount code , Authorize credit card . Week 3–6: Four two‑week cycles. Each cycle delivers 8–12 working features.

: A high-level domain model is created by domain experts and developers to provide a shared understanding of the problem space.

This is the beginning of the repetitive cycle.

The project manager and Chief Programmers assign features to development waves. This planning phase accounts for feature dependencies, system complexity, and team workload. It also assigns class ownership to specific developers. 4. Design by Feature

This book is widely considered the definitive manual for Feature-Driven Development (FDD), authored by the architects who created the methodology. It serves as both a conceptual deep dive and a boots-on-the-ground execution guide. The Core Philosophy

The Problem : A highly skilled developer becomes a blocker because they own too many critical classes.

Oversees the administrative side and budget.

Do not rewrite your entire architecture overnight. Pick a specific, complex module within your current project (e.g., "Billing" or "User Permissions") and apply FDD only there. Step 2: Run the Walkthrough. Hold a 2-hour domain walkthrough with the Chief Architect and domain experts to draft the initial model. Step 3: Decompose the Feature List. Use the "Feature" format: Action + Result + Object . (e.g., "Calculate the total of the shopping cart "). Step 4: Feature Ownership vs. Shared Code. Assign a primary owner to every class the feature touches. This owner drives the design and inspection. Step 5: The Two-Week Rule. If the planning reveals a feature will take more than 10 working days, stop. You have not broken it down enough [9†L36-L37].