Thursday, June 23, 2005

Selling Agile or Agile Selling ?

I suspect this will be the first of many entries here, so here goes with the can of worms: How do you sell an agile approach to delivering projects, factoring in the needs/issues/barriers of the folks in the client: PMs, CTOs, vendor mgt, legal, CFOs ?

We can create the nice glossies and presentations talking about this, that and the other benefit of agile methodologies (whichever one or combination you prefer), but there is more to it than this.

My take on it is more to do with the classic 'Solution Selling' approach: block & tackle question model whereby there are three main lines of questioning : diagnose, explore impact and visualize capabilities, each with a subset series of questions: open, control, confirm... (btw - this Solution Selling is probably another blog entry for the future). The point is that you need to understand the business problem and pain (or latent pain), and then apply your judgement (and agility) as to how you can solve their problem quickly and effectively. I think this is a pragmatic and experiential sell - you need to know your stuff, but be able to iteratively work out the right approach for the problem - sound familiar ?

Others have blogged about the legal side of things, which I think requires a shifting of the mindset on the side of the clients' legal/vendor mgt. It almost like you have to disprove the status quo and show that they business NEVER gets it right first time, and that quick meaningful deliverables (production quality) is actually what the business wants. Some further thoughts from the 'Agile Champion' are here.

As I said, this was just to open up the can of worms. Any first hand experience of others in selling agile approaches to non-buyers would be appreciated ...

1 Comments:

At 6:21 PM, Anonymous Anonymous said...

First off, if a consultancy is not doing agile in some shape or form, then that consultancy probably needs to review its methodologies. One of the primary issues with software development is estimating the cost and delivery date of the application. "Estimate" being the key. For a 6+mth project, estimating gets very very fuzzy. Agile with its iteration concept, and keeping the customer close fixes this issue. Iterations within agile allow a customer to see exactly what he is paying for, and also to delivery based on his priority.

 

Post a Comment

<< Home