Where does all this waste come from?

Abstract

Agile development processes are more flexible than conventional ones. They emphasize iterative development and learning over feedback loops. Nevertheless, we experienced some pitfalls in the application of agile processes in dependable software systems. We present here the experiences we gathered in the construction of high-quality industrial software. Moreover, we will digest our experiences into a conceptual model of waste creation. This model will be refined to a case study where we take appropriate measurements in order to provide empirical evidence for it. Finally, we discuss the implications of the developed model, which helps to estimate the trade-off between agile and traditional software processes.

Balancing Product and Process Assurance for Evolving Security Systems

“…This area of tension was also discussed previously in (Raschke, 2014a) where the authors empirically evaluated the impact of agile development practices on effort for quality assurance. Their cost model basically shows that evolving software architecture causes continuous rework of the documentation for quality assurance, if it is done in parallel.…”