Logo PTI
Polish Information Processing Society
Logo FedCSIS

Annals of Computer Science and Information Systems, Volume 15

Proceedings of the 2018 Federated Conference on Computer Science and Information Systems

Agile to Lean Software Development Transformation: a Systematic Literature Review

,

DOI: http://dx.doi.org/10.15439/2018F53

Citation: Proceedings of the 2018 Federated Conference on Computer Science and Information Systems, M. Ganzha, L. Maciaszek, M. Paprzycki (eds). ACSIS, Vol. 15, pages 969–973 ()

Full text

Abstract. Context: Lean development has been often proposed as an adaptation to agile for scaling-up to larger contexts. Goals: we wanted to better understand the``agile-to-lean'' transformation, in terms of: i) reported benefits, ii) challenges faced, iii) metrics used. Method: we performed a Systematic Literature Review (SLR) about``agile-to-lean'' transformations. Results: reduced lead time, improved flow, continuous improvement, and improved defect fix rate were the main reported benefits. Adaptation to lean thinking, teaching the lean mindset, identification of the concept of waste, and scaling flexibility were the main challenges. Lead time was the most reported metric.

References

  1. X. Wang, “The combination of agile and lean in software development: An experience report analysis,” in 2011 Agile Conference, Conference Proceedings. http://dx.doi.org/10.1109/AGILE.2011.36 pp. 1–9.
  2. P. Middleton and D. Joyce, “Lean software management: Bbc worldwide case study,” IEEE Transactions on Engineering Management, vol. 59, no. 1, pp. 20–32, 2012. http://dx.doi.org/10.1109/TEM.2010.2081675
  3. M. Kalenda, P. Hyna, and B. Rossi, “Scaling agile in large organizations: Practices, challenges, and success factors,” Journal of Software: Evolution and Process, p. e1954. http://dx.doi.org/10.1002/smr.1954
  4. M. Poppendieck, T. Poppendieck, and T. Poppendieck, Lean Software Development: An Agile Toolkit, ser. The agile software development series. Addison-Wesley, 2003. ISBN 9780321150783
  5. A. Shalloway, G. Beaver, and J. R. Trott, Lean-agile software development: achieving enterprise agility. Pearson Education, 2009.
  6. B. Kitchenham and S. Charters, “Guidelines for performing systematic literature reviews in software engineering,” 2007.
  7. P. Middleton, “Lean software development: two case studies,” Software Quality Journal, vol. 9, no. 4, pp. 241–252, 2001. http://dx.doi.org/https://doi.org/10.1023/A:1013754402981
  8. K. B. Stone, “Four decades of lean: a systematic literature review,” International Journal of Lean Six Sigma, vol. 3, no. 2, pp. 112–132, 2012. http://dx.doi.org/https://doi.org/10.1108/20401461211243702
  9. E. Kupiainen, M. V. Mäntylä, and J. Itkonen, “Using metrics in agile and lean software development–a systematic literature review of industrial studies,” Information and Software Technology, vol. 62, pp. 143–163, 2015. http://dx.doi.org/https://doi.org/10.1016/j.infsof.2015.02.005
  10. X. F. Wang, K. Conboy, and O. Cawley, “”leagile” software development: An experience report analysis of the application of lean approaches in agile software development,” Journal of Systems and Software, vol. 85, no. 6, pp. 1287–1299, 2012. http://dx.doi.org/10.1016/j.jss.2012.01.061
  11. T. Hayata, J. Han, and M. Beheshti, “Facilitating agile software development with lean architecture in the dci paradigm,” in 2012 Ninth International Conference on Information Technology - New Generations. http://dx.doi.org/10.1109/ITNG.2012.157 pp. 343–348.
  12. C. R. Jakobsen and T. Poppendieck, “Lean as a scrum troubleshooter,” in 2011 Agile Conference, Conference Proceedings. http://dx.doi.org/10.1109/AGILE.2011.11 pp. 168–174.
  13. R. Kuusela and M. Koivuluoma, “Lean transformation framework for software intensive companies: Responding to challenges created by the cloud,” in 2011 37th EUROMICRO Conference on Software Engineering and Advanced Applications, Conference Proceedings. http://dx.doi.org/10.1109/SEAA.2011.74. ISBN 1089-6503 pp. 378–382.
  14. M. Misaghi and I. Bosnic, “Lean mindset in software engineer ing: A case study in a software house in brazilian state of santa catarina,” vol. 466, pp. 697–707, 2014. http://dx.doi.org/https://doi.org/10.1007/978-3-319-11854-3 60
  15. M. Paasivaara, C. Lassenius, V. T. Heikkila, K. Dikert, and C. Engblom, “Integrating global sites into the lean and agile transformation at ericsson,” 2013 Ieee 8th Int. Conference on Global Software Engineering (Icgse 2013), pp. 134–143, 2013. http://dx.doi.org/10.1109/icgse.2013.25
  16. G. I. U. S. Perera and M. S. D. Fernando, “Enhanced agile software development - hybrid paradigm with lean practice,” in 2007 Int. Conference on Industrial and Information Systems, Conference Proceedings. http://dx.doi.org/10.1109/ICIINFS.2007.4579181. ISBN 2164-7011 pp. 239–244.
  17. K. Petersen and C. Wohlin, “Measuring the flow in lean software development,” Software-Practice and Experience, vol. 41, no. 9, pp. 975–996, 2011. http://dx.doi.org/10.1002/spe.975
  18. P. Rodrı́guez, J. Markkula, M. Oivo, and K. Turula, “Survey on agile and lean usage in finnish software industry,” in Proceedings of the ACM-IEEE International Symposium on Empirical Software Engineering and Measurement, ser. ESEM ’12. New York, NY, USA: ACM, 2012. doi: 10.1145/2372251.2372275. ISBN 978-1-4503-1056-7 pp. 139–148.
  19. P. Rodrı́guez, J. Partanen, P. Kuvaja, and M. Oivo, “Combining lean thinking and agile methods for software development: A case study of a finnish provider of wireless embedded systems detailed,” in 2014 47th Hawaii International Conference on System Sciences, Conference Proceedings. http://dx.doi.org/10.1109/HICSS.2014.586. ISBN 1530-1605 pp. 4770–4779.
  20. U. Samanta, V. S. Mani, and Ieee, “Successfully transforming to lean by changing the mindset in a global product development team,” pp. 135–139, 2015. http://dx.doi.org/10.1109/icgse.2015.17
  21. J. Schnitter and O. Mackert, “Large-scale agile software development at sap ag,” vol. 230, pp. 209–220, 2011. http://dx.doi.org/https://doi.org/10.1007/978-3-642-23391-3 15
  22. D. I. K. Sjøberg, A. Johnsen, and J. Solberg, “Quantifying the effect of using kanban versus scrum: A case study,” IEEE Software, vol. 29, no. 5, pp. 47–53, 2012. http://dx.doi.org/10.1109/MS.2012.110
  23. B. Swaminathan and K. Jain, “Implementing the lean concepts of continuous improvement and flow on an agile software development project: An industrial case study,” in 2012 Agile India, Conf. Proceedings. http://dx.doi.org/10.1109/AgileIndia.2012.12. ISBN 2326-6007 pp. 10–19.
  24. J. Trimble and C. Webster, “From traditional, to lean, to agile development: Finding the optimal software engineering cycle,” in 2013 46th Hawaii Int. Conference on System Sciences, Conference Proceedings. http://dx.doi.org/10.1109/HICSS.2013.237. ISBN 1530-1605 pp. 4826–4833.
  25. K. Vilkki, When Agile Is Not Enough, ser. Lecture Notes in Business Information Processing, 2010, vol. 65, pp. 44–47. ISBN 978-3-642-16415-6
  26. U. Viswanath, “Lean transformation: How lean helped to achieve quality, cost and schedule: Case study in a multi location product development team,” in 2014 IEEE 9th Int. Conference on Global Software Engineering, Conf. Proceedings. http://dx.doi.org/10.1109/ICGSE.2014.13 pp. 95–99.
  27. M. Walter, R. Tramontini, R. M. Fontana, S. Reinehr, and A. Malucelli, From Sprints to Lean Flow: Management Strategies for Agile Improvement, ser. Lecture Notes in Business Information Processing, 2015, vol. 212, pp. 310–318.
  28. M. Pergher and B. Rossi, “Requirements prioritization in software engineering: a systematic mapping study,” in Empirical Requirements Engineering (EmpiRE), 2013 IEEE Third International Workshop on. IEEE, 2013. http://dx.doi.org/10.1109/EmpiRE.2013.6615215 pp. 40–44.