|
Descripción
|
|
|---|---|
| Agile 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 | |
|
Internacional
|
Si |
|
Nombre congreso
|
10th International Conference, PROFES 2009, Proceedings |
|
Tipo de participación
|
960 |
|
Lugar del congreso
|
Oulu, Finland, |
|
Revisores
|
Si |
|
ISBN o ISSN
|
978-3-642-02151-0 |
|
DOI
|
10.1007/978-3-642-02152-7_14 |
|
Fecha inicio congreso
|
15/06/2009 |
|
Fecha fin congreso
|
17/06/2009 |
|
Desde la página
|
171 |
|
Hasta la página
|
184 |
|
Título de las actas
|
Lecture Notes in Business Information Processing.Product-Focused Software Process Improvement |