amp driven development ampdd in a confined space

Tue, Jul 19, 2011

The following video follows Dan Pink’s talk about motivating creative people and how money doesn’t seem to work. You need AMP (Dan’s term) Driven Design (AMPDD - my terminology):

“Hire good people and leave them alone”

This is all very well and I’ve been doing a lot of this over the years but I’ve come to realise lately that AMPDD only works if the level of chaos in an organisation is below a certain level. AMPDD often crosses departmental boundaries. Developers need infrastructure. They need somewhere to host their carefully developed applications and that’s where AMPDD can break down. I took it upon myself to rewrite the provisioning system I originally developed several years ago in the modern idiom of SOA, messaging and the like. I was doing AMPDD. My boss recognised what good developers can do if they’re left to their own devices, as long as they keep in touch and the boss man keeps a strategic eye on things. AMPDD only works within the organisational strategy. You won’t change direction with AMPDD. You’ll just hit a wall.

But I’ve come up against the boundaries of AMPDD a few times recently where I need hardware (vmware slices) which just aren’t available due to lots of factors outwith my control. It’s at times like these that you look at all the hard work you’ve done and shake your head. Up front requirements for hardware (which are simple) are agreed well in advance but come the day, it’s chaos theory that dictates whether the system goes live on time.

Original refs:

comments powered by Disqus