An empirical study of lead-times in incremental and agile software development

Authors:
Kai Petersen
Affiliations:
Blekinge Institute of Technology, Sweden and Ericsson AB, Sweden
Venue:
ICSP'10 Proceedings of the 2010 international conference on New modeling concepts for today's software processes: software process
Year:
2010

Citing 8
Cited 1

Market share rewards to pioneering brands: an empirical analysis and strategic implications

Management Science
Experimentation in software engineering: an introduction

Experimentation in software engineering: an introduction
Embracing Change with Extreme Programming

Computer
Lean Software Development: An Agile Toolkit

Lean Software Development: An Agile Toolkit
Effects of Process Maturity on Quality, Cycle Time, and Effort in Software Product Development

Management Science
Software Effort, Quality, and Cycle Time: A Study of CMM Level 5 Projects

IEEE Transactions on Software Engineering
A comparison of issues and advantages in agile and incremental development between state of the art and an industrial case

Journal of Systems and Software
Context in industrial software engineering research

ESEM '09 Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement

Countermeasure graphs for software security risk assessment: An action research

Journal of Systems and Software

Quantified Score

Hi-index	0.00

Visualization

Abstract

Short lead-times are essential in order to have a first-move advantages and to be able to react on changes on a fast-paced market. Agile software development is a development paradigm that aims at being able to respond quickly to changes in customer needs. So far, to the best of our knowledge no empirical study has investigated lead-times with regard to different aspects (distribution between phases, difference of lead-time with regard to architecture dependencies, and size). However, in order to improve lead-times it is important to understand the behavior of lead-times. In this study the lead-times of a large-scale company employing incremental and agile practices are analyzed. The analysis focuses on 12 systems at Ericsson AB, Sweden.