James Taylor's Decision Management

Third change in Application Development 2.0 iterate don't finish.
One of the biggest problems in systems is an obsession with finishing. IT departments want to get systems off their lists, budget people want to know how complete things are and business people want to know that everything is done. Yet this is a fallacy - systems are never done. Business changes, environment changes, people change and so systems must change too. Building and organizing for iteration - constant change and improvement - is far more effective than marching towards some kind of finish. Use Agile techniques, adopt technology like business rules that handle this "change time" well and change your thinking.
Here's a couple of links you might enjoy:

• Agile decisioning
• Don't forget decisions when using business rules and business processes
• Live from Brainstorm - Achieving Operational Excellence with BPM