TrainingConferencesAbout UsContact UsAdvertiseSQE.comRSS Feed

StickyMinds.com: brain food for building better software

Log In
 Clarify Your Search Criteria

Tips on Using Our Search Feature(s)
 
StickyMinds.com Home
ResourcesTopicsCommunityPowerPassBlogs
Home  >  Detail: Testing, Ka-Ching!



A StickyMinds.com Original
Article Picture
Testing, Ka-Ching!

By Linda Hayes

Send This Content to a FriendGet a Short Link to This ContentPrint This ContentSee User Comments About This Content

Summary: One of the most frustrating aspects of software testing is that it typically is viewed as an expense that should be minimized. Sure, you can argue until you drop that it is cheaper to find problems in test than it is in the field, but deep down everyone still wants to spend as little time and money on testing as they think they can get away with. That's why Linda Hayes always has been motivated to find a way to make testing a profit center. And it seems as if she just found her first real-life example. In this week's column, she describes how one company is positioning to make testing a profitable department.


Ranorex
If you could somehow tie testing to the top line so that it actually generates revenue, then that would turn the whole dynamic inside out. But most companies still are trying to get away with as little testing as possible. I have had a few tantalizing conversations with software companies that at least considered adding testing to their repertoire of products and services, but none of them ever came to fruition--until now.

A German juggernaut software developer, which took over the enterprise resource planning (ERP) market with packaged software that could be configured to adapt to each customer's unique needs, is launching an initiative to offer testing services and technology to its customers. And while this company no doubt plans to make a profit on these solutions, I don't think that is what it is really after.

This company refreshed its technology platform to take advantage of the latest in service-oriented architecture (SOA), and all of its new products have been developed on this platform. As a result, existing customers must upgrade to the new version before the company can realize add-on revenue. Unfortunately, its software supports such a broad spectrum of the enterprise's most critical business processes that many customers are loath to introduce change of any kind, because when they do, it is tedious, time-consuming, and costly.

In fact, when this company surveyed its customers to find out what the most challenging aspects of implementing upgrades were, testing came in at number one. The time, effort, and risk associated with testing such a highly configurable, tightly integrated, and widely used system encouraged customers to avoid making changes as long as possible.

In other words, this company discovered that testing is, in fact, tied to the top line, and it has to help its customers solve the testing problem in order to generate revenue from its new products. Done right, the company can generate revenue from the sale of testing solutions for upgrades, then generate even more from new products that can be sold after the upgrade. Suddenly, testing is an opportunity instead of an obstacle.

If this works, it could represent a profound shift in the way we look at testing. Instead of thinking of it as an expense to be minimized, look at it as revenue to be maximized. Not what’s the least we can do, but what’s the most?

Based on its track record, it would seem that it makes sense to watch what this German juggernaut of software development is doing and learn from it. Any software company whose product is configured or modified by its customers has the opportunity to turn testing into a top-line opportunity while creating happier customers faster by:
  • Generating direct revenue from pre-developed test cases, technology, and services
  • Generating indirect revenue by compressing the implementation cycle for new products and upgrades
  • Enabling future revenue by accelerating the adoption rate for new features and products
  • Creating customer satisfaction through improved reliability and confidence
There are also motivations that are not driven necessarily by the craven greed for money. Once testing generates revenue, more resources will be available to invest, so that overall test coverage and product quality will increase. And as customers coalesce around common test cases and technologies, it will become possible to share test assets, further expanding cooperation and leveraging the community.

Even these feel-good benefits have a potential revenue impact: The quality and functionality of the testing solution could become a competitive weapon in and of itself. Speed and efficiency of implementation, as well as customer satisfaction and community, are advantages that might differentiate otherwise feature-equivalent offerings.

I realize that shifting the entire economic and organizational paradigm for testing is no trivial undertaking and will take a lot of time to unfurl, but I've waited twenty years so far. At least this company has broken ground.


About the Author
Linda G. Hayes is a founder of Worksoft, Inc., developer of next-generation test automation solutions. Linda is a frequent industry speaker and award-winning author on software quality. She has been named as one of Fortune magazine's People to Watch and one of the Top 40 Under 40 by Dallas Business Journal. She is a regular columnist and contributor to StickyMinds.com and Better Software magazine, as well as a columnist for Computerworld and Datamation, author of the Automated Testing Handbook and co-editor Dare To Be Excellent with Alka Jarvis on best practices in the software industry. You can contact Linda at linda@worksoft.com.

Back to Top
 

StickyMinds.com Weekly Column From 7/2/2007 

Member Comments
Add Your CommentExpand Comments
 
Comment:    
by Ed Kuipers 7/14/2007

I think you've got a point there. Testing is expensive and does not contribute to the actual end product delivered to the customer. So is making functional and technical designs. Therefore why test and why design. Just hack some code and throw it at the customer. If he of she finds bugs, hey we call them "undocumented features". If he or she cant use the software because it does not integrate with the business processes, just change the business processen to integrate with the software. If all fails blame it on testers, architects and functional designers (that is, the once that are still involved in the project, you can easily recognize...Read On

Author's Response:
7/14/2007    
After over 20 years in this industry I'm still asking myself the same questions, Ed. As this article proposes, at least figuring to a way to position testing as an investment that pays off in revenue might be a step in the right direction...but hey, I'm open to anything that works!

 
 
Comment:    
by Stephen Barker 7/5/2007

"Ka-Ching" sounds about right to me! Try turning the article round, and you will see a very different picture: the company has a product so bad that no-one can install and use it without buying in specialist consultancy support services (from a monopoly supplier) to integrate the product by tweaking it endlessly. If you were very cynical, you could suggest that the company now has every incentive to make the software virtually unusable until hidden settings are tweaked. (BTW I have no idea who the company is, what it does, what the software is, and this is not an accusation! The article was written in an anomonous sense about a principle...Read On

Author's Response:
7/5/2007    
Are you sure your name is Stephen and not Dilbert? But seriously I should have made it clear that these customers aren't necessarily testing the vendor's software as much as they are testing their own unique configuration and integration of it. And companies do in fact test Windows! I have known many large enterprises to delay upgrades because of the massive effort to verify all of their platform applications on a new OS. It's inescapable that in a complex, distributed application environment that no two enterprises are the same and no single vendor can attempt - let alone achieve - testing for every possible combination and contingency. Given that, it makes sense to at least foster a community that can share as much of this burden as can be made reusable.

 
 
Comment:    
by jaideep khanduja 7/4/2007

Hi Linda, Thanks for the excellent article contentwise and also i found worksoft.com from ur contact info. truly this is a misconcept that quality is a burden or overhead expense on a company whereas actually it is reverse. quality is a boon or tool to cut down your development costs, product failures in the market and customer dissatisfaction. infact it is due to quality that the credit goes to the development team for developing a bug-free product. in real sense quality provides a great thrust to development but remains unnoticed or un-rewarded.
jaideep

Author's Response:
7/4/2007    
Thanks, Jaideep. I agree that testing is more help than hindrance to development even though it often has the reputation as an obstacle to be overcome. Maybe trends like this one will clarify the true value.

 
 
Comment:    
by Patricia Wall 7/3/2007

Thanks for the great article, Linda! We are one global company who ties our testing to the bottom line (or top, depending on your perspective). In fact, some of our customers have become Beta customers for our new product and assist us with in-depth testing. Since we have customer focus teams (CFT's) who support our customers with their installs, many of which are custom or involve external interfaces, we also use our CFT's as liaisons to coordinate with the Beta customers on testing the new product and when an issue is found it becomes a Heatcase. The Heatcase either becomes a bug to fix or a training issue to address. Our rotational...Read On

 
 
Comment:    
by Sankara Narayanan 7/3/2007

Linda,

Thanks for this nice Summary of the German company's Testing Organization. It is good to hear that the Testing Services is a revenue generating group within the Organization. At the same time, it is worth to know how the Software Development group of this is using this Testing Services group. If this Software Development group is trying and striving to minimize the testing costs considering that as an expense, this German company is no different than all other Software Development companies. Can you please throw some light on this?

Author's Response:
7/3/2007    
I don't know how their internal engineering team interacts with the testing solutions team so I can't comment, but we can only assume that they will also be beneficiaries of the test assets that are developed for delivery to customers. If nothing else, more extensive customer testing will provide higher quality feedback!

 
 
Comment:    
by Srinivasan Desikan 7/2/2007

Wonderful article. This is definitely a paradigm change for many testing professionals to look at business opportunity in testing. While a majority of the companies think about how to minimize their testing efforts, they forget to think about how we can minimize the efforts of our customers in deploying and using the products. Beta testing, deployment testing, acceptance testing, product demos, etc., are examples of testing done by the customers. Customer involvement at all stages of testing is the core approach of all agile methodologies asking for more and more efforts from customers. Companies helping their customers reducing their...Read On

Author's Response:
7/3/2007    
Thanks, Srinivasan. I agree that customers are (or should be) an integral part of the test effort - sometimes whether planned or not! Formalizing this relationship can help to expand and improve it. Everyone is a stakeholder in quality and has something to contribute.

 
 
Comment:    
by Robert Rose-Coutre 7/2/2007

Hi Linda, The company you referred to of course must be SAP. I assume that if the packaged software is "configured or modified by its customers," then the test cases must come in a base set for everyone, then each customer modifies the cases to fit its unique configuration of the software package. It sounds like a good step, to offer test cases as a "product" along with the original product being tested, especially if the test cases are easily configurable by customers. The community-potential among customers sharing test case modification ideas, etc., does sound useful. I wonder how the SAP test cases are packaged, e.g., with...Read On

Author's Response:
7/2/2007    
Good guess, Robert! The formal announcement has not been made yet so I don't know exactly what it will include, but I am looking forward to finding out how it manifests, too.

 
Back to Top



 
Ads By Google
What's This?
 
 



Home   |   Resources   |   Topics   |   Community   |   PowerPass



© 2010 StickyMinds.com. All rights reserved.
StickyMinds.com is a division of Software Quality Engineering.
Privacy Policy    Terms & Conditions    Link to StickyMinds.com    Feedback


Avnet

HP Software




STAREAST 


Better Software Conference