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

Standard

Controlling Lost Opportunity Costs in Agile Development – the Basic Lost Opportunity Estimation Model for Requirements Scoping. / Wnuk, Krzysztof; Callele, David; Karlsson, Even-Andre; Regnell, Björn.

Software Business/Lecture Notes in Business Information Processing,. ed. / Michael Cusumano; Bala Iyer; N. Venkatraman. Vol. 114 Springer, 2012. p. 255-260.

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

Harvard

Wnuk, K, Callele, D, Karlsson, E-A & Regnell, B 2012, Controlling Lost Opportunity Costs in Agile Development – the Basic Lost Opportunity Estimation Model for Requirements Scoping. in M Cusumano, B Iyer & N Venkatraman (eds), Software Business/Lecture Notes in Business Information Processing,. vol. 114, Springer, pp. 255-260, Third International Conference, ICSOB 2012, Cambridge, MA, United States, 2012/06/18. https://doi.org/10.1007/978-3-642-30746-1_21

APA

Wnuk, K., Callele, D., Karlsson, E-A., & Regnell, B. (2012). Controlling Lost Opportunity Costs in Agile Development – the Basic Lost Opportunity Estimation Model for Requirements Scoping. In M. Cusumano, B. Iyer, & N. Venkatraman (Eds.), Software Business/Lecture Notes in Business Information Processing, (Vol. 114, pp. 255-260). Springer. https://doi.org/10.1007/978-3-642-30746-1_21

CBE

Wnuk K, Callele D, Karlsson E-A, Regnell B. 2012. Controlling Lost Opportunity Costs in Agile Development – the Basic Lost Opportunity Estimation Model for Requirements Scoping. Cusumano M, Iyer B, Venkatraman N, editors. In Software Business/Lecture Notes in Business Information Processing,. Springer. pp. 255-260. https://doi.org/10.1007/978-3-642-30746-1_21

MLA

Wnuk, Krzysztof et al. "Controlling Lost Opportunity Costs in Agile Development – the Basic Lost Opportunity Estimation Model for Requirements Scoping"., Cusumano, Michael Iyer, Bala Venkatraman, N. (editors). Software Business/Lecture Notes in Business Information Processing,. Springer. 2012, 255-260. https://doi.org/10.1007/978-3-642-30746-1_21

Vancouver

Wnuk K, Callele D, Karlsson E-A, Regnell B. Controlling Lost Opportunity Costs in Agile Development – the Basic Lost Opportunity Estimation Model for Requirements Scoping. In Cusumano M, Iyer B, Venkatraman N, editors, Software Business/Lecture Notes in Business Information Processing,. Vol. 114. Springer. 2012. p. 255-260 https://doi.org/10.1007/978-3-642-30746-1_21

Author

Wnuk, Krzysztof ; Callele, David ; Karlsson, Even-Andre ; Regnell, Björn. / Controlling Lost Opportunity Costs in Agile Development – the Basic Lost Opportunity Estimation Model for Requirements Scoping. Software Business/Lecture Notes in Business Information Processing,. editor / Michael Cusumano ; Bala Iyer ; N. Venkatraman. Vol. 114 Springer, 2012. pp. 255-260

RIS

TY - GEN

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

AU - Wnuk, Krzysztof

AU - Callele, David

AU - Karlsson, Even-Andre

AU - Regnell, Björn

PY - 2012

Y1 - 2012

N2 - 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.

AB - 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.

KW - Requirements management scope management agile development software business

U2 - 10.1007/978-3-642-30746-1_21

DO - 10.1007/978-3-642-30746-1_21

M3 - Paper in conference proceeding

SN - 978-3-642-30745-4

VL - 114

SP - 255

EP - 260

BT - Software Business/Lecture Notes in Business Information Processing,

A2 - Cusumano, Michael

A2 - Iyer, Bala

A2 - Venkatraman, N.

PB - Springer

ER -