Information systems failures—a survey and classification of the empirical literature
Oxford Surveys in Information Technology
A framework for software risk management
Scandinavian Journal of Information Systems
Qualitative Methods in Empirical Studies of Software Engineering
IEEE Transactions on Software Engineering
Value-based software engineering
ACM SIGSOFT Software Engineering Notes
Challenges in requirements engineering
RE '95 Proceedings of the Second IEEE International Symposium on Requirements Engineering
On the Challenges of Business Modeling in Large-Scale Reengineering Projects
ICRE '00 Proceedings of the 4th International Conference on Requirements Engineering (ICRE'00)
Software Acquisition: A Business Strategy Analysis
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Studying Software Engineers: Data Collection Techniques for Software Field Studies
Empirical Software Engineering
"Business Process" Oriented Requirements Engineering Process
RE '05 Proceedings of the 13th IEEE International Conference on Requirements Engineering
Linking the Business View to Requirements Engineering: Long-Term Product Planning by Roadmapping
RE '05 Proceedings of the 13th IEEE International Conference on Requirements Engineering
Understanding Business Strategies of Networked Value Constellations Using Goal- and Value Modeling
RE '06 Proceedings of the 14th IEEE International Requirements Engineering Conference
Improving the Exchange of Requirements and Specifications between Business Partners
RE '09 Proceedings of the 2009 17th IEEE International Requirements Engineering Conference, RE
A value-based approach in requirements engineering: explaining some of the fundamental concepts
REFSQ'07 Proceedings of the 13th international working conference on Requirements engineering: foundation for software quality
RE '11 Proceedings of the 2011 IEEE 19th International Requirements Engineering Conference
Case Study Research in Software Engineering: Guidelines and Examples
Case Study Research in Software Engineering: Guidelines and Examples
| Hi-index | 0.00 |
[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.