Skip to main content
SpringerLink
Log in

Lessons from attempting to backsource a government IT system

  • Teaching Case
  • Published:
Journal of Information Technology Teaching Cases

Abstract

Backsourcing is not a common term and refers to the process of taking back development of a system that was previously outsourced. Even though the term is not a common one, the process that it describes is. Businesses try to reverse outsourcing and start insourcing all the time. The process however is not cost free and certainly is not paved with roses. Herein we report from our own experience of trying to backsource the development and maintenance of a large information system, focusing on the technical problems encountered. The novel aspect of this paper is that it is one of the few that provide insights into the specifics that one has to include in any outsourcing contract, for backsourcing to be possible.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Log in via an institution

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Fig. 1
Fig. 2
Fig. 3

Similar content being viewed by others

References

  • Akoka, J., and I. Comyn-Wattiau. 2006. Developing a framework for analyzing IS/IT backsourcing. In AIM 2006—information systems and collaboration: State of the art and perspectives, 330–340. Luxembourg.

  • Art Gowan Jr., J., and R.G. Mathieu. 2005. The importance of management practices in IS project performance: An empirical study. Journal of Enterprise Information Management 18 (2): 235–255.

    Article  Google Scholar 

  • Butler, N., F. Slack, and J. Walton. 2011. IS/IT backsourcing—a case of outsourcing in reverse? In 2011 44th Hawaii international conference on system sciences (HICSS), 1–10. IEEE.

  • Kotlarsky, J., and L. Bognar. 2012. Understanding the process of backsourcing: Two cases of process and product backsourcing in Europe. Journal of Information Technology Teaching Cases 2 (2): 79–86.

    Article  Google Scholar 

  • Kwak, Y.H., and J. Stoddard. 2004. Project risk management: Lessons learned from software development environment. Technovation 24 (11): 915–920.

    Article  Google Scholar 

  • Nujen, B.B., L.L. Halse, and H. Solli-Sæther. 2015. Backsourcing and Knowledge Re-integration: A case study. In IFIP international conference on advances in production management systems, 191–198. Springer.

  • Samsudin, N.M., A.N. Bakar, and R. Hashim. 2012. Challenges of backsourcing of e-government services: A case study. In 2012 IEEE colloquium on humanities, science and engineering (CHUSER), 463–466. IEEE.

  • Solli-Sæther, H., and P. Gottschalk. 2015. Stages-of-growth in outsourcing, offshoring and backsourcing: Back to the future? Journal of Computer Information Systems 55 (2): 88–94.

    Article  Google Scholar 

  • Whitten, D., and D. Leidner. 2006. Bringing IT back: An analysis of the decision to backsource or switch vendors. Decision Sciences 37 (4): 605–621.

    Article  Google Scholar 

  • Wong, S.F., and P. Jaya. 2008. Drivers of IT backsourcing decision. Communications of the IBIMA 2 (14): 102–108.

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Department of Informatics Engineering, TEI of Central Macedonia, Serres, Greece

    Nicholaos Petalidis

Authors
  1. Nicholaos Petalidis
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Nicholaos Petalidis.

Rights and permissions

Reprints and permissions

About this article

Check for updates. Verify currency and authenticity via CrossMark

Cite this article

Petalidis, N. Lessons from attempting to backsource a government IT system. J Info Technol Teach Cases 8, 90–96 (2018). https://doi.org/10.1057/s41266-017-0026-2

Download citation

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1057/s41266-017-0026-2

Keywords

Search

Navigation