The Benefits of Feature-Driven Development
Feature-Driven Development is not nearly as well known as other Agile software development methodologies like Scrum, Kanban, and Extreme Programming. This is unfortunate because it has some distinct advantages over other Agile methodologies, especially for the development of large and complex systems.
Publication Date: 15 January 2024
Feature-Driven Development (FDD) is a relatively unknown Agile software development model. It is not nearly as popular as other Agile methodologies like Scrum, Kanban, and Extreme Programming, and you would be forgiven for having never heard of it. However, Feature-Driven Development has specific advantages over its better-known Agile family members, and these advantages make it an exceptionally good development model for large and complex systems.
Like other Agile methodologies, Feature-Driven Development focuses on rapidly and regularly delivering small, tangible sets of usable software to users, until an entire system has been delivered. Unlike other Agile methodologies, however, FDD requires a high-level model of the final system, a full list of system features, and a development timeline to be created before any iterative design and development work begins. This difference from other Agile methodologies makes Feature-Driven Development a much better methodology for large and complex development efforts.
Feature-Driven Development has two major advantages over other Agile development methodologies. First, FDD is much easier to scale than other Agile methodologies. Since the FDD process begins with high-level modeling of the entire system and determination of all system features, system development work can easily be spread across large teams, with parallel development work happening on different features at the same time, and all developers working towards the same well defined and documented final system state. Moreover, since FDD decomposes the overall system to be built into small, discrete features, it is easy to accurately monitor overall build progress in terms of the number of features built, in progress, and not started.
In addition to being highly scalable, Feature-Driven Development has the potential to dramatically reduce rework on large and complex projects. Unlike other Agile methodologies, FFD defines at a high level the overall system to be built at the start of a project. This allows developers to understand the entire scope of a system, and where the piece they are building fits within the final whole, while they are doing their development work. As such, Feature-Driven Development allows developers to take future build work into account while they are iteratively designing and developing system features in a way not allowed by any other Agile methodology. FFD therefore allows developers to plan for future system development while they are building current system functionality, and this has a tremendous potential to reduce the rework and refactoring so often associated with Agile development.
While Feature-Driven Development is a great methodology for large and complex projects, it might not be the best methodology for smaller projects because these projects will not greatly benefit from parallel development and do not run a high risk of significant rework. Similarly, FFD is probably not the best option for any project in which minimizing the time to the delivery of first system functionality to users is a primary objective. But for all other projects, Feature-Driven Development is a fantastic option that should be very seriously considered.
Feature-Driven Development is a little-known Agile software development model, but it offers significant advantages over more well-known Agile methodologies, especially for the development of large and complex systems. FFD requires more upfront system design work than methodologies like Scrum, Kanban, and Extreme Programming (but much less than Waterfall), but it also scales better than these methodologies and can result in much less rework – which can reduce overall system development time. As such, Feature-Driven Development is perhaps the best Agile methodology for the development of large and complex systems.
Recent Posts
Rules Should Not apply
Some organizational rules are critically important to keeping people safe from harm. Organizational leaders should ensure these rules are always followed. Other organizational rules exist to help staff know what to expect and to keep operations running smoothly. Making project teams working on critical change initiatives follow these rules can often do more harm than good.
The Importance of Traceability
Many software development projects waste time and resources creating system functionality end-users do not want or need while failing to deliver things end-users have specifically requested. Often poor traceability practices are to blame for these failures.
How and When You Communicate Matters
Most organizations understand that communication can make or break a project. Nonetheless, few organizations actually effectively communicate with staff and stakeholders about key initiatives. In particular, many organizations wait too long to communicate with staff and stakeholders and use horribly ineffective channels when they finally do communicate.
It is So Shiny! I Need to Have It!
It seems like every few years some new, must have process or piece of technology sweeps through industries. When this happens, it can very difficult for leaders of organizations to resist the urge to jump on the bandwagon and adopt the newest thing, even if doing so might be in their organization’s best interest.
The Most Important Aspect of Change Management
It can take a lot of time and effort to complete all of the work required by many formal change management methodologies. If an organization has the resources to complete all of this work, it is often very beneficial to do so. However, if an organization does not have the resources to do this much work, significant gains can still be made by focusing solely on the most important aspect of change management.
You Might Also Like
The Importance of Traceability
Many software development projects waste time and resources creating system functionality end-users do not want or need while failing to deliver things end-users have specifically requested. Often poor traceability practices are to blame for these failures.
It is So Shiny! I Need to Have It!
It seems like every few years some new, must have process or piece of technology sweeps through industries. When this happens, it can very difficult for leaders of organizations to resist the urge to jump on the bandwagon and adopt the newest thing, even if doing so might be in their organization’s best interest.
The Misapplication of Agile and the Myth that Waterfall is Dead
The popularity of Agile project management has led some organizations to use it exclusively and declare other project management methodologies like Waterfall dead. This often leads to Agile being used in situations in which a different project management methodology would work much better, and this in turn results in poor project outcomes and disappointed end users.