Hello,
Did anyone use non-standard feature milestones?
I call the standard milestones those described everywhere in FDD docs:
Walkthrough (1%)
Design (40%)
Design Inspection (3%)
Coding (45%)
Code Review (10%)
Promote to build (1%)
If you ever used non-standard ones, can you publish it here along with the reasoning?
Thanks,
Serguei
Hey Everyone,
I gave a FDD lecture last week (29/6/2006) at the Agile Israel User group.
If anyone's interested here are links to the presentation:
PDF - attached to this post.
PPT - http://www.JustinAngel.Net/files/FeatureDrivenDevelopment.ppt
Webcast (WMV) - http://ttvv.tv/users/publicftp/justinangel/webcast-fdd.wmv (hebrew only, sorry)
The presentation decribes:
- why do we need Agile methodlogies
- what are the common problems with Agile solutions
- eXtreme Programming's limitations
- How Feature-Driven Development solves the common agile issues
Hi all
I've embarked on a new web project at work, and have been trying to follow FDD for the initial planning stages. While its going really well, I'm starting to add development time estimates to features, and I've noted that I need to add in time for initial project setup (server, database, etc). This is a common item in our projects, but I can't see anywhere it would fit.
Here's an interesting article on a decision by HP to end telecommuting for part of its workforce.
What's been even more interesting is to read some of the discussion threads about this article around the net.
There's no one right answer here for all cases. There are some roles and some people and some companies for which telecommuting makes a lot of sense and works. And there are others where it doesn't.
Aside from the people and process concerns, I find tools (technology) to be a huge problem here (still). Collaboration tools need to improve significantly - shared whiteboards, shared editors, shared diagrammers, chat and voice tools, and so on, all need to get much better and they need to be more aware of the recording and subsequent publishing needs (this includes classification and tagging for example). There's the issue of firewall and NAT traversal as well.
There's a lot of pain here for vendors to provide relief for...
Finally, and all too expected, there's been some kneejerk negative reactions to the HP article from some so-called Agilists. "Of course we can work remotely." Interesting isn't it that Agile says we should ideally be co-located with the users but some are now saying that the programmers themselves don't need to be co-located with each other. Hmmm... :? :D
Hi, My name is George (Jorge in spanish) Baroudi, i usually develop software in very small teams, and we are adopting FDD as our standar, we have done quite well with all the processes for the last project but, we were thinking about how would it fit a LOC estimation in between planning and the other processes.
Have someone made LOC estimation from a feature list based on past projects?
We are thinking about using an XML representation of the Database and XSL for generating the code based on columns of the tables in the database, and this will be applied to all levels of the different archetypes of the model.
It's interesting to watch people re-invent or re-learn things (the AJAX movement is particularly fun that way right now). Anyway, here's a fun story about Brooks' Law.
We've had several private emails on when the next FDDI update will be. FYI - we're going to be taking this effort in a different direction. One issue is scope and outcome: interchange or report generation? Another issue is implementing and using XSD.
Jeff
We are pleased to announce that the April 2006 release of FDD Manager, which includes the following enhancements, is now available for download.
Seth writes about marketing and this is a very interesting and balanced post about process.
I am looking for a brief listing of steps to be followed if I were to develop a new product using SCRUM Vs FDD. (example, Step 1: Document all your features should be documented in XYZ document Step 2: There should be a consensus meeting every morning etc). Also, are there any publicly available templates for each of these methods on top of which I could develop my own (or use as-is)?
I want to rapidly develop a product devising a method out of FDD and SCRUM and am looking for the consice information about them without a huge description.
Thank you
