@inproceedings {SE.5.Moloekken-Oestvold.2004.b,
	title = {Does Use of Development Model Affect Estimation Accuracy and Bias?},
	journal = {Product Focused Software Process Improvement: 5th International Conference (PROFES 2004)},
	year = {2004},
	note = {ISBN: 3-540-21421-6},
	month = {April 5-8},
	pages = {17-29},
	publisher = {Springer-Verlag},
	type = {1},
	address = {Kansai Science City, Japan},
	abstract = {Objective. To investigate how the use of incremental and evolutionary development models affects the accuracy and bias of effort and schedule estimates of software projects. Rationale. Advocates of incremental and evolutionary development models often claim that use of these models results in improved estimation accuracy. Design of study. We conducted an in-depth survey, where information was collected through structured interviews with 22 software project managers in 10 different companies. We collected and analyzed information about estimation approach, effort estimation accuracy and bias, schedule estimation accuracy and bias, completeness of delivered functionality and other estimation related information. Results. We found no impact from the development model on the estimation approach. However, we found that incremental and evolutionary projects were less prone to effort overruns. The degree of delivered functionality and schedule estimation accuracy, on the other hand, were seemingly independent of development model. Conclusion. The use of incremental and evolutionary development models may reduce the chance of effort overruns.},
	author = {Kjetil Johan {Mol{\o}kken-{\O}stvold} and A. C. {Lien} and J{\o}rgensen, Magne and Sinan Sigurd {Tanilkan} and Gallis, H. and S. E. {Hove}}
}
@techreport {SE.7.Moloekken-Oestvold.2004,
	title = {Project Estimation in the Norwegian Software Industry - a Summary},
	number = {2004-03},
	year = {2004},
	note = {Results from the BEST-Pro (Better Estimation of Software Tasks and Process Improvement) survey},
	publisher = {Simula Research Laboratory},
	abstract = {This report provides an overview of the results obtained from a survey on project estimation in Norwegian software companies. The survey was conducted between February and November 2003. The main results are: {\textbullet} We observed that 76\% of the projects used more effort than estimated, while 19\% used less. The average effort overrun was 41\%. {\textbullet} Average effort overrun was 67\% in projects with a public client, compared to an average effort overrun of 21\% for projects with a private client. {\textbullet} Projects that used an incremental or evolutionary development approach had an average effort overrun of 24\%, as opposed to the average 55\% overrun for projects that used a waterfall-based development approach. The frequency and magnitude of effort overruns found in this survey seems to be similar to results reported from surveys conducted in other countries in the past 20 years. The observed differences in effort overruns between private and public projects may be caused by differences in bidding procedures, level of client involvement or acceptance procedures. In order to reduce the risk of effort overruns, software companies should: {\textbullet} Focus on analyzing their own estimation performance, and invest in estimation improvement (for instance through experience databases or work breakdown structures). {\textbullet} Differentiate risk buffers based on the type of the customer, development approach and the size of the project. {\textbullet} Try to establish an {\textquotedblleft}as close as possible{\textquotedblright} dialogue with the customers (e.g. through an incremental development approach). All companies should analyse completed projects, in order to benchmark their performance. This allows for improvement efforts to be identified.},
	author = {Kjetil Johan {Mol{\o}kken-{\O}stvold} and J{\o}rgensen, Magne and Sinan Sigurd {Tanilkan} and Gallis, H. and A. C. {Lien} and S. E. {Hove}}
}
@inproceedings {SE.5.Moloekken-Oestvold.2004.a,
	title = {A Survey on Software Estimation in the Norwegian Industry},
	journal = {10th International Software Metrics Symposium (METRICS 2004)},
	year = {2004},
	month = {September 16-18},
	pages = {208-219},
	publisher = {IEEE Computer Society Press},
	type = {1},
	address = {Chicago, USA},
	abstract = {This paper seeks to provide an overview of the estimation methods that software companies apply to estimate their projects, why those methods are chosen, and how accurate they are. In order to improve software estimation accuracy, such knowledge is essential. We conducted an in-depth survey, where information was collected through structured interviews with senior managers from 18 different companies and project managers of 52 different projects. We collected and analyzed information about estimation approach, effort estimation accuracy and bias, schedule estimation accuracy and bias, completeness of delivered functionality and other estimation related information. Our results suggest, for example, that average effort overruns are 41\%, that the software estimation performance has not changed much the last 10-20 years, that expert estimation is the dominating estimation method, that estimation accuracy is not much impacted by use of formal estimation models, and that software managers tend to believe that the estimation accuracy of their company is better than it actually is.},
	author = {Kjetil Johan {Mol{\o}kken-{\O}stvold} and J{\o}rgensen, Magne and Sinan Sigurd {Tanilkan} and Gallis, H. and A. C. {Lien} and S. E. {Hove}}
}
@inproceedings {SE.5.Lien.2001.a,
	title = {Evolutionary Development of Web-Applications - Lessons Learned},
	journal = {European Software Process Improvement Conference (EuroSPI{\textquoteright}2001)},
	year = {2001},
	month = {November},
	publisher = {-},
	type = {1},
	address = {Limerick Institute of Technology, Ireland},
	abstract = {On evolutionary web development in three different companies.},
	author = {A. C. {Lien} and Arisholm, Erik}
}
