ANALYZING IMPENDING FACTORS AND THEIR IMPACT ON SOFTWARE TESTING ORGANIZATION

Suman Kumar Kanth (), Dr. Sanjay Mohapatra () and P C Basak ()
Additional contact information
Suman Kumar Kanth: Delivery Manager, Infosys Limited Bhubaneswar, Odisha
Dr. Sanjay Mohapatra: Associate Professor, Faculty of Business and Management Xavier Institute of Management, Bhubaneswar, India, Odisha
P C Basak: Professor of Management Indira Gandhi National Open University, New Delhi

Far East Journal of Psychology and Business, 2013, vol. 12 No 1 Paper 4 July, issue 4, 47-56

Abstract: This paper is a practitioners view of impact of different parameters like Centralization, Offshoring, Productivity Improvement, Quality and other process improvement on Return on Investment calculation for a CTO (Centralized testing Organization). This analysis can help IT QA (Quality Assurance) management to quantify Return on Investment from different parameters of operation and decide on where to invest for optimum benefit. Return on Investment is one the critical factors that any large / small organization chooses before investing. At all the stages of the project life cycle, Return on Investment calculation is a must - that is at business requirements to design , development, testing and implementation phase. In todays world, independent testing has become very important. The organization needs to do a proper due diligence on selecting testing model, process, time to market, cost etc. For these the organization needs to understand the criteria for selecting the right model for testing which gives the maximum return on investment. This study analyses different parameters and their impact on Return on Investment. This paper does not elaborate on how to establish a CTO. Rather this is an attempt to quantify results after due consideration of various focus areas like - lower cost of operation by offshoring and centralization and savings through Productivity Improvement thru Automated Test Case Execution, savings through Process and tools standardization etc. to implement different parameters within a CTO. The findings are based on authors experience of implementing CTOs for reputed clients and implementing that across big size portfolios. The constraints for pure development projects, product testing projects or open system projects may vary in nature. benefit from automation may be very high for product testing projects or open system projects but not so for legacy mainframe based maintenance projects.

Keywords: Centralized Testing Organization; Return on Investment; Productivity Improvement; Offshoring Sourcing human capital form cost effective locations; Centralization Consolidating testing activities and resource responsibilities; Standardization Using common tool/process across the organization. (search for similar items in EconPapers)
JEL-codes: M1 (search for similar items in EconPapers)
Date: 2013
References: Add references at CitEc
Citations:

Downloads: (external link)
http://www.fareastjournals.com/files/FEJPBV12N1P4.pdf (application/pdf)
http://www.fareastjournals.com/archive_detail.aspx?jid=18&aid=39 (text/html)

Related works:
This item may be available elsewhere in EconPapers: Search for items with the same title.

Export reference: BibTeX RIS (EndNote, ProCite, RefMan) HTML/Text

Persistent link: https://EconPapers.repec.org/RePEc:fej:articl:v:12a:y:2013:i:4:p:47-56

Access Statistics for this article

More articles in Far East Journal of Psychology and Business from Far East Research Centre
Bibliographic data for series maintained by Jim Chau ( this e-mail address is bad, please contact ).