Advertisement

The Human Resources Debt in Software Business

Towards a Research Roadmap
  • Sonja M. Hyrynsalmi
  • Minna M. Rantanen
  • Johannes Holvitie
  • Sami Hyrynsalmi
  • Erkki Sutinen
Conference paper
Part of the Communications in Computer and Information Science book series (CCIS, volume 907)

Abstract

This conceptual-analytical paper presents and defines the concept of ‘human resource debt’ (i.e., HR debt). The presented concept draws from the software engineering field’s recent work in the technical debt management, yet it departures from the existing conceptualizations by focusing on skills and competences of individual employees as well as emphasizing the need to manage the skill pool with conscious decisions. As with its paragons, this novel concept aims to help to understand, control and utilize better the phenomenon by using a simple metaphor. In addition, the metaphor, borrowed from the economics, also emphasizes the potential price that has to be paid back later. In the discussion, the ever-changing software industry is used as an example industrial domain; however, the concept should be generalizable to other fields. Finally, the paper lays foundations for future work and proposes initial actions needed for forming a proper research agenda.

Keywords

Human resource debt Skills Human resource management Talent shortage Technical debt 

References

  1. 1.
    Schwab, K.: The fourth industrial revolution. Foreign Affairs (2018). https://www.foreignaffairs.com/articles/2015-12-12/fourth-industrial-revolution. Accessed 23 Jan 2018
  2. 2.
    OECD: New Markets and New Jobs. No. 255 in OECD Digital Economy Papers. OECD Publishing (2016).  https://doi.org/10.1787/5jlwt496h37l-en
  3. 3.
    World Economic Forum: The Future of Jobs: Employment, Skills and Workforce Strategy for Fourth Industrial Revolution. Global Challenge Insight Report, World Economic Forum, Geneva, Switzerland (2016)Google Scholar
  4. 4.
    Luoma, E., Rönkkö, M., Tahvanainen, S.: Ohjelmistoyrityskartoitus 2017. (Finnish software industry survey 2017) (2017). http://www.softwareindustrysurvey.fi/wp-content/uploads/2017/10/Oskari2017-vfinal.pdf. Accessed 23 Jan 2018
  5. 5.
    Tieto- ja viestintätekniikan ammattilaiset TIVIA ry: Ohjelmisto-osaaminen Suomen talouskasvun ja uudistumisen jarruna - vuonna 2020 Suomesta puuttuu 15 000 ohjelmistoammattilaista (2017). http://www.tivia.fi/lehdistotiedote/ohjelmisto-osaaminen-suomen-talouskasvun-ja-uudistumisen-jarruna. Press release
  6. 6.
    Hyrynsalmi, S.M., Rantanen, M.M., Hyrynsalmi, S.: Do we have what is needed to change everything? A survey of Finnish software businesses on labour shortage and its potential impacts. In: Proceedings of 13th IFIP TC9 Human Choice and Computers Conference: “This Changes Everything”, pp. 1–12 (2018)Google Scholar
  7. 7.
    Metsä-Tokila, T.: Kasvun mahdollistajat - ohjelmistoala ja tekninen konsultointi. Tech. rep., Työ- ja elinkeinoministeriö TEM, Helsinki (2017). http://www.eva.fi/wp-content/uploads/2018/04/eva_analyysi_no_62.pdf
  8. 8.
    Hyrynsalmi, S.M., Rantanen, M.M., Hyrynsalmi, S.: The war for talents in software business: how Finnish software companies are perceiving and coping with the labour shortage? (2018, manuscript in review)Google Scholar
  9. 9.
    Ahopelto, T.: Nollaksi vai ykköseksi. Eva analyysi no 62, Elinkeinoelämän valtuuskunta EVA, Helsinki (2018). http://www.eva.fi/wp-content/uploads/2018/04/eva_analyysi_no_62.pdf
  10. 10.
    Hyrynsalmi, S.M., Rantanen, M.M., Hyrynsalmi, S.: The war of talents in software business: polarisation of the software labour force? In: Proceedings of 7th Well-being in the Information Society: Fighting Inequalities, pp. 1–12 (2018)Google Scholar
  11. 11.
    Avgeriou, P., Kruchten, P., Ozkaya, I., Seaman, C.: Managing technical debt in software engineering (dagstuhl seminar 16162). In: Dagstuhl Reports, vol. 6, no. 4, pp. 110–138 (2016).  https://doi.org/10.4230/DagRep.6.4.110
  12. 12.
    Holvitie, J.: Technical debt in software development – examining premises and overcoming implementation for efficient management. Ph.D. thesis, University of Turku, Turku, Finland (2017)Google Scholar
  13. 13.
    Klotins, E., et al.: Exploration of technical debt in start-ups. In: ICSE-SEIP 2018: 40th International Conference on Software Engineering: Software Engineering in Practice Track, p. 10. ACM, New York (2018).  https://doi.org/10.1145/3183519.3183539
  14. 14.
    Järvinen, P.: On a variety of research output types. Series of Publications D - Net Publications D-2004-6, Department of Computer Sciences, University of Tampere, Tampere, Finland (2004)Google Scholar
  15. 15.
    Kaufman, B.E.: Early Human Resource Management: Issues and Themes, pp. 1–35. Cornell University Press, Ithaca (2008)Google Scholar
  16. 16.
    Legge, K.: What is Human Resource Management?. Macmillan Press Ltd., Hampshire (1995)CrossRefGoogle Scholar
  17. 17.
    Burke, R.J., Ng, E.: The changing nature of work and organizations: implications for human resource management. Hum. Res. Manag. Rev. 16(2), 86–94 (2006).  https://doi.org/10.1016/j.hrmr.2006.03.006. The New World of Work and OrganizationsCrossRefGoogle Scholar
  18. 18.
    Cardon, M.S., Stevens, C.E.: Managing human resources in small organizations: what do we know? Hum. Res. Manag. Rev. 14(3), 295–323 (2004).  https://doi.org/10.1016/j.hrmr.2004.06.001CrossRefGoogle Scholar
  19. 19.
    Brown, C., Hamilton, J.T., Hamilton, J., Medoff, J.L.: Employers Large and Small. Harvard University Press, Cambridge (1990)Google Scholar
  20. 20.
    Storey, D.J., Westhead, P.: Management training in small firms - a case of market failure. Hum. Res. Manag. J. 7, 61–71 (1997).  https://doi.org/10.1111/j.1748-8583.1997.tb00282.xCrossRefGoogle Scholar
  21. 21.
    Baron, J., Hannan, M.: Organizational blueprints for success in high-tech start-ups: lessons from the Stanford project on emerging companies. Calif. Manag. Rev. 44(3), 8–36 (2002).  https://doi.org/10.2307/41166130CrossRefGoogle Scholar
  22. 22.
    Storey, D.J.: Exploring the link, among small firms, between management training and firm performance: a comparison between the UK and other OCED countries. Int. J. Hum. Res. Manag. 15(1), 112–130 (2004).  https://doi.org/10.1080/0958519032000157375CrossRefGoogle Scholar
  23. 23.
    Nowak, M.J., Grantham, C.E.: The virtual incubator: managing human capital in the software industry. Res. Policy 29(2), 125–134 (2000).  https://doi.org/10.1016/S0048-7333(99)00054-2CrossRefGoogle Scholar
  24. 24.
    Cunningham, W.: The wycash portfolio management system. ACM SIGPLAN OOPS Messenger 4(2), 29–30 (1993)CrossRefGoogle Scholar
  25. 25.
    McConnell, S.: Managing technical debt, pp. 1–14. Construx Software Builders Inc. (2008)Google Scholar
  26. 26.
    Kruchten, P., Nord, R.L., Ozkaya, I.: Technical debt: from metaphor to theory and practice. IEEE Softw. 29(6), 18–21 (2012)CrossRefGoogle Scholar
  27. 27.
    Seaman, C., Guo, Y.: Measuring and monitoring technical debt. In: Advances in Computers, vol. 82, pp. 25–46. Elsevier (2011)Google Scholar
  28. 28.
    Letouzey, J.L.: The SQALE method for evaluating technical debt. In: Proceedings of the Third International Workshop on Managing Technical Debt, pp. 31–36. IEEE Press (2012)Google Scholar
  29. 29.
    Fontana, F.A., Pigazzini, I., Roveda, R., Tamburri, D., Zanoni, M., Di Nitto, E.: Arcan: a tool for architectural smells detection. In: 2017 IEEE International Conference on Software Architecture Workshops (ICSAW), pp. 282–285. IEEE (2017)Google Scholar
  30. 30.
    Holvitie, J., Leppänen, V.: Debtflag: technical debt management with a development environment integrated tool. In: 2013 4th International Workshop on Managing Technical Debt (MTD), pp. 20–27 (2013).  https://doi.org/10.1109/MTD.2013.6608674
  31. 31.
    Seaman, C., et al.: Using technical debt data in decision making: potential decision approaches. In: Proceedings of the Third International Workshop on Managing Technical Debt, pp. 45–48. IEEE Press (2012)Google Scholar
  32. 32.
    Zazworka, N., Seaman, C., Shull, F.: Prioritizing design debt investment opportunities. In: Proceedings of the 2nd Workshop on Managing Technical Debt, pp. 39–42. ACM (2011)Google Scholar
  33. 33.
    Cherns, A.: The principles of socio-technical design. Hum. Relat. 29(8), 783–792 (1976)CrossRefGoogle Scholar
  34. 34.
    Enid, M.: The story of socio - technical design: reflections on its successes, failures and potential. Inf. Syst. J. 16(4), 317–342 (2016).  https://doi.org/10.1111/j.1365-2575.2006.00221.xCrossRefGoogle Scholar
  35. 35.
    Mumford, E.: Technology and freedom: a socio-technical approach. In: Coakes, E., Willis, D., Lloyd-Jones, R. (eds.) The New SosioTech. CSCW, pp. 29–38. Springer, Heidelberg (2000).  https://doi.org/10.1007/978-1-4471-0411-7_3CrossRefGoogle Scholar
  36. 36.
    Bødker, S., Grønbæk, K., Kyng, M.: Cooperative design: techniques and experiences from Scandinavian scene, pp. 157–175. Lawrence Erlbaum Associates Inc., New Jersey (1993)Google Scholar
  37. 37.
    Hirschheim, R., Klein, H.K.: A glorious and not-so-short history of the information systems field. J. Assoc. Inf. Syst. 13, 188–235 (2012)Google Scholar
  38. 38.
    Petter, S., DeLone, W., McLean, E.R.: The past, present, and future of “is success”. J. Assoc. Inf. Syst. 13, 341–362 (2012)Google Scholar
  39. 39.
    Järvinen, P.: Research questions guiding selection of an appropriate research method. Series of Publications D - Net Publications D-2004-5, Department of Computer Sciences, University of Tampere, Tampere, Finland (2004)Google Scholar
  40. 40.
    Tamburri, D.A., Kruchten, P., Lago, P., van Vliet, H.: What is social debt in software engineering? In: 2013 6th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE), pp. 93–96 (2013).  https://doi.org/10.1109/CHASE.2013.6614739
  41. 41.
    Tamburri, D.A., Kruchten, P., Lago, P., van Vliet, H.: Social debt in software engineering: insights from industry. J. Internet Serv. Appl. 6(1), 10 (2015).  https://doi.org/10.1186/s13174-015-0024-6CrossRefGoogle Scholar
  42. 42.
    Tom, E., Aurum, A., Vidgen, R.: An exploration of technical debt. J. Syst. Softw. 86(6), 1498–1516 (2013).  https://doi.org/10.1016/j.jss.2012.12.052CrossRefGoogle Scholar
  43. 43.
    Guo, Y., et al.: Tracking technical debt – an exploratory case study. In: 2011 27th IEEE International Conference on Software Maintenance (ICSM), pp. 528–531 (2011).  https://doi.org/10.1109/ICSM.2011.6080824

Copyright information

© Springer Nature Switzerland AG 2018

Authors and Affiliations

  1. 1.University of TurkuTurkuFinland
  2. 2.Turku School of EconomicsUniversity of TurkuTurkuFinland
  3. 3.Department of Future TechnologiesUniversity of TurkuTurkuFinland
  4. 4.Pervasive ComputingTampere University of TechnologyPoriFinland

Personalised recommendations