What is Feature Driven Development (FDD)?

Have you ever been stuck in a software development project dragging on forever without any direction or progress? Or have you experienced the frustration of a product you delivered that didn't meet the client's expectations? These are some of the common challenges faced by developers. As I have experienced the same feelings, I would like to share an important remedy for it. One way to tackle these challenges is the (FDD) Feature Driven Development methodology. This client-centric and iterative approach to software development emphasizes delivering work and ensuring that projects are on track and according to the user’s needs. 

In this article, I’ll explain the world of Feature Driven Development methodology, exploring its principles, benefits, and processes. Whether you're an experienced developer looking to optimize your processes or a project manager looking for an effective development methodology, understanding feature driven development can be a game-changer for your software development projects. 

History of Feature Driven Development Methodology

At the beginning of software development, the waterfall method was followed popularly, where the whole development process is arranged as a linear sequence. Every process happens after the completion of the previous process. This method didn’t have any alternative methods initially. 

Later, feature driven development methodology, an agile approach to software development processes, was devised. This approach was initially developed by Jeff De Luca. He devised this methodology to achieve a software development project in Singapore with 50 developers and a 15-month duration in 1997. 

This FDD methodology had many key features, like a customer-centric approach, delivering reliable output, etc.

What is Feature Driven Development Methodology?

Feature Driven Development (FDD) is an incremental and iterative software development process. It is a lean, agile methodology that organizes software development to make progress on the features. In FDD, a feature is a small, client-valued function that can be implemented in less than two weeks.

The primary objective of feature driven development is to deliver tangible, working software repeatedly and promptly. It emphasizes:

• Quality aspects throughout the process

• Short iterations with tangible deliverables

• Frequent releases

• Accurate monitoring of progress and results

How Does FDD Work?

As discussed earlier, it is an iterative process. Here is the working of feature driven development in agile:

1. Gathering Information: 

Like any other project, the first step is to gather all the requirements and get a detailed understanding of the user’s needs and expectations within the scope of the project.

2. Creating Model:

The software to be developed will have a scope that has requirements of the software. The professional head of the project checks the scope and creates the model for the complete process. 

4. Develop an Overall Model

The project starts with a high-level walkthrough of the system's scope and context. Then, detailed domain models are created for each modeling area.

5. Build a Features List

Using the knowledge gathered from the overall model, a comprehensive list of features is created and categorized into feature sets and significant feature sets.

6. Plan by Feature

After the feature list is created, the development sequence is planned. Features are assigned to programmers.

7. Design by Feature

A design package is produced for each feature. Chief programmers select features for development in the next iteration.

8. Build by Feature

The feature is implemented after design inspection. Unit testing and code inspection are performed before it is integrated into the main build.

Key Principles of FDD

Feature driven development is built on several core principles. They are:

• Domain Object Modeling: Using object models to represent the problem domain.

• Developing by Feature: Organizing work based on feature sets.

• Individual Class Ownership: Assigning clear ownership of code to individuals.

• Feature Teams: Forming small, dynamically created teams for each feature.

• Inspections: Conduct regular code and design inspections.

• Regular Build Schedule: Ensuring the system is always buildable.

• Configuration Management: Maintaining version control for all documents and code.

• Progress Reporting: Providing accurate, timely progress reports at all levels.

The Different Roles in Feature Driven Development

There are six primary roles in an FDD team. One person may take up one or more roles. They are:

1. Project Manager

Oversees administrative and financial aspects of the project.

2. Chief Architect

Responsible for the overall design of the system.

3. Development Manager

Leads the day-to-day development activities and resolves any resource issues.

4. Chief Programmers

Experienced developers who participate in analysis and design and lead small teams in feature development.

5. Class Owners

Developers responsible for the design, coding, testing, and documentation of features.

6. Domain Experts

Individuals with deep knowledge of the business domain who provide requirements and review models.

Benefits of Implementing Feature Driven Development

Adopting FDD in your software development process offers several advantages. These include:

• Frequent, tangible deliverables

• Accurate tracking of progress

• Early detection of errors and misunderstandings

• Improved communication with stakeholders

• Flexibility to adapt to changing requirements

• Enhanced software quality through regular inspections

Challenges in FDD Implementation

While FDD offers many benefits, organizations may face particular challenges when implementing it. Some of the major challenges of feature driven development include:

1. Overemphasis on Upfront Design

The initial modeling phase can sometimes be overextended, delaying actual development.

2. Scalability Concerns

FDD may be challenging to implement in massive projects or distributed teams.

3. Dependency on Individual Expertise

The success of FDD heavily relies on the skills of chief programmers and domain experts.

4. Feature Granularity

Determining the right feature size can take time, impacting planning and execution.

5. Cultural Shift

Teams accustomed to other methodologies may need help to adapt to FDD's practices.

Become a Certified Scrum Master in just 2 days!

Download Brochure

 

FDD vs. Other Agile Methodologies

How does FDD compare to other popular agile methodologies?

1. FDD vs. Scrum

While both are iterative, FDD focuses more on the feature lifecycle, whereas Scrum organizes work into fixed-length sprints.

2. FDD vs. Extreme Programming (XP)

FDD emphasizes upfront design and planning compared to XP's focus on continuous refactoring and pair programming.

3. FDD vs. Kanban

FDD has a more structured process with defined roles, while Kanban focuses on visualizing workflow and limiting work in progress.

Best Practices for Effective Feature Driven Development

To maximize the benefits of feature driven development, consider these best practices:

1. Prioritize Features Effectively

Work closely with stakeholders to identify and prioritize the most valuable features.

2. Keep Features Small and Manageable

Aim for features that can be completed within two weeks to maintain momentum.

3. Conduct Regular Design and Code Inspections

This helps maintain code quality and provides learning opportunities for the team.

4. Encourage Collaboration

Foster open communication between domain experts, developers, and stakeholders.

5. Maintain Accurate Progress Reporting

Use tools to track feature completion and provide visibility to all stakeholders.

6. Embrace Iterative Modeling

Continuously refine and update domain models as understanding the problem domain evolves.

7. Invest in Training

Ensure team members understand FDD principles and practices through proper training.

Tools and Technologies Supporting FDD

Various tools can support FDD implementation:

1. Modeling Tools

• Visual Paradigm

• Enterprise Architect

• Lucidchart

2. Project Management Tools

• Jira

• Trello

• Microsoft Project

3. Version Control Systems

• Git

• Subversion

• Mercurial

4. Continuous Integration Tools

• Jenkins

• Travis CI

• CircleCI

5. Code Review Tools

• Crucible

• Gerrit

• GitHub Pull Requests

Real-world Applications of Feature Driven Development

FDD has been successfully applied in various industries and project types. Some of them include:

1. Financial Services

Banks and financial institutions have used FDD to develop complex trading systems and risk management software.

2. E-commerce

Online retailers have employed FDD to iteratively develop and improve their platforms, focusing on customer-centric features.

3. Healthcare

Medical software companies have utilized FDD to create patient management systems and clinical decision support tools.

4. Telecommunications

Telecom companies have applied FDD to develop network management software and customer service applications.

Conclusion

Feature-driven Development (FDD) offers a practical, realistic, client-centric approach to the software development process that can enhance project outcomes considerably. By keeping the main focus on regularly delivering tangible features, feature driven development helps teams maintain the required momentum, adapt to changing requirements, and ensure that the final result is aligned with the user needs. 

The key to successful feature driven development implementation lies in understanding and adapting its principles to the specific project context. It's not about following a set of rules but instead embracing a clear mindset that prioritizes delivering value to the client through tangible and working features.

Whether you're working on a small internal application or a large-scale enterprise software system, feature driven development can provide a flexible yet structured framework for your team’s development efforts. By fragmenting the project into small manageable features, maintaining a strong focus on design and quality, and fostering collaboration between all stakeholders, feature driven development can aid in navigating the complexities of software development effectively.

As with any methodology, the success of feature driven depends on how well it's implemented and adapted to your team's needs. By understanding its principles, investing in proper training can help you be prepared to refine your approach as you gain experience. With the right dedication and practice, feature driven development can become a powerful tool in your software development process, which will help you timely deliver high-quality software that meets your clients' needs.