An agile approach for managing requirements change to improve learning and adaptability

Published on Jun 1, 2019in Journal of Industrial Information Integration10.615
· DOI :10.1016/J.JII.2018.07.005
Woogon Shim2
Estimated H-index: 2
(LG Electronics),
Seok-Won Lee8
Estimated H-index: 8
(Ajou University)
Sources
Abstract
Abstract Nowadays agile development has become a mainstream development methodology. Yet agile is still lacking in how in-depth it deals with Requirement Engineering (RE) compared to the other development stages. There have been attempts to apply agile RE techniques to traditional development and conversely to apply traditional RE techniques to agile development. But the biggest problem is that it is difficult to maintain the essence of agile which is to “collaborate”, “(iterative and frequent) inspect and adapt”, and “deliver customer value”. In this paper, we define six criteria for an agile requirement management approach and propose a lightweight agile approach that maintains the characteristics of agile while combining the RE techniques of academia, business analyst, and agile & lean community. Furthermore, we show an industrial case study which we've applied our approach.
📖 Papers frequently viewed together
2017
2 Citations
2016
9 Citations
275 Citations
References14
Newest
#1Irum Inayat (Information Technology University)H-Index: 9
#2Siti Salwah Salim (Information Technology University)H-Index: 14
Last. Shahaboddin Shamshirband (IAU: Islamic Azad University)H-Index: 62
view all 5 authors...
We mapped out 17 requirements engineering practices adopted by agile practitioners so far.Identified 5 challenges of traditional requirements engineering overcome by adopting agile requirements engineering.Found 8 challenges posed by following agile requirements engineering.Findings suggest that research context needs attention in terms of more empirical.The empirical results can help to analyse impact of adopting agile requirements engineering. Unlike traditional software development methods, a...
215 CitationsSource
Jun 10, 2015 in ICSOB (International Conference on Software Business)
#1Helena Holmström Olsson (Malmö University)H-Index: 22
#2Jan Bosch (Chalmers University of Technology)H-Index: 68
Software-intensive product companies are becoming increasingly data-driven as can be witnessed by the big data and Internet of Things trends. However, optimally prioritizing customer needs in a mass-market context is notoriously difficult. While most companies use product owners or managers to represent the customer, research shows that the prioritization made is far from optimal. In earlier research, we have coined the term ‘the open loop problem’ to characterize this challenge. For instance, r...
33 CitationsSource
#2Yves PigneurH-Index: 30
Last. Alan SmithH-Index: 3
view all 4 authors...
83 Citations
#1Neil A. Ernst (UBC: University of British Columbia)H-Index: 22
#2Alexander Borgida (RU: Rutgers University)H-Index: 55
Last. John Mylopoulos (University of Trento)H-Index: 94
view all 4 authors...
Innovative companies need an agile approach towards product and service requirements, to rapidly respond to and exploit changing conditions. The agile approach to requirements must nonetheless be systematic, especially with respect to accommodating legal and non-functional requirements. This paper examines how to support lightweight, agile requirements processes which can still be systematically modeled, analyzed and changed. We propose a framework, RE-KOMBINE, which is based on a propositional ...
23 CitationsSource
One of the fundamental principles of DevOps is that any build that successfully passes the gauntlet of automated checks can potentially be delivered into production. Checks can specifically verify whether any new or updated code broke any existing feature. In other words, they guard against regression failures. It is for this reason that automated testing plays such a vital role in the DevOps process.
13 CitationsSource
#1Henrik KnibergH-Index: 2
Lean from the Trenches is all about actual practice. Find out how the Swedish police combined XP, Scrum, and Kanban in a 60-person project. From start to finish, you'll see how to deliver a successful product using Lean principles. We start with an organization in desperate need of a new way of doing things and finish with a group of sixty, all working in sync to develop a scalable, complex system. You'll walk through the project step by step, from customer engagement, to the daily "cocktail par...
22 Citations
#1Eric RiesH-Index: 7
266 Citations
Sep 16, 2010 in ESEM (Empirical Software Engineering and Measurement)
#1Zornitza Racheva (UT: University of Twente)H-Index: 7
#2Maya Daneva (UT: University of Twente)H-Index: 25
Last. Andrea HerrmannH-Index: 6
view all 3 authors...
Requirements (re)prioritization is an essential mechanism of agile development approaches to maximize the value for the clients and to accommodate changing requirements. Yet, in the agile Requirements Engineering (RE) literature, very little is known about how agile (re)prioritization happens in practice. Conceptual models about this process are missing, which, in turn, makes it difficult for both practitioners and researchers to reason about requirements decision-making at inter-iteration time....
23 CitationsSource
#2Yves PigneurH-Index: 30
Buku ini merupakan panduan untuk para visioner, penggerak perubahan, dan pendobrak yang berjuang menantang model bisnis yang sudah ketinggalan zaman dan mendesain perusahaan masa depan. INi adlah buku untuk membangun model bisnis. Dengan memberi anda alat bantu yang efektif, sederhana, dan teruji untuk memahami, merancang, memperbaiki, dan menerapkan model-model bisnis.
1,245 Citations
#1Kenneth Duncan Boness (University of Reading)H-Index: 6
#2Ay UkH-Index: 1
Last. Kecheng Liu (University of Reading)H-Index: 29
view all 4 authors...
This paper describes a technique that can be used as part of a simple and practical agile method for requirements engineering. It is based on disciplined goal-responsibility modelling but eschews formality in favour of a set of practicality objectives. The technique can be used together with Agile Programming to develop software in internet time. We illustrate the technique and introduce lazy refinement, responsibility composition and context sketching. Goal sketching has been used in a number o...
6 Citations
Cited By3
Newest
#1Yong Chen (TAMIU: Texas A&M International University)H-Index: 1
Industrial information integration engineering (IIIE) is a set of foundational concepts and techniques that facilitate the industrial information integration process. In recent years, many applicat...
12 CitationsSource
#1Woogon Shim (Ajou University)H-Index: 1
Agile and lean are now the mainstream tenets of software development. This development methodology is attracting attention because it can develop software that operates quickly despite uncertain situations and limited information (requirements), and it can adaptively develop while checking feedback both frequently and regularly. The key is to welcome change without resistance, which is not limited to development but also requires changes in requirement management. However, there is a lack of pra...
Source
#1Nan Niu (UC: University of Cincinnati)H-Index: 24
#2Daniel Méndez Fernández (TUM: Technische Universität München)H-Index: 16
Abstract This special issue tackles specific challenges of requirements engineering (RE) in agile and interconnected settings. Compared to traditional upfront RE, the practices in agile or open-source software projects tend to be just-in-time, characterized by lightweight representation and continuous refinement of requirements. The special issue features six articles, ranging from conceptual views through analytic reasonings to empirical studies. Altogether, the collection offers important and ...
Source