A web-based Kanban application for enhancing agile project management practices Natalia Moiseienko 0 Mykhailo Moiseienko 0 Diana Lubentsova 0 Kryvyi Rih State Pedagogical University , 54 Universytetskyi Ave., Kryvyi Rih, 50086 , Ukraine 131 138

Agile project management has gained significant traction across various industries due to its ability to adapt to rapidly changing business environments. This paper presents an analysis of agile project management in the digital era, focusing on a comparative study of popular tools and methodologies. We examine the evolution of agile practices from their roots in software development to their application in diverse contexts. The study provides a comparison of Scrum and Kanban methodologies, highlighting their strengths, weaknesses, and suitability for diferent project types. Additionally, we analyze three prominent agile project management tools: Trello, Jira, and Worksection, evaluating their features, usability, and efectiveness in supporting agile practices. To further contribute to the field, we present the development and user evaluation of Kards, a web-based Kanban application designed to facilitate agile adoption.

 eol>Kards agile project management Scrum Kanban agile tools web-based Kanban application agile adoption agile methodologies project management organizational factors continuous improvement 1. Introduction

In recent years, agile project management methodologies have gained significant traction across various industries due to their ability to adapt to rapidly changing business environments and deliver value incrementally [ 1, 2 ]. As organizations increasingly embrace agile approaches, there is a growing need to understand the key concepts, tools, and practices that contribute to successful agile project management.

This research aims to provide an overview of agile project management, focusing on its evolution, comparison with traditional approaches, and application in diverse contexts. To further contribute to the understanding of agile project management, we present the development of a web-based Kanban application designed to facilitate the adoption of agile practices in various project contexts. Additionally, this study undertakes a comparative analysis of two prominent agile methodologies, Scrum and Kanban, to assess their suitability for diferent project types and organizational contexts [ 3 ].

2. Literature review

Agile project management has its roots in the software development industry, where the need for lfexibility and adaptability in the face of rapidly changing requirements led to the creation of the Agile Manifesto in 2001 [ 4 ]. The manifesto outlines four core values and twelve principles that prioritize individuals and interactions, working software, customer collaboration, and responding to change [ 5 ]. These values and principles have since been adopted and adapted across various industries, leading to the development of numerous agile methodologies, such as Scrum, Kanban, and Extreme Programming (XP) [ 6 ].

Agile project management difers significantly from traditional, plan-driven approaches, such as the Waterfall model. While traditional project management emphasizes extensive upfront planning, documentation, and sequential execution of phases, agile methodologies focus on iterative and incremental delivery, cross-functional collaboration, and continuous improvement [ 7 ]. Agile teams work in short iterations, typically lasting 2-4 weeks, allowing for regular feedback and adaptation based on customer input and changing requirements [ 8 ]. This approach enables organizations to deliver value faster, reduce risks, and respond more efectively to market dynamics compared to traditional project management methods.

While agile project management originated in the software development domain, its principles and practices have been successfully applied across various industries, including construction, manufacturing, and services [ 2, 9 ]. However, the adoption of agile in non-software contexts presents unique challenges, such as adapting to physical constraints, regulatory requirements, and entrenched organizational cultures [ 10 ].

Despite these challenges, organizations in diverse industries have reported significant benefits from adopting agile practices. These benefits include increased customer satisfaction, faster time-to-market, improved team morale and productivity, and enhanced ability to manage changing priorities [ 3, 11 ]. For example, in the construction industry, agile practices have been found to improve communication, collaboration, and problem-solving among project stakeholders, leading to reduced waste and increased eficiency [ 12 ].

However, the successful adoption of agile in diferent industries requires a tailored approach that considers the specific characteristics and constraints of each context. Organizations need to invest in training, coaching, and change management eforts to support the transition to agile ways of working and overcome cultural and organizational barriers [ 13 ].

3. Comparative analysis of Scrum and Kanban methodologies

Scrum and Kanban are two of the most widely adopted agile project management methodologies.

Scrum is an iterative and incremental agile framework that focuses on delivering value through time-boxed iterations called sprints [ 14 ]. It emphasizes cross-functional teams, regular meetings (e.g., daily stand-ups, sprint planning, and retrospectives), and the use of artifacts such as product backlogs and burn-down charts to track progress.

Kanban is a lean-inspired agile methodology that focuses on visualizing workflow, limiting work-inprogress (WIP), and continuously improving the process [ 6 ]. It uses a Kanban board to represent the project workflow, with columns depicting the various stages of work and cards representing individual tasks.

Table 1 summarizes the key characteristics, advantages, and disadvantages of Scrum and Kanban methodologies.

The choice between Scrum and Kanban depends on various factors such as project size, complexity, team composition, and organizational culture [ 4 ]. Scrum is often more suitable for projects with welldefined requirements, fixed budgets and timelines, and cross-functional teams. Its structured approach and regular delivery cadence make it a good fit for projects that require predictability and frequent stakeholder engagement.

Kanban, on the other hand, is more suitable for projects with evolving requirements, frequent changes, and a need for flexibility. Its focus on continuous flow and improvement makes it a good choice for projects with a high degree of uncertainty or variability, such as maintenance and support work or creative endeavours.

Both Scrum and Kanban can lead to improved project outcomes, such as increased productivity, quality, and customer satisfaction when implemented properly [ 15 ]. The success of either methodology depends on factors such as team buy-in, management support, and the ability to adapt the practices to the specific project context [ 16 ]. Hybrid approaches that combine elements of both Scrum and Kanban (e.g., Scrumban) can be efective in certain situations, such as projects with a mix of planned and unplanned work [ 17 ]. The efectiveness of Scrum and Kanban can be enhanced by complementary practices such as continuous integration, automated testing, and regular retrospectives [ 18 ].

4. Analysis of agile project management tools

Agile project management tools play a crucial role in supporting the implementation and execution of agile practices.

Trello is a web-based, Kanban-style project management tool that ofers a simple and intuitive interface for organizing and tracking tasks [ 19 ]. It uses boards, lists, and cards to represent projects, stages, and tasks, respectively, allowing teams to collaborate and visualize their workflow easily.

Jira is a powerful and flexible agile project management tool developed by Atlassian, widely used in software development and other industries [ 13 ]. It supports various agile methodologies, including Scrum and Kanban, and ofers extensive features for issue tracking, reporting, and integration with other tools.

Worksection is a cloud-based project management tool that combines agile and traditional project management features, making it suitable for a wide range of projects and industries. It ofers Kanban boards, Gantt charts, and resource management functionalities, among other features.

Table 2 summarizes the key features, strengths, and weaknesses of Trello, Jira, and Worksection.

The choice of an agile project management tool depends on various factors, such as project complexity, team size, industry, and organizational maturity. Trello is well-suited for small to medium-sized projects and teams that value simplicity and ease of use. Its visual and intuitive interface makes it ideal for teams new to agile or those working on relatively straightforward projects [ 19 ].

Jira, on the other hand, is a more powerful and feature-rich tool that caters to the needs of large and complex projects, particularly in software development and IT [ 13 ]. Its extensive customization options and integrations make it suitable for organizations with mature agile practices and those requiring advanced reporting and analytics capabilities.

Worksection strikes a balance between simplicity and functionality, making it a good choice for organizations transitioning from traditional to agile project management or those working on diverse projects across diferent industries. Its combination of Kanban boards, Gantt charts, and resource management features enables teams to adapt their processes based on project requirements and organizational constraints.

Ultimately, the success of an agile project management tool depends on how well it aligns with the organization’s culture, goals, and processes. Organizations should carefully evaluate their needs and constraints before selecting a tool and ensure that adequate training and support are provided to facilitate its adoption and efective use.

Strengths Weaknesses

- Limited reporting - Simple and intuitive interface and analytics - Easy to learn and use - Lack of advanced - Flexible and customizable features for complex

projects - Powerful and feature-rich - Steep learning curve - Suitable for large and complex - Can be overwhelming projects for small teams - Highly customizable and - Higher cost compared extensible to other tools - Combines agile and traditional - Less extensive features integrations compared - Suitable for a wide range of to Jira projects - Limited customization - Afordable pricing plans options

 5. Development of the web-based Kanban application

To further support the adoption of agile project management practices, a web-based Kanban application, named “Kards”, was developed as part of this research (figure 1).

Kards aims to provide a simple and accessible tool for individuals and teams to manage their projects using the Kanban methodology. The application targets a wide range of users, including software development teams, small businesses, and individuals seeking to adopt agile practices for personal project management [ 20 ].

Kards ofers a set of core features and functionalities designed to support the efective implementation of Kanban principles, as summarized in table 3.

The development of Kards followed an iterative and user-centred design process involving close collaboration between the development team and potential users. Key stages of the process included: 1. Conducting user interviews and surveys to identify pain points and desired features. 2. Creating low-fidelity wireframes and interactive prototypes to visualize the application’s layout and functionality. 3. Developing a clean and intuitive user interface, following best practices for usability and accessibility. 4. Implementing the application using modern web technologies, such as HTML, CSS, and JavaScript, and integrating with a back-end API for data storage and retrieval. 5. Conducting usability tests with representative users to gather feedback and identify areas for improvement [ 21 ].

To assess the usability and efectiveness of Kards, a user study was conducted with 20 participants from various backgrounds. Participants were asked to complete a set of tasks using the application and provide feedback through a questionnaire and semi-structured interviews.

The results of the user study indicated that Kards was perceived as highly usable and efective in supporting Kanban-based project management. Participants highlighted the application’s intuitive interface, ease of use, and valuable features such as WIP limits and analytics. Some areas for improvement were also identified, such as the need for more advanced filtering options and better onboarding for new users.

The findings suggest that Kards has the potential to facilitate the adoption of agile project management practices, particularly among teams and individuals new to Kanban. By providing a simple and accessible tool, Kards can help organizations overcome some of the barriers to agile adoption and realize the benefits of increased transparency, collaboration, and continuous improvement in their project management eforts.

 6. Implications for agile project management practice

The comparative analysis of agile tools (Trello, Jira, and Worksection) and methodologies (Scrum and Kanban) highlights several important lessons for practitioners: 1. The choice of agile tools and methodologies should be based on a thorough understanding of project characteristics, team dynamics, and organizational culture [ 4 ]. 2. Agile tools and methodologies are not one-size-fits-all solutions; their efectiveness depends on how well they are adapted to the specific project context [ 16 ]. 3. The success of agile practices relies heavily on factors such as team collaboration, communication, and continuous improvement, which should be actively fostered and supported [ 15 ]. 4. Hybrid approaches that combine elements of diferent agile methodologies can be efective in addressing the limitations of individual approaches and tailoring the process to the project needs [ 17 ].

Based on the lessons learned, the following recommendations can guide practitioners in selecting and implementing agile approaches: 1. Carefully consider factors such as project size, complexity, team composition, and organizational culture when selecting agile tools and methodologies [ 9 ]. 2. Begin with a pilot project or a small-scale implementation to gain experience and gather feedback before scaling agile practices to larger initiatives [ 22 ]. 3. Provide adequate training and ongoing coaching to help team members understand and apply agile principles and practices efectively [ 13 ]. 4. Encourage open communication, regular feedback, and a focus on learning and adapting throughout the project lifecycle [ 7 ]. 5. Tailor agile practices to the specific needs of the project and the organization, and be willing to adjust the approach based on lessons learned and changing circumstances [ 2 ].

The Kards Kanban application, developed as part of this research, has the potential to contribute to the adoption and efectiveness of agile project management practices in several ways: 1. Lowering barriers to entry – by providing a simple, intuitive, and accessible tool for implementing Kanban, Kards can help teams and individuals new to agile overcome the initial hurdles and start realizing the benefits of visual workflow management [ 20 ]. 2. Facilitating collaboration and transparency – the real-time updates, notifications, and commenting features of Kards can enhance team collaboration and provide greater visibility into project progress, fostering a culture of transparency and accountability [ 21 ]. 3. Supporting continuous improvement – the analytics and reporting capabilities of Kards can help teams track key metrics, identify bottlenecks, and make data-driven decisions to optimize their processes and improve performance over time [ 23 ]. 4. Promoting agile best practices – by incorporating features such as WIP limits and visual workflow management, Kards can help teams adopt and adhere to agile best practices, even if they are not fully familiar with the underlying principles [ 24 ].

As more teams and organizations adopt tools like Kards, the collective experience and lessons learned can contribute to the growing body of knowledge on agile project management, leading to the refinement of practices and the development of new approaches tailored to the evolving needs of projects and organizations.

 7. Conclusion

This paper has explored the concepts, challenges, and solutions related to agile project management through a comprehensive literature review, an analysis of agile tools and methodologies, and the development of a web-based Kanban application. The study has yielded several key findings and contributions that have implications for both researchers and practitioners in the field.

The literature review has highlighted the core principles and benefits of agile project management, as well as the challenges and barriers to its adoption in various industries. The comparative analysis of agile tools (Trello, Jira, and Worksection) and methodologies (Scrum and Kanban) has provided insights into their strengths, weaknesses, and suitability for diferent project contexts. The development and evaluation of the Kards Kanban application have demonstrated the potential of tailored agile tools to support and enhance agile practices in real-world settings.

However, this study has some limitations that should be acknowledged. First, the literature review captured only studies in the 5-year timeframe, from 2020 to 2024. Second, the analysis of agile tools and methodologies was based on a limited set of popular approaches and may not reflect the full diversity of agile practices. Third, the evaluation of the Kards application was conducted with a relatively small sample of users (bachelor students majoring in Programming) and may not be generalizable to all project contexts.

Declaration on Generative AI: During the preparation of this work, the authors used Claude 3 Opus in order to: Drafting content, Generate literature review. After using this service, the authors reviewed and edited the content as needed and takes full responsibility for the publication’s content.

 [1] P. V. Zahorodko , Overview of Agile frameworks in Computer Science education , Educational Dimension 9 ( 2023 ) 206 - 214 . doi: 10 .31812/ed.645. [2] F. Pinciroli , Selection of agile project management approaches based on project complexity , Journal of Software: Evolution and Process ( 2024 ). doi: 10 .1002/smr.2716. [3] S. Yongliang , C. P. Y. Sharon , Exploring the impact of agile project management practices on supply chain resilience and sustainability: A case study of the manufacturing industry , Journal of Modern Project Management 10 ( 2022 ) 300 - 319 . doi: 10 .19255/JMPM029020. [4] A. Agbejule , L. Lehtineva, The relationship between traditional project management, agile project management and teamwork quality on project success , International Journal of Organizational Analysis 30 ( 2022 ) 124 - 136 . doi: 10 .1108/IJOA-02-2022-3149. [5] T. Dingsøyr , Y. Petit , Managing layers of risk: Uncertainty in large development programs combining agile software development and traditional project management , in: Project Risk Management: Managing Software Development Risk , De Gruyter, 2021 , pp. 75 - 96 . doi: 10 .1515/ 9783110652321 - 005 . [6] M. L. Drury-Grogan , The Changes in Team Cognition and Cognitive Artifact Use During Agile Software Development Project Management, Project Management Journal 52 ( 2021 ) 127 - 145 . doi: 10 .1177/8756972820960301. [7] A. Cruz , A. Tereso , A. C. Alves , Traditional, agile and lean project management: A systematic literature review , Journal of Modern Project Management 8 ( 2020 ) 86 - 95 . doi: 10 .19255/JMPM02407. [8] T. Thesing , C. Feldmann , M. Burchardt , Agile versus Waterfall Project Management: Decision model for selecting the appropriate approach to a project , Procedia Computer Science 181 ( 2021 ) 746 - 756 . doi: 10 .1016/j.procs. 2021 . 01 .227. [9] T. Žužek , Ž. Gosar, J. Kušar , T. Berlec, Adopting agile project management practices in nonsoftware SMEs: A case study of a Slovenian medium-sized manufacturing company , Sustainability 12 ( 2020 ) 9245 . doi: 10 .3390/su12219245. [10] E. Sońta-Drączkowska , A. Krogulec , Challenges of scaling agile in large enterprises and implications for project management , International Journal of Managing Projects in Business 17 ( 2024 ) 360 - 384 . doi: 10 .1108/IJMPB-11-2023-0244. [11] R. Kurniawan , D. Budiastuti , M. Hamsal , W. Kosasih, The impact of balanced agile project management on firm performance: the mediating role of market orientation and strategic agility , Review of International Business and Strategy 30 ( 2020 ) 457 - 490 . doi: 10 .1108/RIBS-03-2020-0022. [12] S. Chathuranga , S. Jayasinghe , J. Antucheviciene , R. Wickramarachchi , N. Udayanga , W. A. S. Weerakkody , Practices Driving the Adoption of Agile Project Management Methodologies in the Design Stage of Building Construction Projects , Buildings 13 ( 2023 ). doi: 10 .3390/buildings13041079. [13] M. Hamsal , M. Ichsan , A. R. Utomo , A. A. Fahira , R. E. Wetik , The Relationship Analysis Between Knowledge & Skills, Organizational Drivers, and Perceived Success in Implementation of Agile Project Management: Case Study of PT XYZ , International Journal of Operations and Quantitative Management 27 ( 2021 ) 111 - 126 . doi: 10 .46970/ 2021 .27. 2 .2. [14] P. Raj , P. Sinha , Project management in era of Agile and DevOps methodlogies , International Journal of Scientific and Technology Research 9 ( 2020 ) 1024 - 1033 . [15] V. M. B. Garcia , C. D. P. Martens , R. B. Carvalho , M. L. Martens , Contributions of entrepreneurial orientation in the use of agile methods in project management , Innovation and Management Review 18 ( 2021 ) 17 - 33 . doi: 10 .1108/INMR-01-2019-0002. [16] E. Zavyalova , D. Sokolov , A. Lisovskaya , Agile vs traditional project management approaches: Comparing human resource management architectures , International Journal of Organizational Analysis 28 ( 2020 ) 1095 - 1112 . doi: 10 .1108/IJOA-08-2019- 1857 . [17] S. H. Kim , C. I. Song , K. H. Yang , Big data project management by agile approach: In the case of the Seoul Metropolitan City Owl Bus , International Journal of Services and Operations Management 39 ( 2021 ) 316 - 336 . doi: 10 .1504/IJSOM. 2021 . 116103 . [18] A. Mas , A.-L. Mesquida , M. Pacheco, Supporting the deployment of ISO-based project management processes with agile metrics , Computer Standards and Interfaces 70 ( 2020 ). doi: 10 .1016/j.csi. 2019 . 103405 . [19] E. Weflen , C. A. MacKenzie , I. V. Rivero , An influence diagram approach to automating lead time estimation in Agile Kanban project management , Expert Systems with Applications 187 ( 2022 ). doi: 10 .1016/j.eswa. 2021 . 115866 . [20] K. I. Jaafreh , M. M. Abu-Jalil , The impact of adopting project management pillars (agile) on the success of marketing entrepreneurial products in Jordan , Jordan Journal of Business Administration 16 ( 2020 ) 237 - 257 . [21] N. H. M. Ali , F. Ahmad , N. I. Abidin , S. Suhaili , M. A. A. Rahman , H. Harun , M. Awang , N. H. A. Hamid , M. K. Musa , N. Hamidon , F. M. Yusop , M. M. Syafiq Syazwan , Agile Project Management Software for Construction and Management Industries , in: M. A. A. Zaini , M. Jusoh , N. Othman (Eds.), Proceedings of the 3rd International Conference on Separation Technology, Lecture Notes in Mechanical Engineering , Springer Singapore, Singapore, 2021 , pp. 101 - 111 . doi: 10 .1007/ 978 -981-16-0742- 4 _ 7 . [22] C. Noteboom , M. Ofori , K. Sutrave , O. El-Gayar , Agile project management: A systematic literature review of adoption drivers and critical success factors , in: B. T .X. (Ed.), Proceedings of the Annual Hawaii International Conference on System Sciences, volume 2020-January , IEEE Computer Society, 2021 , pp. 6775 - 6784 . [23] B. Marder , P. Ferguson , C. Marchant , M. Brennan , C. Hedler , M. Rossi , S. Black , R. Doig, ' Going agile': Exploring the use of project management tools in fostering psychological safety in group work within management discipline courses , International Journal of Management Education 19 ( 2021 ). doi: 10 .1016/j.ijme. 2021 . 100519 . [24] L. Mayo-Alvarez , S. Del-Aguila-Arcentales , A. Alvarez-Risco , M. Chandra Sekar , N. M. Davies , J. A. Yáñez , Innovation by integration of Drum-Bufer-Rope (DBR) method with Scrum-Kanban and use of Monte Carlo simulation for maximizing throughput in agile project management , Journal of Open Innovation: Technology, Market, and Complexity 10 ( 2024 ). doi: 10 .1016/j.joitmc. 2024 . 100228 .