Autonomous agile teams: Challenges and future directions for research

According to the principles articulated in the agile manifesto, motivated and empowered software developers relying on technical excellence and simple designs, create business value by delivering working software to users at regular short intervals. These principles have spawned many practices. At the core of these practices is the idea of autonomous, self-managing, or self-organizing teams whose members work at a pace that sustains their creativity and productivity. This article summarizes the main challenges faced when implementing autonomous teams and the topics and research questions that future research should address

Enterprise agile transformation model: Barriers, enablers and best practices to implement Agile Methods

Agile Methods currently represent one of the most discussed topics in organisations and teams working with technological products. However, there are still few scientific studies that clearly explain how an organisation can adopt these methods. This thesis has three main objectives, where was developed a study for each: (i) identify in the literature the best practices to implement and manage an agile project portfolio, (ii) identify the barriers and enablers of an Agile Transformation and (iii) expand a theoretical model that allows organisations to carry out an Agile Transformation. The first study used a qualitative approach to carry out a systematic literature review. The second study used a quantitative approach to identify the barriers and enablers. The third study used a qualitative approach to develop the Enterprise Agile Transformation Model. This thesis concluded that, for the implementation and management of an agile portfolio of projects, there are four relevant dimensions to consider. The key four barriers and five enablers for the success of an Agile Transformation were also identified. The Enterprise Agile Transformation Model considers actions to mitigate barriers and enhance the enablers of an Agile Transformation and provides recommendations to increase the agile maturity of organisations. The academic contribution focuses on filling the gap in the scientific literature on Agile Transformations and Agile Project Portfolio Management. For practice, the contribution involves providing a theoretical model with tools, strategies, and recommendations for the implementation of Agile Methods in organisations.Os Métodos Agile representam atualmente um dos temas mais discutidos nas organizações e equipas que trabalham com produtos tecnológicos. No entanto, ainda existe um conjunto reduzido de estudos científicos que expliquem, de uma forma clara, como uma organização pode adotar estes métodos. Esta tese apresenta três objetivos principais, onde foi desenvolvido um estudo para cada um: (i) identificar na literatura as melhores práticas para implementar e gerir um portefólio de projetos agile, (ii) identificar as barreiras e facilitadores de uma Transformação Agile e (iii) expandir um modelo teórico que permita conduzir as organizações a realizar uma Transformação Agile. O primeiro estudo recorreu à abordagem qualitativa para realizar a revisão sistemática da literatura. O segundo estudo utilizou uma abordagem quantitativa para identificar as barreiras e facilitadores. O terceiro estudo utilizou uma abordagem qualitativa para desenvolver o modelo teórico Enterprise Agile Transformation Model. Esta tese concluiu que, para a implementação e gestão de um portefólio de projetos agile, existem quatro dimensões relevantes a considerar. Foram também identificadas quatro barreiras e cinco facilitadores determinantes para o sucesso de uma Transformação Agile. Já o Enterprise Agile Transformation Model, considera ações para mitigar as barreiras e potenciar os facilitadores de uma Transformação Agile e apresenta recomendações para aumentar a maturidade ágil das organizações. A contribuição académica consiste em colmatar a lacuna existente na literatura científica sobre Transformações Agile e gestão de portefólio de projetos agile. Para a prática, a contribuição passa por dar ferramentas, estratégias e recomendações para a implementação de Métodos Agile nas organizações

“Primus inter Pares”?—The Perception of Emergent Leadership Behavior in Agile Software Development Teams

Despite being a key feature of Agile Software Development (ASD), self-organization within ASD teams has received limited research attention. Hence, this study furthers our understanding of how informal emergent leadership may develop within ASD teams by combining knowledge on ASD teams with extant research on emergent leadership. In an exploratory mixed-method study of two Scrum teams, we observed two specific types of emergent leaders, namely, a “detail-oriented structurer”, and a “big picture coordinator.” For emergent leadership to develop, the Scrum master had to create a “leadership gap.” Given this leadership gap, emergent leadership may develop in a circular manner: specific behaviors of team members and their perceptions may provide the basis for emergent leadership, which combined with implicit leadership theories of team members give rise to a leadership structure. Our results add to research on emergent leadership and increase our understanding of self-organization in ASD teams

Finnish Enterprise Agile Transformations : A Survey Study

Peer reviewe

Charting Coordination Needs in Large-Scale Agile Organisations with Boundary Objects and Methodological Islands

Large-scale system development companies are increasingly adopting agile methods. While this adoption may improve lead-times, such companies need to balance two trade-offs: (i) the need to have a uniform, consistent development method on system level with the need for specialised methods for teams in different disciplines (e.g., hardware, software, mechanics, sales, support); (ii) the need for comprehensive documentation on system level with the need to have lightweight documentation enabling iterative and agile work. With specialised methods for teams, isolated teams work within larger ecosystems of plan-driven culture, i.e., teams become agile “islands”. At the boundaries, these teams share knowledge which needs to be managed well for a correct system to be developed. While it is useful to support diverse and specialised methods, it is important to understand which islands are repeatedly encountered, the reasons or factors triggering their existence, and how best to handle coordination between them. Based on a multiple case study, this work presents a catalogue of islands and the boundary objects between them. We believe this work will be beneficial to practitioners aiming to understand their ecosystems and researchers addressing communication and coordination challenges in large-scale development

On the real world practice of Behaviour Driven Development

Surveys of industry practice over the last decade suggest that Behaviour Driven Development is a popular Agile practice. For example, 19% of respondents to the 14th State of Agile annual survey reported using BDD, placing it in the top 13 practices reported. As well as potential benefits, the adoption of BDD necessarily involves an additional cost of writing and maintaining Gherkin features and scenarios, and (if used for acceptance testing,) the associated step functions. Yet there is a lack of published literature exploring how BDD is used in practice and the challenges experienced by real world software development efforts. This gap is significant because without understanding current real world practice, it is hard to identify opportunities to address and mitigate challenges. In order to address this research gap concerning the challenges of using BDD, this thesis reports on a research project which explored: (a) the challenges of applying agile and undertaking requirements engineering in a real world context; (b) the challenges of applying BDD specifically and (c) the application of BDD in open-source projects to understand challenges in this different context. For this purpose, we progressively conducted two case studies, two series of interviews, four iterations of action research, and an empirical study. The first case study was conducted in an avionics company to discover the challenges of using an agile process in a large scale safety critical project environment. Since requirements management was found to be one of the biggest challenges during the case study, we decided to investigate BDD because of its reputation for requirements management. The second case study was conducted in the company with an aim to discover the challenges of using BDD in real life. The case study was complemented with an empirical study of the practice of BDD in open source projects, taking a study sample from the GitHub open source collaboration site. As a result of this Ph.D research, we were able to discover: (i) challenges of using an agile process in a large scale safety-critical organisation, (ii) current state of BDD in practice, (iii) technical limitations of Gherkin (i.e., the language for writing requirements in BDD), (iv) challenges of using BDD in a real project, (v) bad smells in the Gherkin specifications of open source projects on GitHub. We also presented a brief comparison between the theoretical description of BDD and BDD in practice. This research, therefore, presents the results of lessons learned from BDD in practice, and serves as a guide for software practitioners planning on using BDD in their projects

The Impact of Requirements on Systems Development Speed: A Multiple-Case Study in Automotive

Automotive\ua0manufacturers have historically adopted rigid\ua0requirements\ua0engineering processes. This allowed them to meet safety-critical\ua0requirements\ua0when producing\ua0a\ua0highly complex and differentiated product out of the integration of thousands of physical and software components. Nowadays, few software-related domains are as rapidly changing as the\ua0automotive\ua0industry.\ua0In\ua0particular, the needs of improving\ua0development\ua0speed\ua0are increasingly pushing companies\ua0in\ua0this domain toward new ways of developing software.\ua0In\ua0this paper, we investigate how the goal to increase\ua0development\ua0speed\ua0impacts how\ua0requirements\ua0are managed\ua0in\ua0the\ua0automotive\ua0domain. We start from\ua0a\ua0manager perspective, which we then complement with\ua0a\ua0more general perspective. We used\ua0a\ua0qualitative\ua0multiple-case\ua0study, organized\ua0in\ua0two steps.\ua0In\ua0the first step, we had 20 semi-structured interviews, at two\ua0automotive\ua0manufacturers. Our sampling strategy focuses on manager roles, complemented with technical specialists.\ua0In\ua0the second step, we validated our results with 12 more interviews, covering nine additional respondents and three recurring from the first step.\ua0In\ua0addition to validating our qualitative model, the second step of interviews broadens our perspective with technical experts and change managers. Our respondents indicate and rank six aspects of the current\ua0requirements\ua0engineering approach that\ua0impact\ua0development\ua0speed. These aspects include the negative\ua0impact\ua0of\ua0a\ua0requirements\ua0style dominated by safety concerns as well as decomposition of\ua0requirements\ua0over many levels of abstraction. Furthermore, the use of\ua0requirements\ua0as part of legal contracts with suppliers is seen as hindering fast collaboration. Six additional suggestions for potential improvements include domain-specific tooling, model-based\ua0requirements, test automation, and\ua0a\ua0combination of lightweight upfront\ua0requirements\ua0engineering preceding\ua0development\ua0with precise specifications post-development. Out of these 12 aspects, seven can likely be addressed as part of an ongoing agile transformation. We offer an empirical account of expectations and needs for new\ua0requirements\ua0engineering approaches\ua0in\ua0the\ua0automotive\ua0domain, necessary to coordinate hundreds of collaborating organizations developing software-intensive and potentially safety-critical\ua0systems

Agile Processes in Software Engineering and Extreme Programming

This open access book constitutes the proceedings of the 22nd International Conference on Agile Software Development, XP 2021, which was held virtually during June 14-18, 2021. XP is the premier agile software development conference combining research and practice. It is a unique forum where agile researchers, practitioners, thought leaders, coaches, and trainers get together to present and discuss their most recent innovations, research results, experiences, concerns, challenges, and trends.  XP conferences provide an informal environment to learn and trigger discussions and welcome both people new to agile and seasoned agile practitioners. This year’s conference was held with the theme “Agile Turns Twenty While the World Goes Online”. The 11 full and 2 short papers presented in this volume were carefully reviewed and selected from 38 submissions. They were organized in topical sections named: agile practices; process assessment; large-scale agile; and short contributions

Integration of Virtual Programming Lab in a process of teaching programming EduScrum based

Programming teaching is a key factor for technological evolution. The efficient way to learn to program is by programming and hard training and thus feedback is a crucial factor in the success and flow of the process. This work aims to analyse the potential use of VPL in the teaching process of programming in higher education. It also intends to verify whether, with VPL, it is possible to make students learning more effective and autonomous, with a reduction in the volume of assessment work by teachers. Experiments were carried out with the VPL, in the practical-laboratory classes of a curricular unit of initiation to programming in a higher education institution. The results supported by the responses to surveys, point to the validity of the model