When ROI is Overkill



Email    print   
May 1, 2004 —  (Page 1 of 3)
Return on investment (ROI), risk analysis, requirements analysis, alignment with strategic objectives-it's a given that these methodologies should be used for judging the merits of a software investment.

So, why do our hearts sink at the prospect of doing these analyses? The answer is simple: They don't work. Oh, they might be fine for big-ticket enterprisewide software, but for lower-cost software these heavyweight techniques don't work for several reasons.

One is that predicting the value of an uncertain asset over time is counterproductive when it can more easily and accurately be demonstrated in a trial.

Another is that analysis processes often introduce "paralysis by analysis" into organizations; people are unwilling to invest time and effort into getting something approved. In many cases, the ROI predictions are often incorrect due to errors in assumptions or calculations. Also, a predictive approach encourages bloatware, with large unnecessary feature sets satisfying a requirements analysis but not necessarily benefiting users.

Imagine you've used a product intensively for two weeks and found that it meets all of your requirements at a reasonable cost. It would be pretty galling then to be told by some manager to try out three similar products, write a report and make a presentation to top managers.

An evaluation is a far more productive use of resources than a prediction, which often relies on false or exaggerated claims from the vendor. The best way to determine a technology's potential and value is to put it to the test in your environment.

Paralysis by analysis. The company I work for sells software tools for software developers, DBAs and application testers. The people interested in our products are intelligent, highly trained and generally well paid. They work on projects that involve spending hundreds of thousands, often millions, of dollars. You would think that they'd have little difficulty justifying the purchase of inexpensive tools.

Wrong. Often developers, DBAs and testers can order software only after they jump through lots of time-consuming hoops to justify the purchase to management. Not surprisingly, some don't bother going through the laborious requisition and evaluation process, despite really needing the tool; the process is just too painful. I pity the folks working in government departments and large multinationals, who often tell us that they need the tool right away but can't get it approved for another three months.




Pages 1 2 3 


Share this link: http://sdt.bz/27850
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE

 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb