FDD vs. Scrum

Attribute	FDD	Scrum
Development Process	Iterative and incremental	Iterative and incremental
Roles	Chief Programmer, Domain Expert, Developer, Tester	Product Owner, Scrum Master, Development Team
Meetings	Regular design and code inspections	Daily stand-up meetings, Sprint Planning, Sprint Review, Sprint Retrospective
Artifacts	Feature list, Feature sets, Class ownership	Product Backlog, Sprint Backlog, Increment
Iterations	Feature-driven iterations	Sprints

Introduction

When it comes to software development methodologies, two popular approaches are Feature-Driven Development (FDD) and Scrum. Both methodologies have their own unique attributes and are used by teams to deliver projects successfully. In this article, we will compare the key attributes of FDD and Scrum to help you understand the differences between the two.

Team Structure

In FDD, the team is typically divided into smaller sub-teams, each responsible for a specific feature or set of features. These sub-teams work in parallel to develop the features assigned to them. On the other hand, Scrum teams are cross-functional and self-organizing, with all team members working together on the same set of tasks. This allows for better collaboration and communication among team members in Scrum.

Project Planning

When it comes to project planning, FDD focuses on creating a detailed feature list at the beginning of the project. This feature list is then broken down into smaller tasks that are assigned to the sub-teams. In contrast, Scrum uses a backlog of user stories that are prioritized by the product owner. The team then selects a set of user stories to work on during each sprint, which typically lasts 2-4 weeks.

Iterative Development

Both FDD and Scrum follow an iterative development approach, but the way they implement it differs. In FDD, the development process is broken down into short iterations, with each iteration focusing on a specific feature or set of features. This allows for a more structured and predictable development process. On the other hand, Scrum uses sprints, which are time-boxed iterations where the team works on a set of user stories. This allows for more flexibility and adaptability in the development process.

Documentation

Documentation is an important aspect of software development, and both FDD and Scrum have their own approaches to it. In FDD, documentation is created as part of the development process, with each feature having its own design document. This helps in maintaining a clear understanding of the project requirements and design. In Scrum, documentation is kept to a minimum, with the focus being on working software over comprehensive documentation. This allows for faster delivery of features and quicker feedback from stakeholders.

Feedback and Adaptability

One of the key differences between FDD and Scrum is how they handle feedback and adaptability. In FDD, feedback is typically gathered at the end of each iteration, allowing for adjustments to be made before moving on to the next iteration. This ensures that the project stays on track and meets the requirements. On the other hand, Scrum encourages continuous feedback throughout the development process, with regular sprint reviews and retrospectives. This allows for quicker identification of issues and changes to be made in real-time.

Conclusion

In conclusion, both FDD and Scrum are effective software development methodologies that have their own unique attributes. FDD is more structured and focused on detailed planning and documentation, while Scrum is more flexible and emphasizes collaboration and adaptability. The choice between FDD and Scrum ultimately depends on the specific needs and requirements of the project. By understanding the key differences between the two methodologies, teams can choose the one that best suits their project goals and objectives.