Identification of criteria affecting software project monitoring task of Agile Kanban method

Alaidaros, Hamzah; Omar, Mazni; Romli, Rohaida

doi:10.1063/1.5055423

Cited by 10 publications

(19 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Currently, the Agile Kanban method has been well received and used for developing software projects among software development organizations (SDOs) [1]. This is because this method has greater consistency in managing software engineering (SE) projects [2]. The annual 'State of Agile' report shows that the adoption of the Agile Kanban method in SDOs has increased sharply from 39% to 65% in recent years [3], [4].…”

Section: Introductionmentioning

confidence: 99%

“…However, the progress monitoring task of the Agile Kanban method has significant lacks in terms of tracking, controlling, and visualizing the workflows' progress. This problem has negative impacts on software projects' success because the delays in project scheduling lead to late delivery [7], [8].…”

Section: Introductionmentioning

confidence: 99%

“…Agile Kanban method needs to be improved through three components that play crucial roles and impact the current issues of progress monitoring tasks [2]. The first component is to integrate Kanban method with earned value analysis (EVA) method to have an adequate technique for effective progress tracking.…”

Section: Introductionmentioning

confidence: 99%

“…The first component is to integrate Kanban method with earned value analysis (EVA) method to have an adequate technique for effective progress tracking. This is because Kanban method needs to be integrated with a complementary method to keep the project schedule progresses as it is planned [5], [7]. The second component is to generate the optimum work-inprogress (WIP) limits for each stage in Kanban board.…”

Section: Introductionmentioning

confidence: 99%

“…The third component is to visualize useful insights for the workflow to help project managers make meaningful decisions regarding the projects' progress. Nevertheless, Kanban board neither reports how much of work is left nor provides some indications of where the project ought to be [7], [10].…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

An Improved Software Project Monitoring Task Model of Agile Kanban Method: A Practitioners’ Perspective

Omar¹,

Alaidaros²,

Romli³

2020

Int. J. Adv. Sci. Eng. Inf. Technol.

Self Cite

View full text Add to dashboard Cite

Monitoring software project development is essential to ensure that the project progress is according to budget, schedule, and quality expectations. Currently, Agile Methods (AMs) have received wide recognition within the software engineering (SE) field due to their flexibility and effectiveness. One of the AMs methods used in managing software project development is Kanban method. This method is gaining attention due to its ability to enhance understanding, visibility, and controlling the project workflow. Thus, this paper aims to discuss the initial result of the proposed model for improving the software project monitoring task of the Agile Kanban method (i-KAM). To achieve this aim, the expert review method was used to ensure that suitable components and associated criteria have been included in i-KAM. In this study, six domain experts, which are software practitioners, have been identified based on predefined characteristics. The proposed model was verified based on five dimensions, which are understandability, relevance, feasibility, organization, and comprehensiveness. The experts' opinions and comments were obtained and subsequently quantified by using descriptive analysis. Findings revealed that this study has fulfilled its objective and has acquired constructive suggestions from the practitioners' perspective. Future work will continue to enhance i-KAM according to the recommendations and remarks from the experts. A focus group and case study methods could be conducted in order to validate the revised i-KAM. Besides, a prototype will be developed and then implemented within a real software development setting.

show abstract

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations