Monitoring Bottlenecks in Agile and Lean Software Development Projects – A Method and Its Industrial Use
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.
KeywordsSoftware Development Software Project Optimal Capacity Test Execution Software Development Project
Unable to display preview. Download preview PDF.
- 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.Petersen, K., Wohlin, C.: Measuring the flow in lean software development. Software: Practice and Experience, n/a–n/a(2010)Google Scholar
- 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.Dettmer, H.W.: Goldratt’s theory of constraints: a systems approach to continuous improvement. ASQC Quality Press, Milwaukee (1997)Google Scholar
- 9.Dettmer, H.W.: The logical thinking process: a systems approach to complex problem solving. ASQ Quality Press, Milwaukee (2007)Google Scholar
- 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
- 12.Liker, J.K.: The Toyota way: 14 management principles from the world’s greatest manufacturer. McGraw-Hill, New York (2004)Google Scholar
- 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.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.Dolcemascolo, D.: Improving the extended value stream: lean for the entire supply chain. Productivity Press, New York (2006)Google Scholar
- 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.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