Desenvolvimento ágil FDD

Summary

Feature-Driven Development (FDD) is an Agile methodology that emphasizes delivering quick, client-focused results through regular, incremental feature updates. Developed by Jeff De Luca in the late 1990s, FDD prioritizes functionality over traditional system breakdowns, with continuous testing and delivery of features. It is designed to work for teams of all sizes, ensuring stakeholders' needs are met with clear, measurable progress. The methodology integrates quality assurance, domain modeling, and effective team collaboration, with key roles like project manager, chief architect, and development team working together to deliver high-quality software efficiently.

Takeaways

• 😀 FDD (Feature-Driven Development) was created by Jeff de Luca in the late 1990s, initially used in large-scale banking systems.
• 😀 FDD focuses on 'development driven by functionality,' where each feature is developed and tested independently before being delivered to the client.
• 😀 The methodology is customer-centric, aiming to deliver value through early and frequent deliveries of working features.
• 😀 FDD involves consistent application of quality metrics throughout the development process to ensure high standards.
• 😀 Regular deliveries of small, functional features allow clients to track progress and provide feedback during the project lifecycle.
• 😀 FDD accommodates both small and large teams, making it versatile and adaptable to different project sizes and complexities.
• 😀 The development process in FDD starts with domain object modeling, where the system is modeled by the entire team using UML.
• 😀 The methodology is based on four main practices: domain object modeling, feature-driven development, regular deliveries, and team formation.
• 😀 Teams are structured around specific features, with roles like project manager, domain architect, modeling team, and feature developers.
• 😀 Code ownership is emphasized, with developers managing code quality, using version control systems, and ensuring proper configuration management.
• 😀 Progress and performance are tracked using graphical reports, offering insights into bottlenecks, progress, and areas for improvement.

Q & A

What is Feature-Driven Development (FDD)?

Feature-Driven Development (FDD) is an agile methodology that emphasizes building software by focusing on specific, well-defined features. It was developed in the late 1990s by Jeff De Luca and is used to deliver high-quality results quickly, with frequent testing and client involvement.

Who created FDD, and when was it developed?

FDD was created by Jeff De Luca in the late 1990s, around 1997/98. It was first applied in a banking system but later became widely used in various industries.

How does FDD differ from other agile methodologies?

FDD differs from other agile methodologies by focusing specifically on delivering features. It structures development around a list of defined features, which are tested and delivered regularly, allowing for clear, measurable progress.

What is the main goal of FDD from a customer perspective?

The main goal of FDD is to provide customers with meaningful, tangible results early and continuously. It focuses on delivering features that add value to the client and ensuring their satisfaction with frequent releases.

What are some key benefits of using FDD?

FDD benefits include rapid and frequent delivery of working features, clear visibility into progress through graphical tracking, high customer satisfaction, and quality control through continuous testing and metrics.

What is the role of the Project Manager in FDD?

In FDD, the Project Manager is responsible for overseeing the project, ensuring it stays on track, and acting as the main point of contact between the development team and the client.

How does the team structure work in FDD?

The team in FDD is structured around the different roles required for the development of features. Key roles include the Project Manager, Chief Architect, Modeling Team, Feature Teams, and Configuration Management. Teams are formed based on domain expertise and functionality needs.

What is the significance of Domain Object Modeling in FDD?

Domain Object Modeling in FDD is crucial for creating a shared understanding of the system. It involves analyzing, modeling, and defining the system collaboratively with the whole team, ensuring alignment with business goals.

How does FDD handle testing and quality assurance?

FDD places a strong emphasis on quality through continuous testing. Each feature is developed, tested, and delivered iteratively. Quality metrics are applied from the start of the project to ensure the final product meets client expectations.

What tools and methods does FDD use to track project progress?

FDD uses graphical representations such as progress charts and visual models to track the development of features. These tools help the team and stakeholders monitor progress, identify bottlenecks, and improve efficiency.