@article {Grimstad.2006.1,
	title = {Software Effort Estimation Terminology: the Tower of Babel},
	journal = {Information and Software Technology},
	volume = {48},
	number = {4},
	year = {2006},
	pages = {302-310},
	abstract = {This paper provides a review of how software development effort estimation terms are used in software engineering textbooks and research papers. We found that the term {{\textquoteleft}}effort estimate{\textquoteright} frequently is applied without any clarification of its meaning. It is therefore difficult to determine whether the authors{\textquoteright} intended interpretation is an estimate of {{\textquoteleft}}most likely effort{\textquoteright}, {{\textquoteleft}}planned effort{\textquoteright}, {{\textquoteleft}}budgeted effort{\textquoteright}, or something else. This is problematic as these terms are not equivalent and are used for different purposes. The lack of clarity of {{\textquoteleft}}effort estimate{\textquoteright} lowers the quality and interpretability of surveys on software effort estimation accuracy, i.e., it is not clear what the estimation accuracy results really mean. This reduces the estimation evaluation and learning possibilities. We suggest guidelines on how to reduce this terminology ambiguity. To the authors{\textquoteright} knowledge, this is the first published review of software cost estimation terminology.},
	author = {Grimstad, Stein and J{\o}rgensen, Magne and Kjetil Johan {Mol{\o}kken-{\O}stvold}}
}
