Feature-Driven Development

Articles inspired by Feature-Driven Development

• An Introduction to Feature-Driven Development: Part One
  Feature-Driven Development (FDD) is one of the agile processes not talked or written about very much. Often mentioned in passing in agile software development books and forums, few actually know much about it. However, if you need to apply agile to larger projects and teams, it is worthwhile taking the time to understand FDD a little more.
  Read the full article...
  
  
• An Introduction to Feature-Driven Development: Part Two
  Once there is an initial overall model (FDD Process #1), an initial overall features list (FDD Process #2), and an initial overall plan (FDD Process #3) in place, an FDD project is ready to start delivering the required software feature by feature.
  Read the full article...
  
  
• FDD: Processes
  FDD is documented as five processes, each described on no more than one double-sided letter-sized piece of paper.
  Read the full article...
  
  
• FDD: People
  Feature Driven Development defines six key project roles and implicitly suggests a number of supporting and additional roles.
  Read the full article...
  
  
• FDD: Practices
  Like all good software development processes, Feature Driven Development is built around a core set of best practices.
  Read the full article...
  
  
• FDD: Feature Teams
  Sections of code, usually classes in object-oriented programming, all have a specified developer as their owner. When it is time for a feature to be developed, the Chief Programmer forms a new feature team comprising all the developers whose classes used to implement the feature.
  Read the full article...
  
  
• FDD: Packages
  Notes exploring the recording of artifacts produced during the two engine room processes of Feature Driven Development, Design By Feature (DBF) and Build By Feature (BBF).
  Read the full article...
  
  
• Feature-Driven Development to the Rescue
  FDD is targeted at the core problem of software construction; it fits very nicely between existing requirements efforts and formal system testing processes. We take a look at how FDD can help put a project back on track by examining its influence in each activity within the core of a software development project.
  Read the full article...
  
  
• FDD: Projects
  A software process functions within a context, that of a software development project.
  Read the full article...
  
  
• FDD: An Introduction
  Feature-Driven development is an agile, model-centric, business requirements-driven process for developing software invented by Jeff De Luca. FDD is also characterised by an emphasis on quality throughout the process, and timely, accurate, meaningful status reporting and progress tracking for all levels of leadership.
  Read the full article...
  
  
• A Practical Guide to FDD - References
  The books, etc., referenced in A Practical Guide to Feature-Driven Development
  Read the full article...
  
  
• Developer Ailments
  Developers. You got to love them ... or else they leave you ... with a half-coded system and no documentation! Therefore, this is a somewhat light-hearted look at some common ailments that seem to afflict developers throughout the world. All puns and bad jokes are intended. You have been warned!
  Read the full article...
  
  
• Feature-Driven Development and Extreme Programming
  Feature Driven Development was introduced in Chapter 6 of the book, Java Modeling in Color with UML. Mac Felsing and I elaborated on the topic in our book,A Practical Guide to Feature-Driven Development. Software development process is an emotional issue so here's a few key quotes from the chapter to keep in mind when reading this...
  Read the full article...
  
  
• The Charge of the Light Brigade
  Tennysons poem about the infamous action of the Light Brigade at the battle of Balaclava
  Read the full article...