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

Research output: Chapter in Book/Report/Conference proceedingPaper in conference proceeding

Bibtex

@inproceedings{27f72c5ea2d7439cac849cb63482edfd,
title = "Controlling Lost Opportunity Costs in Agile Development – the Basic Lost Opportunity Estimation Model for Requirements Scoping",
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.",
keywords = "Requirements management scope management agile development software business",
author = "Krzysztof Wnuk and David Callele and Even-Andre Karlsson and Bj{\"o}rn Regnell",
year = "2012",
doi = "10.1007/978-3-642-30746-1_21",
language = "English",
isbn = "978-3-642-30745-4",
volume = "114",
publisher = "Springer",
number = "2",
pages = "255--260",
editor = "Michael Cusumano and Bala Iyer and N. Venkatraman",
booktitle = "Software Business/Lecture Notes in Business Information Processing,",
address = "Germany",

}