Agile Pitfalls
Broman, Susanna (2017)
Metropolia Ammattikorkeakoulu
2017
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2017053111592
https://urn.fi/URN:NBN:fi:amk-2017053111592
Tiivistelmä
The purpose of this study was to identify the most common pitfalls of agile software development and to provide a checklist for overcoming these issues. The use of agile methods has been a rising trend in the software development and the number of agile pitfalls organizations are facing is endless, but there are a lot of same mistakes many organizations are doing one after another. There is no case company involved in the study but the subject was chosen due to authors own interest in agile methods.
Qualitative research methodology was used in this study. The research data consisted of interview discussions with five agile professionals representing different organizations.
The results of the interviews revealed the most common issues organizations are facing in agile software development. The interviewees had rather similar views and it became obvious that the same issues were taking place repeatedly in different organizations. The interviewees embraced agile in many ways but felt that it was often used without careful consideration. In addition, a lack of sufficient pre-requisites and knowledge was experienced, leading to issues with quality, communication and efficiency.
The author recommends that organizations planning to go agile would use a checklist to ensure awareness of the possible pitfalls and the way they can be avoided. It is recommended to consider whether it is reasonable to use agile instead of traditional methods, what kind of agile approach to select and to create a change management strategy with an execution plan.
Qualitative research methodology was used in this study. The research data consisted of interview discussions with five agile professionals representing different organizations.
The results of the interviews revealed the most common issues organizations are facing in agile software development. The interviewees had rather similar views and it became obvious that the same issues were taking place repeatedly in different organizations. The interviewees embraced agile in many ways but felt that it was often used without careful consideration. In addition, a lack of sufficient pre-requisites and knowledge was experienced, leading to issues with quality, communication and efficiency.
The author recommends that organizations planning to go agile would use a checklist to ensure awareness of the possible pitfalls and the way they can be avoided. It is recommended to consider whether it is reasonable to use agile instead of traditional methods, what kind of agile approach to select and to create a change management strategy with an execution plan.