Software Process Evolution at the SEL
IEEE Software
Applied software measurement (2nd ed.): assuring productivity and quality
Applied software measurement (2nd ed.): assuring productivity and quality
Traceability aspects of impact analysis in object-oriented systems
Journal of Software Maintenance: Research and Practice
Lean Software Development: Two Case Studies
Software Quality Control
Lean Software Development: An Agile Toolkit
Lean Software Development: An Agile Toolkit
Queueing Networks and Markov Chains
Queueing Networks and Markov Chains
Requirements Abstraction Model
Requirements Engineering
Introducing Lean Principles with Agile Practices at a Fortune 500 Company
AGILE '06 Proceedings of the conference on AGILE 2006
A Model for Technology Transfer in Practice
IEEE Software
Functional size measurement revisited
ACM Transactions on Software Engineering and Methodology (TOSEM)
An Experience-Based Approach for Test Execution Effort Estimation
ICYCS '08 Proceedings of the 2008 The 9th International Conference for Young Computer Scientists
Measuring the flow in lean software development
Software—Practice & Experience
Lean software management case study: Timberline inc.
XP'05 Proceedings of the 6th international conference on Extreme Programming and Agile Processes in Software Engineering
IS development/IT operations alignment in system development projects: a multi-method research
International Journal of Business Information Systems
Hi-index | 0.00 |
Software process improvement methods help to continuously refine and adjust the software process to improve its performance (e.g., in terms of lead-time, quality of the software product, reduction of change requests, and so forth). Lean software development propagates two important principles that help process improvement, namely identification of waste in the process and considering interactions between the individual parts of the software process from an end-to-end perspective. A large shift of thinking about the own way of working is often required to adopt lean. One of the potential main sources of failure is to try to make a too large shift about the ways of working at once. Therefore, the change to lean has to be done in a continuous and incremental way. In response to this we propose a novel approach to bring together the quality improvement paradigm and lean software development practices, the approach being called Software Process Improvement through the Lean Measurement (SPI-LEAM) Method. The method allows to assess the performance of the development process and take continuous actions to arrive at a more lean software process over time. The method is under implementation in industry and an initial evaluation of the method has been performed.