Agile Software Process Improvement by Learning from Financial and Fintech Companies: LHV Bank Case Study
A large shift towards the use of agile software development in different industrial sectors is evident nowadays. Financial institutions are not unfamiliar with this tendency since they have the need to respond faster to the changes in their business environments. This is partly due to the new generation of financial technology (fintech) companies that have shown a significant difference in time to market and in speeding up software development. To compete with fintech companies, financial institutions are looking for improving their software development processes focusing on applying agile practices in a better way. This article presents a set of proposals to improve software development in the LHV Bank. The set of proposals has been determined through a literature review and interviews conducted in two leading financial institutions and two fintech companies. The analysis done allowed us to understand the best practices that are currently being applied, how they are implemented, and which ones are suitable for application in LHV Bank.
KeywordsAgile software development Financial institutions Fintech companies Software process improvement
This research was supported by the institutional research grant IUT20-55 of the Estonian Research Council.
- 1.Beck, K., et al.: Manifesto for agile software development (2001)Google Scholar
- 2.Couzens, J.: Implementing an enterprise system at Suncorp using agile development. In: Australian Software Engineering Conference: ASWEC 2009, vol. 20, pp. 35–39 (2009)Google Scholar
- 5.Jureczko, M.: The level of agility in testing process in a large scale financial software project, software engineering techniques in progress. Oficyna Wydawnicza Politechniki Wroclawskiej, pp. 139–152 (2008)Google Scholar
- 6.Kniberg, H., Skarin, M.: Kanban and Scrum - Making the Most of Both (2010)Google Scholar
- 7.Kyte, A., Norton, D., Wilson, N.: Ten Things the CIO Needs to Know About Agile Development. Gartner, United States of America (2014)Google Scholar
- 8.Ladas, K.: Scrumban and Other Essays on Kanban Systems for Lean Software Development. Modus Cooperandi Press, Seattle (2008)Google Scholar
- 11.Nordea, A.: Uniform Heartbeat with Help from Scaled Agile Framework and IJI. Ivar Jacobson International SA (2015)Google Scholar
- 12.Reddy, A.: The Scrumban [R]evolution: Getting the Most Out of Agile, Scrum, and Lean Kanban. Pearson Education Inc., Boston (2016)Google Scholar
- 13.Ries, E.: Startup, The Lean: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses. New York (2011)Google Scholar
- 16.Scott, E., Pfahl, D., Hebig, R., Heldal, R., Knauss, E.: Initial results of the HELENA survey conducted in Estonia with comparison to results from Sweden and worldwide. In: Felderer, M., Méndez Fernández, D., Turhan, B., Kalinowski, M., Sarro, F., Winkler, D. (eds.) PROFES 2017. LNCS, vol. 10611, pp. 404–412. Springer, Cham (2017). https://doi.org/10.1007/978-3-319-69926-4_29CrossRefGoogle Scholar
- 17.Seffernick, T.R.: Enabling agile in a large organization our journey down the yellow brick road. In: 2007 Agile Conference (AGILE) (2007)Google Scholar
- 18.Svejvig, P., Nielsen, A.: The dilemma of high level planning in distributed agile software projects an action research study in a Danish bank. In: Šmite, D., Moe, N., Ågerfalk, P. (eds.) Agility Across Time and Space, pp. 171–182. Springer, Heidelberg (2010). https://doi.org/10.1007/978-3-642-12442-6_12CrossRefGoogle Scholar