Agile Process Feature driven development (FDD)
ü
Feature Driven Development was created by Jeff De Luca and Peter
Coad in 1997 to help save a failed banking project in Singapore. They were
attempting to use domain object modelling, which is an object-oriented method,
but the project was too large and there were numerous requirements.
ü
Peter Coad was enlisted to create an evolutionary domain object modelling
method. The result was Feature Driven Development, which emphasized iterative
development, quality, and working software, as well as a flexible and adaptable
project management system and an ease of use by both customers and developers.
ü
Feature driven development (FDD) is highly and short iterative
software development process.
ü
Feature driven development (FDD) focuses to the quality at all the
steps of the agile process.
ü
Feature driven development (FDD) delivers frequent, tangible
working results at all steps
ü
Feature driven development (FDD) Provides accurate and meaningful
progress and status information, with the minimum of overhead and disruption
for the developers.
ü Feature
driven development (FDD) is adored by client, managers and developers
ü It
has roles for project managers, chief architects, development managers, lead
programmers, class owners, and domain experts.
ü Its
four major practices are object-oriented design, iterative development,
inspections, and configuration management. Its deliverables include class diagrams,
sequence diagrams, feature sets, and the software products themselves. Its main
goal is to frequently produce tangible, high-quality working software. Feature
Driven Development uses the values of agile methods and is a close cousin to
Scrum, although not as popular.
Benefits of FDD
ü
FDD decomposes or breaks down the entire project domain into small
projects, which can be solved in a small period of time, usually 2 weeks
decomposed tasks independent to each other reduces the need of communication.
ü
FDD splits the project so that it will be fit in an iteration
process and the timeline between analysis and test is reduced early discovery
of errors reduces the cost of fixing the errors.
ü
In FDD concept of Quality is broadened so as not just to test the
code, but also include things such as coding standards, measuring audits and
metrics in the code.
Phases of the Feature driven development (FDD)
ü
Develop an overall model
ü
Build a features list
ü
Plan by feature
ü
Design by feature
ü
Build by feature.