Approaches to implementing the lean methodology in software development: A survey

Approaches to implementing the lean methodology in software development: A survey

Behzad Boostanchi, Behrouz Minaei


Lean thinking is making its way into the software industry these days. After its successful application in manufacturing, some researchers tried to bring it into the software engineering field, which has resulted in a couple of practical approaches. However, no structured survey of the existing literature in this field has been conducted so far. In this paper, we studied the different proposed approaches to using the lean discipline in software production. We tried to classify these approaches into three main categories: Lean as a subset of agile, Lean as a standalone methodology, and Lean hybrid approaches. We reviewed the significant developments in each category and outlined their possible challenges. Then we propose a higher-level classification. This survey concludes with a short discussion on the differences between lean and other software development methodologies.


Software Engineering, Development Methodologies, Agile, Lean, Categorization, Survey


  • [1] B. Randell, “The 1968/69 NATO Software Engi-neering Reports,” NATO Software Engineering Reports, 1996. [Online]. Available: [Accessed: 01-Jan-2020].
  • [2] K. Bek, J. Grenning, and T. C. Erren, “Manifesto for Agile Software Development,” Agile Manifesto, 2001. [Online]. Available: [Accessed: 10-Jan-2020].
  • [3] M. Cusumano, The Japanese Automobile Industry: Technology and Management at Nissan and Toyota (Har-vard East Asian Monographs). Harvard University Asia Center, 1989.
  • [4] J. F. Krafcik, “Triumph of the lean production sys-tem,” Sloan Management Review, vol. 30, pp. 41–52, 1988.
  • [5] J. P. Womack, D. T. Jones, and D. Roos, The Ma-chine That Changed the World. Simon and Schuster, 2008.
  • [6] M. Graban, “The Term ‘Lean Production’ is 25 Years Old – Some Thoughts on the Original John Krafcik Article,” Lean Blog, 2013. [Online]. Available: [Accessed: 10-Jan-2020].
  • [7] D. J. Anderson, “Lean software development,” Microsoft MSDN, 2012. [Online]. Available: [Accessed: 10-Jan-2020].
  • [8] Y. Monden, Toyota Production System. Boston, MA: Springer Science & Business Media, 2012.
  • [9] H. Jonsson, “Lean Software Development: A Sys-tematic Review,” IDT Miniconference on Interesting Results in Computer …, 2012.
  • [10] J. K. Liker, The Toyota Way. McGraw Hill Profes-sional, 2003.
  • [11] D. Nave, “How to compare six sigma, lean and the theory of constraints,” 2002.
  • [12] G. Tennant, Six Sigma. Gower Publishing, Ltd., 2001.
  • [13] J. Antony and C. Fergusson, “Six Sigma in the software industry: results from a pilot study,” Manage-rial Auditing Journal, vol. 19, no. 8, pp. 1025–1032, Oct. 2004.
  • [14] C. B. Tayntor, Six Sigma software development. 2007.
  • [15] R. Moore, L. S. C. C. Inc, 1998, “Theory of con-straints and lean manufacturing: friends or foes,”
  • [16] K. Alvarez, D. Aldas, J. R. 2. I. C. on, 2017, “To-wards Lean Manufacturing from Theory of Con-straints: A Case Study in Footwear Industry - IEEE Conference Publication,”
  • [17] M. Alsmadi, A. Almani, and Z. Khan, “Imple-menting an integrated ABC and TOC approach to enhance decision making in a Lean context,” Interna-tional Journal of Quality & Reliability Management, vol. 31, no. 8, pp. 906–920, Aug. 2014.
  • [18] D. A. de Jesus Pacheco African Journal of Busi-ness2015, “TOC, lean and six sigma: The missing link to increase productivity?,”
  • [19] D. J. Anderson, Agile Management for Software En-gineering. Prentice Hall Professional, 2003.
  • [20] R. L. Nord, I. Ozkaya, and R. S. Sangwan, “Mak-ing architecture visible to improve flow management in lean software development,” IEEE Softw., 2012.
  • [21] M. Poppendieck and T. Poppendieck, Lean Soft-ware Development. Addison-Wesley, 2003.
  • [22] C. Larman and B. Vodde, Scaling Lean & Agile Development. Pearson Education, 2008.
  • [23] C. Larman and B. Vodde, Practices for Scaling Lean & Agile Development. Pearson Education, 2010.
  • [24] J. O. Coplien and G. Bjørnvig, Lean Architecture. John Wiley & Sons, 2011.
  • [25] D. Bulkin, “Lean Software & Systems Consortium Reorganizes as Lean Systems Society,” 2012.
  • [26] Lean System Society, “Lean Systems Society Cre-do,” May 2012.
  • [27] A. Shalloway, G. Beaver, and J. R. Trott, Lean-Agile Software Development. Pearson Education, 2009.
  • [28] M. Poppendieck and T. Poppendieck, Implement-ing Lean Software Development. Pearson Education, 2007.
  • [29] K. Schwaber and M. Beedle, Agile Software Devel-opment with Scrum. 2002.
  • [30] J. A. Highsmith, Agile Software Development Eco-systems. Addison-Wesley Professional, 2002.
  • [31] D. G. Reinertsen, The Principles of Product Devel-opment Flow. Celeritas Pub, 2009.
  • [32] Lean Kanban University, “The Kanban Method,” Lean Kanban University, 2014. [Online]. Available: [Ac-cessed: 10-Jan-2019].
  • [33] C. Ladas, “Modeling kanban systems as Petri nets,” Lean Software Engineering, 2008. [Online]. Available: [Accessed: 10-Jan-2020].
  • [34] C. Ladas, “CONWIP systems,” Lean Software En-gineering, 2009. [Online]. Available: [Accessed: 01-Oct-2020].
  • [35] C. Ladas, “A swimlane for ad-hoc workflow,” Lean Software Engineering, 2009. [Online]. Available: [Accessed: 10-Jan-2020].
  • [36] P. Brodzinski, “The Kanban Story: Moving Cards Back,” 2010. [Online]. Available: [Accessed: 10-Jan-2020].
  • [37] A. Maglyas, U. Nikula, and K. Smolander, “Lean Solutions to Software Product Management Prob-lems,” IEEE Softw., vol. 29, no. 5, pp. 40–46, 2012.
  • [38] A. Janes and G. Succi, Lean Software Development in Action. Berlin, Heidelberg: Springer, 2014.
  • [39] V. R. Basili, G. Caldiera, and H. D. Rombach, Experience Factory. Hoboken, NJ, USA: John Wiley & Sons, Inc., 2002.
  • [40] S. Astromskis, “Towards a gqm model for is de-velopment process selection,” presented at the The tarpuniversitetine magistrantu ir doktorantu konfer-encija, Kaunas,Lithuania, 2011.
  • [41] L. Lavazza, E. Frumento, and R. Mazza, “GQM-Based Definition and Evaluation of Software Project Success Indicators.,” ICSOFT, vol. 586, no. 13, pp. 228–249, 2015.
  • [42] I. Perera, “A Blended Process Model for Agile Software Development with Lean Concept,” in Future Manufacturing Systems, no. 2, Sciyo, 2010.
  • [43] R. Brenner and S. Wunder, “Scaled Agile Frame-work: Presentation and real world example,” present-ed at the 2015 IEEE Eighth International Conference on Software Testing, Verification and Validation Workshops (ICSTW), 2015, pp. 1–2.
  • [44] A. Elssamadisy, “Has SAFe Cracked the Large Agile Adoption Nut?,” 2013.
  • [45] C. ONeil, G. Clark, and G. Evans, “The SAFe way to Lean Software Development,” Scaled Agile, 2014. [Online]. Available: [Accessed: 10-Jan-2020].
  • [46] Scaled Agile, “PSI/Release Abstract,” 2014. [Online]. Available: [Accessed: 12-Jan-2017].
  • [47] O. Turetken, I. Stojanov, and J. J. M. Trienekens, “Assessing the adoption level of scaled agile devel-opment: a maturity model for Scaled Agile Frame-work,” Journal of Software: Evolution and Process, Jul. 2016.
  • [48] J. Hurtado, “Open Kanban - An Open Source, Ultra Light, Agile & Lean Method,” 2013. [Online]. Available: [Accessed: 10-Jan-2020].
  • [49] J. Hurtado, “Improving Scrum with the Kanban-Ace Framework,” 2016.
  • [50] A. Przybylek and M. K. Olszewski, “Adopting collaborative games into Open Kanban,” presented at the 2016 Federated Conference on Computer Science and Information Systems (FedCSIS, 2016, pp. 1539–1543.
  • [51] J. Hurtado, “How to get started with Open Kan-ban in 5 Minutes,”, 2014. [Online]. Available: [Ac-cessed: 10-Jan-2020].
  • [52] “5 Lean Tools and Principles to Integrate into Six Sigma - iSixSigma,” 26-Feb-2010. [Online]. Available: [Accessed: 10-Jan-2020].
  • [53] D. L. Hallowell, “Software Development Con-vergence: Six Sigma-Lean-Agile,”, 2014. [Online]. Available: [Accessed: 12-Jan-2017].
  • [54] A. Correia, A. Gonçalves, and S. Misra, “Integrat-ing the Scrum Framework and Lean Six Sigma.,” IC-CSA, vol. 11623, no. 12, pp. 136–149, 2019.
  • [55] C. Ladas, “scrum-ban,” Lean Software Engineering, 2008. [Online]. Available: [Accessed: 10-Jan-2020].
  • [56] C. Ladas, Scrumban - Essays on Kanban Systems for Lean Software Development., 2009.
  • [57] R. J. Qureshi, M. O. Alassafi, and H. M. Shahzad, “Lean Agile Integration for the Development of Large Size Projects,” 2019.
  • [58] S. Chatterjee, “The waterfall that won"t go away,” ACM SIGSOFT Software Engineering Notes, vol. 35, no. 1, pp. 9–10, Jan. 2010.
  • [59] The Waterfall Alliance, [Online]. Available: [Accessed: 06-Feb-2017].
  • [60] R. J. Kusters, Y. van de Leur, W. G. M. M. Rut-ten, and J. J. M. Trienekens, “When Agile Meets Wa-terfall - Investigating Risks and Problems on the Inter-face between Agile and Traditional Software Devel-opment in a Hybrid Development Organization.,” ICEIS, pp. 271–278, 2017.
  • [61] M. Kuhrmann, P. Diebold, J. Münch, P. Tell, V. Garousi, M. Felderer, K. Trektere, F. McCaffery, O. Linssen, E. Hanser, and C. R. Prause, “Hybrid soft-ware and system development in practice - waterfall, scrum, and beyond.,” ICSSP, pp. 30–39, 2017.
  • [62] T. L. Whitaker, “Differences between Waterfall, Iterative Waterfall, Scrum and Lean Software Devel-opment,”, 2009. [Online]. Available: [Accessed: 12-Jan-2017].
  • [63] W. R. Bischofberger and G. Pomberger, “Con-cepts and Tools for Exploratory Programming,” in System Alerts, no. 4, Berlin, Heidelberg: Springer Ber-lin Heidelberg, 1992, pp. 75–108.
  • [64] P. Carvalho, “Agile Testing vs Exploratory Test-ing,”, 2014. [Online]. Available: [Accessed: 10-Jan-2020].
  • [65] S. Kharytonov, “Waterfall, RUP and Agile: Which is Right for You,”, 2009. [Online]. Available: [Accessed: 10-Jan-2020].