Skip to main content

The Benefits and Consequences of Workarounds in Software Development Projects

  • Conference paper

Part of the book series: Lecture Notes in Business Information Processing ((LNBIP,volume 210))

Abstract

Workarounds have existed in software from the very beginning. Being a formalized collection of knowledge rather than a physical artifact, software allows shortcuts in its development process. The shortcuts serve various purposes, like releasing a product to the market faster or postponing the solution of a problem. In this article, we present the findings of an investigation of workarounds in two software companies. Our analysis reveals that the decisions to take a workaround to resolve a technical issue are often intentional and forced by time-to-market requirements. However, the stakeholders are not always familiar with the negative consequences of taking workarounds, like additional hours, costs, and poor quality. We argue that the decision to take a workaround is often made by business managers who see short-term benefits only while developers have to deal with negative consequences in long-term.

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

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Brooks, F.: The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition. Addison-Wesley Professional (1995)

    Google Scholar 

  2. Boehm, B.: A spiral model of software development and enhancement. Computer 21(5), 61–72 (1988)

    Article  Google Scholar 

  3. McConnell, S.: Rapid Development: Taming Wild Software Schedules. Microsoft Pr. (1996)

    Google Scholar 

  4. Fan, M., Kumar, S., Whinston, A.: Short-term and long-term competition between providers of shrink-wrap software and software as a service. European Journal of Operational Research 196(2), 661–671 (2009)

    Article  MATH  MathSciNet  Google Scholar 

  5. Azad, B., King, N.: Enacting computer workaround practices within a medication dispensing system. European Journal of Information Systems 17(3), 264–278 (2008)

    Article  Google Scholar 

  6. Cunningham, W.: The WyCash Portfolio Management System. In: OOPSLA Addendum to the Proceedings, pp. 29–30 (1992)

    Google Scholar 

  7. Tom, E., Aurum, A., Vidgen, R.: An exploration of technical debt. Journal of Systems and Software 86(6), 1498–1516 (2013)

    Article  Google Scholar 

  8. Halbesleben, J., Wakefield, D., Wakefield, B.: Workarounds in health care settings: Literature review and research agenda. Health Care Management Review 33(1), 2–12 (2008)

    Article  Google Scholar 

  9. Alter, S.: Theory of Workarounds. Communications of the Association for Information Systems 34, Article 55 (2014)

    Google Scholar 

  10. IBM, Customer Care Handbook (2004)

    Google Scholar 

  11. Koppel, R., Wetterneck, T., Telles, J.L., Karsh, B.-T.: Workarounds to Barcode Medication Administration Systems: Their Occurrences, Causes, and Threats to Patient Safety. Journal of American Medical Information Association 15(4), 408–423 (2008)

    Article  Google Scholar 

  12. Russell, B.: You gotta lie to it: software applications and the management of technological change in a call centre. New Technology, Work and Employment 22(2), 132–145 (2007)

    Article  Google Scholar 

  13. Guo, Y., Seaman, S.: A Portfolio Approach to Technical Debt Management. In: 2nd Workshop on Managing Technical Debt, New York, NY, USA, pp. 31–34 (2011)

    Google Scholar 

  14. Mäntylä, M., Lassenius, C.: Subjective evaluation of software evolvability using code smells: An empirical study. Empirical Software Engineering 11(3), 395–431 (2006)

    Article  Google Scholar 

  15. Nagarjuna, V., Mamidenna, S.: Personality Characteristics of Commerce and Engineering Graduates – A Comparative Study. Journal of the Indian Academy of Applied Psychology 34(2), 303–308 (2008)

    Google Scholar 

  16. Perrow, C.: The Analysis of Goals in Complex Organizations. American Sociological Review 26(6), 854–866 (1961)

    Article  Google Scholar 

  17. Ritti, R.: Work Goals of Scientists and Engineers. Industrial Relations: A Journal of Economy and Society 7(2), 118–131 (1968)

    Google Scholar 

  18. Dver, A.: Software Product Management Essentials, 2nd edn. Anclote Press (2008)

    Google Scholar 

  19. Dzida, W., Herda, S., Itzfeldt, W.D.: User-perceived Quality of Interactive Systems. In: Proceedings of the 3rd International Conference on Software Engineering, Piscataway, NJ, USA, pp. 188–195 (1978)

    Google Scholar 

  20. Aladwani, A., Palvia, P.: Developing and validating an instrument for measuring user-perceived web quality. Information & Management 39(6), 467–476 (2002)

    Article  Google Scholar 

  21. Klein, H., Myers, M.: A Set of Principles for Conducting and Evaluating Interpretive Field Studies in Information Systems. MIS Quarterly 23(1), 67–93 (1999)

    Article  Google Scholar 

  22. Walsham, G.: Interpretive case studies in IS research: nature and method. European Journal of Information Systems 4(2), 74–81 (1995)

    Article  Google Scholar 

  23. Corbin, J., Strauss, A.: Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory, 3rd edn. SAGE Publications, Los Angeles (2007)

    Google Scholar 

  24. Lim, E., Taksande, N., Seaman, C.: A Balancing Act: What Software Practitioners Have to Say about Technical Debt. IEEE Software 29(6), 22–27 (2012)

    Article  Google Scholar 

  25. Kekre, S., Krishnan, M., Srinivasan, K.: Drivers of Customer Satisfaction for Software Products: Implications for Design and Service Support. Management Science 41(9), 1456–1470 (1995)

    Article  MATH  Google Scholar 

  26. Li, W., Shatnawi, R.: An empirical study of the bad smells and class error probability in the post-release object-oriented system evolution. Journal of Systems and Software 80(7), 1120–1128 (2007)

    Article  Google Scholar 

  27. Boehm, B.: Software Engineering-as It is. In: 4th International Conference on Software Engineering, Piscataway, NJ, USA, pp. 11–21 (1979)

    Google Scholar 

  28. Gregor, S.: The Nature of Theory in Information Systems. MIS Quarterly 30(3), 611–642 (2006)

    Google Scholar 

  29. Sjøberg, D., Dybå, T., Anda, B., Hannay, J.: Building Theories in Software Engineering. In: Shull, F., Singer, J., Sjøberg, D. (eds.) Guide to Advanced Empirical Software Engineering, pp. 312–336. Springer, London (2008)

    Chapter  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Jesse Yli-Huumo .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2015 Springer International Publishing Switzerland

About this paper

Cite this paper

Yli-Huumo, J., Maglyas, A., Smolander, K. (2015). The Benefits and Consequences of Workarounds in Software Development Projects. In: Fernandes, J., Machado, R., Wnuk, K. (eds) Software Business. ICSOB 2015. Lecture Notes in Business Information Processing, vol 210. Springer, Cham. https://doi.org/10.1007/978-3-319-19593-3_1

Download citation

  • DOI: https://doi.org/10.1007/978-3-319-19593-3_1

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-319-19592-6

  • Online ISBN: 978-3-319-19593-3

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics