Details
| Original language | English |
|---|---|
| Title of host publication | Product-Focused Software Process Improvement -18th International Conference, PROFES 2017, Proceedings |
| Editors | Burak Turhan, Dietmar Winkler, Federica Sarro, Marcos Kalinowski, Daniel Mendez Fernandez, Michael Felderer |
| Publisher | Springer Verlag |
| Pages | 19-27 |
| Number of pages | 9 |
| ISBN (print) | 9783319699257 |
| Publication status | Published - 28 Oct 2017 |
| Event | 18th International Conference on Product-Focused Software Process Improvement, PROFES 2017 - Innsbruck, Austria Duration: 29 Nov 2017 → 1 Dec 2017 |
Publication series
| Name | Lecture Notes in Computer Science |
|---|---|
| Volume | 10611 LNCS |
| ISSN (Print) | 0302-9743 |
| ISSN (electronic) | 1611-3349 |
Abstract
Context: Agile software development (ASD) uses ‘agile’ artefacts such as user stories and product backlogs as well as ‘non-agile’ artefacts, for instance designs and test plans. Rationales for incorporating especially non-agile artefacts by an agile team mainly remain unknown territory. Goal: We start off to explore influences on artefacts usage, and state our research question as: To what extent does maturity relate to the usage of artefacts in ASD in software product organizations? Method: In our multiple case study 14 software product organizations were visited where software product management maturity was rated and their artefacts usage listed. Results: We found maturity to be negatively correlated with the non-agile/all artefacts ratio. In other words, the more mature software product management is, the fewer non-agile artefacts are used in ASD. Conclusions: This suggests that an organizational factor influences an agile team in its artefacts usage, contradictory to the concept of self-organizing agile teams.
Keywords
- Agile, Artefacts, Maturity, Software product management
ASJC Scopus subject areas
- Mathematics(all)
- Theoretical Computer Science
- Computer Science(all)
- General Computer Science
Cite this
- Standard
- Harvard
- Apa
- Vancouver
- BibTeX
- RIS
Product-Focused Software Process Improvement -18th International Conference, PROFES 2017, Proceedings. ed. / Burak Turhan; Dietmar Winkler; Federica Sarro; Marcos Kalinowski; Daniel Mendez Fernandez; Michael Felderer. Springer Verlag, 2017. p. 19-27 (Lecture Notes in Computer Science; Vol. 10611 LNCS).
Research output: Chapter in book/report/conference proceeding › Conference contribution › Research › peer review
}
TY - GEN
T1 - Influence of software product management maturity on usage of artefacts in agile software development
AU - Wagenaar, Gerard
AU - Overbeek, Sietse
AU - Lucassen, Garm
AU - Brinkkemper, Sjaak
AU - Schneider, Kurt
N1 - Publisher Copyright: © Springer International Publishing AG 2017. Copyright: Copyright 2017 Elsevier B.V., All rights reserved.
PY - 2017/10/28
Y1 - 2017/10/28
N2 - Context: Agile software development (ASD) uses ‘agile’ artefacts such as user stories and product backlogs as well as ‘non-agile’ artefacts, for instance designs and test plans. Rationales for incorporating especially non-agile artefacts by an agile team mainly remain unknown territory. Goal: We start off to explore influences on artefacts usage, and state our research question as: To what extent does maturity relate to the usage of artefacts in ASD in software product organizations? Method: In our multiple case study 14 software product organizations were visited where software product management maturity was rated and their artefacts usage listed. Results: We found maturity to be negatively correlated with the non-agile/all artefacts ratio. In other words, the more mature software product management is, the fewer non-agile artefacts are used in ASD. Conclusions: This suggests that an organizational factor influences an agile team in its artefacts usage, contradictory to the concept of self-organizing agile teams.
AB - Context: Agile software development (ASD) uses ‘agile’ artefacts such as user stories and product backlogs as well as ‘non-agile’ artefacts, for instance designs and test plans. Rationales for incorporating especially non-agile artefacts by an agile team mainly remain unknown territory. Goal: We start off to explore influences on artefacts usage, and state our research question as: To what extent does maturity relate to the usage of artefacts in ASD in software product organizations? Method: In our multiple case study 14 software product organizations were visited where software product management maturity was rated and their artefacts usage listed. Results: We found maturity to be negatively correlated with the non-agile/all artefacts ratio. In other words, the more mature software product management is, the fewer non-agile artefacts are used in ASD. Conclusions: This suggests that an organizational factor influences an agile team in its artefacts usage, contradictory to the concept of self-organizing agile teams.
KW - Agile
KW - Artefacts
KW - Maturity
KW - Software product management
UR - http://www.scopus.com/inward/record.url?scp=85034580290&partnerID=8YFLogxK
U2 - 10.1007/978-3-319-69926-4_2
DO - 10.1007/978-3-319-69926-4_2
M3 - Conference contribution
AN - SCOPUS:85034580290
SN - 9783319699257
T3 - Lecture Notes in Computer Science
SP - 19
EP - 27
BT - Product-Focused Software Process Improvement -18th International Conference, PROFES 2017, Proceedings
A2 - Turhan, Burak
A2 - Winkler, Dietmar
A2 - Sarro, Federica
A2 - Kalinowski, Marcos
A2 - Mendez Fernandez, Daniel
A2 - Felderer, Michael
PB - Springer Verlag
T2 - 18th International Conference on Product-Focused Software Process Improvement, PROFES 2017
Y2 - 29 November 2017 through 1 December 2017
ER -