Abstract The success of agile work heavily depends on people and their approach to challenges, with the agile mindset emerging as a pivotal driver. Despite its importance, Information Systems (IS) research lacks a systematic overview of the contexts where the agile mindset is relevant and the research gaps that remain. This study addresses this gap by systematically examining the factors influencing and resulting from the agile mindset in IS contexts and, for the first time, demonstrating its broad relevance across diverse IS domains. We conducted a systematic literature review, analyzing 62 relevant papers from IS research. Our findings show that the agile mindset plays a central role in four key areas: (1) implementing agile methods or scaled agile frameworks during agile transformations, (2) applying digital tools and driving digital transformation, (3) supporting coaching, training, and education, and (4) leadership and management. This study’s originality lies in highlighting the agile mindset’s wide-ranging applicability, offering practitioners actionable insights for designing processes and mechanisms to enhance the success of agile work in IS. Additionally, researchers are provided with a roadmap of open questions and future research opportunities to deepen our understanding of this critical concept in IS contexts.

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.

Starting from software development, Agile approaches are spreading across a broad range of industries and functions, with many great challenges.Mindset, as one of the crucial human factors of individuals in Agile, influences people's decision-making and affects every aspect of behavior and action.However, many organizations and teams face big challenges in achieving an Agile Mindset of their individuals.In addition to an often-unclear understanding of the Agile Mindset, various aspects of it such as success factors and indications are largely unknown, which makes it extremely difficult to establish an Agile Mindset.Motivated by this, our study aims to conduct a literature review by answering comprehensive research questions related to the Agile Mindset regarding publication demographics, importance, definitions, characteristics, elements, critical success factors, indicators, activities for development of Agile Mindset, and future directions of 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.

Software development with its unique characteristics having knowledge-intensive and human-oriented aspects and complex domains, challenges organizations. The timely outcomes with high quality and desired cost that directly affect customer satisfaction have an important place in many organizations, including banks. In the last decade, as an emerging technique for business processes management, process mining has been applied in many domains, including manufacturing, supply chain, government, healthcare, and software engineering. There are limited number of studies on process mining techniques carried out for the software process, especially in the banking sector. A lack of tool infrastructure enabling to run the entire software development process and the challenges in integrating processed data from separated varying tools and assets complicate the use of process mining for software processes. This paper aims to identify the improvement points in the software development process of the Kuveyt Turk Participation Bank in Turkey through the surfacing actions. The findings and results are gathered by the application of process mining techniques of bupaR, and evaluation is provided by experts in the bank. After that, the relevant process improvements are identified. The results of this paper show that using process mining provides the organization with beneficial results, in particular, and a comprehensive view of the end-to-end Software Development Life Cycle (SDLC) processes.

The right way to agility should start with a proper agile mindset instead of applying Agile methods directly.However, apart from the manifesto, it is unlikely to find a comprehensive set of Agile principles that can serve for an improved agile mindset.Our study intends to fulfill this gap in a systematic way: providing a list of the Agile methods along with their principles within a single source, in the way of providing a better understanding of the concept of agility from a wide and exhaustive perspective.To do so, the collected 105 principles were content-analyzed in order to group them into 32 categories for a higher-level abstraction.These categories then were subsumed into two main categories.The whole grouping process was reviewed by one expert and the list was adjusted accordingly.Then, based on the consolidated list of the categorized principles, analysis and evaluations were made by the authors.As a part of the evaluations, semi-structured interviews with two experts were conducted to evaluate the categorized principles in general, especially in terms of their contribution to agility.

Information Technology (IT) is a complex domain.In order to properly manage IT related processes, several frameworks including ITIL (Information Technologies Infrastructure Library), COBIT (Control OBjectives for Information and related Technologies), IT Service CMMI (IT Service Capability Maturity Model) and many others have emerged in recent decades.Meanwhile, the prevalence of Agile methods has increased, posing the coexistence of Agile approach with different IT frameworks already adopted in organizations.More specifically, the pursuit of being agile in the area of digitalization pushes organizations to go for agile transformation while preserving full compliance to IT frameworks for the sake of their survival.The necessity for this coexistence, however, brings its own challenges and solutions for harmonizing the requirements of both parties.In this paper, we focus on harmonizing the requirements of COBIT and Scrum in a same organization, which is especially challenging when a full compliance to COBIT is expected.Therefore, this study aims to identifying the challenges of and possible solutions for the coexistence of Scrum and COBIT (version 4.1 in this case) in an organization, by considering two case studies: one from the literature and the case of Akbank delivered in this study.Thus, it extends the corresponding previous case study from two points: adds one more case study to enrich the results from the previous case study and provides more opportunity to make generalization by considering two independent cases.

Today's turbulent business environment is compelling software development providers to face several challenges. As a response to this case, adoption of SCRUM methods is increasing. COBIT, on the other side, has domination in information technology (IT) and is a de-facto standard providing an IT governance model with international set of generally accepted IT control objectives. Considered the coverage of SCRUM and COBIT (version 4.1 in this case), a coexistence of them in a same organization has a possibility of emergence for organizations that want to use SCRUM in their COBIT environments. While a rationalized, engineering-based approach has dominated software development almost since its inception and has a co-occurrence and similarities with COBIT, melting COBIT and SCRUM in an organization is very new and can be an intriguing subject. This study holds the aim of shedding light on organizations by focusing on the identification of risks, challenges and issues of SCRUM implementation within a COBIT environment. This study works as a risk map for organizations that have opportunity to tailor COBIT. It also exhibits a list of challenges for organizations that must fully comply with COBIT framework.