An iterative and gradual way to deal with programming advancement, Feature-Driven Development. (FDD) is gotten from the Agile system and is viewed as one approach to actualize it. Like Waterfall, FDD is commonly seen as a more established philosophy, a kind of antecedent to present-day Lean/Agile usage. FDD still spotlights on the objective of conveying working programming now and again and is a particular customer driven methodology, making it a solid match for littler improvement groups.
Highlights are a central bit of FDD. Highlights are esteemed customer bits of work that, as indicated by the FDD approach, ought to be conveyed like clockwork.
To deliver substantial programming regularly and productively, FDD has five stages; the first is to build up a general model. Next, form a component rundown and afterwards plan by each element. The last two steps structure by highlight and work by include will require up most of the exertion.
At each progression, status announcing is urged and tracks progress, results, and potential mistakes. Albeit productive reaction to change is one of FDD’s better properties, a comprehension of the customer’s necessities and the general model toward the start of the task can diminish any amazements during advancement.
Furthermore, any element that takes longer than about fourteen days to plan and assemble must be additionally separated into independent highlights until it meets the fourteen-day rule. The unbending structure of FDD makes it less alluring to groups who parity venture driven and break-fix kinds of work.
