scholarly journals Requirements engineering practice and problems in agile projects: results from an international survey

2016 ◽  
Author(s):  
Stefan Wagner ◽  
Daniel Méndez Fernández ◽  
Michael Felderer ◽  
Marcos Kalinowski
Keyword(s):  
Requirements Engineering ◽  
Continuous Improvement ◽  
Agile Development ◽  
Engineering Practice ◽  
Free Text ◽  
Acceptance Test ◽  
International Survey ◽  
Empirical Knowledge ◽  
Test Driven Development ◽  
Development Processes

Requirements engineering (RE) is considerably different in agile development than in traditional processes. Yet, there is little empirical knowledge on the state of the practice and contemporary problems in agile RE. As part of a bigger survey initiative (Naming the Pain in Requirements Engineering), we build an empirical basis on such aspects of agile RE. Based on the responses from 92 people representing 92 organizations, we found that agile RE concentrates on free-text documentation of requirements elicited with a variety of techniques. Many manage explicit traces between requirements and code. Furthermore, the continuous improvement of RE is done because of intrinsic motivation. Important experienced problems include unclear requirements and communication flaws. Hence, agile RE is in several aspects not so different from RE in other development processes. We plan to investigate specific techniques, such as acceptance-test-driven development, in a future survey to better capture what is special in agile RE.

scholarly journals Requirements engineering practice and problems in agile projects: results from an international survey

2016 ◽  
Author(s):  
Stefan Wagner ◽  
Daniel Méndez Fernández ◽  
Michael Felderer ◽  
Marcos Kalinowski
Keyword(s):  
Requirements Engineering ◽  
Continuous Improvement ◽  
Agile Development ◽  
Engineering Practice ◽  
Free Text ◽  
Acceptance Test ◽  
International Survey ◽  
Empirical Knowledge ◽  
Test Driven Development ◽  
Development Processes

Requirements engineering (RE) is considerably different in agile development than in traditional processes. Yet, there is little empirical knowledge on the state of the practice and contemporary problems in agile RE. As part of a bigger survey initiative (Naming the Pain in Requirements Engineering), we build an empirical basis on such aspects of agile RE. Based on the responses from 92 people representing 92 organizations, we found that agile RE concentrates on free-text documentation of requirements elicited with a variety of techniques. Many manage explicit traces between requirements and code. Furthermore, the continuous improvement of RE is done because of intrinsic motivation. Important experienced problems include unclear requirements and communication flaws. Hence, agile RE is in several aspects not so different from RE in other development processes. We plan to investigate specific techniques, such as acceptance-test-driven development, in a future survey to better capture what is special in agile RE.

scholarly journals Agile Requirements Engineering in Practice: Status Quo and Critical Problems

2018 ◽  
Vol 21 (1) ◽  
Author(s):  
Stefan Wagner ◽  
Daniel Méndez Fernández ◽  
Marcos Kalinowski ◽  
Michael Felderer
Keyword(s):  
Requirements Engineering ◽  
Continuous Improvement ◽  
Status Quo ◽  
Agile Development ◽  
Free Text ◽  
Empirical Knowledge ◽  
Data Analyses ◽  
Critical Problems ◽  
Development Processes ◽  
Agile Requirements

Requirements Engineering (RE) is being treated differently in agile development when compared to more traditional development processes. Yet, there is little empirical knowledge on the state of the practice and contemporary problems in agile RE. As part of a bigger survey initiative (Naming the Pain in Requirements Engineering), the main goal of this paper is to build an empirical basis on such aspects of agile RE, based on the responses of representatives from 92 different organisations. Our survey data analyses revealed that agile RE concentrates on free-text documentation of requirements elicited with a variety of techniques. The backlog is the central means to deal with changing requirements. Commonly traces between requirements and code are explicitly managed and testing and RE are typically aligned. Furthermore, continuous improvement of RE is performed due to intrinsic motivation and RE standards are commonly practiced. Among the main problems, we highlight incomplete requirements, communication flaws and moving targets. Those problems were reported to happen commonly in agile projects and to have critical consequences, including project failure. Overall, our findings show that most organisations conduct RE in a way we would expect and that agile RE is in several aspects not so different from RE in other development processes.

SaaS Requirements Engineering for Agile Development

2013 ◽  
pp. 64-93 ◽  
Author(s):  
Asif Qumer Gill ◽  
Deborah Bunker
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Business Process ◽  
Development Process ◽  
Business Processes ◽  
Software As A Service ◽  
Agile Development ◽  
Agile Practices ◽  
Development Processes ◽  
Agile Software

The emergence of Software as a Service (SaaS) has made it possible to develop dynamic and complex business processes as eServices. The development of business processes as eServices (SaaS) can be assisted by the means of adaptive or agile development processes. The development of business processes in terms of SaaS require to perform SaaS requirements engineering (RE), which is an important phase of a software development process for the success of any project. The challenge here is how best to do SaaS RE (e.g. mapping business process to eServices) and select agile development practices for developing business processes in terms of SaaS. In order to address this challenge, an integrated agile RE model for SaaS project development environments is outlined within this chapter. The purpose of the proposed RE model is to aid in iteratively determining SaaS requirements in short iterations as opposed to the “only first and onetime upfront” phase of a development process. Each identified SaaS requirement or a set of requirements for a given iteration is linked to a single or set of specific agile practices for implementation in short iterations. This model can be used as a guideline by organisations wishing to understand the challenging task of mapping business processes to SaaS and its implementation by using agile software development processes or practices.

scholarly journals An Exploratory Study of Requirements Engineering Practice in Indonesia – Part 1: Concepts and Problems

2019 ◽  
Vol 4 (1) ◽  
pp. 90
Author(s):  
Tri Astoto Kurniawan
Keyword(s):  
Requirements Engineering ◽  
Exploratory Study ◽  
Engineering Practice ◽  
Project Schedule ◽  
Online Questionnaire ◽  
Statistical Research ◽  
Web Based ◽  
Research Findings ◽  
Development Processes ◽  
Survey Results

This paper provides the first part of statistical research findings of an exploratory study of the requirements engineering practice utilized in software development processes in Indonesia. This first part attempts to reveal facts regarding concepts and problems exist in such requirements engineering practice. We developed a comprehensive online questionnaire consisting of both closed- and open-ended questions in order to capture such facts. We invited 158 participant candidates represent industry and higher education institutions, however, 31 of them joined our web-based survey. Results show that most of participants are agree that requirements engineering must be properly performed in order to clearly define the valid product. They, however, encounter some difficulties in implementing requirements engineering concept in practice due to a tight project schedule, inappropriate skill of the analysts and inadequate tools.

SaaS Requirements Engineering for Agile Development

2015 ◽  
pp. 660-688
Author(s):  
Asif Qumer Gill ◽  
Deborah Bunker
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Business Process ◽  
Development Process ◽  
Business Processes ◽  
Software As A Service ◽  
Agile Development ◽  
Agile Practices ◽  
Development Processes ◽  
Agile Software

The emergence of Software as a Service (SaaS) has made it possible to develop dynamic and complex business processes as eServices. The development of business processes as eServices (SaaS) can be assisted by the means of adaptive or agile development processes. The development of business processes in terms of SaaS require to perform SaaS requirements engineering (RE), which is an important phase of a software development process for the success of any project. The challenge here is how best to do SaaS RE (e.g. mapping business process to eServices) and select agile development practices for developing business processes in terms of SaaS. In order to address this challenge, an integrated agile RE model for SaaS project development environments is outlined within this chapter. The purpose of the proposed RE model is to aid in iteratively determining SaaS requirements in short iterations as opposed to the “only first and onetime upfront” phase of a development process. Each identified SaaS requirement or a set of requirements for a given iteration is linked to a single or set of specific agile practices for implementation in short iterations. This model can be used as a guideline by organisations wishing to understand the challenging task of mapping business processes to SaaS and its implementation by using agile software development processes or practices.

SaaS Requirements Engineering for Agile Development

2014 ◽  
pp. 351-380
Author(s):  
Asif Qumer Gill ◽  
Deborah Bunker
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Business Process ◽  
Development Process ◽  
Business Processes ◽  
Software As A Service ◽  
Agile Development ◽  
Agile Practices ◽  
Development Processes ◽  
Agile Software

The emergence of Software as a Service (SaaS) has made it possible to develop dynamic and complex business processes as eServices. The development of business processes as eServices (SaaS) can be assisted by the means of adaptive or agile development processes. The development of business processes in terms of SaaS require to perform SaaS requirements engineering (RE), which is an important phase of a software development process for the success of any project. The challenge here is how best to do SaaS RE (e.g. mapping business process to eServices) and select agile development practices for developing business processes in terms of SaaS. In order to address this challenge, an integrated agile RE model for SaaS project development environments is outlined within this chapter. The purpose of the proposed RE model is to aid in iteratively determining SaaS requirements in short iterations as opposed to the “only first and onetime upfront” phase of a development process. Each identified SaaS requirement or a set of requirements for a given iteration is linked to a single or set of specific agile practices for implementation in short iterations. This model can be used as a guideline by organisations wishing to understand the challenging task of mapping business processes to SaaS and its implementation by using agile software development processes or practices.

scholarly journals Modelo Aplicable A La Gestión De Procesos Ágiles De Desarrollo De Software Basado En Cmmi –Dev 1.3 Y Scrum

2015 ◽  
Vol 3 (1) ◽  
Author(s):  
Adriana Iglesias ◽  
Acellys Messino ◽  
Patty Pedroza ◽  
Ricardo Llanos
Keyword(s):  
Best Practices ◽  
Software Development ◽  
Continuous Improvement ◽  
Process Management ◽  
Model Development ◽  
Agile Development ◽  
Total Quality ◽  
Model Quality ◽  
Development And Management ◽  
Buenas Prácticas

El presente Artículo de Investigación propone un modelo orientado a las necesidades de calidad total en las organizaciones dedicadas al desarrollo de software conforme a la alineación de los procesos de desarrollo y gestión con los objetivos organizacionales; lo cual hace pertinente la formulación de un modelo de gestión de procesos de desarrollo basado en los principios y prácticas del enfoque ágil, orientado hacia la aplicación de buenas prácticas y procesos de mejora continua. El modelo planteado se denomina SUMM - “Modelo Unificado de Madurez de Scrum” y está orientado a la gestión de procesos ágiles de desarrollo de software enmarcados en las buenas prácticas de CMMI-DEV 1.3 y el marco de trabajo de SCRUM. SUMM consta de cinco niveles de madurez, de acuerdo a la representación por etapas de CMMI - DEV, estos niveles a su vez están compuestos de Metas, Objetivos, Prácticas e Indicadores que permitirán a la organización poder emplear un modelo de desarrollo ágil de calidad, enfocados en procesos de mejora continua.AbstractThis article of Research proposes a model oriented to the needs of total quality in organizations dedicated to software development according to the alignment of development and management processes with organizational objectives, which makes the formulation of relevant management model development process based on the principles and practices of agile approach towards the application of best practices and continuous improvement processes. The proposed model is called SUMM - "Unified Model Scrum Maturity" and is focused on process management software development agile framed in the best practices of CMMI-DEV 1.3 and SCRUM framework. SUMM consists of five maturity levels, according to the staged representation of CMMI - DEV, these levels in turn are composed of Goals, Objectives, Practices and indicators that enable the organization to employ an agile development model quality focused on continuous improvement processes.

Sign in / Sign up

Export Citation Format

Share Document