Search results

“Agile management” refers to a set of management goals, principles, values and practices that emerged to speed up software. Now its tools and culture are spreading to all kinds of organizations throughout the world—from R&D to top management teams. As some corporations race to become “agile” they can lose sight of the essential ideas and practices of Agile methodology

In September 2016, a group of large firms came together in New York to see whether they could agree on what Agile stood for in their own organizations. They aspired to create workplaces that draw on everyone’s creative talents and kindle everyone’s potential in workplaces that respect individuals and are highly productive and profitable. The firms involved were members of the SD Learning Consortium (SDLC)—a non-profit corporation.

As it is being adopted in a wide variety of corporate settings since 2001, the core concept of Agile has evolved.

To be fully entrepreneurial, the whole organization needs to embrace the Agile mindset and function as an interactive network, not a top-down bureaucracy with just a few teams implementing Agile tools and processes.

As Agile is being increasingly adopted by all corporate functions and levels of management it is essential to focus the whole organization on creating value for the customer.

Numerous approaches from the field of economics already exist for the improvement of business processes. In the field of software development, work has been done on improving development processes. For years, the focus here has been on agile approaches. Although various approaches for improving business processes exist, it is becoming increasingly difficult to adapt business processes to the fast-moving conditions of the market and the business environment. Agile approaches address this issue. Thus, not only software development processes, but also business processes should benefit from agile approaches.

To this end, values and principles of the Agile Manifesto, agile methods such as Scrum, and various agile practices such as the Kanban board should be applied in business processes. This paper examines the work already done on this topic. With the help of a systematic literature review (SLR), literature studies dealing with the implementation of the agile approach in business processes are identified.

This paper presents, investigates and contrasts 12 primary sources dealing with agile and business processes and shows how they are different/ equal regarding three research questions.

We provide an overview of existing approaches handling the combination of agile and business processes to improve business processes.

The application of agility principles and methodologies on Enterprise Architecture (EA) is a promising field. This paper aims to provide an in-depth study of the Agile Enterprise Architecture (AEA) by studying EA practitioners’ perspectives to propose a foundational framework for AEA.

The authors formulate a foundational framework that defines the AEA motivators, enablers and blockers using the agile manifesto as one of the AEA enablers where a total of 156 EA stakeholders with at least one year of experience in enterprise architecture were surveyed, and a set of hypotheses was analyzed and tested based on the proposed framework. The authors also develop a quantitative method to evaluate the agility index of the EA based on the introduced framework.

The research results show with significance that enterprise architects perceive positively the application of the agility methodologies on the enterprise architecture. This perception is primarily affected by the enterprise size, the EA dependency and the agile methodologies awareness. The findings also indicate that AEA is primarily motivated by the Business and IT Change Ready and Responsive EA. Finally, an EA Agility Index (EAAI) was designed to assess the agility application of the EA based on the three forces, i.e. motivators, enablers and blockers.

Because of the chosen research approach and the sample size, the research results may lack generalizability. Also, EAAI designed was not thoroughly tested.

The paper includes implications for the design and development of an EA Agility Index, and the need to increase the awareness of the agility methodologies to overcome the blocker of the unfamiliarity with the agile methodologies implying that the current business models in enterprise must be more aligned with the agile methodologies.

While there are efforts to develop AEA frameworks, one of the major findings of the literature review conducted is that there is evident research gap in the literature on the perception and associated factors of the EA stakeholders on having an agile enterprise architecture. This paper attempts to fill this gap.

Agile principles have been widely used in software development team practice since the creation of the Agile Manifesto. Studies have examined variables related to agile principles without systematically considering the relationships among key team, agile methodology, and process variables underlying the agile principles and how these variables jointly influence the achievement of software development agility. In this study, the authors tested a team/methodology–process–agility model that links team variables (team autonomy and team competence) and methodological variable (iterative development) to process variables (communication and collaborative decision-making), which are in turn linked to software development agility (ability to sense, respond and learn).

Survey data from one hundred and sixty software development professionals were analyzed using structural equation modeling methods.

The results support the team/methodology–process–agility model. Process variables (communication and collaborative decision-making) mediated the effects of team (autonomy and competence) and methodological (iterative development) variables on software development agility. In addition, team, methodology and process variables had different effects on the three dimensions of software development agility.

The results contribute to the literature on organizational IT management by establishing a team/methodology–process–agility model that can serve as a basis for developing a core theoretical foundation underlying agile principles and practices. The results also have practical implications for organizations in understanding and managing holistically the different roles that agile methodological, team and process factors play in achieving software development agility.

By learning how to overcome implementation challenges, the Agile methodology can enable organizations to cope with the 21st Century marketplace and deliver what customers expect and demand: easy, quick, convenient, personalized responsiveness at scale.”

The 10 major implementation challenges are addressed.

Agile offers a methodology that can improve the chances of building a new product or service that people will actually buy, use and like.

A key Agile principle – doing work in small iterative cycles with customer feedback at the end of each cycle – is a transformative idea.

The author has recently made on-site visits to leading corporations that have adopted Agile. The “Agile” managers he met recognize that the future of their firm depends on inspiring those doing the work to accelerate innovation and add genuine value to customer, that enhancing that capacity depends on giving autonomy to self-organizing teams within broad parameters of control.

This study aims to examine the relationship between the agile way of working and team performance and engagement. Furthermore, psychological safety climate was investigated as a mediator of this relationship. As organizations are increasingly adopting the agile way of working method beyond the information technology (IT) setting, the authors researched its effects in teams across a variety of functional domains.

Survey data was collected from 97 agile teams working in various functional domains in a multinational bank. The data was analyzed using structural equation modeling.

Results indicated that the agile way of working is directly and positively related to team engagement and performance. Moreover, psychological safety climate acted as a partial mediator of each of the respective outcomes.

This study illustrated that the agile way of working is beneficial for teams beyond the IT setting, as it is positively associated with psychological safety climate, engagement and performance across functional domains.

The purpose of this paper is to demonstrate how agile project management can foster creativity in project teams.

The study is based on an extensive literature review of agile project management and team creativity and is matching these two to answer the following research questions: (1) how agile project management approach can foster creativity in project teams? and (2) which principles and practices promoted by the most popular agile methodologies enhance creativity in project teams?

Five creativity-conducive spaces in agile project management were identified and integrated into a conceptual framework, namely, a space for generative social interactions, a space for learning, a space for change and adaptation, a space for exploration and a space promoting team members' well-being. In the next step, based on a thorough analysis of seven widespread agile project management methods, a large number of agile principles and practices were mapped into each of the five conceptual spaces.

This study provides new insights into how agile project management can foster creativity in project teams. The conceptual framework developed in this paper might be utilized to enhance creativity in agile teams, it can also serve as a starting point for future research.

Agile software development is an emerging approach in software engineering, initially proposed and promoted by a group of 17 software professionals who practice a set of “lightweight” methods, and share a common set of values of software development. They consolidated their thoughts, and defined these methods as “agile”. The approaches are based on experiences and best practices from the past by the above‐mentioned group of 17 software professionals. The purpose of this article is to outline the history and evolution of agile software development practices, their principles, and the criticisms as reported by the software development community.

A comprehensive literature review was undertaken to do this research.

Based on the literature review, this paper provides a comprehensive document that helps the practitioners working in the area of the agile software development.

This article will provide comprehensive material for the researchers in the area of agile software development. It will also be very useful for the practitioners practicing software development in the area of agile software development.

This study aims to create a better understanding of how practitioners implement and work Agile while balancing the tensions arising between stability and change.

A grounded theory approach was used to explore what happens in practice when software development teams implement and work Agile. The empirical data consists of twenty semi-structured interviews with practitioners working in fourteen different organizations and in six different Agile roles.

As a result, a substantive theory was presented of continuously balancing between stability and change in Agile teams. In addition, the study also proposes three guidelines that can help organizations about to change their way of working to Agile.

The inherent limitation of a grounded theory study is that a substantial theory can only explain the specific contexts explored in that study. Thus, this study's contribution is a substantial theory that needs to be further developed and improved.

The proposed guidelines can help organizations about to change their way of working to Agile. They can also assist organizations in switching from “doing Agile” to “being Agile”, thus becoming more successful.

The new perspective that this study contributes is the fact that our discovered categories show that several inherent processes are ongoing at the same time in order to balance the need to have both stability and change.