Controlling Lost Opportunity Costs in Agile Development – The Basic Lost Opportunity Estimation Model for Requirements Scoping

  • Krzysztof Wnuk
  • David Callele
  • Even-Andre Karlsson
  • Björn Regnell
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 114)


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.


Requirements management scope management agile development software business 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    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)CrossRefGoogle Scholar
  2. 2.
    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)Google Scholar
  3. 3.
    The Agile manifesto, (accessed January 2012)
  4. 4.
    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)CrossRefGoogle Scholar
  5. 5.
    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)CrossRefGoogle Scholar
  6. 6.
    Beck, K.: eXtreme Programming Explained: Embrace Change. Addison Wesley (2000)Google Scholar
  7. 7.
    Cao, L., Ramesh, B.: Agile Requirements Engineering Practices: An Empirical Study. IEEE Soft. 25, 60–67 (2007)CrossRefGoogle Scholar
  8. 8.
    Dixit, A., Pindych, R.: Investment Under Uncertainty. Princeton Univ. Press (1994)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2012

Authors and Affiliations

  • Krzysztof Wnuk
    • 1
  • David Callele
    • 2
  • Even-Andre Karlsson
    • 3
  • Björn Regnell
    • 1
  1. 1.Department of Computer ScienceLund UniversitySweden
  2. 2.Department of Computer ScienceUniversity of SaskatchewanSaskatchewanCanada
  3. 3.AddALotLundSweden

Personalised recommendations