Are clients ready for Scrum?

As mentioned in my previous post I’m looking to bring a scrum-like process to my current project.  During the various kickoff meetings for the project I’ve realized that the client will probably have a difficult time embracing a more agile process.  The client is used to “conventional” development practices that start with large requirement documents, a big one time release at the end of the project, and a very detailed project plan defining “all” the tasks that will occur throughout the project.  They think this is what is required to build software.  This looks to be the biggest challenge yet.  Smaller clients with less exposure to traditional processes seem to be more open to “different approaches” but the larger clients have the waterfall methodology so ingrained into their corporations that it will be difficult to show them the ways of agile.

What have you used to help your larger clients who have waterfall ingrained into all their processes and procedures move to a more agile methodology?  Who did you have to sell on the ideas of agile to gain traction?

# re: Are clients ready for Scrum?

Monday, December 13, 2004 2:41 AM by Wes    
I don't have the answers but you can bet I'll be following your post b/c I am going through the same thing right now on a new project. They (the client) are used to having a full technical design document up front to base their project plan on (for the entire project) within a few days of handing over a requirements document. This implies that we have the time/knowledge available to do enough detailed planning up front to give an accurate estimate. If you go against the grain and let them know that big upfront design generally doesn't work and their requirements aren't at the level that they need to be in terms of detail to make an accurate design, you may anger them b/c you are "stalling" for some reason. :)

# re: Are clients ready for Scrum?

Monday, December 13, 2004 3:36 AM by Steve    
That's my primary concern. Telling them that a different approach is being taken may make them think that we're saying their way is wrong. Additionally as you stated they might think that you're stalling for some reason which prevents them from "doing their work."

# re: Are clients ready for Scrum?

Monday, December 13, 2004 5:31 PM by Howard van Rooijen    
I've got a few thoughts on this area - I'm trying to put a post together but in the mean time this was posted to the SellingAgile newsgroup (<a target="_new" href="http://finance.groups.yahoo.com/group/SellingAgile/">http://finance.groups.yahoo.com/group/SellingAgile/</a>):

From: Reginald Braithwaite-Lee
Sent: 03 December 2004 13:31
To: [SellingAgile]
Subject: [SellingAgile] Practical tips for selling agile in a traditional setting

&quot;Do not bill yourself as Team Agile. Do not make a big deal about
trying Agile. In fact, try to bring as little additional attention to
the team as possible. The team will need time to work through even a
single practice, to measure its benefit, to tweak its implementation,
and to ultimately embrace or reject it. You do not want to tie your
team's hands or put them under the microscope.

Let the results of your foray into Agile speak for themselves. If the
team's performance is improved, your customer, your boss, and your
customer's boss are all likely to notice. Answering that Agile
practices were the key to your success will serve your team much
better than heralding the results that Agile practices are going to
bring to your project once you've explained them to everyone … and
once the team has implemented them … and worked through all the issues
… and then explained why it all took longer than you thought. &quot;

From an excellent article on adding agile practices to a tradtional
project:

<a target="_new" href="http://tinyurl.com/6f5p3">http://tinyurl.com/6f5p3</a>

This and many similar links are available on my weblog:

<a target="_new" href="http://www.braithwaite-lee.com/weblog/">http://www.braithwaite-lee.com/weblog/</a>

...or directly from del.icio.us (RSS available):

<a target="_new" href="http://del.icio.us/raganwald/weblog">http://del.icio.us/raganwald/weblog</a>

# re: Are clients ready for Scrum?

Monday, December 13, 2004 9:36 PM by Jay Glynn    
First step is to determine why you think a more agile process would be better in this situation. In another post you mention that it is due to an aggressive schedule. This would probably be the wrong reason to introduce a new methodolgy, especially one that doesn't speed up the overall process. Doing a bunch of little releases doesn't give the client the **finished** product any sooner. You could be setting yourself and your client up for failure.

# re: Are clients ready for Scrum?

Thursday, April 28, 2005 9:42 AM by Rob Addis    
Clients need to buy into using Agile from the start. You need to educate them as to why this will add value to both parties how it will help you help them.

If you identify the project as a possible candidate (you're not building a nuclear power plant and if you haven't used Scrum etc before best to start on small projects).

Meet with the client before scope is even discussed and engage them in using an agile development process, pick apart what went wrong in the management of their last project i.e. how they ended up with so many change requests etc.

My point again is it should be up front and done at the start.

Post a Comment

 
 
Prove you're not a spammer: 
0 + 1 =