Systematic analysis of the incremental process as a base for comparison with the agile process

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

1 Citation (Scopus)

Abstract

Background: The number of studies that quantitatively reveal the effect of using Agile models on development performance is scarce. Aim: In this paper, we explain the analysis of a plan-driven. Incremental Process within Siemens EC. carried out to understand its performance as a base for the comparison with the Agile Process. Method: We introduce a method to systematically analyze a software development process to understand its performance quantitatively, and explain the application of the method on the System Test phase of the Incremental Process. Results: The utilization of the analysis method practically contributed to the implementation which was completed in 8 person-days. An analysis of derived measure values indicated that there was no outlier value in the interval of mean ± 3 standard deviation for the measures. Conclusions: We expect that the method will be more beneficial in capturing the context of the Agile Process and its measures.

Original languageEnglish
Title of host publication15th Annual Conference on Evaluation and Assessment in Software Engineering, EASE 2011
Pages86-90
Number of pages5
Edition1
DOIs
Publication statusPublished - 2011
Event15th Annual Conference on Evaluation and Assessment in Software Engineering, EASE 2011 - Durham, United Kingdom
Duration: 11 Apr 201112 Apr 2011

Publication series

NameIET Seminar Digest
Number1
Volume2011

Conference

Conference15th Annual Conference on Evaluation and Assessment in Software Engineering, EASE 2011
Country/TerritoryUnited Kingdom
CityDurham
Period11/04/1112/04/11

Keywords

  • GQM
  • process performance
  • product quality
  • quantitative analysis
  • software development models
  • software measurement

Fingerprint

Dive into the research topics of 'Systematic analysis of the incremental process as a base for comparison with the agile process'. Together they form a unique fingerprint.

Cite this