Feature Driven Development

We are currently moving towards Feature Driven Development and I am looking for templates for a Feature List. Is there a template someone can provide me? Is there a Feature List Matrix that I can use?

I have been reading about the application of FDD for web development, but have noticed people mentioning that FDD doesn't cater to the following important parts of the SDLC,

* Requirements gathering
* Interface design
* Testing
* Deployment

- Is this true?
- What are others doing to cover these steps in FDD?

Tim Bray says W3C XML Schemas (XSD) suck.

Hear, hear!

Here's the link to Tim's blog entry.

And here's a link to Slashdot thread on the topic.

Here's a couple of related posts well worth reading.

The first by James Bach.

...Actually, I have had many clashes with people who claim to own the word agile. It’s not just Brian. But some agilists in the capital “A” camp don’t limit themselves to it. Ward Cunningham is a great example. Find Ward. Meet him. Talk to him. He gives agile methodology a good name. I have had similar positive experiences with Alastair Cockburn and Martin Fowler.

There are at least two agile software development communities, then. My community practices agile development in an open-ended way...

Here's an interesting post by James Coplien. link

This may be a silly question but is there another name for the Parking Lot Chart? We've mixed our Agile practices using Scrum and the Parking Lot chart for project communication. It's just that "Parking Lot" has become a term that signifies a story or other task that is sitting off to the side waiting for someone to get to it.

The Parking Lot Chart however is a great tool to communicate the "active" status of an Agile project. I don't want the people who I communicate with to get confused that anything in this chart is "waiting" on anything.

Anyway, just wondering if there's an alternative name for this fantastic tool.

We are planning to move towards scrum based approach for software development. However the thing that is still unclear is how can the testing process be adopted in the Scrum approach. It seems to be easier to break features into tasks based on dev resources available and start and end of a Sprint. Would QA typically start after the first dev Sprint 1 is completed? If so, the challenge would the testing volume may not same always but they start and end date for QA would have to line up with Sprint 2 of dev cycle and in this case the number of QA resources would never be same in each Sprint. Hope I am making sense.

Hello,

I was actually searching the Internet for issue-based SCM and came upon your site after recalling something about FDD on CmCrossroads.com. I was wondering how 'you' define FDD and how it differs from issue-based software change and configuration management (SCM)? I've also seen AccuRev Inc. mention issue-based engineering management having integrated SCM with issue tracking.

Does FDDTracker integrate with any other source control tools like AccuRev, Rational Clearcase or PVCS?

Thank you,
Josh

FDDPMA is a free, open source, web-based FDD project management tools.
It is deployed to www.fddpma.net and may be downloaded from sourceforge.net web site.

What's new?
- Implemented export/import according to FDDI specification
- Updated user guide. Read about export/import in chapter 20
- Improved rendering under Firefox browser
- Minor bug fixes and enhancements

Hi All,
I'm new to FDD. I would like to know what is the difference between Key Roles, Supporting Roles & Additional Roles in FDD? Further how do you determine which one role(actor) will go under which category (Key Roles/Suporting Roles/Additional Roles)?
Thanks,
Ritin