Why switch to Agile - besides failure
There's a thread currently bouncing around the Yahoo Agile group as to why organizations would consider switching to Agile. A lot has been said about project failures and there's debating back and forth as to what statistical data is out there to back a company's decision to switch.
The way I see things is that both Waterfall projects and Agile projects succeed and fail. So it's not just because projects fail that one should switch. Most certainly that's a big reason. But there's many other reasons why company's should switch. One only needs to read the Chaos report by the Standish group to realize that there's most likely a better way to do things than traditional methods. Lets face it. There were a lot of smart people behind the Agile movement and so there were reasons that they sought to find a better way.
So what are the other reasons to switch, there are many tell tale signs to look for in your organization for example and this is not an exhaustive list:
- Features take longer and longer to get implemented
- New releases take longer and longer to get out
- Ever increasing QA cycles at the end of every release
- Increased bug counts release on release
- Increased support calls/emails
- Morale problems on the team
- Unsatisfied customers
I don't think any statistics should play a role in making the final decisions. But the statistics sure do show a growing trend. So I would take a long hard look at what's working and what's not working in your organization. It might just be that you're experiencing any number of issues listed above or many others. If this is the case, I'd at least start experimenting with Agile on a small project or a new project initiative and then you be the judge.
But if you do decide, do it properly so that you give it your best shot.
Written by Jack Milunksy - COO at Brightspark, certified ScrumMaster and Co-founder of Agilebuddy (Agile project management software that lets you easily Create, Estimate, Plan and Track your software development projects). For great Agile tips follow Jack at: www.twitter.com/agilebuddy. To get more info on Agilebuddy please visit: www.agilebuddy.com





I have received many requests to assist with Agile training and deployment. I am humbled by your interest and, being a huge proponent of Agile, want to help any way I can by providing consulting where I am able to.





Well said - thanks for the help!
Posted by: Bill Curci | 01/28/2009 at 09:52 AM
One thing to note about the group that created the Agile Manifesto... We gathered together because we were each practicing different lightweight methodologies that flew in the face of Waterfall or Heavyweight processes. We distilled those common threads that seemed to pervade each of our methodologies and experiences. In other words, it was more of an observational or anecdotal result versus a gathering to "come up with a new agile process."
Posted by: Jon Kern | 01/31/2009 at 08:01 AM
In the long run, we more than doubled programmer productivity. We also broke down some of the inherent opposition between programmers and QA techs. The sense of team (unity) was the best benefit in my experience.
Details:
I participated in an agile-scrum-six sigma group that implemented much of these lean methodologies. This department was able to double programmer productivity almost immediately—but there was some temporary stress increase as the change from waterfall to agile was made—they were able to produce a User’s Guide for each feature while the programming and QA was happening, and they were able to release features most needed by customers in a truly agile and quick manner.
Posted by: Richard Lynn Paul | 05/05/2009 at 10:43 AM
Great points. All of them. One other phenomenon that occurs in tandem with increased morale - serious programmers that enjoy productive environments prefer going to work at companies with a proven Agile track record.
Thanks for an awesome article. I look forward to using it as a point in my discussions on the topic. - JR Fent
Posted by: JR Fent | 05/07/2009 at 12:34 PM
Hi JR,
Thanks for the positive feedback. Much appreciated.
I recently attended Railsconf. Every developer I spoke to there said they loved working in an agile environment.
Cheers
Jack
Posted by: Jack Milunsky | 05/08/2009 at 12:05 PM
Hey Jack.
Yes - Even at our regional meetings, such as our Ruby Meetup Group and at the Los Angeles Ruby Conf (larubyconf) - Agile is an area that we have speakers presenting on quite often.
-JR
Posted by: JR Fent | 08/18/2010 at 10:23 PM
I am interested in this article. Please if you send me the email address more about this article? thanks
Posted by: biletul zilei | 11/27/2010 at 01:03 AM
I participated in an agile-scrum-six sigma group that implemented much of these lean methodologies. This department was able to double programmer productivity almost immediately
awesome thanks
Posted by: Fire Detection | 03/20/2011 at 05:31 PM
Houses are not cheap and not every person is able to buy it. Nevertheless, home loans was created to support people in such hard situations.
Posted by: IrmaGreene19 | 11/30/2011 at 01:13 AM