Details
| Original language | English |
|---|---|
| Title of host publication | Proceedings - 2020 IEEE/ACM International Conference on Software and System Processes, ICSSP 2020 |
| Pages | 185-188 |
| Number of pages | 4 |
| ISBN (electronic) | 9781450375122 |
| Publication status | Published - 26 Jun 2020 |
| Event | International Conference on Software and Systems Process (ICSSP'20) - Duration: 26 Jun 2020 → 28 Jun 2020 |
Abstract
Agile methods were proposed to address the problems of traditional or plan-based software development, e.g., late customer feedback or resistance to change. However, unlike plan-based methods, they are not designed for long-term planning or to cope with large projects. Software companies want the ability of a fast reaction to changes but also the ability of long-term planning. To profit from the strength of both approaches, software companies often use a combination of agile and plan-based methods, called hybrid development approaches. These approaches depend on the respective context of each company. Therefore, the companies have to properly arrange and connect the phases, activities, roles, and artifacts from plan-based and agile approaches individually in their hybrid development approach. This is considered as the organization of hybrid development approaches. However, the organization of hybrid approaches is often difficult for the companies. Until now, research considers only the chosen development methods without the organization of hybrid development approaches. With my work, I want to strengthen the understanding of how hybrid approaches are organized and get a detailed picture of the challenges when organizing hybrid approaches. Based on my findings, I want to develop measures to support practitioners while organizing their development approach.
Keywords
- Hybrid software development, agile software development, plan-based software development, software process
ASJC Scopus subject areas
- Computer Science(all)
- Hardware and Architecture
- Computer Science(all)
- Software
Cite this
- Standard
- Harvard
- Apa
- Vancouver
- BibTeX
- RIS
Proceedings - 2020 IEEE/ACM International Conference on Software and System Processes, ICSSP 2020. 2020. p. 185-188.
Research output: Chapter in book/report/conference proceeding › Conference contribution › Research › peer review
}
TY - GEN
T1 - Towards Improving the Organization of Hybrid Development Approaches
AU - Prenner, Nils
PY - 2020/6/26
Y1 - 2020/6/26
N2 - Agile methods were proposed to address the problems of traditional or plan-based software development, e.g., late customer feedback or resistance to change. However, unlike plan-based methods, they are not designed for long-term planning or to cope with large projects. Software companies want the ability of a fast reaction to changes but also the ability of long-term planning. To profit from the strength of both approaches, software companies often use a combination of agile and plan-based methods, called hybrid development approaches. These approaches depend on the respective context of each company. Therefore, the companies have to properly arrange and connect the phases, activities, roles, and artifacts from plan-based and agile approaches individually in their hybrid development approach. This is considered as the organization of hybrid development approaches. However, the organization of hybrid approaches is often difficult for the companies. Until now, research considers only the chosen development methods without the organization of hybrid development approaches. With my work, I want to strengthen the understanding of how hybrid approaches are organized and get a detailed picture of the challenges when organizing hybrid approaches. Based on my findings, I want to develop measures to support practitioners while organizing their development approach.
AB - Agile methods were proposed to address the problems of traditional or plan-based software development, e.g., late customer feedback or resistance to change. However, unlike plan-based methods, they are not designed for long-term planning or to cope with large projects. Software companies want the ability of a fast reaction to changes but also the ability of long-term planning. To profit from the strength of both approaches, software companies often use a combination of agile and plan-based methods, called hybrid development approaches. These approaches depend on the respective context of each company. Therefore, the companies have to properly arrange and connect the phases, activities, roles, and artifacts from plan-based and agile approaches individually in their hybrid development approach. This is considered as the organization of hybrid development approaches. However, the organization of hybrid approaches is often difficult for the companies. Until now, research considers only the chosen development methods without the organization of hybrid development approaches. With my work, I want to strengthen the understanding of how hybrid approaches are organized and get a detailed picture of the challenges when organizing hybrid approaches. Based on my findings, I want to develop measures to support practitioners while organizing their development approach.
KW - Hybrid software development
KW - agile software development
KW - plan-based software development
KW - software process
UR - http://www.scopus.com/inward/record.url?scp=85092524491&partnerID=8YFLogxK
U2 - 10.1145/3379177.3390304
DO - 10.1145/3379177.3390304
M3 - Conference contribution
SP - 185
EP - 188
BT - Proceedings - 2020 IEEE/ACM International Conference on Software and System Processes, ICSSP 2020
T2 - International Conference on Software and Systems Process (ICSSP'20)
Y2 - 26 June 2020 through 28 June 2020
ER -