Agile software development approach for 'ad-hoc' IT projects

Restrictive Scrum assumptions make the effectiveness of this approach debatable in projects deviating from typical execution conditions. This article delivers a comprehensive software development approach for both academic and commercial Information Technology (IT) projects effectuated by teams tha...

Full description

Bibliographic Details
Main Authors: Michal Kuciapski, Bartosz Marcinkowski
Format: Article
Language:English
Published: UMinho Editora 2023-12-01
Series:International Journal of Information Systems and Project Management
Subjects:
Online Access:https://revistas.uminho.pt/index.php/ijispm/article/view/5539
_version_ 1797373896114044928
author Michal Kuciapski
Bartosz Marcinkowski
author_facet Michal Kuciapski
Bartosz Marcinkowski
author_sort Michal Kuciapski
collection DOAJ
description Restrictive Scrum assumptions make the effectiveness of this approach debatable in projects deviating from typical execution conditions. This article delivers a comprehensive software development approach for both academic and commercial Information Technology (IT) projects effectuated by teams that are hampered by significantly unsystematic participation of project members and mercurial internal communication. The nature of ‘ad-hoc’ projects imposes another level of difficulty in terms of both managing the conduct of such a project and ensuring the quality of the end product. Multicyclic action research enabled a gradual adaptation of the Scrum approach to support such project conditions. This study introduces major alterations to Sprint implementation and minor enhancements within the documentation process to streamline knowledge sharing among Development Team members. Proposed key alterations include the evolution of Daily Scrum towards Weekly Scrum, the possibility of extending Sprints length, the eventuality to switch team members during Sprint due to substantial failure to meet deadlines, having at least two team members responsible for a single Product Backlog Item (PBI) at all times, as well as exclusion of Burndown Chart in favor for Development Team members updating their working time. Positive validation of enhancements in mixed settings confirms that the generic Scrum framework can be adapted to support highly volatile projects. The proposed approach is suitable not only for carrying out software development initiatives that rely heavily on the skills of external experts and/or volunteers. It also supports traditional Scrum teams that seek to reduce their exposure to risk arising from organizational changes.
first_indexed 2024-03-08T18:57:04Z
format Article
id doaj.art-96e23d0b963143f18a0b5da5fb2c4650
institution Directory Open Access Journal
issn 2182-7788
language English
last_indexed 2024-03-08T18:57:04Z
publishDate 2023-12-01
publisher UMinho Editora
record_format Article
series International Journal of Information Systems and Project Management
spelling doaj.art-96e23d0b963143f18a0b5da5fb2c46502023-12-28T10:38:25ZengUMinho EditoraInternational Journal of Information Systems and Project Management2182-77882023-12-0111410.12821/ijispm110402Agile software development approach for 'ad-hoc' IT projectsMichal Kuciapski0Bartosz Marcinkowski1Department of Business Informatics, University of GdanskDepartment of Business Informatics, University of Gdansk Restrictive Scrum assumptions make the effectiveness of this approach debatable in projects deviating from typical execution conditions. This article delivers a comprehensive software development approach for both academic and commercial Information Technology (IT) projects effectuated by teams that are hampered by significantly unsystematic participation of project members and mercurial internal communication. The nature of ‘ad-hoc’ projects imposes another level of difficulty in terms of both managing the conduct of such a project and ensuring the quality of the end product. Multicyclic action research enabled a gradual adaptation of the Scrum approach to support such project conditions. This study introduces major alterations to Sprint implementation and minor enhancements within the documentation process to streamline knowledge sharing among Development Team members. Proposed key alterations include the evolution of Daily Scrum towards Weekly Scrum, the possibility of extending Sprints length, the eventuality to switch team members during Sprint due to substantial failure to meet deadlines, having at least two team members responsible for a single Product Backlog Item (PBI) at all times, as well as exclusion of Burndown Chart in favor for Development Team members updating their working time. Positive validation of enhancements in mixed settings confirms that the generic Scrum framework can be adapted to support highly volatile projects. The proposed approach is suitable not only for carrying out software development initiatives that rely heavily on the skills of external experts and/or volunteers. It also supports traditional Scrum teams that seek to reduce their exposure to risk arising from organizational changes. https://revistas.uminho.pt/index.php/ijispm/article/view/5539project managementagilesoftware developmentsystems engineeringScrumadaptation
spellingShingle Michal Kuciapski
Bartosz Marcinkowski
Agile software development approach for 'ad-hoc' IT projects
International Journal of Information Systems and Project Management
project management
agile
software development
systems engineering
Scrum
adaptation
title Agile software development approach for 'ad-hoc' IT projects
title_full Agile software development approach for 'ad-hoc' IT projects
title_fullStr Agile software development approach for 'ad-hoc' IT projects
title_full_unstemmed Agile software development approach for 'ad-hoc' IT projects
title_short Agile software development approach for 'ad-hoc' IT projects
title_sort agile software development approach for ad hoc it projects
topic project management
agile
software development
systems engineering
Scrum
adaptation
url https://revistas.uminho.pt/index.php/ijispm/article/view/5539
work_keys_str_mv AT michalkuciapski agilesoftwaredevelopmentapproachforadhocitprojects
AT bartoszmarcinkowski agilesoftwaredevelopmentapproachforadhocitprojects