Agile software development
Home > Ask the Software Quality Experts > Software Process Models and Methodologies Questions & Answers > Agile software development: Proving the benefits
Ask The Software Quality Expert: Questions & Answers
EMAIL THIS

Agile software development: Proving the benefits

Bas de Baar EXPERT RESPONSE FROM: Bas de Baar

Pose a Question
Other Software Quality Categories
Meet all Software Quality Experts
Become an Expert for this site


Software quality news and advice
Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


>
QUESTION POSED ON: 02 April 2007
Our company is exploring the potential of going agile for software development. While I and others here completely understand the benefits of doing so, convincing the business of investing in our transformation is proving somewhat harder. I can find many references from other companies stating that they have seen direct benefits but this is never supported with hard data. We are planning to run a series of pilots to demonstrate to ourselves the benefits, but I need to get hold of industry benchmark data that I can use to present a business case back to my organization. Do you have any clues or suggestions which can help?

>
EXPERT RESPONSE

There is not much real hard data publicly available that shows benefits of using agile software development approaches. The data that is available doesn't bring you much either; what use is a statement that company X had a productivity increase after introducing Scrum? Who knows if the circumstances are comparable with yours? Who knows what other factors contributed to the sudden increase?

Running the pilot projects is, in my opinion, the way to proof its benefits. However, before plunging into the water, consider what your current problems are; try to express them in metrics like productivity, number of bugs found, time to market, user acceptance. Define the root causes for your most prominent problems, explain how agile would solve them, and after the pilot compare historic metrics with the new ones. That is what you need to convince management.

Oversimplified example: the time between software finished and user acceptance is too long. Cause: users see the software late in the process. Agile solution: close and early user involvement. You can measure the time it takes between completion and the formal acceptance. Should be better.

Of course, this is a very simple example, but keep in mind: every technique tries to solve a problem; if you don't have that problem, introducing the technique will not improve anything. Define the problem, define the metric, explain and implement the correct technique or method, and compare the metrics.

More information:


Sound Off! -   Be the first to post a message to Sound Off!


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


RELATED CONTENT
Software Process Models and Methodologies
Agile development across continents
How long should an iteration be?
Is iterative development a new process?

Agile software development
Software development groups take many routes to Agile
Tools of the Agile trade
Agile practitioners face challenges, but see process improvements
Survey: Agile interest high, but waterfall still used by many
Even Shatner says development needs to be flexible
Scrum and requirements gathering
The Software Project Manager's Bridge to Agility: Chapter 5, Scope Management
Ivar Jacobson: Useful app dev practices trump full-blown processes
The role of architecture in agile development
Five agile testing perils to watch out for

Scrum software development
Software development groups take many routes to Agile
Scrum and requirements gathering
Using iterations to help balance priority and risk
Agile development: Not just for 'agilists' anymore
Agile Software Development: The Cooperative Game, 2nd Edition -- Chapter 3, Communicating, Cooperating Teams
Agile 101: What you need to know about agile software development
Agile development: Don't forget the documentation
Varying SDLC methodologies among development teams
Addressing software quality issues with development models, methods
Agile development best for delivering products on target

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
acceptance test  (SearchSoftwareQuality.com)
iteration  (SearchSoftwareQuality.com)
planning board  (SearchSoftwareQuality.com)
planning game  (SearchSoftwareQuality.com)
release  (SearchSoftwareQuality.com)
release plan  (SearchSoftwareQuality.com)
spike  (SearchSoftwareQuality.com)
stand-up  (SearchSoftwareQuality.com)
story  (SearchSoftwareQuality.com)
timebox  (SearchSoftwareQuality.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary



Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
Browse our Expert Advice

About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Reprints  |  Site Map




All Rights Reserved, Copyright 2006 - 2008, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts