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, 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 of Agile Mindset, activities for development and future directions of research
2
Dostęp do pełnego tekstu na zewnętrznej witrynie WWW
Among the Agile methods, Scrum and Kanban are common in software development and they are considered the two most powerful ones influencing the direct results of projects. Despite the importance of knowing their relative strengths and advantages and integrating them that can yield 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 together by comparing or integrating them. Our final set includes 38 empiric-based studies posing primary information on 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, the properties of transitions from one to another such as transition directions (such as Scrum to Kanban, Kanban to Scrum or Scrum/Kanban to Hybrid), transition years, and transition reasons. The outputs can be interesting for both the industry and researchers. For example, nearly all of my transitioning organizations are moving from Scrum to Kanban or to a 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 the both use flow instead of sprint.
3
Dostęp do pełnego tekstu na zewnętrznej witrynie WWW
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.
4
Dostęp do pełnego tekstu na zewnętrznej witrynie WWW
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.
JavaScript jest wyłączony w Twojej przeglądarce internetowej. Włącz go, a następnie odśwież stronę, aby móc w pełni z niej korzystać.