Comments on: Does Agile Solve the Right Problem? http://www.yuwantitwhen.com/blog/2008/06/22/does-agile-solve-the-right-problem/ Practical methods for successful software management. Mon, 03 Aug 2009 05:32:33 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Bill Miller http://www.yuwantitwhen.com/blog/2008/06/22/does-agile-solve-the-right-problem/comment-page-1/#comment-449 Bill Miller Wed, 02 Jul 2008 01:09:46 +0000 http://www.yuwantitwhen.com/blog/?p=56#comment-449 Kelly, I've posted additional thoughts on your reply in this recent post: <a href="http://www.yuwantitwhen.com/blog/2008/07/01/agile-content-is-the-goal/" rel="nofollow">Agile Content is the Goal</a> Kelly,

I’ve posted additional thoughts on your reply in this recent post:

Agile Content is the Goal

]]> By: Bill Miller http://www.yuwantitwhen.com/blog/2008/06/22/does-agile-solve-the-right-problem/comment-page-1/#comment-444 Bill Miller Sat, 28 Jun 2008 11:48:42 +0000 http://www.yuwantitwhen.com/blog/?p=56#comment-444 Kelly, Thanks for visiting and commenting. It's always nice and appreciated when a visitor takes the time to offer commentary. I'm unconvinced that things are all that different on the web. Change is important on the web, but the web has changed the focus to changing content over changing features. As bloggers, our struggle is to offer new content over new features. I believe that's the struggle for many companies on the web. I wrote a lengthy reply to your comment supporting that point, and I decided to offer it as a posting. I'll have it out by Monday. Kelly,

Thanks for visiting and commenting. It’s always nice and appreciated when a visitor takes the time to offer commentary.

I’m unconvinced that things are all that different on the web. Change is important on the web, but the web has changed the focus to changing content over changing features.

As bloggers, our struggle is to offer new content over new features. I believe that’s the struggle for many companies on the web.

I wrote a lengthy reply to your comment supporting that point, and I decided to offer it as a posting. I’ll have it out by Monday.

]]> By: Kelly Waters http://www.yuwantitwhen.com/blog/2008/06/22/does-agile-solve-the-right-problem/comment-page-1/#comment-443 Kelly Waters Sat, 28 Jun 2008 08:40:17 +0000 http://www.yuwantitwhen.com/blog/?p=56#comment-443 You make some good points, but with so much software being web-based these days, the rollout and customer change problem you describe is simply not an issue. In this case noone needs a 'reason to upgrade', they just get software improvements as and when they're ready, rather than waiting for one big release from time to time. With Windows products that require a rollout, I do agree that customers typically don't want frequent releases. Frequent delivery of working software is still an important principle of agile development though, even if you choose not to release it to customers every time. The other thing worth considering in this case, though, is whether or not the software is as easy as possible and seamless to upgrade. My virus checking software, for example, is downloading new anti-virus information in the background whenever it's available and is not putting the onus on me to go and get it and install it. Having said all of this, some products can be more static than others. On the web, a web year is like 7 years offline, due to the amount of innovation taking place at present. In this case you do have to respond moer quickly to compete. Kelly Waters http://www.agile-software-development.com You make some good points, but with so much software being web-based these days, the rollout and customer change problem you describe is simply not an issue. In this case noone needs a ‘reason to upgrade’, they just get software improvements as and when they’re ready, rather than waiting for one big release from time to time.

With Windows products that require a rollout, I do agree that customers typically don’t want frequent releases. Frequent delivery of working software is still an important principle of agile development though, even if you choose not to release it to customers every time.

The other thing worth considering in this case, though, is whether or not the software is as easy as possible and seamless to upgrade. My virus checking software, for example, is downloading new anti-virus information in the background whenever it’s available and is not putting the onus on me to go and get it and install it.

Having said all of this, some products can be more static than others. On the web, a web year is like 7 years offline, due to the amount of innovation taking place at present. In this case you do have to respond moer quickly to compete.

Kelly Waters
http://www.agile-software-development.com

]]>