Enhancing Software Project Success : A Comparative Analysis of Scrum and Kanban in Agile Project Management.
Ferdous, Md Robayet; Ahammed, Md Riyaz (2025)
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2025061021971
https://urn.fi/URN:NBN:fi:amk-2025061021971
Tiivistelmä
The paper compares Scrum and Kanban Agile methodologies, explaining their usage, advantages and disadvantages in different software development settings. To see how the methods affect teamwork, speed of work, openness to change and company integration, semi-structured interviews were conducted using a qualitative approach.
According to what we’ve found, Scrum helps when requirements are stable and different roles belong to the same team, thanks to its defined roles, specific stages and everyday meetings. Regulations tend to make the system easier to predict and hold people responsible, but sometimes they cannot adapt to rapid changes. Kanban, however, relies on visualizing workflow and makes it easier to deliver continuously which is good for both unstable conditions and supporting organizations.
The research points out that leadership, how mature the team is and the company’s culture are all important when adopting Agile. If both management and employees are ready, cultural methods from the top and the bottom can be useful. Scrumban models which unite Scrum and Kanban, have become useful for teams that want to use both frameworks at once. The paper summarizes by telling practitioners that Agile adoption should involve choosing the best framework and making sure that it matches with the organization’s structure, promotes collaboration and encourages growth and autonomy.
According to what we’ve found, Scrum helps when requirements are stable and different roles belong to the same team, thanks to its defined roles, specific stages and everyday meetings. Regulations tend to make the system easier to predict and hold people responsible, but sometimes they cannot adapt to rapid changes. Kanban, however, relies on visualizing workflow and makes it easier to deliver continuously which is good for both unstable conditions and supporting organizations.
The research points out that leadership, how mature the team is and the company’s culture are all important when adopting Agile. If both management and employees are ready, cultural methods from the top and the bottom can be useful. Scrumban models which unite Scrum and Kanban, have become useful for teams that want to use both frameworks at once. The paper summarizes by telling practitioners that Agile adoption should involve choosing the best framework and making sure that it matches with the organization’s structure, promotes collaboration and encourages growth and autonomy.