Abstract Agile software development has reached wide adoption in various countries including Turkey, even though from which its original cultural backgrounds differ. In Turkey, many organizations have started to adopt Agile approaches more and more in their software development processes. This interest in the country's software development is parallel to what the academic literature on Agile in the country exhibits. However, despite the prevalence of Agile in Turkey, there is a lack of sufficient secondary research and comprehensive review on Agile in Turkey, which poses a significant necessity for further investigation. Considering this gap, we performed a quantitative bibliometric analysis of Agile software development publications produced by Turkish organizations in a holistic and broad approach both for scholars and practitioners. We provide a summary of relevant academic studies that emerged in Agile research in Turkey by focusing on many aspects including bibliometric properties of papers, researchers, affiliations, venues, and thematic contents that are separated into 15 sub‐research questions. After delivering results based on the questions, we discuss the results and findings of our study and present implications regarding the findings. The main contributions of our work are twofold. First, the paper may help the readers to have a quick idea, understand the subject, and gain insight from a large volume of scientific data. Second, the paper can help readers to use these analyses to form future research.

Abstract4Among the Agile methods, Scrum and Kanban are widely used in software development and they are considered the two most effective ones influencing the direct results of projects.Despite the importance of knowing their relative strengths and advantages and integrating them to achieve better results than individual use, none of the secondary studies provide extensive knowledge on the topic.In this paper, we performed a Systematic Literature Review (SLR) study to investigate the characteristics of the empirical studies which involve Scrum and Kanban by comparing or integrating them.Our final set includes 38 studies posing primary information on the advantages of each method over another one, the properties including artifacts, roles, and events from Scrum and Kanban in combining them in a hybrid way, and the properties of transitions from one to another such as transition directions (Scrum to Kanban, Kanban to Scrum or Scrum/Kanban to Hybrid), transition years, and transition reasons.The outputs can be interesting for both industry and researchers.For example, nearly all of the transitioning organizations are moving from Scrum to Kanban or to hybrid method.Among the reasons for the transitions, the problems experienced with Scrum are remarkable.In comparison, Kanban stands out clearly in a positive way.Almost all of the teams combining both use flow instead of a sprint.