Uncategorized

Making delivery a habit rather than a fluke


More and more people are arguing that agile doesn’t work..

Even more people argue that – we’ve been doing this anyway! It’s the old stuff re-packaged!

Whatever your view, one thing is clear.  Delivery needs to become a habit not a fluke. If one agile project can’t be delivered to the satisfaction of stakeholders and customers alike, then it sure as hell means that none of the others will totally be either.

Agile is about practise but it is also about doing a certain number of things in a VERY disciplined way.  The problem we have today with the proliferation of the ‘expert’ on the internet, (self-proclaimed ones mostly) is that the academic foundations of agile/ Scrum/ Lean are often ignored. Without the proper homework under-lying these methodologies, there is a weakening of them that leads to a dilution at scale.  This is why the proper training is so important.

What’s more, lip service to an agile way of working is not good enough either and will not lead to a delivery culture.  Agile challenges the command and control manager.  If the organisational culture incentives this way of working then there is little hope for Agile to flourish in this environment.

Empowerment is an easy word to write but a very hard thing to teach.  Empowerment comes from changing behaviours and this is what many who start on the agile journey don’t recognise up front.

Here is the guide we suggest for the agile journey:

1. Observe what’s broken and also what’s working well

2. Baseline where you are

3. Work with senior executives on culture and prioritisation of projects.  Gain buy in.

4. Build a course that gives everyone a common understanding

5. Create champions

6. Coach and follow up as necessary

Check out some of my colleague Fiona’s ideas on embedding empowerment: http://www.valuingyou.co.uk/

 

But I have to agree with these guys:

http://www.netobjectives.com/blogs/why-agile-may-not-work-you-lean-agile-will

http://www.forbes.com/sites/stevedenning/2012/04/17/the-case-against-agile-ten-perennial-management-objections/

http://r-stylelab.com/company/blog/software-product-development/12-fatal-mistakes-in-agile-development

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s