Some Findings Concerning Requirements in Agile Methodologies

Rodriguez Gonzalez, Pilar, Yagüe Panadero, Agustín ORCID: https://orcid.org/0000-0002-4761-0901, Alarcón Cavero, Pedro Pablo ORCID: https://orcid.org/0000-0003-4285-5333 and Garbajosa Sopeña, Juan ORCID: https://orcid.org/0000-0003-0161-3485 (2009). Some Findings Concerning Requirements in Agile Methodologies. "Product-Focused Software Process Improvement", v. 32 (n. 4); pp. 171-184. ISSN 1865-1348. https://doi.org/10.1007/978-3-642-02152-7_14.

Descripción

Título: Some Findings Concerning Requirements in Agile Methodologies
Autor/es:
Tipo de Documento: Artículo
Título de Revista/Publicación: Product-Focused Software Process Improvement
Fecha: Junio 2009
ISSN: 1865-1348
Volumen: 32
Número: 4
Materias:
ODS:
Escuela: E.U. de Informática (UPM) [antigua denominación]
Departamento: Organización y Estructura de la Información [hasta 2014]
Licencias Creative Commons: Reconocimiento - Sin obra derivada - No comercial

Texto completo

[thumbnail of INVE_MEM_2009_70574.pdf]
Vista Previa
PDF (Portable Document Format) - Se necesita un visor de ficheros PDF, como GSview, Xpdf o Adobe Acrobat Reader
Descargar (677kB) | Vista Previa

Resumen

gile methods have appeared as an attractive alternative to conventional methodologies. These methods try to reduce the time to market and, indirectly, the cost of the product through flexible development and deep customer involvement. The processes related to requirements have been extensively studied in literature, in most cases in the frame of conventional methods. However, conclusions of conventional methodologies could not be necessarily valid for Agile; in some issues, conventional and Agile processes are radically different. As recent surveys report, inadequate project requirements is one of the most conflictive issues in agile approaches and better understanding about this is needed. This paper describes some findings concerning requirements activities in a project developed under an agile methodology. The project intended to evolve an existing product and, therefore, some background information was available. The major difficulties encountered were related to non-functional needs and management of requirements dependencies.

Más información

ID de Registro: 5340
Identificador DC: https://oa.upm.es/5340/
Identificador OAI: oai:oa.upm.es:5340
Identificador DOI: 10.1007/978-3-642-02152-7_14
URL Oficial: http://www.springerlink.com/content/pv437275074272...
Depositado por: Memoria Investigacion
Depositado el: 02 Dic 2010 11:15
Ultima Modificación: 20 Abr 2016 14:10