Large-Scale Agile Frameworks: A Comparative Review

This study aims to identify and systematically compare the main large-scale agile frameworks that companies can adopt to manage the work of large-scale and distributed teams. Through this, companies can more consciously perform a better-informed decision on the choice of the framework that best fits the practices and challenges of their organizations. This work employs a qualitative approach supported by an exploratory analysis that identifies and explores the processes of migration to a large-scale agile. In the first phase, fifteen assessment criteria for scaling agile are discussed. In a second phase, these criteria are used to perform a comparative analysis of six large-scale agile frameworks (i.e., DAD, LeSS, Nexus, SAFe, Scrum at Scale, and Spotify). The findings reveal there isn't a dominant large-scale agile framework in all dimensions. However, it is possible to identify frameworks like Nexus and Spotify that target smaller teams and offer low technical complexity. These frameworks easily accommodate changes, while there are other frameworks like SAFe and DAD that offer high levels of scalability but require more demanding and deep efforts in changing work processes in an organization

Building lean thinking in a telecom software development organization: strengths and challenges.

The potential shown by Lean in different domains has aroused interest in the software industry. However, it remains unclear how Lean can be effectively applied in a domain such as software development that is fundamentally different from manufacturing. This study explores how Lean principles are implemented in software development companies and the challenges that arise when applying Lean Software Development. For that, a case study was conducted at Ericsson R&D Finland, which successfully adopted Scrum in 2009 and subsequently started a comprehensible transition to Lean in 2010. Focus groups were conducted with company representatives to help devise a questionnaire supporting the creation of a Lean mindset in the company (Team Amplifier). Afterwards, the questionnaire was used in 16 teams based in Finland, Hungary and China to evaluate the status of the transformation. By using Lean thinking, Ericsson R&D Finland has made important improvements to the quality of its products, customer satisfaction and transparency within the organization. Moreover, build times have been reduced over ten times and the number of commits per day has increased roughly five times.The study makes two main contributions to research. First, the main factors that have enabled Ericsson R&D?s achievements are analysed. Elements such as ?network of product owners?, ?continuous integration?, ?work in progress limits? and ?communities of practice? have been identified as being of fundamental importance. Second, three categories of challenges in using Lean Software Development were identified: ?achieving flow?, ?transparency? and ?creating a learning culture

Characterising project management of lean initiatives in industrial companies - crossing perspectives based on case studies

The paper mainly aims to characterise project management (PM) practices of industrial Lean initiatives by analysing and comparing three main topics: PM approaches, PM teams, and project alignment with the company's strategy. This research encompasses two exploratory industrial case studies with an extensive literature review. Key professionals were interviewed to obtain an in-depth vision of the field. The study results allowed characterising project management practices of industrial Lean initiatives in industrial companies based on the following dimensions: 1. Understand the needs; 2. Find a suitable team; 3. Use visual tools; 4. Apply a continuous improvement (CI) approach; 5. Identify KPIs for the context; 6. Get support from the top management. This work fills a gap related to studying the PM practices applied during the implementation of Lean initiatives, proposing a schematic representation of PM variables and actors in industrial Lean initiatives. Identifying the main variables and actors that industrial companies use to develop Lean initiatives can be insightful for Lean practitioners in the context of project management.This work was partially supported by FCT – Fundação para a Ciência e Tecnologia within the R&D Units Project Scope UIDB/00319/2020

Applying Agile Lean to Global Software Development

Although challenges of Global Software Development (GSD) are well known in the industry, practitioners and the organizations look for ways to improve results and overcome challenges. Companies have tried to implement many workable solutions possible to solve issues like poor communication, lack of trust, low morale and many other such issues prevalent in the distributed setting. With the success of agile, the methodology gained interest in leveraging its benefits to alleviate some of these challenges. Similarly, lean was also implemented in distributed software development to resolve issues. While each methodology provided some improvement in the results achieved in global software development, many issues persisted and the desired growth/results were not received. Recent years have seen an increased interest of applying a combination of agile and lean software development paradigms to resolve current industry issues in the area and meet the needs of rapid changing environment. This study aims to study the current practices of the combination of agile lean existing in the industry and how it can be utilized in the global software development. The study focuses on challenges faced to implement agile lean and successful sustainable implementation of agile lean in an environment of global software development

Systematic Literature Review of Trend and Characteristic Agile Model

Agile is a methodology and engineering approach for software development that encourages change in collaboration through tasks carried out at various stages of the software development life cycle. Scaled Agile Framework, Kanban, Scrum, Lean, Extreme Programming, Crystal, Dynamic System Development Method, and Feature Driven Development are a few of the approaches that go along with agile. Each of these approaches has distinct traits and qualities of its own. Every engineer and researcher needs to be aware of the benefits and characteristics of each method before deciding to use one. In order to assist engineers and researchers who will use one of these methods, this research will analyze it. The method used in this paper is a systematic literature review, which involved at 52 papers published in the previous eight years, from 2018 to 2022. This method is carried out by determining research questions, determining library initiation and selection, determining inclusion and exclusion criteria, and finally performing data extraction. This essay seeks to establish: (i) Study trends on each agile technique from 2018 to 2022 and (ii) Each agile method's characteristics. The results of this literature review indicate that Scrum and Extreme Programming have overtaken other agile methodologies as the most popular agile techniques over the last eight years. Through an analysis of the characteristics of each methodology, namely the development approach, suggested iteration time period, team communication, project size, project documentation, design, workflow approach, project coordinator, role assignment, coding, testing, and the nature of customer interaction, it is found that Scrum and Extreme Programming do have several advantages over other methodologies

Is agile project management applicable to construction?

This paper briefly summarises the evolution of Agile Project Management (APM) and differentiates it from lean and agile production and ‘leagile’ construction. The significant benefits being realized through employment of APM within the information systems industry are stated. The characteristics of APM are explored, including: philosophy, organizational attitudes and practices, planning, execution and control and learning. Finally, APM is subjectively assessed as to its potential contribution to the pre-design, design and construction phases. In conclusion, it is assessed that APM offers considerable potential for application in predesign and design but that there are significant hurdles to its adoption in the actual construction phase. Should these be overcome, APM offers benefits well beyond any individual project

The hidden pitfalls of Kanban in software development

ABSTRACT: Objectives of the Study: The objective of this thesis is to explore the hidden pitfalls of Kanban in software development. The aim is to discover the reasons behind the pitfalls and actions that nourish Kanban's failure. Academic background and methodology: Software development industry has been shifting towards more iterative, responsive and people-oriented development methods, which present the values of lean and agile thinking. Being characterized as the antidote for bureaucracy, the shift towards agile development methodologies has been one of the most significant factors affecting the software industry. Kanban as an agile change management framework has been perceived as the fairy godmother of software development making the reasons behind struggling Kanban projects particularly interesting. Thesis interviews five agile experts in the software development and studies their experiences of unsuccessful Kanban implementations. Emphasis is given to similar experiences and perceptions on how Kanban fails to redeem its value proposition. Findings: The primary finding of the study is that an organization that is unable to change its mindset to support Kanban is a pitfall affecting the whole project, inevitably causing Kanban to fail. This is a challenge that all agile methods have in common. Agile can flourish only when agile values are being appreciated. The secondary finding is that many software teams claiming to be using Kanban have implemented only a shallow imitation of the real method thus creating a superficial implementation, which prevents achieving Kanban induced benefits. Thus, creating a superficial implementation, which prevents achieving Kanban induced benefits. Furthermore, the erroneous human interpretation of what Kanban really is and how to apply it correctly is a key factor contributing to the emerge of the pitfalls. Keywords: Kanban, software development, pitfall, agile, change management, framewor

Development of a continuous improvement process for agile software development teams

Dissertação de mestrado integrado em Industrial Engineering and ManagementThe fast growth of the technology market has triggered the highest levels of competitiveness and globalization in the current business environment. The present VUCA (Volatile, Uncertain, Complex and Ambiguous) world and the continuous pursuit for new products and services has increased customer's demands, requiring the companies to be more flexible than ever by delivering software with quality, in time and within budget while in search of excellence and success. To reach this purpose, many software organizations have been adopting Agile Methodologies combined with Continuous Improvement projects, in order to achieve an improvement in customer satisfaction, providing products with higher quality, lower costs and in shorter time to the market. The ENG-P department at Bosch Braga, had a track record of some practices of Scrum but it was recognized that most teams were inefficient in taking advantage of the improvement opportunities that arose during the Sprint Retrospective ceremonies and transform them into improvements for the team. The objective of this dissertation project was to design a process for the inception of Continuous Improvement (CI) in one team of the ENG-P department, that could define the actions that needed to be taken after the Retrospective ceremony, in order to make the most out of the suggestions given by the team. By combining the Scrum cycle and the Lean philosophy, this CI process helped the team analyze problems or improvement opportunities and proceed to their prioritization, planning, implementation and evaluation, making the team more effective in problem-solving, more motivated and, consequently, more productive. The first step was to define which CI strategy would be implemented. Between analytical and benchmark approaches, the PDCA was the one selected to serve as foundation for the CI process due to its application to improve processes, products or services in any organization. After the implementation and standardization of the CI process in the daily work of the team, the final results showed that this new method doubled the suggestions implementation rate when compared with the previous results obtained by only performing the Retrospective ceremony. In addition, the accumulation of small improvements throughout time were responsible for substantial changes in the team. The level of motivation, involvement, empowerment and teamwork increased, there was a better visual task and time management, the communication improved, and a mindset of continuous improvement was built within the team.O rápido crescimento do mercado tecnológico despoletou os mais altos níveis de competitividade e globalização no atual ambiente de negócios. O presente mundo VUCA (volátil, incerto, complexo e ambíguo) e a procura contínua por novos produtos e serviços levou a um aumento das exigências dos clientes, obrigando as empresas a tornarem-se mais flexíveis e a fornecer software com qualidade, atempadamente e dentro do orçamento, enquanto procuram alcançar a excelência e o sucesso próprio. Com foco neste objetivo, muitas empresas de desenvolvimento de software têm recentemente adotado metodologias ágeis em simbiose com projetos de melhoria contínua, com a finalidade de obterem uma maior satisfação do cliente, fornecendo produtos com maior qualidade e custos mais baixos. O departamento ENG-P da Bosch Braga já possuía no seu histórico algumas práticas de Scrum, mas reconheceu-se que a maioria das equipas eram ineficientes no aproveitamento das oportunidades de melhoria que surgiam durante a cerimónia Retrospetiva e transformá-las em melhorias para a equipa. O objetivo deste projeto de dissertação foi projetar um processo para a implementação de uma estratégia de Melhoria Contínua numa equipa do departamento ENG-P. Este definiu as ações a serem tomadas após a Retrospetiva, de forma a aproveitar ao máximo as sugestões dadas pela equipa. A combinação entre o ciclo Scrum e a filosofia Lean auxiliou a equipa na análise de problemas ou oportunidades de melhoria, na sua priorização, planeamento, implementação e avaliação. Estas ações permitiram que a equipa se tornasse mais motivada e eficaz na resolução de problemas e, consequentemente, mais produtiva. A primeira etapa consistiu na definição da estratégia de melhoria contínua a ser implementada. Entre abordagens de benchmark e analíticas, o ciclo PDCA foi a técnica selecionada como base ao processo devido à sua aplicabilidade na melhoraria de processos, produtos ou serviços. Após a implementação e padronização do processo no trabalho diário da equipa, os resultados demostraram que a sua adoção duplicou a taxa de implementação de sugestões da equipa, quando comparado a resultados obtidos apenas com realização da Retrospetiva, aumentando a capacidade de resolução de problemas da equipa. Além disso, pequenas melhorias alcançadas ao longo do tempo trouxeram grandes mudanças para a equipa. O nível de motivação, envolvimento e teamwork aumentou, existiu uma melhor gestão visual das tarefas e do tempo, a comunicação melhorou e foi construída uma mentalidade de melhoria contínua dentro da equipa

Thoughts on Current and Future Research on Agile and Lean: Ensuring Relevance and Rigor

Over the past two decades, research in the area of agile and lean software development has mirrored the strong growth of the use of agile and lean methodologies. However, while these research streams have made a significant contribution in the use of agile and lean methodologies, much of the recent research lacks the rigor and relevance to make an impact in research and practice. For example, many of the studies have not measured the actual use of agile or lean methods nor had a significant theoretical grounding. Furthermore, agile research has not expanded to fully cover emerging opportunities and challenges. A deeper theoretical motivation on agile and lean software development can help demonstrate how the principles of, for example, agile software development, may be transferred to these other areas, and hence, broaden the research’s relevance. This paper provides commentary intended to help push the agile and lean research agenda forward, and outlines three key critieria that future researchers should consider when conducting research on the phenomenon of agile. The paper also provides an example for the use of the criteria, and presents several initial, open research questions that could help increase the use of agile, including the use of agile and lean concepts in other IT and non-IT contexts