A Systematic Mapping Study on Scrum and Kanban in Software Development
Hossain, Arif (2023)
2023
Julkaisu on tekijänoikeussäännösten alainen. Teosta voi lukea ja tulostaa henkilökohtaista käyttöä varten. Käyttö kaupallisiin tarkoituksiin on kielletty.
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi-fe2023060552468
https://urn.fi/URN:NBN:fi-fe2023060552468
Tiivistelmä
Background: Agile methodologies, such as Scrum and Kanban, have gained significant popularity in software development organizations. However, there is a need to compare and contrast these methodologies to determine their effectiveness and suitability in specific conditions.
Objective: The objective of this systematic mapping study is to compare Scrum and Kanban in software development organizations and identify their methodological differences, benefits, drawbacks, and current/future trends.
Method: A comprehensive literature review was conducted, analyzing 47 primary studies. Data synthesis and analysis were performed to extract relevant information on the characteristics of Scrum and Kanban.
Results: The study identified several methodological differences between Scrum and Kanban, highlighting their unique characteristics and implementation considerations. The study presents a detailed breakdown of the reported differences, benefits, drawbacks, and trends associated with these methodologies.
Conclusions: Choosing between Scrum and Kanban depends on the specific needs, context, and goals of the organization. Scrum excels in areas such as path clarity, delivery time, and teamwork, while Kanban offers advantages in flexibility, easy transition, and focus on work. The findings emphasize the importance of understanding requirements, team dynamics, project characteristics, and customer expectations when selecting an agile methodology. This systematic mapping study contributes to the understanding of Scrum and Kanban in software development organizations. By considering the findings, organizations can make informed decisions and optimize their agile practices to enhance productivity, efficiency, and quality in software development projects.
Objective: The objective of this systematic mapping study is to compare Scrum and Kanban in software development organizations and identify their methodological differences, benefits, drawbacks, and current/future trends.
Method: A comprehensive literature review was conducted, analyzing 47 primary studies. Data synthesis and analysis were performed to extract relevant information on the characteristics of Scrum and Kanban.
Results: The study identified several methodological differences between Scrum and Kanban, highlighting their unique characteristics and implementation considerations. The study presents a detailed breakdown of the reported differences, benefits, drawbacks, and trends associated with these methodologies.
Conclusions: Choosing between Scrum and Kanban depends on the specific needs, context, and goals of the organization. Scrum excels in areas such as path clarity, delivery time, and teamwork, while Kanban offers advantages in flexibility, easy transition, and focus on work. The findings emphasize the importance of understanding requirements, team dynamics, project characteristics, and customer expectations when selecting an agile methodology. This systematic mapping study contributes to the understanding of Scrum and Kanban in software development organizations. By considering the findings, organizations can make informed decisions and optimize their agile practices to enhance productivity, efficiency, and quality in software development projects.