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
The natural
habitat of Scrum and XP-inspired approaches is a small team of skilled and
disciplined developers. It remains a significant challenge to scale these
approaches to larger projects and larger teams. Some have been successful but
many have struggled.
Feature-Driven
Development (FDD) invented by Jeff De
Luca is different. While just as
applicable for small teams, Jeff designed FDD from the ground up to work for a
larger team. Larger teams present different challenges. For example, a small
team of disciplined and highly skilled developers by definition is likely to
succeed regardless of which agile method they use. In contrast, it is
unrealistic to expect that everyone in a larger team is equally skilled and
disciplined. For this and other reasons, FDD makes different choices to Scrum
and XP in a number of areas.
In the
first part of this two-part article, we briefly introduce the ‘just enough’
upfront activities that FDD uses to support the additional communication that
inevitably is needed in a larger project/team. In the second part of the
article, we cover how the highly iterative delivery part of FDD differs from
Scrum and XP-inspired approaches.
Fonte: http://agile.dzone.com/articles/introduction-feature-driven
Fonte: http://agile.dzone.com/articles/introduction-feature-driven
Nenhum comentário:
Postar um comentário