Advanced

Risk Identification on the Interface Between Business Case and Requirements

Callele, David; Penzenstadler, Birgit and Wnuk, Krzysztof LU (2013) International Workshop on Requirements Engineering: Foundation for Software Quality, 2013 7830. p.253-268
Abstract
Motivation: The requirements engineering (RE) research community is aware of the importance of performing feasibility studies before starting requirements elicitation. Unfortunately, projects still frequently fail to achieve commercial success, responsibility is often unknown, and requirements engineers may be deemed responsible for mistakes made by others. Problem: There is neither empirical evidence available from a post-mortem risk analysis for projects that performed adequate RE but commercially failed nor guidance for requirements engineers on validating a business case analysis to mitigate this risk. Principal idea: By performing a post-mortem analysis of software development projects that failed to achieve commercial success, we... (More)
Motivation: The requirements engineering (RE) research community is aware of the importance of performing feasibility studies before starting requirements elicitation. Unfortunately, projects still frequently fail to achieve commercial success, responsibility is often unknown, and requirements engineers may be deemed responsible for mistakes made by others. Problem: There is neither empirical evidence available from a post-mortem risk analysis for projects that performed adequate RE but commercially failed nor guidance for requirements engineers on validating a business case analysis to mitigate this risk. Principal idea: By performing a post-mortem analysis of software development projects that failed to achieve commercial success, we investigate the root causes for the failures and, in most cases, trace the causes back to business case issues. We identify risk areas and provide practical due diligence guidance to the practitioner. Contribution: This exploratory case study performs an in-depth review of a detailed post-mortem analysis of three software development projects performed over a 2.5 year period. Each of the analyzed projects failed to make the expected transition to commercialization despite using appropriate RE techniques and achieving satisfactory deliverables. The analysis identifies risk factors that the RE practitioner should consider and we provide a checklist for RE practitioners to use when checking for these risks in an antecedent business case as part of their due diligence. A low-cost commercial viability assessment technique, employing Fermi approximation, is provided to equip the RE practitioner with a risk mitigation tool in the absence of business analyst resources. (Less)
Please use this url to cite or link to this publication:
author
organization
publishing date
type
Chapter in Book/Report/Conference proceeding
publication status
published
subject
keywords
Risk identication, risk mitigation, commercial risk, due diligence, commercialization, commercial success, success factors, business case, business analyst
host publication
Requirements Engineering: Foundation for Software Quality / Lecture Notes in Computer Science
editor
Doerr, Joerg; Andreas L., Opdahl; and
volume
7830
pages
15 pages
publisher
Springer
conference name
International Workshop on Requirements Engineering: Foundation for Software Quality, 2013
conference location
Essen, Germany
conference dates
2013-04-08 - 2013-04-11
external identifiers
  • scopus:84875856285
ISSN
0302-9743
1611-3349
ISBN
978-3-642-37421-0
DOI
10.1007/978-3-642-37422-7_18
project
EASE
language
English
LU publication?
yes
id
102b9f6e-ded7-4b38-b464-f56d3a67fca4 (old id 4194042)
date added to LUP
2013-12-10 13:09:29
date last changed
2019-01-06 03:23:37
@inproceedings{102b9f6e-ded7-4b38-b464-f56d3a67fca4,
  abstract     = {Motivation: The requirements engineering (RE) research community is aware of the importance of performing feasibility studies before starting requirements elicitation. Unfortunately, projects still frequently fail to achieve commercial success, responsibility is often unknown, and requirements engineers may be deemed responsible for mistakes made by others. Problem: There is neither empirical evidence available from a post-mortem risk analysis for projects that performed adequate RE but commercially failed nor guidance for requirements engineers on validating a business case analysis to mitigate this risk. Principal idea: By performing a post-mortem analysis of software development projects that failed to achieve commercial success, we investigate the root causes for the failures and, in most cases, trace the causes back to business case issues. We identify risk areas and provide practical due diligence guidance to the practitioner. Contribution: This exploratory case study performs an in-depth review of a detailed post-mortem analysis of three software development projects performed over a 2.5 year period. Each of the analyzed projects failed to make the expected transition to commercialization despite using appropriate RE techniques and achieving satisfactory deliverables. The analysis identifies risk factors that the RE practitioner should consider and we provide a checklist for RE practitioners to use when checking for these risks in an antecedent business case as part of their due diligence. A low-cost commercial viability assessment technique, employing Fermi approximation, is provided to equip the RE practitioner with a risk mitigation tool in the absence of business analyst resources.},
  author       = {Callele, David and Penzenstadler, Birgit and Wnuk, Krzysztof},
  editor       = {Doerr, Joerg and Andreas L., Opdahl},
  isbn         = {978-3-642-37421-0},
  issn         = {0302-9743},
  keyword      = {Risk identication,risk mitigation,commercial risk,due diligence,commercialization,commercial success,success factors,business case,business analyst},
  language     = {eng},
  location     = {Essen, Germany},
  pages        = {253--268},
  publisher    = {Springer},
  title        = {Risk Identification on the Interface Between Business Case and Requirements},
  url          = {http://dx.doi.org/10.1007/978-3-642-37422-7_18},
  volume       = {7830},
  year         = {2013},
}