>I have to ask... why does it have to be one or the other or one over >the other? And why does it even matter if they are the opposite of >each other, if that's even true?
Agreed. My perception of "feature driven development" is that you build
the product incrementally, one feature at a time. Hopefully the first
feature you build is the most important one. This does not mean in any
way that the feature can't be a result of solid UCD research.
My shop is Agile right now, and we're making UCD work. UCD and feature
driven development can and should coexist. I don't think they are
opposites at all.
BTW - is my perception of feature driven development correct?