Hi everyone,
I'm currently working on a Masters degree, and part of my thesis is going to be an investigation into the preceived failures of agile methodologies from the software development team perspective.
I'm interested in what your views on this are.
Having used FDD a bit, I haven't noted any specific failings, but there are (to me, at least) some very problematic areas in implementing XP, especially from my perspective as a business analyst.
Any help would be awesome.
Thanks
Dominic
When performing process 1 - Develop an overall model - it is advised (..mandated?! :o) to model the underlying domain, bounded by a scope, where 'requirements are a depth check or a validity check of the shape within the scope'. I want to check some of the assumptions about this activity and question the thinking when hit by BPR.
I have been using RUP for the past 3 years and have joined a company that uses FDD. My problem is, I do not know how to approach FDD. I tried reading documents from nebulon web site but I am still not clear.
Can you use UML in FDD ? If yes which diagrams would you use in different stages ?
What actions or steps will you take when you
1. Plan by Feature
2. Design by Feature
3. Build by Feature
Are there any people who are proponents or practitioners of FDD (or adapters of some elements of the FDD process) close to the Atlanta, GA area? I'm interested in any experiences with this methodology.
Martin Westbrook
You are our 1000th registered user.
:-) 8-) :-)
Hi All,
Just a quick question to ask if there is any Sydney FDD SIG?
If not, would there be enough interest in getting one going?
My company is in the process of introducing FDD and I would find it interesting to be able to talk face-to-face to people who have gone through or are going through the same process.
Cheers
Mark Buckley
The Methods & Tools newsletter has just released in its html archive section "Delivering Real Business Value using Feature Driven Development" written by Grant Cause
This article provides a basic overview of FDD.
I have a general question on implementation in the seperation of concerns model.
Having read the semi-finished paper on seperation of concerns in one of the other threads, I'm a little confused on some aspects of its implementation.
For example in my example simple PD, I have say these classes:
Customer <>--- Account <>--- Transaction
I have to deal with these "external" systems: a database, a message queue that will get me legacy information on all 3 objects.
I also have a "service locater" (or factory or whatever, you get what i mean :P) that will link my specific subsystem implementations to my problem domain interfaces.
Hello Jeff:
I have proposed the use of FDD approach for a project in my current organization. Moving from a traditional requirements development process I will appreciate if you can provide some details on the Non Functional requirements development process using FDD.
Thanks,
Can anyone recommend a good tool to manage / track features, feature sets, releases, etc.?
