Please explain Feature Driven Development in a nutshell?

My Business Analyst calls their documentation FDD, but it just seems overwhelmed by details.

In a Nutshell
An 'in a nutshell' example would be good, since I'm trying to reduce unnecessary detail and confusion. I want to add clarity, and an Occam's' razor approach to the documentation.

Thanks for your help,

Here's what I found

  • "good"? Define "good" please. You have a resource. What's not "good" about it? – S.Lott Apr 26 '11 at 10:05
  • 1
    Does anybody wish to help me understand Feature-Drive-Development? – DisEngaged Apr 26 '11 at 11:33
  • 1
    @FXquincy: Define "good" please. You have a resource. What's not "good" about it? What don't you understand? What more do you need? What part confuses you? We don't know what it takes to help you understand. We don't know you very well. – S.Lott Apr 26 '11 at 11:46
  • corrected, see question – DisEngaged Apr 26 '11 at 13:29
  • @FXquincy: Define "good" please. You've amplified what you want, but we still don't know what you consider "good". Detailed? Expensive? Long? Short? Color Graphics? Animations? – S.Lott Apr 26 '11 at 14:44

There's an entire website dedicated to the subject: http://www.featuredrivendevelopment.com/ it even recommends books.

Maybe your Business Analyst could share a little of his/her knowledge with you? Asking questions is a strength.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.