Feature-Driven
INFORMATION
The first real-world application of the Feature Driven Development
methodology was on a 50-person software-development project for a
Singapore-based financial institution, and the first public discussion
of the methodology was in the 1999 book Java Modeling in Color with UML.
Overview
Feature Driven Development (FDD) is an agile framework
that, as its name suggests, organises software development around
making progress on features. Features in the FDD context, though, are
not necessarily product features in the commonly understood sense. They
are, rather, more akin to user stories in Scrum.
FDD Design.
FDD was designed to follow a five-step development process, built
largely around discrete “feature” projects. That project lifecycle looks
like this:
Develop an overall model Build a features list Plan by feature Design by feature Build by feature.
Strengths:
Allows larger teams to move products forward with continuous success Leverages pre-defined development standards, so teams are able to move quickly Simple five-step process allows for more rapid development.Weaknesses:
Does not work efficiently for smaller projects Highly dependent on lead developers or programmers Less written documentation, which can lead to confusion.Downloadable reference material being added in due course.
Downloadable reference material being added in due course.
Downloadable reference material being added in due course.