To provide a more practical set of guidelines for prioritizing, the first thing is to identify SCSs and their win conditions. Direct stakeholders of testing are developers and project managers, who directly interact with the testing team. However, in the spirit of value-based software engineering important parties for testing are customers. Customers are the source of value objectives, which set the context and scope of testing. Marketing and product managers assist in testing for planning releases, pricing, promotion, and distribution.
We will look at three factors that must be considered when prioritizing the testing order of new features, and they represent SCSs’s win conditions:
1).The business importance of having the features. It gives information as to what extent mutually agreed requirements are satisfied and to what extent the software meets their value propositions.
2).The quality risk of each feature. For project managers it supports risk management and progress estimation. The focus is on identifying and eliminating risks that are potential value breakers and inhibit value achievements.
3).The cost estimation for testing each feature. Testing managers are interested in the identification of problems particularly the problem trends that helps to estimate and control testing process.
Replaced/Superseded by document(s)
For a software project to succeed, acceptable quality must be
achieved within an acceptable cost, providing business value to the customers, and keeping delivery time short. Software testing is a strenuous and expensive process and is often not organized to maximize business value. In this article, we propose a practical value based software testing method which aligns the internal
test process with the value objectives coming from the customers and the market. Our case study in a real-life business project shows that this method helps manage testing process effectively and efficiently.