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,