I just completed my first project using (a bastardization of) FDD.
The project was small, so I felt like I could leave out some pieces of FDD without too much impact.
Mostly I skipped through Process #1, #2, & #3 quickly and did a lot of reiterative design at each #4. However the real negative impact on the project came because I skipped the validation steps on #4 & #5.
Now, I'm beginning a 2.0 release of the project and am hoping to adher more strictly to FDD. Since I'm just starting to "Develop an Overall Model" I figured I should get some feedback.
The first thing I think I'll wrestle with is when I try to capture the customer's Wish list for 2.0 as a Feature list.
There are three main Objects in the application (Hold, HoldAvp, and Ware - as background, this is a QA Hold application for manufacturing).
The original intent was to have defect information associated with a Hold instance. The customer has asked to associate multiple defects with each Hold. After talking with the domain expert, it is clear that they actually want a defect per instance of HoldAvp. From a modeling perspective, it is clear what they want. However, this feature(set) will be too large for a single iteration.
Can anyone provide some hints on how to go about breaking this featureset into individual features?
Any help is appreciated. I'm reading as much as I can; but since I'm on my own trying to implement this methodology (if it's successful we might adopt it for all projects) I'm just trying to get as much feedback as possible.