Experimentation in software engineering: an introduction
Experimentation in software engineering: an introduction
Systems Engineering
Antecedents and consequences of team potency in software development projects
Information and Management
ICSEA '07 Proceedings of the International Conference on Software Engineering Advances
Providing value to customers in software development through lean principles
Software Process: Improvement and Practice - Advances in Software Process Improvement
From Traditional to Streamline Development — opportunities and challenges
Software Process: Improvement and Practice - Special Issue on Systems Interoperability
Predicting weekly defect inflow in large software projects based on project planning and test status
Information and Software Technology
A framework for developing measurement systems and its industrial evaluation
Information and Software Technology
Using Models to Develop Measurement Systems: A Method and Its Industrial Use
IWSM '09 /Mensura '09 Proceedings of the International Conferences on Software Process and Product Measurement
Information and Software Technology
Measuring the flow in lean software development
Software—Practice & Experience
Information and Software Technology
Hi-index | 0.00 |
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.