Agile Data.org

I recently found this website, referred by Brett Morgan's Weblog. The company I work for has been developing (and releasing ;) software to solve this kind of problems since 1989, so it's good to find new people sharing our points of view. 

We are used to the idea that database schemas are static structures that can't be modified. The usual development practice is to build a 'complete' database schema at the beginning of the development cycle and then keep it unchanged. We know that we will have to change that schema later, because the business needs will change, but we try to fool ourselves.

Our idea is that regarding the database, you should proceed in the same way that methodologies like XP suggest. Start with the simplest design possible and then refactor the database when you need to add new functionality. That's the problem our tools try to solve.