Monitoring Bottlenecks in Agile and Lean Software Development Projects – A Method and Its Industrial Use

  • Miroslaw Staron
  • Wilhelm Meding
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 6759)


In the face of growing competition software projects have to deliver software products faster and with better quality – thus leaving little room for unnecessary activities or non-optimal capacity. To achieve the desired high speed of the projects and the optimal capacity,bottlenecks existing in the projects have to be monitored and effectively removed. The objective of this research is to show experiences from a mature software development organization working according to Lean and Agile software development principles. By conducting a formal case study at Ericsson we were able to elicit and automate measures required to monitor bottlenecks in software development workflow, evaluated in one of the projects. The project developed software for one of the telecom products and consisted of over 80 developers. The results of the case study include a measurement system with a number of measures/indicators which can indicate existence of bottlenecks in the flow of work in the project and a number of good practices helping other organizations to start monitoring bottlenecks in an effective way – in particular what to focus on when designing such a measurement system.


Software Development Software Project Optimal Capacity Test Execution Software Development Project 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Staron, M., et al.: A method for forecasting defect backlog in large streamline software development projects and its industrial evaluation. Information and Software Technology 52, 1069–1079 (2010)CrossRefGoogle Scholar
  2. 2.
    Mehta, M., et al.: Providing value to customers in software development through lean principles. Software Process: Improvement and Practice 13, 101–109 (2008)CrossRefGoogle Scholar
  3. 3.
    Tomaszewski, P., et al.: From Traditional to Streamline Development - Opportunities and Challenges. Software Process Improvement and Practice 2007, 1–20 (2007)Google Scholar
  4. 4.
    Petersen, K., Wohlin, C.: Measuring the flow in lean software development. Software: Practice and Experience, n/a–n/a(2010)Google Scholar
  5. 5.
    Oppenheim, B.W.: Lean product development flow. Syst. Eng. 7, 2 (2004)CrossRefGoogle Scholar
  6. 6.
    Höst, M., et al.: Exploring bottlenecks in market-driven requirements management processes with discrete event simulation. Journal of Systems and Software 59, 323–332 (2001)CrossRefGoogle Scholar
  7. 7.
    Jasmine, K.S., Vasantha, R.: Identification Of Software Performance Bottleneck Components In Reuse based Software Products With The Application Of Acquaintanceship Graphs. In: International Conference on Software Engineering Advances, ICSEA 2007, p. 34 (2007)Google Scholar
  8. 8.
    Dettmer, H.W.: Goldratt’s theory of constraints: a systems approach to continuous improvement. ASQC Quality Press, Milwaukee (1997)Google Scholar
  9. 9.
    Dettmer, H.W.: The logical thinking process: a systems approach to complex problem solving. ASQ Quality Press, Milwaukee (2007)Google Scholar
  10. 10.
    Perera, G.I.U.S., Fernando, M.S.D.: Enhanced agile software development - hybrid paradigm with LEAN practice. In: International Conference on Industrial and Information Systems (ICIIS), pp. 239–244 (2007)Google Scholar
  11. 11.
    Akg, A.E., et al.: Antecedents and consequences of team potency in software development projects. Inf. Manage. 44, 646–656 (2007)CrossRefGoogle Scholar
  12. 12.
    Liker, J.K.: The Toyota way: 14 management principles from the world’s greatest manufacturer. McGraw-Hill, New York (2004)Google Scholar
  13. 13.
    Staron, M., et al.: A Framework for Developing Measurement Systems and Its Industrial Evaluation. Information and Software Technology 51, 721–737 (2008)CrossRefGoogle Scholar
  14. 14.
    Staron, M., Meding, W.: Predicting Weekly Defect Inflow in Large Software Projects based on Project Planning and Test Status. Information and Software Technology, p. (available online) (2007)Google Scholar
  15. 15.
    Staron, M., Meding, W.: Using Models to Develop Measurement Systems: A Method and Its Industrial Use. Presented at the Software Process and Product Measurement, Amsterdam, NL (2009)Google Scholar
  16. 16.
    Dolcemascolo, D.: Improving the extended value stream: lean for the entire supply chain. Productivity Press, New York (2006)Google Scholar
  17. 17.
    International Standard Organization and International Electrotechnical Commission, ISO/IEC 15939 Software engineering – Software measurement process, International Standard Organization/International Electrotechnical Commission, Geneva (2007)Google Scholar
  18. 18.
    Meding, W., Staron, M.: The Role of Design and Implementation Models in Establishing Mature Measurement Programs. Presented at the Nordic Workshop on Model Driven Engineering, Tampere, Finland (2009)Google Scholar
  19. 19.
    Wohlin, C., et al.: Experimentation in Software Engineering: An Introduction. Kluwer Academic Publisher, Boston (2000)CrossRefzbMATHGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2011

Authors and Affiliations

  • Miroslaw Staron
    • 1
  • Wilhelm Meding
    • 2
  1. 1.Department of Computer Science and EngineeringUniversity of GothenburgSweden
  2. 2.Ericsson SW Research ABSweden

Personalised recommendations