Icons / Logo / Facebook Created with Sketch. Icons / Logo / Google Created with Sketch. Icons / Logo / ORCID Created with Sketch. Branding/Logomark minus Citation Combined Shape Icon/Bookmark-empty Icon/Copy Icon/Collection Icon/Close Copy 7 no author result Created with Sketch. Icon/Back Created with Sketch. Match!

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

Published on Aug 1, 2018in Journal of Industrial Information Integration
· DOI :10.1016/j.jii.2018.07.005
Woogon Shim1
Estimated H-index: 1
(LG Electronics),
Seok-Won Lee12
Estimated H-index: 12
(Ajou University)
Cite
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.
  • References (15)
  • Citations (2)
Cite
References15
Newest
Published on Oct 1, 2015in Computers in Human Behavior 4.31
Irum Inayat7
Estimated H-index: 7
(Information Technology University),
Siti Salwah Salim11
Estimated H-index: 11
(Information Technology University)
+ 2 AuthorsShahaboddin Shamshirband34
Estimated H-index: 34
(IAU: Islamic Azad University)
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...
Published on Jan 1, 2015 in ICSOB (International Conference on Software Business)
Helena Holmström Olsson18
Estimated H-index: 18
(Malmö University),
Jan Bosch48
Estimated H-index: 48
(Chalmers University of Technology)
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...
Published on Jan 1, 2015in The Quality Management Journal
Nicole Radziwill2
Estimated H-index: 2
Published on Jul 1, 2014in Information Systems 2.07
Neil A. Ernst19
Estimated H-index: 19
(UBC: University of British Columbia),
Alexander Borgida41
Estimated H-index: 41
(RU: Rutgers University)
+ 1 AuthorsJ. Mylopolous74
Estimated H-index: 74
(University of Trento)
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 ...
Published on Jan 1, 2012
Michael Hüttermann1
Estimated H-index: 1
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.
Published on Dec 21, 2011
Henrik Kniberg1
Estimated H-index: 1
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...
Published on Sep 16, 2010 in ESEM (Empirical Software Engineering and Measurement)
Zornitza Racheva7
Estimated H-index: 7
(UT: University of Twente),
Maya Daneva21
Estimated H-index: 21
(UT: University of Twente),
Andrea Herrmann10
Estimated H-index: 10
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....
Published on Oct 20, 2010
Alexander Osterwalder16
Estimated H-index: 16
,
Yves Pigneur27
Estimated H-index: 27
Published on Jan 1, 2008
Kenneth Duncan Boness5
Estimated H-index: 5
(University of Reading),
Ay Uk1
Estimated H-index: 1
+ 1 AuthorsKecheng Liu20
Estimated H-index: 20
(University of Reading)
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...
Published on Aug 1, 2007
Kenneth Duncan Boness5
Estimated H-index: 5
(University of Reading),
Rachel Harrison20
Estimated H-index: 20
This paper describes a technique that can be used as part of a simple and practical agile method for requirements engineering. 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 of real-world development projects, one of which is described here.
Cited By2
Newest
Nan Niu (UC: University of Cincinnati), Daniel Méndez Fernández14
Estimated H-index: 14
(TUM: Technische Universität München)
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 ...
Geraldo Torres G. Neto (UPE: Universidade de Pernambuco), Wylliams Santos1
Estimated H-index: 1
(UPE: Universidade de Pernambuco)
+ -3 AuthorsTiziana Margaria31
Estimated H-index: 31
(UL: University of Limerick)