Artefacts and Agile Method Tailoring in Large-Scale Offshore Software Development Programmes (original) (raw)
Related papers
How Product Owner Teams Scale Agile Methods to Large Distributed Enterprises
Software development teams in large scale offshore enterprise development programmes are often under intense pressure to deliver high quality software within challenging time contraints. Project failures can attract adverse publicity and damage corporate reputations. Agile methods have been advocated to reduce project risks, improving both productivity and product quality. This article uses practitioner descriptions of agile method tailoring to explore large scale offshore enterprise development programmes with a focus on product owner role tailoring, where the product owner identifies and prioritises customer requirements. In glob-alised projects, the product owner must reconcile competing business interests, whilst generating and then prioritising large numbers of requirements for numerous development teams. The study comprises eight international companies, based in London, Bangalore and Delhi. Interviews with 46 practitioners were conducted between February 2010 and May 2012. Grounded theory was used to identify that product owners form into teams. The main contribution of this research is to describe the nine product owner team functions identified: groom, prioritiser, release master, technical architect, governor, communicator, traveller, intermediary and risk assessor. These product owner functions arbitrate between conflicting customer requirements, approve release schedules, disseminate architectural design decisions, provide technical governance and propogate information across teams. The functions identified in this research are mapped to a scrum of scrums process, and a taxonomy of the functions shows how focusing on either decision-making or information dissemination in each helps to tailor agile methods to large scale offshore enterprise development programmes. Keywords agile software development · scrum · large scale offshore enterprise development programmes · product owner · product owner teams · grounded theory.
Software Development Artifacts in Large Agile Organizations: A Comparison of Scaling Agile Methods
Data-Centric Business and Applications, 2019
Agile frameworks or methods such as Scrum, Kanban and Extreme Programming are widely adopted and used by small teams within large organizations and start-ups. Established Enterprises, banks, and technology giants are aiming to introduce and implement agile methods that helps organize process in high complexity organizations. Main challenges due to higher complexity relates but are not limited to multiple value streams development pipelines orchestration, communications among many distributed teams, inter team dependencies management, information flow between teams. It can be said that large organizations need to deliver, adapt or introduce new methods to manage development organizations and deliver needed artifacts. Purpose-This paper aims to compare possible agile frameworks for scaling development organizations working in an agile culture, and their outcomes materialized as artifacts.
A Tale Of Two Agile Implementations: A Cross-Case Exploratory Analysis
There is a growing trend towards the adoption of agile methods for information systems development in organisations due to the pressures for products and services to be faster to market. This paper examines the introduction and use of agile methods in two significantly different organizations; a bank and an international law firm. The adoption of agile methods in one organization was deemed a success whereas in the other it was not, although the agile approach did salvage an ongoing project, but was not considered for further use. The cases were investigated via action research and the analysis adopted the competing values framework as the theoretical lens. This framework takes a cultural perspective to organisational effectiveness and requires the mapping of organisations into a four-quadrant model along the dimensions of organisational focus (internal versus external) and flexibility (change versus stability). Differences in the two cases and the organisational environments were examined for the purpose of identifying factors related to the successful and sustained adoption of agile methods. One organisation clearly emphasized stability over change and an internal focus, whereas the other was almost the complete opposite. The findings demonstrate the organisational cultural differences of the two organisations and their importance in the successful adoption of agile methods. Organisations should be aware of these differences and be wary of adopting agile development methods in otherwise historically and culturally non-agile organisations..
Influences on Agile Practice Tailoring in Enterprise Software Development
2012 Agile India, 2012
Agile development projects have become a reality in large enterprises using offshore development models. A case study involving seven international companies with offices in Bangalore, India, and London, UK was conducted, including interviews with 19 practitioners. The contribution of this paper is to illustrate the reasons for tailoring Agile practices within the context of large enterprises. The findings show that scrum roles and practices did not conflict with enterprise policies or processes and were thought to improve product quality and productivity. However, agile practices from the XP tradition were not so widely adopted. Test driven development did not integrate well within enterprises where independent quality assurance teams were constituted as separate departments. Continuous integration was found to be challenging where enterprise software products required time consuming regression testing and elaborate code release processes. While adoption of coding standards and collective code ownership are necessary to facilitate interaction between disparate stakeholder groups.
Important Considerations for Agile Software Development Methods Governance
After introducing Agile approach in 2001, several Agile methods were founded over the last decade. Agile values such as customer collaboration, embracing changes, iteration and frequent delivery, continuous integration, etc. motivate all software stakeholders to use these methods in their projects. Moving to Agile methods needs a huge change in organization and involved people. This change is a fundamental and critical mutation. The main issue is that Agile transition and governance action plan needs to consider different aspects of change related issues. Conduction a Grounded Theory study with participation of 37 Agile experts from 13 countries showed that software companies should consider three main factors before inception of transformation action plan: Adoption styles, Method selection and Awareness of challenges and constraints. These fundamental considerations encompass many critical items for Agile movement and adoption process. However these items may lead to different results in different companies, but they should be studied in deep before any transition action plan.
A Post-colonial Analysis of Agile Software Development Methods in ICT4D
2020
There is evidence that agile approaches to information system development can improve product quality and developer productivity. However, successful adoption of these approaches appears to depend on adaptation to specific contexts. This research contributes to a broader goal to understand what it means to “be agile” in the presence of adaptations to the specific context. To pursue our research objectives, we have performed 31 semi-structured recorded and transcribed practitioner interviews from three companies in Lebanon. The interview transcripts were analysed using an approach informed by grounded theory. Agile methods enable learning and improvement through team conversations. Yet, the practitioners in our study shun public self-evaluation, finding it difficult to discuss areas for improvement in public. We also found legacy “top down” management practices that undermine team autonomy and local client companies lack experience of engaging with agile processes. In a more positive...
IFIP Advances in Information and Communication Technology, 2010
In a Scandinavian company developing a healthcare information system (IS) at three Scandinavian sites they succeeded in taking agile processes into use across the three sites. After a fourth development site in India was added the use of agile development processes gradually came to an end and plan-driven processes took over. In this paper we report from a month-long study where our analysis of the case shows that the cause for giving up agile was threefold: (1) The cultural distance between India and Scandinavia was too great. (2) There were telling differences in competence and (3) the presence of knowledge asymmetry. From this analysis we develop a grounded theory explaining the necessary preconditions for succeeding with a global process for agile IS development.
Agile Challenges in Practice: A Thematic Analysis
As agile is maturing and becoming more widely adopted, it is important that researchers are aware of the challenges faced by practitioners and organisations. We undertook a thematic analysis of 193 agile challenges collected at a series of agile conferences and events during 2013 and 2014. Participants were mainly practitioners and business representatives along with some academics. The challenges were thematically analysed by separate authors, synthesised, and a list of seven themes and 27 sub-themes was agreed. Themes were Organisation, Sustainability, Culture, Teams, Scale, Value and Claims and Limitations. We compare our findings against previous attempts to identify and categorise agile challenges. While most themes have persisted we found a shift of focus towards sustainability, business engagement and transformation, as well as claims and limitations. We identify areas for further research and a need for innovative methods of conveying academic research to industry and industrial problems to academia.