Software risk management
A systematic approach to derive the scope of software product lines
Proceedings of the 21st international conference on Software engineering
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Agile Software Development with Scrum
Agile Software Development with Scrum
A comprehensive product line scoping approach and its validation
Proceedings of the 24th International Conference on Software Engineering
e-R&D – Effectively Managing Process Diversity
Annals of Software Engineering
A Cost-Value Approach for Prioritizing Requirements
IEEE Software
Object-oriented modeling with ADORA
Information Systems - The 13th international conference on advanced information systems engineering (CAiSE*01)
A field study of requirements engineering practices in information systems development
RE '95 Proceedings of the Second IEEE International Symposium on Requirements Engineering
Invented requirements and imagined customers: requirements engineering for off-the-shelf software
RE '95 Proceedings of the Second IEEE International Symposium on Requirements Engineering
Decision Making Methodology in Support of the Business Rules Lifecycle
RE '97 Proceedings of the 3rd IEEE International Symposium on Requirements Engineering
Software Requirements
Evolving Beyond Requirements Creep: A Risk-Based Evolutionary Prototyping Model
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
An Industrial Survey of Requirements Interdependencies in Software Product Release Plannin
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Product-Line Requirements Specification (PRS): An Approach and Case Study
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Qualitative Research in Information Systems: A Reader
Qualitative Research in Information Systems: A Reader
Risk Management during Requirements
IEEE Software
Bridging models across the software lifecycle
Journal of Systems and Software - Special issue: Best papers on Software Engineering from the SEKE'01 Conference
Software Product Line Engineering: Foundations, Principles and Techniques
Software Product Line Engineering: Foundations, Principles and Techniques
Requirements Abstraction Model
Requirements Engineering
Towards a Reference Framework for Software Product Management
RE '06 Proceedings of the 14th IEEE International Requirements Engineering Conference
Global Software Development Handbook (Auerbach Series on Applied Software Engineering Series)
Global Software Development Handbook (Auerbach Series on Applied Software Engineering Series)
Empirical Software Engineering
Information and Software Technology
A Systematic Review of Software Development Cost Estimation Studies
IEEE Transactions on Software Engineering
A Method for Early Requirements Triage and Selection Utilizing Product Strategies
APSEC '07 Proceedings of the 14th Asia-Pacific Software Engineering Conference
Empirical studies of agile software development: A systematic review
Information and Software Technology
The impact of agile practices on communication in software development
Empirical Software Engineering
Can We Beat the Complexity of Very Large-Scale Requirements Engineering?
REFSQ '08 Proceedings of the 14th international conference on Requirements Engineering: Foundation for Software Quality
Requirements Engineering in the Development of Large-Scale Systems
RE '08 Proceedings of the 2008 16th IEEE International Requirements Engineering Conference
RE '09 Proceedings of the 2009 17th IEEE International Requirements Engineering Conference, RE
Customer Involvement in Requirements Management: Lessons from Mass Market Software Development
RE '09 Proceedings of the 2009 17th IEEE International Requirements Engineering Conference, RE
A systematic review on strategic release planning models
Information and Software Technology
Handshaking between software projects and stakeholders using implementation proposals
REFSQ'07 Proceedings of the 13th international working conference on Requirements engineering: foundation for software quality
Requirements Determination is Unstoppable: An Experience Report
RE '10 Proceedings of the 2010 18th IEEE International Requirements Engineering Conference
A case study on benefits and side-effects of agile practices in large-scale requirements engineering
Proceedings of the 1st Workshop on Agile Requirements Engineering
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
Analyzing an industrial strategic release planning process: a case study at roche diagnostics
REFSQ'13 Proceedings of the 19th international conference on Requirements Engineering: Foundation for Software Quality
Hi-index | 0.00 |
Context: Scope management is a core part of software release management and often a key factor in releasing successful software products to the market. In a market-driven case, when only a few requirements are known a priori, the risk of overscoping may increase. Objective: This paper reports on findings from a case study aimed at understanding overscoping in large-scale, market-driven software development projects, and how agile requirements engineering practices may affect this situation. Method: Based on a hypothesis of which factors that may be involved in an overscoping situation, semi-structured interviews were performed with nine practitioners at a large, market-driven software company. The results from the interviews were validated by six (other) practitioners at the case company via a questionnaire. Results: The results provide a detailed picture of overscoping as a phenomenon including a number of causes, root causes and effects, and indicate that overscoping is mainly caused by operating in a fast-moving market-driven domain and how this ever-changing inflow of requirements is managed. Weak awareness of overall goals, in combination with low development involvement in early phases, may contribute to 'biting off' more than a project can 'chew'. Furthermore, overscoping may lead to a number of potentially serious and expensive consequences, including quality issues, delays and failure to meet customer expectations. Finally, the study indicates that overscoping occurs also when applying agile requirements engineering practices, though the overload is more manageable and perceived to result in less wasted effort when applying a continuous scope prioritization, in combination with gradual requirements detailing and a close cooperation within cross-functional teams. Conclusion: The results provide an increased understanding of scoping as a complex and continuous activity, including an analysis of the causes, effects, and a discussion on possible impact of agile requirements engineering practices to the issue of overscoping. The results presented in this paper can be used to identify potential factors to address in order to achieve a more realistic project scope.