Towards Elimination of Testing Debt in Outsourced IS Development Projects: A View from the Client Side

  • Michal Doležel
Conference paper


Although issues connected with outsourced information systems (IS) projects as well as origins of software project failures have been a part of research literature for several years, software testing is still sometimes viewed as “ugly duckling” in the field of IS research. In this paper software testing is presented as a key part of IS development projects and as a potential source of project failures. From the perspective of client organizations, potential sources of testing debt and consequent project risks in an outsourced project environment are identified. Also, initial findings how to eliminate these problems are presented. Several key principles of recommended client IS development project management practice are proposed, as this paper generally advocates for better test and quality governance from the client side than current observed practices. Additionally, the role of cognitive and psychosocial factors is briefly introduced and some proposals for further research are presented.


Information systems development Outsourcing Vendor management Testing Test governance Technical debt Mum effect Whistle-blowing 



This paper describes the outcome of a research that has been accomplished as a part of the Research program funded by Internal Grant Agency grant number IG406013.


  1. 1.
    Jain RP, Poston RS, Simon JC (2011) An empirical investigation of client managers’ responsibilities in managing offshore outsourcing of software-testing projects. IEEE Trans Eng Manag 58(4):743–757CrossRefGoogle Scholar
  2. 2.
    Chua A (2009) Exhuming IT projects from their graves: an analysis of eight failure cases and their risk factors. J Comput Inf Syst 49(3):31–39MathSciNetGoogle Scholar
  3. 3.
    Savolainen P, Ahonen JJ, Richardson I (2012) Software development project success and failure from the supplier’s perspective: a systematic literature review. Int J Proj Manag 30(4):458–469CrossRefGoogle Scholar
  4. 4.
    Brown N, Ozkaya I, Sangwan R, Seaman C, Sullivan K, Zazworka N, Cai Y et al (2010) Managing technical debt in software-reliant systems. In: Proceedings of the FSE/SDP workshop on future of software engineering research—FoSER’10, p 47Google Scholar
  5. 5.
    Cusumano M (2008) Managing software development in globally distributed teams. Commun ACM 51(2):15–17CrossRefGoogle Scholar
  6. 6.
    Galin D (2004) Software quality assurance. From theory to implementation. Pearson Education Limited, HarlowGoogle Scholar
  7. 7.
    Shah H, Sinha S, Harrold MJ (2011) Outsourced, offshored software-testing practice: vendor-side experiences. In: 2011 IEEE sixth international conference on global software engineering, pp 131–140Google Scholar
  8. 8.
    International Software Testing Qualifications Board (2012) Standard glossary of terms used in Software Testing v. 2.2.
  9. 9.
    Keil M, Smith H, Pawlowski S, Jin L (2004) “Why didn’t somebody tell me?”: climate, information asymmetry, and bad news about troubled projects. Data Base Adv Inf Syst 35(2):65–81CrossRefGoogle Scholar
  10. 10.
    Kataja A, Tuunanen T (2006) Information systems development methods and reducing information asymmetry: a way to decrease project escalation in outsourcing? In: Proceedings of the 14th European conference on information systems, ECIS 2006, pp 1–8Google Scholar
  11. 11.
    Mäntylä MV, Itkonen J, Iivonen J (2012) Who tested my software? Testing as an organizationally cross-cutting activity. Softw Qual J 20(1):145–172CrossRefGoogle Scholar
  12. 12.
    Black R (2002) Managing the testing process: practical tools and techniques for managing hardware and software testing, 2nd edn. Wiley, Hoboken, NJGoogle Scholar
  13. 13.
    Ahonen J, Junttila T, Sakkinen M (2004) Impacts of the organizational model on testing: three industrial cases. Empir Softw Eng 9(4):275–296CrossRefGoogle Scholar
  14. 14.
    Sanz A, García J, Saldaña J, Amescua A (2009) A proposal of a process model to create a Test Factory. In: ICSE workshop on software quality 2009, Vancouver, pp 65–70Google Scholar
  15. 15.
    Lu Y, Käkölä T (2011) A dynamic life-cycle model for the provisioning of software testing services: experiences from a case study in the Chinese ICT sourcing market. In: 19th European conference on information systems, ECIS 2011Google Scholar
  16. 16.
    McBride T (2008) The mechanisms of project management of software development. J Syst Softw 81(12):2386–2395CrossRefGoogle Scholar
  17. 17.
    Sabherwal R (2003) The evolution of coordination in outsourced software development projects: a comparison of client and vendor perspectives. Inf Organization 13(3):153–202CrossRefGoogle Scholar
  18. 18.
    Schulmeyer GG (2008) Handbook of software quality assurance, 4th edn. Artech House, Boston, MAGoogle Scholar
  19. 19.
    Charankar M (2011) Achieving better test governance. Pract PM J (9).
  20. 20.
    Natovich J, Natovich R, Derzy Z (2011) Withholding bad news in information technology projects: the effect of positive psychology. In: PACIS 2011—15th Pacific Asia conference on information systems: quality research in PacificGoogle Scholar
  21. 21.
    Festinger L (1957) A theory of cognitive dissonance. Stanford University Press, Stanford, CAGoogle Scholar
  22. 22.
    Rouse A, Corbitt B (2007) Understanding information systems outsourcing success and risks through the lens of cognitive biases. In: Proceedings of the 15th European conference on information systems, ECIS 2007, pp 1167–1178Google Scholar
  23. 23.
    Park C, Im G, Keil M (2008) Overcoming the mum effect in IT project reporting: impacts of fault responsibility and time urgency. J Assoc Inf Syst 9(7):409–431Google Scholar
  24. 24.
    Robey D, Keil M (2001) Blowing the whistle on troubled software projects. Commun ACM 44(4):87–93CrossRefGoogle Scholar
  25. 25.
    Ramingwong S, Sajeev A (2007) Offshore outsourcing: the risk of keeping mum. Commun ACM 50(8):101–103CrossRefGoogle Scholar
  26. 26.
    Schein EH (2010) Organizational culture and leadership, 4th edn. Wiley, Hoboken, NJGoogle Scholar
  27. 27.
    Sommerville I (2007) Software engineering, 8th edn. Addison Wesley, HarlowzbMATHGoogle Scholar
  28. 28.
    Baskerville R, Myers M (2004) Special issue on action research in information systems: making IS research relevant to practice—foreword. MIS Q 28(3):329–335Google Scholar
  29. 29.
    Avison D, Baskerville R, Myers M (2001) Controlling action research projects. Inf Technol People 14(1):28–45CrossRefGoogle Scholar
  30. 30.
    Susman G, Evered R (1978) An assessment of the scientific merits of action research. Adm Sci Q 23(4):582–603CrossRefGoogle Scholar
  31. 31.
    Guo Y, Seaman C (2011) A portfolio approach to technical debt management. In: MTD’11 Proceedings of the 2nd workshop on managing technical debt, pp 31–34Google Scholar
  32. 32.
    Tian J (2005) Software quality engineering. Wiley, Hoboken, NJCrossRefGoogle Scholar

Copyright information

© Springer International Publishing Switzerland 2014

Authors and Affiliations

  1. 1.Department of Information TechnologiesUniversity of Economics, PraguePragueCzech Republic

Personalised recommendations