A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2017; you can also visit the original URL.
The file type is application/pdf
.
Controlling Lost Opportunity Costs in Agile Development – The Basic Lost Opportunity Estimation Model for Requirements Scoping
[chapter]
2012
Lecture Notes in Business Information Processing
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
doi:10.1007/978-3-642-30746-1_21
fatcat:pmcduhifnvcurmkizfwtwtcur4