Making a Strong Case for Requirements Management

Is Requirements Management a smart investment right now? What’s the expected ROI for an RM tool? Does your executive team view RM as a “must have” or a “nice to have” solution?kevin_roi_analysis.JPG

I find myself having conversations on these topics with customers almost every day so I thought I’d write about the analysis we do to help answer those questions. These are great discussions and with any enterprise software purchase, it’s a good practice to assess the total cost of ownership and determine the anticipated return on investment (ROI). And, especially in a tough economy, this is even more critical.

The good news is that in the field of requirements management, there’s a pretty thorough model that exists. We use an ROI model developed for Software Quality Engineering (Stickyminds.com) by Richard Denney, a software and process management consultant. This model has been used by many in the industry to assess the value of requirements management.

It helps quantify the tangible cost savings and benefit-to-cost ratio for these 4 key benefits of RM:

  1. Improved team efficiency
  2. Avoiding lost requirements
  3. Avoiding unnecessary work
  4. Reducing requirements defects

On average, the cost savings we’re seeing for companies range from $300k – $400k per year for a team size of 20 though there are a handful of variables to consider to customize the analysis to your team.roi_analysis_snapshot.jpg

That being said, getting a good return assumes commitment and from the team and that the requirements tool isn’t shelfware.

We’ve seen that it’s easier to be successful when the development process matches team dynamics and the tools selected have team buy in.

If you are thinking about the value of requirements management or how to quantify a requirements management solution, let me know. I’ll share our version of the spreadsheet and ROI doc. Email me at kthomson@jamasoftware.com.

2 Comments

  1. Posted May 21, 2008 at 11:10 am | Permalink

    Interesting analysis. Assuming one is using a tool to assist in RM, is it a full time role?

  2. Posted May 28, 2008 at 9:04 am | Permalink

    Kevin, I would be interested in your doumentation on this.

    Another benefit to measuring ROI on projects is that you can use it to evaluate the effectiveness of your product managers/business analysts (http://requirements.seilevel.com/blog/2006/01/measuring-product-manager-performance.html).

    Unfortunately, most projects don’t do this!

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*