Domain Object Modeling refers to the collaborative process of creating visual models that represent the domain and its various components. The models comprise entities, relationships and attributes, and provide a shared understanding of the problem domain among the project stakeholders. Using these visual models, team members can ensure that the system being developed reflects reality and context of the business. The modeling process helps to identify necessary features and provides a foundation for the subsequent steps in the Feature Driven Development process.

Developing by Feature is the core principle of Feature-Driven Development. This approach promotes breaking down the system into smaller, manageable units of work, known as features. Each feature represents a functional requirement or user story that contributes value to the system. Developing by Feature enables teams to build the software incrementally, allowing for rapid delivery of functionality, easier tracking of progress, and improved adaptability to changing requirements. By focusing on delivering features, the team can stay aligned with customer priorities, and ensure that the system built meets the needs of its users.

Individual Class Ownership is a concept in Feature Driven Development that promotes code quality and maintainability by assigning responsibility for individual classes to developers. In FDD, the responsibility for designing, implementing, and maintaining a class is assigned to a single developer, ensuring that there is a clear point of contact for questions or changes related to the class. This ownership fosters a sense of pride and accountability in the work of each developer, driving them to produce high-quality code and making it easier for the entire team to work collaboratively.

Feature Teams are small, cross-functional units formed to focus on the planning, design, and implementation of features within a project. Comprised of members from various disciplines, such as developers, testers, and business analysts, these teams promote collaboration, communication and fast decision-making. Feature Teams work to rapidly deliver features to customers in an iterative manner, closely following the principle of Developing by Feature. Team members continually assess and refine their efforts, enabling them to respond quickly to feedback and adapt to changing requirements, ultimately ensuring a high-quality and relevant product.

Inspections are a technique used in Feature Driven Development to ensure the quality and accuracy of code, designs, and other project deliverables. Regular inspections involve the review and evaluation of features, code, or other work products by a team of qualified peers. The inspection process helps to identify defects, misunderstandings, and areas for improvement, enabling the team to address issues early in the development process. Inspections can be both formal and informal, creating a culture of continuous learning and improvement within the team and ensuring a high level of quality in the final product.

The FDD Process Model refers to the five-step approach used in Feature Driven Development. The first step is Develop an Overall Model, where a high-level model of the domain is created to establish a shared understanding of the system. The second step is Build a Features List, where features are identified and grouped under subject areas. The third step is Plan by Feature, where a project plan is developed based on feature sets and priorities. The fourth step is Design by Feature, which involves creating detailed design drawings for each feature, including class diagrams and interaction diagrams. The final step is Build by Feature, where developers build and integrate the features following the designs, and ongoing code reviews and inspections are conducted. This iterative process ensures continuous improvement and accurate development according to client requirements.

Feature Decomposition is the process of breaking down requirements into small, manageable parts known as features. Features are client-valued, functional elements, usually representing user actions or visible system behavior. Decomposing requirements into features facilitates accurate estimation, prioritization, and efficient development. The process involves identifying the subject area, which is a logical grouping of features, and then finding various features within each subject area. Each feature is described in terms of an action, a result, and the subject area it belongs to. Feature Decomposition ultimately allows the team to develop and deliver incremental value to the client throughout the project.

The Chief Programmer is a key role in Feature Driven Development, responsible for coordinating the development process and ensuring technical excellence. This individual has deep technical expertise in software development and often has a strong architectural knowledge base. They are responsible for driving design decisions and leading the team through the FDD process, including design by feature and build by feature. They also facilitate code inspections and act as mentors to the development team. These individuals are often highly experienced developers who possess strong leadership qualities and have demonstrated an ability to deliver high-quality software on time and within budget.

FDD Progress Tracking is the process of monitoring and visualizing the development progress of features in an FDD project. The tracking board, or Feature Completion Chart, is a visual tool that allows teams to track the status of each feature, enabling better visibility of the current state of work and completed tasks. This board includes columns for feature sets, planned features, implemented features, completed inspections, and approved features. This transparency aids in communication, ensuring that all team members are aware of progress and can make informed decisions regarding scheduling, prioritization, and scope adjustments. Furthermore, progress tracking enables teams to adapt their work patterns based on empirical data, which in turn, promotes continuous improvement and efficient project management.

FDD Reporting and Metrics are critical components of an Feature Driven Development project, as they provide important insights into the project's progress and performance. FDD relies on comprehensive metrics that measure the number of features planned, completed, and approved, as well as the amount of work required to complete the remaining features. Metrics such as features delivered per week, feature implementation time per programmer, and code inspection throughput are calculated and analyzed to inform decision-making processes in the project. By evaluating these metrics, project teams can identify areas of improvement, make informed scope adjustments, and revise project plans to optimize efficiency while ensuring the delivery of high-quality software.