Search results
1 – 10 of over 9000Silke Bambauer-Sachse and Thomas Helbling
Agile methods have considerably transformed project management. The purpose of this study is to analyze the impact of agile (as compared to plan-driven) methods on customer…
Abstract
Purpose
Agile methods have considerably transformed project management. The purpose of this study is to analyze the impact of agile (as compared to plan-driven) methods on customer satisfaction in the context of knowledge-intensive business services.
Design/methodology/approach
This study uses a survey examining the experiences of 361 customers with different outsourced software projects in Switzerland and a regression-based model to test the hypotheses.
Findings
The findings show that agile approaches can lead to higher customer satisfaction than plan-driven approaches, but the impact size is not as substantial as expected. The effect does not depend on the number of specification changes.
Practical implications
Managers must be aware that merely switching from a plan driven to an agile approach will not lead to substantial improvement in customer satisfaction. Satisfaction with the process is a more important driver of overall customer satisfaction than satisfaction with the service outcome. Thus, providers of knowledge-intensive services should train their employees in recognizing the importance of the cooperation process.
Originality/value
So far, the positive impact of agile methods is often only based on anecdotal evidence as well as on surveys examining the supplier perspective. This study provides support for the positive impact of agile methods on customer satisfaction, an important response variable from a marketing perspective, which has not been examined before in the context considered here.
Details
Keywords
Jan Pries-Heje and Richard Baskerville
The purpose of this paper is to use translation theory to develop a framework (called FTRA) that explains how companies adopt agile methods in a discourse of fragmentation and…
Abstract
Purpose
The purpose of this paper is to use translation theory to develop a framework (called FTRA) that explains how companies adopt agile methods in a discourse of fragmentation and articulation.
Design/methodology/approach
A qualitative multiple case study of six firms using the Scrum agile methodology. Data were collected using mixed methods and analyzed using three progressive coding cycles and analytic induction.
Findings
In practice, people translate agile methods for local settings by choosing fragments of the method and continuously re-articulating them according to the exact needs of the time and place. The authors coded the fragments as technological rules that share relationships within a framework spanning two dimensions: static-dynamic and actor-artifact.
Research limitations/implications
For consistency, the six cases intentionally represent one instance of agile methodology (Scrum). This limits the confidence that the framework is suitable for other kinds of methodologies.
Practical implications
The FTRA framework and the technological rules are promising for use in practice as a prescriptive or even normative frame for governing methodology adaptation.
Social implications
Framing agile adaption with translation theory surfaces how the discourse between translocal (global) and local practice yields the social construction of agile methods. This result contrasts the more functionalist engineering perspective and privileges changeability over performance.
Originality/value
The use of translation theory and the FTRA framework to explain how agile adaptation (in particular Scrum) emerges continuously in a process where method fragments are articulated and re-articulated to momentarily suit the local setting. Complete agility that rapidly and elegantly changes its own environment must, as a concomitant, rapidly and elegantly change itself. This understanding also elaborates translation theory by explaining how the articulation and re-articulation of ideas embody the means by which ideas travel in practice.
Details
Keywords
Subhas Misra, Vinod Kumar, Uma Kumar, Kamel Fantazy and Mahmud Akhter
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…
Abstract
Purpose
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.
Design/methodology/approach
A comprehensive literature review was undertaken to do this research.
Findings
Based on the literature review, this paper provides a comprehensive document that helps the practitioners working in the area of the agile software development.
Originality/value
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.
Details
Keywords
Francisco Loforte Ribeiro and Manuela Timóteo Fernandes
Agile methods have proven successful in increasing customer satisfaction and decreasing time and cost to market under uncertain conditions. Key characteristics of agile methods…
Abstract
Purpose
Agile methods have proven successful in increasing customer satisfaction and decreasing time and cost to market under uncertain conditions. Key characteristics of agile methods are lean, flexibility and highly iterative development with a strong emphasis on stakeholder involvement. Today construction firms in general and small to medium‐sized enterprises (SMEs) in particular are surviving in a drastic competitive environment in which they are facing more and more challenges. Additional innovation is needed in the construction sector, with increased participation from more competitive SMEs. The main purpose of this paper is to present a model to prioritize available management systems to help SMEs address the challenge of today's market competition more effectively.
Design/methodology/approach
The research methodology used is that of interpretative case study and grounded theory based on a strong empirical foundation, on which new theoretical insight into knowledge management as an autonomous action is developed. The paper looks at ways by which SMEs are managed, based on the empirical data collected from 12 case studies. It presents the empirical findings drawn from the case studies. Finally, the adoption of agile methods is subjectively assessed as to its potential contribution for improving the business processes of small and medium construction firms.
Findings
It is assessed that agile methods offers considerable potential for application in construction SMEs and that there are significant hurdles to its adoption in the actual phase. Should these be overcome, agile methods offers benefits well beyond any individual company.
Practical implications
Construction firms need to be aware of the advantages of new management paradigms and practices. The analysis shows that SMEs in the construction sector have to internalize agile values into their business processes to reap the benefits of agile methods. It also reveals that existing practices show some kind of agile flavours.
Originality/value
Agile principles and methods are explored, including: philosophy, values, practices and benefits. The management approaches used by construction SMEs are analyzed and discussed. The paper presents recommendations and insights for enhancing the performance and efficiency of SMEs by adopting agile values in their business processes.
Details
Keywords
Agile is the new popular management change method and agile has lots of momentum. Management consulting firms are promoting agile via articles and newsletters. While history does…
Abstract
Purpose
Agile is the new popular management change method and agile has lots of momentum. Management consulting firms are promoting agile via articles and newsletters. While history does not repeat itself, it often rhymes, and thus agile will probably be a successful change effort in some organizations. On the other hand, there is a high probability that agile will not deliver the expected results for most organizations. History reveals that about two-thirds of the change efforts are deemed unsuccessful – regardless of the actual change method. In this paper, we present the results of a systematic literature review on agile and we compare and contrast it with other similar organizational change methods. The purpose of this paper is to explore what one may learn from the history of the earlier change methods in terms of how organizations may succeed in their agile efforts.
Design/methodology/approach
The paper is based on a structured literature review of the agile concept – including agile transformation, and with a specific focus on critical success factors.
Findings
In addition to presenting the state of the art on agile in general, we identify, structure and categorize critical success factors (CSF) for agile. From the 13 categories, we form three clusters, which constitute a 3P framework (purpose, process and people). We also compare and contrast the CSF literature regarding agile with CSFs for organizational change in general. history indicates that most organizational change efforts are not successful. Based on the framework and the discussion, we provide recommendations to hopefully increase the probability of successful agile implementations.
Originality/value
Given the relative novelty or at least the renewed interest in agile, a structured literature review of the current status of this “new” method provides value as it may help organizations and managers to not repeat old mistakes – once again.
Details
Keywords
Adriano Rehder, João Valsecchi Souza, Roberto Marx and Mario Sergio Salerno
Agile methods are increasingly being applied in the contexts of innovation beyond traditional information technology (IT) and physical product development projects, such as when…
Abstract
Purpose
Agile methods are increasingly being applied in the contexts of innovation beyond traditional information technology (IT) and physical product development projects, such as when process improvements are being implemented. Nevertheless, this phenomenon is still recent and little addressed in the literature, with few descriptions of empirical cases. This study aims to address this gap.
Design/methodology/approach
This multiple case study aims to present and discuss the application of Agile practices embedded in large companies’ innovation value chains, focusing on improvements of business processes. The following research question is pursued: How are large companies applying elements of Agile methods to their innovation processes when implementing incremental improvements in their operational processes? Based on the idea that the Agile-Stage-Gate model is an alternative to this challenge, this study investigates the application of this hybrid model in two large Brazilian companies by presenting their idiosyncrasies, lessons learned, adaptations, challenges and benefits.
Findings
Overall, it was observed that the experience with the application of the Agile-Stage-Gate model is positive for these companies, with better customer engagement, easier project control and increased productivity of the project team.
Originality/value
For those aiming to implement the Agile-Stage-Gate model, this paper identifies the main adaptations made in order to combine the purist approaches and critical success factors for its implementation.
Details
Keywords
Anna Schmitt and Sabrina Hörner
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…
Abstract
Purpose
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.
Design/methodology/approach
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.
Findings
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.
Originality/value
We provide an overview of existing approaches handling the combination of agile and business processes to improve business processes.
Details
Keywords
Tarek Kaddoumi and Mohamed Watfa
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…
Abstract
Purpose
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.
Design/methodology/approach
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.
Findings
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.
Research limitations/implications
Because of the chosen research approach and the sample size, the research results may lack generalizability. Also, EAAI designed was not thoroughly tested.
Practical implications
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.
Originality/value
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.
Details
Keywords
Shekhar Rathor, Weidong Xia and Dinesh Batra
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…
Abstract
Purpose
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).
Design/methodology/approach
Survey data from one hundred and sixty software development professionals were analyzed using structural equation modeling methods.
Findings
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.
Originality/value
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.
Details
Keywords
Jörg Rainer Noennig, Filipe Mello Rose, Paul Stadelhofer, Anja Jannack and Swati Kulashri
Digitalising cities requires new urban governance processes that account for rapidly changing environments and technological advances. In this context, agile development methods…
Abstract
Purpose
Digitalising cities requires new urban governance processes that account for rapidly changing environments and technological advances. In this context, agile development methods have become valuable, if not necessary. However, agile development contradicts public administration practices of risk aversion and long-term planning. The purpose of this study is to discuss practical avenues for navigating these two contradictions by adapting agile development to the needs of public sector organisations.
Design/methodology/approach
The authors review the collaborative elaboration of Dresden’s smart city strategy as a critical case study. Dresden’s smart city strategy was developed using agile development and quadruple-helix innovation. The year-long co-creation process involved stakeholders from various groups to conceive an integrated and sustainable vision for digitalisation-based urban development.
Findings
Despite the apparent contradictions, this study finds that key aspects of agile development are feasible for public sector innovation. Firstly, risks can be strategically managed and distributed among administration and non-administration stakeholders. Secondly, while delivering value through short iterative loops, adherence to formal processes remains possible. Informal feedback cycles can be harmoniously combined with official statements, allowing iterative progress.
Research limitations/implications
The empirical material is based on a single case study and thus risks overemphasising the general applicability of the proposed methods.
Practical implications
This paper outlines practical steps to greater agility for public administration engaged in digitalising cities. The paper conceptualises a forward and lateral momentum for the agile development of a smart city strategy that aims to reconcile formal policymaking processes with short-term loops and risk aversion with experimental value creation. This approach balanced risks, created value and enhanced the strategy‘s alignment with strategic frameworks, ultimately promoting innovation in the public sector.
Originality/value
This paper proposes a novel, empirically grounded conceptualisation of implementing agile methods that explicitly recognises the peculiarities of public administrations. It conceptualises the orchestrated and pragmatic use of specific agile development methods to advance the digitalisation of cities.
Details