Abstract
We present a model for estimating the final keep/cancel decision point, on a per-feature basis, for scope inclusion in a future release. The Basic Lost Opportunity Estimation Model (BLOEM), based on data from a company that uses an agile-inspired software development model, supports feature selection when the time-dependent business value estimates change as the requirements analysis progresses. The initial BLOEM validation, conducted on a set of 166 features, suggests that the model can valuable input to the feature selection process for a given release, helping to control lost opportunity costs due to feature cancellation. Limitations of BLOEM are discussed and issues for further research are presented.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
Regnell, B., Brinkkemper, S.: Market-Driven Requirements Engineering for Software Products. In: Aurum, A., Wohlin, C. (eds.) Engineering and Managing Software Requirements, pp. 287–308. Springer, Berlin (2005)
Wnuk, K., Regnell, B., Karlsson, L.: What Happened to Out Features? Visualization and Understanding of Scope Change Dynamics in a Large-Scale Industrial Setting. In: 17th IEEE Int. Requirements Engineering Conference, pp. 41–50. IEEE Press, New York (2009)
The Agile manifesto, http://agilemanifesto.org/ (accessed January 2012)
Racheva, Z., Daneva, M., Sikkel, K., Herrmann, A., Wieringa, R.: Do We Know Enough about Requirements Prioritization in Agile Projects: Insights from a Case Study. In: 18th IEEE International Requirements Engineering Conference, pp. 147–156. IEEE Computer Society, Washington, DC (2010)
Wnuk, K., Callele, D., Regnell, B.: Guiding requirements scoping using ROI: towards agility, openness and waste reduction. In: 18th IEEE Int. Requirements Engineering Conference, pp. 409–410. IEEE Press, New York (2010)
Beck, K.: eXtreme Programming Explained: Embrace Change. Addison Wesley (2000)
Cao, L., Ramesh, B.: Agile Requirements Engineering Practices: An Empirical Study. IEEE Soft. 25, 60–67 (2007)
Dixit, A., Pindych, R.: Investment Under Uncertainty. Princeton Univ. Press (1994)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2012 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Wnuk, K., Callele, D., Karlsson, EA., Regnell, B. (2012). Controlling Lost Opportunity Costs in Agile Development – The Basic Lost Opportunity Estimation Model for Requirements Scoping. In: Cusumano, M.A., Iyer, B., Venkatraman, N. (eds) Software Business. ICSOB 2012. Lecture Notes in Business Information Processing, vol 114. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-30746-1_21
Download citation
DOI: https://doi.org/10.1007/978-3-642-30746-1_21
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-30745-4
Online ISBN: 978-3-642-30746-1
eBook Packages: Computer ScienceComputer Science (R0)