Feature Driven Development (FDD)

-

Overview:
A quick overview of Feature Driven Development (FDD)—an iterative software development methodology intended for use by large teams working on a project using object-oriented technology.

What is FDD?
Feature Driven Development (FDD) is an iterative software development methodology intended for use by large teams working on a project using object-oriented technology. The methodology description includes some prescription about what tasks should be done and what roles should be doing them, so many do not consider it a truly agile methodology.

Why is FDD useful?
FDD is useful because it demonstrates that you can focus on domain modeling on an iterative and incremental project, and because it demonstrates that agile-like methodologies can scale. FDD shows that teams can spend a short amount of time at the beginning of the project to establish a clear understanding of the domain in which they are working and use that understanding to formulate a rough plan without getting stuck in analysis and design paralysis.

How to use FDD?
  1. Develop an Overall Model: A team is formed of development team members and people familiar with the business domain to build an overall model of the domain, in order to establish the scope of the system and provide a common understanding the of the domain.
  2. Build a Features List: The team then develops a comprehensive list of features and groups these features into feature sets, and then major feature sets.
  3. Plan by Feature: The team establishes a development plan that includes the order in which feature sets will be realized, which Chief Programmers are responsible for which feature sets, and which Class Owners are responsible for each class.
  4. Design by Feature and Build by Feature: The team launches into a series of Design by Feature and Build by Feature iterations where they break into Feature Teams and design, build, and test features in two-week time boxes.
  5. Repeat step 4 until no more features exist.


The FDD project lifecycle.



FDD also defines a collection of supporting roles, including:
  • Domain Manager
  • Release Manager
  • Language Guru
  • Build Engineer
  • Toolsmith
  • System Administrator
  • Tester
  • Deployer
  • Technical Writer

How would Agile Modeling (AM) be applied on an FDD project? The principles and practices can be clearly applied to FDD's two modeling-oriented steps - develop an overall model and design by feature. The only apparent mismatch between the two processes is FDD's practice of class ownership and AM's practice of collective ownership, but I would argue that this isn't the case. FDD's practice pertains to coding but does not to modeling, on a FDD project people work together in teams to model, along the lines of AM's model with others practice, and therefore several people will be working on your shared collection of modeling artifacts.

References:
Feature Driven Development (FDD)

Comments

  1. Lauren21.9.23

    A quick overview of a feature provides a concise yet comprehensive understanding. It condenses essential information, aiding users in grasping functionality swiftly. How Better Get This efficient approach enhances user.

    ReplyDelete

Post a Comment

Popular posts from this blog

Agile Model

-
Image
Agile Method This article is a introduction to Agile software development methodologies and it's application. This is not only suitable for software developers but also for Team Leaders, Project Managers, Product Managers, Development Managers, Testers, QA Managers, QA Engineers, Technical Writers, UX Designers, anyone involved in the delivering software.It doesn't describe any code or technology it's an method or an software engineering model which helps to develop a tool to it's best requirements or goals. Agile Method is a combination of various sprint cycles initially of 1 to 4 weeks per sprint cycle. Deployment is alligned with the changing business need after the completion of every sprint cycle. Agile adapts of frequent feedback by delivering workable product after every iteration/sprint cycle end. In other words Agile Method is a series of short iteration/sprint cycles. Agile Model is an incremental version of multiple waterfall model cycle so,br the cha...
Read more

How to verify systems designed in Business Analyst

-
Image
Verification is what most people think of when they hear the word testing — it’s the process of testing whether a business analysis solution does what it’s designed to do. During verification, the testing team (which may consist of developers, quality assurance [QA] people, and some business analysts [BAs]) put the software through its paces to both confirm that it operates as expected and ensure that it conforms to the design specifications laid out earlier in the project. Verification testing includes four phases — one pretest phase and three phases of actual testing. Smoke Test Also called a build verification test, a smoke test is a pretest that determines whether full testing can even begin in the first place. It reveals any simple failures in the solution that may prevent you from executing the tests in the next three phases. Some project teams may link this test to unit testing. Unit Test The unit test is the first actual phase of testing. It involves testing each uni...
Read more

WBS - Work Breakdown Structure

-
Image
We have known multiple documents and plans used during project management like scope creep method, product backlog, charts, BRD, FRS and SDD. But to keep a track of project and deliverables we need is a tracker. WBS i.e. Work Breakdown Structure provides a detailed breakdown of tasks, resource requiredness and effort estimation. Depending upon organization how one prepares it i.e. tool used can differ. Commonly used tools are Ms Excel, Smartsheet & Google sheets. With reference to workbreakdownstructure A work breakdown structure (WBS) is a key project deliverable that organizes the team's work into manageable sections. The Project Management Body of Knowledge (PMBOK) defines the work breakdown structure as a "deliverable oriented hierarchical decomposition of the work to be executed by the project team." Dividing complex projects to simpler and manageable tasks is the process identified as Work Breakdown Structure (WBS). Usually, the project managers use this m...
Read more