Nothing Special   »   [go: up one dir, main page]

skip to main content
research-article

Enhancing agile software development in the banking sector—A comprehensive case study at LHV

Published: 01 July 2021 Publication History

Abstract

FinTech companies are challenging established financial institutions' dominance by offering the same products with a superior customer experience and delivering new features faster. The adoption of agile software development partially enables this competitive advantage. In response to this challenge, banks explore how they can improve their agile processes. LHV, a mid‐sized bank, uses agile practices but faces the challenge of further improvement to stay competitive with FinTech companies. In this article, we explore how LHV can improve its agile software development process. We conduct a case study at LHV where we first derive eight change proposals based on a literature review and interviews. Then, we report on how LHV implemented the change proposals and their perceived impact. Our results stress the importance of taking a coherent approach to improving agile processes by considering both business units and operations involved in the product life‐cycle. It is also necessary to align organizational structures to enable team autonomy by, for instance, decentralizing decision authority. Finally, it is beneficial to adapt agile practices to their context and have an IT architecture and technology supporting the agile approach.

Graphical Abstract

We conducted a comprehensive case study to enhance the agile software process development at LHV, an Estonian bank. Our results stress the importance of (1) having an organizational‐wide agile mindset; (2) the alignment among organizational structures, products, and practices; (3) the coexistence of different practices and methods; and (4) a technical environment and software architecture that is coherent with the adopted agile practices.

References

[1]
Gai K, Qiu M, Sun X. A survey on FinTech. J Netw Comput Appl. 2018;103:262‐273.
[2]
Vasiljeva T, Lukanova K. Commercial banks and Fintech companies in the digital transformation: Challenges for the future. J Bus Manag. 2016(11):25‐33.
[3]
Lee I, Shin YJ. Fintech: Ecosystem, business models, investment decisions, and challenges. Bus Horiz. 2018;61(1):35‐46.
[4]
Hajrizi E, Bytyci F. Agile software development process at financial institution in kosovo. IFAC‐PapersOnLine. 2015;48(24):153‐156.
[5]
Reddy A. The Scrumban [R]evolution: Getting the Most Out of Agile, Scrum, and Lean Kanban. Boston, United States: Addison‐Wesley Professional; 2015.
[6]
Chow T, Cao D‐B. A survey study of critical success factors in agile software projects. J Syst Softw. 2008;81(6):961‐971.
[7]
Aldahmash A, Gravell AM, Howard Y. A review on the critical success factors of agile software development. European conference on software process improvement. Springer; 2017:504‐512.
[8]
Romanova I, Kudinska M. Banking and fintech: A challenge or opportunity? Contemp Stud Econ Fin Anal. 2016;98:21‐35.
[9]
Dyba T. An empirical investigation of the key factors for success in software process improvement. IEEE Trans Softw Eng. 2005;31(5):410‐424.
[10]
Rainer A, Hall T. Key success factors for implementing software process improvement: a maturity‐based analysis. J Syst Softw. 2002;62(2):71‐84.
[11]
Razavi AM, Ahmad R. Agile development in large and distributed environments: a systematic literature review on organizational, managerial and cultural aspects. 2014 8th. malaysian software engineering conference (mysec): IEEE; 2014:216‐221.
[12]
Putta A. Scaling agile software development to large and globally distributed large‐scale organizations. ICGSE'18. ACM. New York, NY, USA: Association for Computing Machinery; 2018:141‐144. https://doi.org/10.1145/3196369.3196386
[13]
Dikert K, Paasivaara M, Lassenius C. Challenges and success factors for large‐scale agile transformations: a systematic literature review. J Syst Softw. 2016;119:87‐108.
[14]
Livermore JA. Factors that significantly impact the implementation of an agile software development methodology. J Softw. 2008;3(4):31‐36.
[15]
Lindvall M, Basili V, Boehm B, et al. Empirical findings in agile methods. Conference on extreme programming and agile methods. Berlin/Heidelberg, Germany: Springer; 2002:197‐207.
[16]
Ivar Jacobson International . Nordea A Uniform Heartbeat with Help from Scaled Agile Framework ® and IJI. 2015. https://www.ivarjacobson.com/sites/default/files/field_iji_file/article/nordea_case_study1.pdf
[17]
Birkinshaw J. What to expect from agile. MIT Sloan Manag Rev. 2018;59(2):39‐42.
[18]
Jacobs P, Schlatmann B, Mahadevan D. Ing's agile transformation. The McKinsey Quarterly; 2017.
[19]
Couzens JA. Implementing an enterprise system at Suncorp using Agile development. IEEE; 2009.
[20]
Kilu E, Milani F, Scott E, Pfahl D. Agile software process improvement by learning from financial and FinTech companies: LHV bank case study, International conference on software quality. Lecture Notes in Business Information Processing, Vol 338. Springer, Cham; 2019:57‐69.
[21]
Pino FJ, García F, Piattini M. Software process improvement in small and medium software enterprises: a systematic review. Softw Qual J. 2008;16(2):237‐261.
[22]
Niazi M, Mishra A, Gill AQ. What do software practitioners really think about software process improvement project success? An exploratory study. Arab J Sci Eng. 2018;43(12):7719‐7735.
[23]
Boehm B, Turner R. Management challenges to implementing agile processes in traditional development organizations. IEEE Softw. 2005;22(5):30‐39.
[24]
Paasivaara M, Lassenius C, Heikkilä VT. Inter‐team coordination in large‐scale globally distributed scrum: Do scrum‐of‐scrums really work? Proceedings of the 2012 acm‐ieee international symposium on empirical software engineering and measurement: IEEE; 2012:235‐238.
[25]
Laanti M, Kettunen P. Safe Adoptions in Finland: A Survey Research. Cham: Springer; 2019;81‐87.
[26]
Suryaatmaja K, Wibisono D, Ghazali A, Fitriati R. Uncovering the failure of agile framework implementation using SSM‐based action research. Palgrave Commun. 2020;6(1):1‐18.
[27]
Misra SC, Kumar V, Kumar U. Identifying some important success factors in adopting agile software development practices. J Syst Softw. 2009;82(11):1869‐1890.
[28]
Miler J, Gaida P. On the agile mindset of an effective team—an industrial opinion survey. In: 2019 federated conference on computer science and information systems (fedcsis). New York, New York, US: IEEE; 2019:841‐849.
[29]
Salameh A, Bass JM. Spotify tailoring for architectural governance. International conference on agile software development. Berlin/Heidelberg, Germany: Springer; 2020:236‐244.
[30]
Stray V, Moe NB, Hoda R. Autonomous agile teams: challenges and future directions for research. Proceedings of the 19th international conference on agile software development: Companion: ACM; 2018:1‐5.
[31]
Salameh A, Bass J. Influential factors of aligning spotify squads in mission‐critical and offshore projects—a longitudinal embedded case study. International conference on product‐focused software process improvement. Berlin/Heidelberg, Germany: Springer; 2018:199‐215.
[32]
Moe NB, Dingsøyr T, Dybå T. Understanding self‐organizing teams in agile software development. 19th australian conference on software engineering (ASWEC 2008). New York, New York, US: IEEE; 2008:76‐85.
[33]
Moe NB, Dahl BH, Stray V, Karlsen LS, Schjødt‐Osmo S. Team autonomy in large‐scale agile. Proceeding of the 52nd Hawaii International Conference on System Sciences (HICSS 2019). Honolulu, United States: ScholarSpace, AIS Electronic Library; 2019:6997‐7006. https://doi.org/10.24251/HICSS.2019.839
[34]
Keenan F. Agile process tailoring and problem analysis (aptly). IEEE; 2004.
[35]
Berkani A, Causse D, Thomas L. Triggers analysis of an agile transformation: the case of a central bank. Procedia Comput Sci. 2019;164:449‐456.
[36]
Roses LK, Windmöller A, Carmo EA. Favorability conditions in the adoption of agile method practices for software development in a public banking. JISTEM‐J Inf Syst Technol Manag. 2016;13(3):439‐458.
[37]
Mikalsen M, Stray V, Moe NB, Backer I. Shifting conceptualization of control in agile transformations. International conference on agile software development: Springer; 2020:173‐181.
[38]
Svejvig P, Nielsen A‐DF. The dilemma of high level planning in distributed agile software projects: an action research study in a danish bank. Agility across time and space: Springer; 2010:171‐182.
[39]
Seffernick TR. Enabling agile in a large organization our journey down the yellow brick road. Agile 2007 (AGILE 2007). New York, New York, US: IEEE; 2007:200‐206.
[40]
Runeson P, Höst M. Guidelines for conducting and reporting case study research in software engineering. Empir Softw Eng. 2009;14(2):131.
[41]
Yin RK. Case Study Research and Applications: Design and Methods. Thousand Oaks, California, United States: Sage publications; 2017.
[42]
Flyvbjerg B. Five misunderstandings about case‐study research. Qual Inq. 2006;12(2):219‐245.
[43]
Kitchenham B, Pickard L, Pfleeger SL. Case studies for method and tool evaluation. IEEE Softw. 1995;12(4):52‐62.
[44]
Saldana J. The Coding Manual For Qualitative Researchers. 3rd ed. London: Sage Publications; 2009.
[45]
Ladas C. Scrumban and Other Essays on Kanban Systems for Lean. Seattle, WA, United States: Modus Cooperandi Press; 2008.
[46]
Jureczko M. The level of agility in testing process in a large scale financial software project. In: T. Hruška, L. Madeyski, M. Ochodek, eds. Software engineering techniques in progress: Oficyna Wydawnicza Politechniki Wrocławskiej; 2008:139‐152.
[47]
Niven PR, Lamorte B. Objectives and Key Results: Driving Focus, Alignment, and Engagement With OKRs. Hoboken, New Jersey: John Wiley & Sons; 2016.
[48]
Kyte A, Norton D, Wilson N. Ten Things the CIO Needs to Know About Agile Development: Gartner; 2014.
[49]
Kniberg H, Skarin M. Kanban and Scrum—making the most of both (Enterprise Software Development). Lulu.com; 2010.
[50]
Sutherland J, Schwaber K. The scrum guide, 268. The definitive guide to scrum: the rules of the game. Scrum.org; 2013.
[51]
Al‐Baik O, Miller J. The kanban approach, between agility and leanness: a systematic review. Empir Softw Eng. 2015;20(6):1861‐1897.
[52]
Nurdiani I, Börstler J, Fricker S, Petersen K. A preliminary checklist for capturing baseline situations in studying the impacts of agile practices introduction IEEE; 2018:25‐28.
[53]
Rolland K, Dingsoyr T, Fitzgerald B, Stol K‐J. Problematizing agile in the large: alternative assumptions for large‐scale agile development Association for Information Systems (AIS); 2016:1‐21.
[54]
Marques R, da Silva MM, Ferreira DR. Assessing agile software development processes with process mining: a case study, Vol 1. IEEE; 2018:109‐118.
[55]
Scott E, Milani F, Pfahl D. Data science and empirical software engineering. Contemporary empirical methods in software engineering. Berlin/Heidelberg, Germany: Springer; 2020:217‐233.
[56]
Vom Brocke J, Rosemann M. Handbook on Business Process Management 1: Introduction, Methods, and Information Systems. Berlin/Heidelberg, Germany: Springer; 2014.
[58]
Myrbakken H, Colomo‐Palacios R. Devsecops: a multivocal literature review. Software Process Improvement and Capability Determination. Cham: Springer; 2017:17‐29.

Cited By

View all
  • (2024)Towards engineering higher quality intelligent environments: a multi case study approachSoftware Quality Journal10.1007/s11219-024-09678-032:3(1075-1135)Online publication date: 1-Sep-2024
  • (2023)Surveying the Academic Literature on the Use of OKR (Objective and Key Results)Proceedings of the XIX Brazilian Symposium on Information Systems10.1145/3592813.3592934(427-434)Online publication date: 29-May-2023
  • (2022)Software Process Evaluation from User Perceptions and Log DataJournal of Software: Evolution and Process10.1002/smr.243834:4Online publication date: 5-Apr-2022

Recommendations

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image Journal of Software: Evolution and Process
Journal of Software: Evolution and Process  Volume 33, Issue 7
July 2021
129 pages
ISSN:2047-7473
EISSN:2047-7481
DOI:10.1002/smr.v33.7
Issue’s Table of Contents

Publisher

John Wiley & Sons, Inc.

United States

Publication History

Published: 01 July 2021

Author Tags

  1. agile software development
  2. case study
  3. financial institutions
  4. FinTech
  5. software process improvement

Qualifiers

  • Research-article

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)0
  • Downloads (Last 6 weeks)0
Reflects downloads up to 04 Oct 2024

Other Metrics

Citations

Cited By

View all
  • (2024)Towards engineering higher quality intelligent environments: a multi case study approachSoftware Quality Journal10.1007/s11219-024-09678-032:3(1075-1135)Online publication date: 1-Sep-2024
  • (2023)Surveying the Academic Literature on the Use of OKR (Objective and Key Results)Proceedings of the XIX Brazilian Symposium on Information Systems10.1145/3592813.3592934(427-434)Online publication date: 29-May-2023
  • (2022)Software Process Evaluation from User Perceptions and Log DataJournal of Software: Evolution and Process10.1002/smr.243834:4Online publication date: 5-Apr-2022

View Options

View options

Get Access

Login options

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media