Feature Driven Development

Hi,
it-agile (http://www.it-agile.de) translated the FDD processed to German.

It is downloadable as PDF.

Stefan

Microsoft MVP Donald Belcham to Speak on Visual Studio, C# vNext, Aspect Oriented Programming, Live Mesh

Hi,
I am going through the FDD process
As i was going through one of the hey processes Designing By feature , i was looking at some of the examples for FDD Overall Object Model after Task 5 i.e. Refining the Object Model but i would like to know if anybody has got an Ideal Object Model going by the key points addressed in the task
It would prove to be the sample Object Model while developing my model.
Kindly request somebody to help regarding the same.
Divya

Would like to hear experience of other PMs on MDM & CDI based initiatives with in their organization. What worked for them and what did not.

Click to read a user story of domain modeling Domain modelling using color uml

All,

I have been reading all about FDD, Agile, SCRUM, etc. I think these are all useful and can be applied successfully to many types of projects, however; I cant find any real data that shows that these approaches actually work. I am not talking about anecdotal data, but rather quantitative data that shows that these approaches are truly beneficial.

I attended the Agile 2008 conference in Toronto Canada. This is a post to discuss what I saw and didn't see at the conference. I personally spoke to about 15% of the attendees.

What I did observe:
1. Toronto is a beautiful city; New York wishes it could be this nice.
2. Scrum is what the practitioners see as the most agile of methodologies. Two days of classes will make you a Scrum master. When scrum grows up it wants to be FDD.
3. XP has some good parts; but I see them as just good solid programming practices that Cheif Programmers teach and coach on a project.

Hi,
I understand that FDD really works well when you are trying to built something that is pure coding. However, what if you have other systems which interact with each other in the domain model. In a use case diagram these systems would be considered actors.

Thanks

Hi,
I have read about FDD and I like it. But before you start a project you have to get requirements from the client. I noticed that with FDD it starts with the domain modeling of course this domain modeling is built by getting information from the initial requirements.

What kind of requirement type best suites FDD for the initial requirements phase. Once I get to the domain modeling I understand how to do features, but features get their input from the domain modeling and the initial requirements, right?

FDD is many things but you can distill it down to these two things.

1. It says you take the time to establish a clear target to hit first. This is the essence of the startup processes. The modeling process is an informational/analytical activity to give enough understanding so that a project baseline can be set; a baseline with good coverage and good accuracy. The PM view of that is being able to answer questions such as "how far along are you" and "how far is there left to go." The developer view of that is the understanding and context for construction; see see point 2 next.