Prioritizing agile benefits and limitations in relation to practice usage
(2016) In Software Quality Journal 24(2). p.447-482- Abstract
In recent years, there has been significant shift from rigid development (RD) toward agile. However, it has also been spotted that agile methodologies are hardly ever followed in their pure form. Hybrid processes as combinations of RD and agile practices emerge. In addition, agile adoption has been reported to result in both benefits and limitations. This exploratory study (a) identifies development models based on RD and agile practice usage by practitioners; (b) identifies agile practice adoption scenarios based on eliciting practice usage over time; (c) prioritizes agile benefits and limitations in relation to (a) and (b). Practitioners provided answers through a questionnaire. The development models are determined using hierarchical... (More)
In recent years, there has been significant shift from rigid development (RD) toward agile. However, it has also been spotted that agile methodologies are hardly ever followed in their pure form. Hybrid processes as combinations of RD and agile practices emerge. In addition, agile adoption has been reported to result in both benefits and limitations. This exploratory study (a) identifies development models based on RD and agile practice usage by practitioners; (b) identifies agile practice adoption scenarios based on eliciting practice usage over time; (c) prioritizes agile benefits and limitations in relation to (a) and (b). Practitioners provided answers through a questionnaire. The development models are determined using hierarchical cluster analysis. The use of practices over time is captured through an interactive board with practices and time indication sliders. This study uses the extended hierarchical voting analysis framework to investigate benefit and limitation prioritization. Four types of development models and six adoption scenarios have been identified. Overall, 45 practitioners participated in the prioritization study. A common benefit among all models and adoption patterns is knowledge and learning, while high requirements on professional skills were perceived as the main limitation. Furthermore, significant variances in terms of benefits and limitations have been observed between models and adoption patterns. The most significant internal benefit categories from adopting agile are knowledge and learning, employee satisfaction, social skill development, and feedback and confidence. Professional skill-specific demands, scalability, and lack of suitability for specific product domains are the main limitations of agile practice usage. Having a balanced agile process allows to achieve a high number of benefits. With respect to adoption, a big bang transition from RD to agile leads to poor quality in comparison with the alternatives.
(Less)
- author
- Solinski, Adam and Petersen, Kai
- publishing date
- 2016-06-01
- type
- Contribution to journal
- publication status
- published
- subject
- keywords
- Agile, Benefits, Limitations, Practice adoption, Prioritization
- in
- Software Quality Journal
- volume
- 24
- issue
- 2
- pages
- 36 pages
- publisher
- Springer
- external identifiers
-
- scopus:84907495216
- ISSN
- 0963-9314
- DOI
- 10.1007/s11219-014-9253-3
- project
- Embedded Applications Software Engineering
- language
- English
- LU publication?
- no
- id
- 933f4df9-2b21-4c60-a9bf-7356114ba8ee
- date added to LUP
- 2018-09-27 12:33:53
- date last changed
- 2024-04-15 12:11:02
@article{933f4df9-2b21-4c60-a9bf-7356114ba8ee,
abstract = {{<p>In recent years, there has been significant shift from rigid development (RD) toward agile. However, it has also been spotted that agile methodologies are hardly ever followed in their pure form. Hybrid processes as combinations of RD and agile practices emerge. In addition, agile adoption has been reported to result in both benefits and limitations. This exploratory study (a) identifies development models based on RD and agile practice usage by practitioners; (b) identifies agile practice adoption scenarios based on eliciting practice usage over time; (c) prioritizes agile benefits and limitations in relation to (a) and (b). Practitioners provided answers through a questionnaire. The development models are determined using hierarchical cluster analysis. The use of practices over time is captured through an interactive board with practices and time indication sliders. This study uses the extended hierarchical voting analysis framework to investigate benefit and limitation prioritization. Four types of development models and six adoption scenarios have been identified. Overall, 45 practitioners participated in the prioritization study. A common benefit among all models and adoption patterns is knowledge and learning, while high requirements on professional skills were perceived as the main limitation. Furthermore, significant variances in terms of benefits and limitations have been observed between models and adoption patterns. The most significant internal benefit categories from adopting agile are knowledge and learning, employee satisfaction, social skill development, and feedback and confidence. Professional skill-specific demands, scalability, and lack of suitability for specific product domains are the main limitations of agile practice usage. Having a balanced agile process allows to achieve a high number of benefits. With respect to adoption, a big bang transition from RD to agile leads to poor quality in comparison with the alternatives.</p>}},
author = {{Solinski, Adam and Petersen, Kai}},
issn = {{0963-9314}},
keywords = {{Agile; Benefits; Limitations; Practice adoption; Prioritization}},
language = {{eng}},
month = {{06}},
number = {{2}},
pages = {{447--482}},
publisher = {{Springer}},
series = {{Software Quality Journal}},
title = {{Prioritizing agile benefits and limitations in relation to practice usage}},
url = {{http://dx.doi.org/10.1007/s11219-014-9253-3}},
doi = {{10.1007/s11219-014-9253-3}},
volume = {{24}},
year = {{2016}},
}