Rethinking Agility in Databases

Part VI: Structure and Information, Revisited

Fri, 09 May 2008 22:43:21 GMT

By Max Guernsey, III - Managing Member, Hexagon Software LLC
A new discussion of how structure, behavior, data, and information relate in the database world.

Part V: Collaboration

Fri, 28 Mar 2008 10:25:15 GMT

By Max Guernsey, III - Managing Member, Hexagon Software LLC
A discussion of how the need for collaboration doesn't change between Agile software and databases.

Part IV: Change

Sat, 08 Mar 2008 22:46:29 GMT

by Max Guernsey, III - Managing Member, Hexagon Software LLC
Ruminations on the nature of change in the database world as opposed to in the software world.

Part III: Testing

Fri, 29 Feb 2008 19:03:31 GMT

By Max Guernsey, III - Managing Member, Hexagon Software LLC
We consider how current testing practices apply to the database world.

Part II: Builds & Deployment

Mon, 25 Feb 2008 17:48:21 GMT

By Max Guernsey, III - Managing Member, Hexagon Software LLC
Here we talk about how we should think of database creation. Many of us currently think of it as an operational concern. This can lead to a number of stumbling blocks when attempting to introduce agility...

Part I: Evolution

Sat, 23 Feb 2008 11:57:11 GMT

By Max Guernsey, III - Managing Member, Hexagon Software LLC
In this installment we discuss what I think is one of the most central and least portable practices: evolutionary development. Why is this so important? It's the practice that let's designs emerge. Without the ability to change our design for the better, we have to plan for every kind of variation; if not every variant. Why does it not work with data? Simple: databases don’t evolve.

A New Series: Rethinking Agility in Databases

Sat, 23 Feb 2008 03:29:29 GMT

Author: Max Guernsey, III - Managing Member, Hexagon Software LLC
We cannot simply reapply the Agile practices we have developed for software development to databases. Instead, we need to reduce these practices to their essence - the principles which underly them. From those principles, we can then rebuild practices for databases.