Feature Driven Development

I recently read Head First PMP which describes Project Management (PM) in a very visual and understandable way. The book is at the same time the Study Guide for the worldwide acknowledged PMP certificate from PMI Institute. I say this because it makes PM more tangible for people who are new to this field.

Hi to every one. I'm making an investigation about different methodologies and it's relation with database development, in a software development process. And I want to know how FDD include the database development process in its own methodology and how the FDD development team accomplishes task related to databases.

An interview with Jeff recorded in Hamburg, 2007.

From the se-radio website: "As the inventor of FDD Jeff gives short introduction to the method itself, talks about the basic ideas behind FDD and discusses with us how FDD relates to other members of the agile family."

A presentation on FDD by Henning Wolf at XP Days 2007.

http://www.it-agile.de/fddvortrag.html

This is a stencil for OmniGraffle on Mac OS X. It contains various versions of the four color archetypes to make drawing color models much easier using OmniGraffle.

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

The attached document is a Guide for Chief programmers. The document was written for "Software Architecture and Engineering" course at Harvard University. This year the course is applying FDD to implement the course project. The document describes the typical activities that Chief Programmers perform during FDD iteration.

Cutting content seems to be the prevalent way of meeting deadlines in projects that are running late. But why waste effort and time on things that most likely, will go at the first sign of trouble? Why don’t make the decisions about what is important and what is not up-front, and only start work on the latter if we have the necessary time to do it?

By combining critical chain and incremental development, we can create a plan and execute projects, which guaranties, with a set probability, the delivery of an agreed subset of the total functionality by a stipulated date.

You are the project manager of a large project, testing is uncovering faults, trouble reports (TRs) are starting to pileup, the release date is coming soon. Are they going to be fixed on time? What could you do to help? Are there any bottlenecks? Where should you assign more resources?
Sounds familiar? Have you been there? This article will explain how could you answer these questions by using an old method called Line of Balance in a new way.

This is a recently updated set of slides I use for 60-90 minute FDD overview presentations. These replace the older set at nebulon.com and elsewhere on the web.