Comments on: ROI of Application Development http://www.agilitysoftware.com/2007/06/13/roi-of-application-development/ Join the self-serve automation revolution Sun, 13 Jun 2010 15:32:01 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Ed French http://www.agilitysoftware.com/2007/06/13/roi-of-application-development/comment-page-1/#comment-80 Ed French Thu, 14 Jun 2007 21:03:54 +0000 http://www.workforceinabox.com/2007/06/13/roi-of-application-development/#comment-80 Alastair, Great points. I've sometimes thought that the ROI should be risk-adjusted. Big risky projects should have to meet a different ROI barrier to small and low-risk projects. Some of those extra "nice to have" features can have an impact on the risk that the project doesn't provide the planned benefits. Ed Alastair,

Great points.
I’ve sometimes thought that the ROI should be risk-adjusted. Big risky projects should have to meet a different ROI barrier to small and low-risk projects. Some of those extra “nice to have” features can have an impact on the risk that the project doesn’t provide the planned benefits.

Ed

]]> By: Alastair Bathgate http://www.agilitysoftware.com/2007/06/13/roi-of-application-development/comment-page-1/#comment-79 Alastair Bathgate Thu, 14 Jun 2007 17:10:07 +0000 http://www.workforceinabox.com/2007/06/13/roi-of-application-development/#comment-79 Ciaran It's a fair point. My view is that a professionally designed and coded application is not a "nice to have" it is an essential. Within any application there needs to be some bells and whistles to give a good user experience. Major chunks of functionality, however, should be checked against ROI measured in financial terms (increased income, improved margin, reduced cost etc). What represents a major chunk? That's probably a grey area that could command a post in its own right. Ciaran
It’s a fair point.
My view is that a professionally designed and coded application is not a “nice to have” it is an essential. Within any application there needs to be some bells and whistles to give a good user experience. Major chunks of functionality, however, should be checked against ROI measured in financial terms (increased income, improved margin, reduced cost etc).
What represents a major chunk? That’s probably a grey area that could command a post in its own right.

]]> By: Ciaran http://www.agilitysoftware.com/2007/06/13/roi-of-application-development/comment-page-1/#comment-78 Ciaran Thu, 14 Jun 2007 17:00:30 +0000 http://www.workforceinabox.com/2007/06/13/roi-of-application-development/#comment-78 Just a thought - do nice-to-haves give an overall feel of quality or professionalism to an application or solution that can't be so easily quantified? Just a thought – do nice-to-haves give an overall feel of quality or professionalism to an application or solution that can’t be so easily quantified?

]]> By: Sunjay http://www.agilitysoftware.com/2007/06/13/roi-of-application-development/comment-page-1/#comment-77 Sunjay Wed, 13 Jun 2007 15:53:46 +0000 http://www.workforceinabox.com/2007/06/13/roi-of-application-development/#comment-77 Excellent 6th ingredient! That's something we've learned the hard way so many times that we forget to mention it, but it definitely bares repeating and focus. Excellent 6th ingredient! That’s something we’ve learned the hard way so many times that we forget to mention it, but it definitely bares repeating and focus.

]]>