Method for Identification of Waste in the Process of Software Development in Agile Teams Using Lean and Scrum

  • Márcio Trovão BufonEmail author
  • Adriano Galindo LealEmail author
Conference paper
Part of the Communications in Computer and Information Science book series (CCIS, volume 1027)


Waste in software development projects is defined as anything that consumes resources such as time, effort, room, and money without adding value to the customer. Methods and techniques to identify waste indicators, which are specific for each project, are applied to part of total interactions and the development phases; and spend analysts and developers’ time and effort. Therefore, this paper aims to define a method to identify waste within the software development process in Scrum teams, from data based on JIRA tool, which supports software development planning, management and controlling activities. According to the bibliographic review are defined: (i) indicators for types of waste according to Lean software development principles; (ii) JIRA’s attributes, mathematical operators, keywords, functions and reports related to such indicators. In the proposed method are defined requirements that establish a semantic relation between each indicator variables and formulas to the set of JIRA’S attributes, functions and keywords and, based on them, queries in JIRA Query Language are implemented to quantify the indicators. The method validation is performed using graphics that show queries results classified and grouped by project, indicator and type of waste, acquired from a software project base for a company in the Brazilian financial market. Through the quantitative analysis of results, it is possible to suggest a hypothesis for the occurrence of the types of observed wastes.


Waste Scrum Lean JIRA 



The second author gratefully acknowledges the financial support from grants #2019/01664-6 and #2017/50343-2, São Paulo Research Foundation (FAPESP).


  1. 1.
    Poppendieck, M.P.T.: Leading Lean Software Development: Results Are not the Point, 1st edn. Pearson, Upper Saddle River (2009)Google Scholar
  2. 2.
    Ikonen, M., et al.: Exploring the sources of waste in Kanban software development projects. In: Proceedings - 36th EUROMICRO Conference on Software Engineering and Advanced Applications, SEAA 2010, pp. 376–381 (2010)Google Scholar
  3. 3.
    Poppendieck, M.P.T.: Lean Software Development: An Agile Toolkit. Addison-Wesley Longman Publishing Co., Inc., Boston (2003)Google Scholar
  4. 4.
    Petersen, K., Wohlin, C.: Measuring the flow in lean software development BT - focus on agile software development. Softw. Pract. Exp. 41(9), 975–996 (2011)CrossRefGoogle Scholar
  5. 5.
    Behroozi, N., Kamandi, A.: Waste elimination of agile methodologies in web engineering. In: 2016 2nd International Conference on Web Research, ICWR 2016, pp. 102–107 (2016)Google Scholar
  6. 6.
    Nord, R.L., Ozkaya, I., Sangwan, R.S.: Making architecture visible to improve flow management in lean software development. IEEE Softw. 29(5), 33–39 (2012)CrossRefGoogle Scholar
  7. 7.
    Jonsson, H., Larsson, S., Punnekkat, S.: Synthesizing a comprehensive framework for lean software development. In: Proceedings - 39th Euromicro Conference Series on Software Engineering and Advanced Applications, SEAA 2013, pp. 1–8 (2013)Google Scholar
  8. 8.
    Murphy, T.E., West, M., Mann, K.J.: Gartner Accessed 11 Nov 2017
  9. 9.
    Poppendieck e Poppendieck (2011)Google Scholar
  10. 10.
    Bell, S.C., Orzen, M.A.: Lean IT: Enabling and Sustaining Your Lean Transformation. CRC Press, Boca Raton (2016)Google Scholar
  11. 11.
    Sedano, T., Ralph, P., Peraire, C.: Software development waste. In: 2017 IEEE/ACM 39th International Conference on Software Engineering (ICSE), pp. 130–140 (2017)Google Scholar
  12. 12.
    Petersen, K., Wohlin, C.: Software process improvement through the lean measurement (SPI-LEAM) method. J. Syst. Softw. 83(7), 1275–1287 (2010)CrossRefGoogle Scholar
  13. 13.
    Pressman, Roger S.: Software Engineering - A professional Approach, pp. 77–79. McGraw-Hill Science, New York (2016)Google Scholar
  14. 14.
    Atlassian: JIRA Software. Accessed 6 May 2018

Copyright information

© Springer Nature Switzerland AG 2019

Authors and Affiliations

  1. 1.Institute of Technological Research - IPTSão PauloBrazil

Personalised recommendations