agile programming and agile db design

I am in a place where people peddle agile approach. Four months have passed by, with two teams, each comprising 10 developers, working from two states. No refactoring has done at db level; nor is it going to happen. The shop hired a j2ee caching specialist, and he advised pagination and on-the-fly sorting at db-level, and he parrots scalability. Another snake oil product!

For a query, we have joined 10 tables to get the required for a particular screen. Many other queries need at least 7 tables. When people designed tables in previous iterations, they had no clue about the requirements for the future requirements.

Is this what agile programming and db design is about? Received on Tue Jan 23 2007 - 11:17:22 CST