Planning optimal agile releases via requirements optimization

Research output: Contribution in Book/Catalog/Report/Conference proceedingConference contribution

Abstract

This paper focuses on improving requirements quality in agile projects by determining requirements prioritization. Current methods suggest to take into account business value in order to determine the requirements priority rank. In practice it was observed that many other factors enter into the equation, such as implementation cost and functionality dependencies. Since agile methods suggest that priority should be customer/user's prerogative, taking all relevant factors becomes challenging without decision supporting tools. Our research question is the following: How can we formulate the agile release decision problem, and which computations can we do over requirements models to recommend solutions to that decision problem? Our contributions are the following: (i) we formulate this agile release decision problem as an optimization problem, (ii) we provide a modelling language to represent instances of this problem as requirements models, and (iii) we describe an online tool to make the models and solve the resulting optimization problem instances.

Original languageEnglish
Title of host publicationProceedings - 2016 IEEE 24th International Requirements Engineering Conference Workshops, REW 2016
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages10-16
Number of pages7
ISBN (Electronic)9781509036943
DOIs
Publication statusPublished - 12 Jan 2017
Event24th IEEE International Requirements Engineering Conference Workshops, REW 2016 - Beijing, China
Duration: 12 Sept 201616 Sept 2016

Conference

Conference24th IEEE International Requirements Engineering Conference Workshops, REW 2016
Country/TerritoryChina
CityBeijing
Period12/09/1616/09/16

Keywords

  • Agile methodology
  • Goal models
  • Requirements optimization
  • Requirements prioritization

Fingerprint

Dive into the research topics of 'Planning optimal agile releases via requirements optimization'. Together they form a unique fingerprint.

Cite this