Human Related Challenges in Agile Software Development of Government Outsourcing Project

Nisyak, Amaliah Khoirun; Rizkiyah, Khairiyah; Raharjo, Teguh

doi:10.23919/eecsi50503.2020.9251899

Cited by 7 publications

(33 citation statements)

References 30 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Agile has emerged as a highly adopted methodology for software development projects. Implementing Agile requires distinctive practices compared to traditional RE (Nisyak et al, 2020;Ochodek & Kopczyńska, 2018). Practices, namely collaboratively planning short iterations or conducting daily team meetings that were traditionally not seen as integral to RE, now serve as catalysts for embracing lightweight requirements-related approaches such as crafting user stories (Ochodek et al, 2020).…”

Section: Agile Requirements Engineeringmentioning

confidence: 99%

“…The absence of a stable relationship between shareholders and teams in reaching an agreement on user requirements and quality of use, particularly when collaborating with end users, presents notable challenges (Fontana & Marczak, 2020;Rizkiyah et al, 2020;Schön et al, 2017). Moreover, communication difficulties between business stakeholders and engineers compound the complexities of aligning customer and vendor expectations (Nisyak et al, 2020;Noor et al, 2014;Palomares et al, 2021;Wohlrab et al, 2018).…”

Section: Lack Of Communication With Stakeholders (C4)mentioning

confidence: 99%

“…The failure of software development can be attributed to issues concerning the roles, responsibilities, and commitment of the individuals involved (Nisyak et al, 2020). Agile methodologies emphasize the significance of self-driven teams with a strong sense of commitment.…”

Section: Lack Of Individual Commitment (C5)mentioning

confidence: 99%

“…The active participation and accessibility of clients/customers significantly enhance the likelihood of project success (Rizkiyah et al, 2020). However, neglecting the inclusion of customer representatives in crucial activities like the Sprint Review can result in detrimental effects, including ineffective feedback processes and a lack of clarity regarding project progress (Nisyak et al, 2020).…”

Section: Lack Of Stakeholder Availability (C6)mentioning

confidence: 99%

See 3 more Smart Citations

Barriers of Agile Requirements Engineering in the Public Sector: A Systematic Literature Review

Tri Utami,

Raharjo,

Zharif Mustaqim

et al. 2024

IJIKM

View full text Add to dashboard Cite

Aim/Purpose: The objective of this study is to summarize the challenges of Agile Requirements Engineering (Agile RE) in the public sector in republican and constitutional monarchy nations. Additionally, it offers recommendations to address these challenges. Background: Failure of IT projects in the public sector results in financial losses for the state and loss of public trust, often attributed to issues in requirements engineering such as prioritization of user needs and excessive scope of requirements. IT projects can have a higher success rate with Agile RE, but there are also drawbacks. Therefore, this study holds significance by presenting a thorough framework designed to pinpoint and overcome the challenges associated with Agile RE to increase the success rate of IT projects. Methodology: This study employs a Systematic Literature Review (SLR) protocol in the field of software engineering or related domains, which consists of three main phases: planning the review, conducting the review with a snowballing approach, and reporting the review. Furthermore, the authors perform open coding to categorize challenges based on the Agile methodologies adoption factor model and axial coding to map potential solutions. Contribution: The authors assert that this research enriches the existing literature on Agile RE, specifically within the public sector context, by mapping out challenges and possible solutions that contribute to creating a foundation for future studies to conduct a more in-depth analysis of Agile adoption in the public sector. Furthermore, it compares the barriers of Agile RE in the public sector with the general context, leading to the discovery of new theories specifically for this field. Findings: Most challenges related to Agile RE in the public sector are found in the people and process aspects. Project and organizational-related are subsequent aspects. Therefore, handling people and processes proficiently is imperative within Agile RE to prevent project failure. Recommendations for Practitioners: Our findings offer a comprehensive view of Agile RE in the public sector in republican and constitutional monarchy nations. This study maps the challenges encountered by the public sector and provides potential solutions. The authors encourage practitioners to consider our findings as a foundation for adopting Agile methodology in the public sector. Furthermore, this study can assist practitioners in identifying existing barriers related to Agile RE, pinpointing elements that contribute to overcoming those challenges, and developing strategies based on the specific needs of the organizations. Recommendation for Researchers: Researchers have the potential to expand the scope of this study by conducting research in other countries, especially African countries, as this study has not yet encompassed this geographic region. Additionally, they can strengthen the evidence linking Agile RE challenges to the risk of Agile project failure by performing empirical validation in a specific country. Impact on Society: This research conducts a comprehensive exploration of Agile RE within the public sector, serving as a foundation for the successful adoption of Agile methodology by overcoming obstacles related to Agile RE. This study highlights the importance of managing people, processes, projects, and organizational elements to increase the success of Agile adoption in the public sector. Future Research: In the future, researchers should work towards resolving the limitations identified in this study. This study has not provided a clear prioritization of challenges and solutions according to their significance. Therefore, future researchers can perform a Fuzzy Analytical Hierarchical Process (F-AHP) to prioritize the proposed solutions.

show abstract

Section: Agile Requirements Engineeringmentioning

confidence: 99%

Section: Lack Of Communication With Stakeholders (C4)mentioning

confidence: 99%

Section: Lack Of Individual Commitment (C5)mentioning

confidence: 99%

Section: Lack Of Stakeholder Availability (C6)mentioning

confidence: 99%

See 2 more Smart Citations

Barriers of Agile Requirements Engineering in the Public Sector: A Systematic Literature Review

Tri Utami,

Raharjo,

Zharif Mustaqim

et al. 2024

IJIKM

View full text Add to dashboard Cite

show abstract

“…( 4) Mechanism to report underlying conflicts between different DMs: A conflict can be defined as when a significant difference is observed between the score of two DMs due to their different perspective and understanding of requirements. This conflict may impact the overall ranking of the vendors (Manata et al 2021;Mbanaso et al 2009;Nisyak et al 2020;Stingl and Geraldi 2017;Saaty 1983).…”

Section: Techniques For Vendor Selectionmentioning

confidence: 99%

A framework for software vendor selection by applying Inconsistency and Conflict Removal (ICR) method

Rani,

Mishra,

Omerovic

2023

Int J Syst Assur Eng Manag

View full text Add to dashboard Cite

In a software ecosystem, companies’ stakeholders make various decisions and perform various tasks to ensure the strategic and architectural goals of the company. Analyzing vendor capabilities and making decisions to select software vendors requires expert professionals. To analyze vendors’ capabilities and accessing them according to the company’s strategic and architectural goals is presently an ad-hoc and manual process. Presently, there is no systematic process for ‘vendor analysis and selection’ specifically for the software industry. Therefore, this study introduces a novel framework which elaborates all the tasks required for vendor proposal evaluation. It also includes the automatic detection of inconsistencies and conflicts prevalent during this process. A new method called ‘Inconsistency and Conflict Removal (ICR)’ is proposed as part of this framework. ICR automates the process of spotting inconsistencies and conflicts by taking scores of vendor capabilities as input reported by different decision-makers. Further, to illustrate this framework, ‘a case of Hospital’ has been considered. This study provides valuable knowledge that would facilitate organizations in software vendor selection. It will lead to substantial savings in terms of economics, such as actual costs, time, and improved administrative processes.

show abstract

A survey on security and human-related challenges in agile software deployment

Patel

Datta

2021

2021 International Conference on Computational Science and Computational Intelligence (CSCI)

View full text Add to dashboard Cite

Human Related Challenges in Agile Software Development of Government Outsourcing Project

Cited by 7 publications

References 30 publications

Barriers of Agile Requirements Engineering in the Public Sector: A Systematic Literature Review

Barriers of Agile Requirements Engineering in the Public Sector: A Systematic Literature Review

A framework for software vendor selection by applying Inconsistency and Conflict Removal (ICR) method

A survey on security and human-related challenges in agile software deployment

Contact Info

Product

Resources

About