The Experts below are selected from a list of 3555 Experts worldwide ranked by ideXlab platform
Wilhelm Meding - One of the best experts on this subject based on the ideXlab platform.
-
identifying risky areas of Software code in agile Lean Software Development an industrial experience report
Conference on Software Maintenance and Reengineering, 2014Co-Authors: Vard Antinyan, Wilhelm Meding, Miroslaw Staron, Johan Wranker, Anders Henriksson, Per Osterstrom, Erik Wikstrom, Jörgen HanssonAbstract:Modern Software Development relies on incremental delivery to facilitate quick response to customers' requests. In this dynamic environment the continuous modifications of Software code can cause risks for Software developers; when developing a new feature increment, the added or modified code may contain fault-prone or difficult-to-maintain elements. The outcome of these risks can be defective Software or decreased Development velocity. This study presents a method to identify the risky areas and assess the risk when developing Software code in Lean/Agile environment. We have conducted an action research project in two large companies, Ericsson AB and Volvo Group Truck Technology. During the study we have measured a set of code properties and investigated their influence on risk. The results show that the superposition of two metrics, complexity and revisions of a source code file, can effectively enable identification and assessment of the risk. We also illustrate how this kind of assessment can be successfully used by Software developers to manage risks on a weekly basis as well as release-wise. A measurement system for systematic risk assessment has been introduced to two companies.
-
Monitoring Evolution of Code Complexity in Agile/Lean Software Development - A Case Study at Two Companies
2013Co-Authors: Vard Antinyan, Wilhelm Meding, Miroslaw Staron, Per Österströ, Henric Bergenwall, Johan Wranker, Jörgen Hansson, Anders HenrikssonAbstract:One of the distinguishing characteristics of Agile and Lean Software Development is that Software products “grow” with new functionality with relatively small increments. Continuous customer demands of new features and the companies’ abilities to deliver on those demands are the two driving forces behind this kind of Software evolution. Despite the numerous benefits there are a number of risks associated with this kind of growth. One of the main risks is the fact that the complexity of the Software product grows slowly, but over time reaches scales which makes the product hard to maintain or evolve. The goal of this paper is to present a measurement system for monitoring the growth of complexity and drawing attention when it becomes problematic. The measurement system was developed during a case study at Ericsson and Volvo Group Truck Technology. During the case study we explored the evolution of size, complexity, revisions and number of designers of two large Software products from the telecom and automotive domains. The results show that two measures needed to be monitored to keep the complexity Development under control - McCabe’s complexity and number of revisions.
-
monitoring evolution of code complexity in agile Lean Software Development a case study at two companies
13th Symposium on Programming Languages and Software Tools SPLST 2013 - Proceedings, 2013Co-Authors: Vard Antinyan, Wilhelm Meding, Miroslaw Staron, Per Österströ, Henric Bergenwall, Johan Wranker, Jörgen Hansson, Anders HenrikssonAbstract:One of the distinguishing characteristics of Agile and Lean Software Development is that Software products “grow” with new functionality with relatively small increments. Continuous customer demands of new features and the companies’ abilities to deliver on those demands are the two driving forces behind this kind of Software evolution. Despite the numerous benefits there are a number of risks associated with this kind of growth. One of the main risks is the fact that the complexity of the Software product grows slowly, but over time reaches scales which makes the product hard to maintain or evolve. The goal of this paper is to present a measurement system for monitoring the growth of complexity and drawing attention when it becomes problematic. The measurement system was developed during a case study at Ericsson and Volvo Group Truck Technology. During the case study we explored the evolution of size, complexity, revisions and number of designers of two large Software products from the telecom and automotive domains. The results show that two measures needed to be monitored to keep the complexity Development under control - McCabe’s complexity and number of revisions.
-
release readiness indicator for mature agile and Lean Software Development projects
International Conference on Agile Software Development, 2012Co-Authors: Miroslaw Staron, Wilhelm Meding, Klas PalmAbstract:Large companies like Ericsson increasingly often adopt the principles of Agile and Lean Software Development and develop large Software products in iterative manner – in order to quickly respond to customer needs. In this paper we present the main indicator which is sufficient for a mature Software Development organization in order to predict the time in weeks to release the product. In our research project we collaborated closely with a large Agile+Lean Software Development project at Ericsson in Sweden. This large and mature Software Development project and organization has found this main indicator – release readiness – to be so important that it was used as a key performance indicator and is used in controlling the Development of the product and improving organizational performance. The indicator was developed and validated in an action research project at one of the units of Ericsson AB in Sweden in one of its largest projects.
-
monitoring bottlenecks in agile and Lean Software Development projects a method and its industrial use
Product Focused Software Process Improvement, 2011Co-Authors: Miroslaw Staron, Wilhelm MedingAbstract:In the face of growing competition Software projects have to deliver Software products faster and with better quality - thus leaving little room for unnecessary activities or non-optimal capacity. To achieve the desired high speed of the projects and the optimal capacity,bottlenecks existing in the projects have to be monitored and effectively removed. The objective of this research is to show experiences from a mature Software Development organization working according to Lean and Agile Software Development principles. By conducting a formal case study at Ericsson we were able to elicit and automate measures required to monitor bottlenecks in Software Development workflow, evaluated in one of the projects. The project developed Software for one of the telecom products and consisted of over 80 developers. The results of the case study include a measurement system with a number of measures/indicators which can indicate existence of bottlenecks in the flow of work in the project and a number of good practices helping other organizations to start monitoring bottlenecks in an effective way - in particular what to focus on when designing such a measurement system.
Miroslaw Staron - One of the best experts on this subject based on the ideXlab platform.
-
identifying risky areas of Software code in agile Lean Software Development an industrial experience report
Conference on Software Maintenance and Reengineering, 2014Co-Authors: Vard Antinyan, Wilhelm Meding, Miroslaw Staron, Johan Wranker, Anders Henriksson, Per Osterstrom, Erik Wikstrom, Jörgen HanssonAbstract:Modern Software Development relies on incremental delivery to facilitate quick response to customers' requests. In this dynamic environment the continuous modifications of Software code can cause risks for Software developers; when developing a new feature increment, the added or modified code may contain fault-prone or difficult-to-maintain elements. The outcome of these risks can be defective Software or decreased Development velocity. This study presents a method to identify the risky areas and assess the risk when developing Software code in Lean/Agile environment. We have conducted an action research project in two large companies, Ericsson AB and Volvo Group Truck Technology. During the study we have measured a set of code properties and investigated their influence on risk. The results show that the superposition of two metrics, complexity and revisions of a source code file, can effectively enable identification and assessment of the risk. We also illustrate how this kind of assessment can be successfully used by Software developers to manage risks on a weekly basis as well as release-wise. A measurement system for systematic risk assessment has been introduced to two companies.
-
Monitoring Evolution of Code Complexity in Agile/Lean Software Development - A Case Study at Two Companies
2013Co-Authors: Vard Antinyan, Wilhelm Meding, Miroslaw Staron, Per Österströ, Henric Bergenwall, Johan Wranker, Jörgen Hansson, Anders HenrikssonAbstract:One of the distinguishing characteristics of Agile and Lean Software Development is that Software products “grow” with new functionality with relatively small increments. Continuous customer demands of new features and the companies’ abilities to deliver on those demands are the two driving forces behind this kind of Software evolution. Despite the numerous benefits there are a number of risks associated with this kind of growth. One of the main risks is the fact that the complexity of the Software product grows slowly, but over time reaches scales which makes the product hard to maintain or evolve. The goal of this paper is to present a measurement system for monitoring the growth of complexity and drawing attention when it becomes problematic. The measurement system was developed during a case study at Ericsson and Volvo Group Truck Technology. During the case study we explored the evolution of size, complexity, revisions and number of designers of two large Software products from the telecom and automotive domains. The results show that two measures needed to be monitored to keep the complexity Development under control - McCabe’s complexity and number of revisions.
-
monitoring evolution of code complexity in agile Lean Software Development a case study at two companies
13th Symposium on Programming Languages and Software Tools SPLST 2013 - Proceedings, 2013Co-Authors: Vard Antinyan, Wilhelm Meding, Miroslaw Staron, Per Österströ, Henric Bergenwall, Johan Wranker, Jörgen Hansson, Anders HenrikssonAbstract:One of the distinguishing characteristics of Agile and Lean Software Development is that Software products “grow” with new functionality with relatively small increments. Continuous customer demands of new features and the companies’ abilities to deliver on those demands are the two driving forces behind this kind of Software evolution. Despite the numerous benefits there are a number of risks associated with this kind of growth. One of the main risks is the fact that the complexity of the Software product grows slowly, but over time reaches scales which makes the product hard to maintain or evolve. The goal of this paper is to present a measurement system for monitoring the growth of complexity and drawing attention when it becomes problematic. The measurement system was developed during a case study at Ericsson and Volvo Group Truck Technology. During the case study we explored the evolution of size, complexity, revisions and number of designers of two large Software products from the telecom and automotive domains. The results show that two measures needed to be monitored to keep the complexity Development under control - McCabe’s complexity and number of revisions.
-
release readiness indicator for mature agile and Lean Software Development projects
International Conference on Agile Software Development, 2012Co-Authors: Miroslaw Staron, Wilhelm Meding, Klas PalmAbstract:Large companies like Ericsson increasingly often adopt the principles of Agile and Lean Software Development and develop large Software products in iterative manner – in order to quickly respond to customer needs. In this paper we present the main indicator which is sufficient for a mature Software Development organization in order to predict the time in weeks to release the product. In our research project we collaborated closely with a large Agile+Lean Software Development project at Ericsson in Sweden. This large and mature Software Development project and organization has found this main indicator – release readiness – to be so important that it was used as a key performance indicator and is used in controlling the Development of the product and improving organizational performance. The indicator was developed and validated in an action research project at one of the units of Ericsson AB in Sweden in one of its largest projects.
-
monitoring bottlenecks in agile and Lean Software Development projects a method and its industrial use
Product Focused Software Process Improvement, 2011Co-Authors: Miroslaw Staron, Wilhelm MedingAbstract:In the face of growing competition Software projects have to deliver Software products faster and with better quality - thus leaving little room for unnecessary activities or non-optimal capacity. To achieve the desired high speed of the projects and the optimal capacity,bottlenecks existing in the projects have to be monitored and effectively removed. The objective of this research is to show experiences from a mature Software Development organization working according to Lean and Agile Software Development principles. By conducting a formal case study at Ericsson we were able to elicit and automate measures required to monitor bottlenecks in Software Development workflow, evaluated in one of the projects. The project developed Software for one of the telecom products and consisted of over 80 developers. The results of the case study include a measurement system with a number of measures/indicators which can indicate existence of bottlenecks in the flow of work in the project and a number of good practices helping other organizations to start monitoring bottlenecks in an effective way - in particular what to focus on when designing such a measurement system.
Giancarlo Succi - One of the best experts on this subject based on the ideXlab platform.
-
FISEE - Experience of Mixed Learning Strategies in Teaching Lean Software Development to Third Year Undergraduate Students
Frontiers in Software Engineering Education, 2020Co-Authors: Ilya Khomyakov, Sergey Masyagin, Giancarlo SucciAbstract:Teaching is always a challenging task, especially in the current fast-paced and changing world. Universities curricula and instructional practices should take into account growing and changing demands of both industry and students themselves. Given all these factors, a Lean Software Development course for third year BS has been developed and continues to evolve at Innopolis University, Russia. In the course, Lean methods are used both for teaching Lean Software Development skill, and for teaching Lean via other, not directly related to programming, collaborative tasks, i.e. writing a research paper. Besides, Lean methodology is used by the course Development team for course design. As a result, this approach helps not only to develop the theoretical and practical skills that students can apply in various spheres of life but also to engage the students and to maintain their attention throughout the course without any overload.
-
experience of mixed learning strategies in teaching Lean Software Development to third year undergraduate students
International Workshop on Frontiers in Software Engineering Education, 2019Co-Authors: Ilya Khomyakov, Sergey Masyagin, Giancarlo SucciAbstract:Teaching is always a challenging task, especially in the current fast-paced and changing world. Universities curricula and instructional practices should take into account growing and changing demands of both industry and students themselves. Given all these factors, a Lean Software Development course for third year BS has been developed and continues to evolve at Innopolis University, Russia. In the course, Lean methods are used both for teaching Lean Software Development skill, and for teaching Lean via other, not directly related to programming, collaborative tasks, i.e. writing a research paper. Besides, Lean methodology is used by the course Development team for course design. As a result, this approach helps not only to develop the theoretical and practical skills that students can apply in various spheres of life but also to engage the students and to maintain their attention throughout the course without any overload.
-
DEVOPS - A Lean and Devops Approach to Teach Lean Software Development.
Software Engineering Aspects of Continuous Development and New Paradigms of Software Production and Deployment, 2018Co-Authors: Vladimir Ivanov, Dmitry Krasnikhin, Stanislav Litvinov, Sergey Masyagin, Giancarlo SucciAbstract:This paper describes application of Lean methodology in IT education in a context of an undergraduate course on “Lean Software Development” with a full devops pragmatics in mind. Strong connection between Software Development and delivery processes can be build on top of established Lean practices. Which means that implementation of end-to-end automation by devops approach needs good understanding of Lean principles and mindset. The course exposes students to the core concepts underneath Lean Development in Software engineering, beyond myths and legends, emphasizing how it relates to the general principles of Lean Development.
-
a Lean and devops approach to teach Lean Software Development
International Workshop on Software Engineering Aspects of Continuous Development and New Paradigms of Software Production and Deployment, 2018Co-Authors: V K Ivanov, Dmitry Krasnikhin, Stanislav Litvinov, Sergey Masyagin, Giancarlo SucciAbstract:This paper describes application of Lean methodology in IT education in a context of an undergraduate course on “Lean Software Development” with a full devops pragmatics in mind. Strong connection between Software Development and delivery processes can be build on top of established Lean practices. Which means that implementation of end-to-end automation by devops approach needs good understanding of Lean principles and mindset. The course exposes students to the core concepts underneath Lean Development in Software engineering, beyond myths and legends, emphasizing how it relates to the general principles of Lean Development.
-
Lean Software Development in action
2014Co-Authors: Andrea Janes, Giancarlo SucciAbstract:This book illustrates how goal-oriented, automated measurement can be used to create Lean organizations and to facilitate the Development of Lean Software, while also demonstrating the practical implementation of Lean Software Development by combining tried and trusted tools. In order to be successful, a Lean orientation of Software Development has to go hand in hand with a companys overall business strategy. To achieve this, two interrelated aspects require special attention: measurement and experience management. In this book, Janes and Succi provide the necessary knowledge to establish Lean Software company thinking, while also exploiting the latest approaches to Software measurement. A comprehensive, company-wide measurement approach is exactly what companies need in order to align their activities to the demands of their stakeholders, to their business strategy, etc. With the automatic, non-invasive measurement approach proposed in this book, even small and medium-sized enterprises that do not have the resources to introduce heavyweight processes will be able to make their Software Development processes considerably more Lean. The book is divided into three parts. Part I, Motivation for Lean Software Development, explains just what Lean Production means, why it can be advantageous to apply Lean concepts to Software engineering, and which existing approaches are best suited to achieving this. Part II, The Pillars of Lean Software Development, presents the tools needed to achieve Lean Software Development: Non-invasive Measurement, the Goal Question Metric approach, and the Experience Factory. Finally, Part III, Lean Software Development in Action, shows how different tools can be combined to enable Lean Thinking in Software Development. The book primarily addresses the needs of all those working in the field of Software engineering who want to understand how to establish an efficient and effective Software Development process. This group includes developers, managers, and students pursuing an M.Sc. degree in Software engineering.
Pilar Rodríguez - One of the best experts on this subject based on the ideXlab platform.
-
Advances in Using Agile and Lean Processes for Software Development
Advances in Computers, 2019Co-Authors: Pilar Rodríguez, Mika V. Mäntylä, Markku Oivo, Lucy Ellen Lwakatare, Pertti Seppänen, Pasi KuvajaAbstract:Abstract Software Development processes have evolved according to market needs. Fast changing conditions that characterize current Software markets have favored methods advocating speed and flexibility. Agile and Lean Software Development are in the forefront of these methods. This chapter presents a unified view of Agile Software Development, Lean Software Development, and most recent advances toward rapid releases. First, we introduce the area and explain the reasons why the Software Development industry begun to move into this direction in the late 1990s. Section 2 characterizes the research trends on Agile Software Development. This section helps understand the relevance of Agile Software Development in the research literature. Section 3 provides a walk through the roots of Agile and Lean thinking, as they originally emerged in manufacturing. Section 4 develops into Agile and Lean for Software Development. Main characteristics and most popular methods and practices of Agile and Lean Software Development are developed in this section. Section 5 centers on rapid releases, continuous delivery, and continuous deployment, the latest advances in the area to get speed. The concepts of DevOps, as a means to take full (end-to-end) advantage of Agile and Lean, and Lean start-up, as an approach to foster innovation, are the focus of the two following 6 DevOps , 7 The Lean Startup Movement . Finally, Section 8 focuses on two important aspects of Agile and Lean Software Development: (1) metrics to guide decision making and (2) technical debt as a mechanism to gain business advantage. To wrap up the chapter, we peer into future directions in the area.
-
Supporting Lean Software enterprises with agile Development methods
2014Co-Authors: Harri Kaikkonen, Janne Harkonen, Harri Haapasalo, Pilar RodríguezAbstract:Lean principles have been seen as a potential answer to the current issues of faster Development cycles and more frequent releases, as Software businesses are changing towards more service-oriented offerings and cloud-based business structures. Agile Software Development methods have played an important role in resolving the same issues at Development level. This article creates a framework for Lean Software enterprise theory by linking Lean theory, Lean Software Development, and agile Software Development methods. The findings are tested through an empirical study conducted in two significant Software engineering organizations. This article presents a conceptual Lean Software Development system that clearly combines Lean and agile. The important role of people and culture is also emphasized. Agile Software Development methods are characterized as the tools of Lean Software Development and while Lean Software Development is seen as a change beyond agile, agile approach is required for competitive advantage.
-
Supporting Lean Software Enterprises with Agile Development Methods-Identifying the Relationship between Lean and Agile
2014Co-Authors: Harri Kaikkonen, Janne Harkonen, Harri Haapasalo, Pilar RodríguezAbstract:Lean principles have been seen as a potential answer to the current issues of faster Development cycles and more frequent releases, as Software businesses are changing towards more service-oriented offerings and cloud-based business structures. Agile Software Development methods have played an important role in resolving the same issues at Development level. This article creates a framework for Lean Software enterprise theory by linking Lean theory, Lean Software Development, and agile Software Development methods. The findings are tested through an empirical study conducted in two significant Software engineering organizations. This article presents a conceptual Lean Software Development system that clearly combines Lean and agile. The important role of people and culture is also emphasized. Agile Software Development methods are characterized as the tools of Lean Software Development and while Lean Software Development is seen as a change beyond agile, agile approach is required for competitive advantage.
-
building Lean thinking in a telecom Software Development organization strengths and challenges
International Conference on Software and System Process, 2013Co-Authors: Pilar Rodríguez, Kirsi Mikkonen, Markku Oivo, Pasi Kuvaja, Juan GarbajosaAbstract: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’.
-
Combining Lean thinking and agile Software Development : how do Software-intensive companies use them in practice?
2013Co-Authors: Pilar RodríguezAbstract:Software engineering is advancing according to market needs. Consequently, Software Development methods that initially caused controversies such as Agile, and more recently Lean, are increasingly being adopted by the Software industry. Particularly, Lean Software Development, which was initially regarded as one of the Agile methods, is acquiring an identity of its own as a means to scale Agile. However, Lean thinking is still open to interpretation in the domain of Software Development, which differs fundamentally from the manufacturing domain where Lean originally emerged. Specific issues such as the essence of Lean Software Development, the compatibility of Lean and Agile and the best combination of them are not properly understood. This dissertation addresses Lean thinking and its combination with Agile in the field of Software Development, by providing empirical evidence on how Software-intensive organisations use them in practice. The research was performed in four phases. First, the relevant literature was analysed to identify research opportunities. Second, a survey strategy was used to investigate status and trends in the adoption of Agile and Lean. The third phase explored in detail how Agile and Lean are combined in practice, by conducting case studies on two large-scale, industryleading companies that were transforming their processes from Agile Software Development into Lean Software Development. Finally, in the fourth phase, the results of the previous research phases were synthetized to draw conclusions and outline implications. The results of the study confirmed the interest of practitioners in using a combination of Agile and Lean. Unlike in manufacturing, the borders of Agile and Lean are not clearly defined in the Software domain. The results provided evidence of numerous compatibilities between Agile and Lean in Software Development. Generally, the use of Agile methods at a prescriptive level is guided by Lean principles. However, Lean thinking also brings new practical elements to Software Development processes, such as Kanban, work-in-progress limits, a ‘pull’ and ‘less waste’oriented culture and an extended emphasis on transparency and collaborative Development. The results showed the fundamental importance of practices that enable quick feedback, fast learning and adaptation.
Xiaofeng Wang - One of the best experts on this subject based on the ideXlab platform.
-
Lean Software Development what exactly are we talking about
Lean Enterprise Software and Systems, 2013Co-Authors: Oisin Cawley, Xiaofeng Wang, Ita RichardsonAbstract:As the Software Engineering landscape continues to evolve and new paradigms are introduced, there can be a tendency for both industry and academia to enthusiastically embrace new approaches and march forward under whatever banner conventional wisdom has decided to adopt. One such banner is Lean Software Development, a paradigm that continues to see a growth in interest driven by the need for cost reductions within industry. The term Lean attracts the attention of business, but precisely how it applies within Software Development is still being debated. In addition, its relationship to the better understood agile methodologies is also a topic for debate. Having been drawn into this research area ourselves, we present here a review of Lean Software Development and try to distil out for the reader some understanding of this somewhat undefined topic. We conclude with some thoughts on where this subject might go to from here.
-
LESS - Lean Software Development – What Exactly Are We Talking About?
Lean Enterprise Software and Systems, 2013Co-Authors: Oisin Cawley, Xiaofeng Wang, Ita RichardsonAbstract:As the Software Engineering landscape continues to evolve and new paradigms are introduced, there can be a tendency for both industry and academia to enthusiastically embrace new approaches and march forward under whatever banner conventional wisdom has decided to adopt. One such banner is Lean Software Development, a paradigm that continues to see a growth in interest driven by the need for cost reductions within industry. The term Lean attracts the attention of business, but precisely how it applies within Software Development is still being debated. In addition, its relationship to the better understood agile methodologies is also a topic for debate. Having been drawn into this research area ourselves, we present here a review of Lean Software Development and try to distil out for the reader some understanding of this somewhat undefined topic. We conclude with some thoughts on where this subject might go to from here.
-
Agile and Lean Service-Oriented Development: Foundations, Theory, and Practice
2012Co-Authors: Xiaofeng Wang, Isidro Ramos, Richard VidgenAbstract:Challenges in unpredictable markets, changing customer requirements, and advancing information technologies have lead to progression towards service oriented engineering and agile and Lean Software Development. These prevailing approaches to Software systems provide solutions to challenges in demanding business environments.Agile and Lean Service-Oriented Development: Foundations, Theory and Practice explores the groundwork of service-oriented and agile and Lean Development and the conceptual basis and experimental evidences for the combination of the two approaches. Highlighting the best tools and guidelines for these Developments in practice, this book is essential for researchers and practitioners in the Software Development and service computing fields.
-
leagile Software Development an experience report analysis of the application of Lean approaches in agile Software Development
Journal of Systems and Software, 2012Co-Authors: Xiaofeng Wang, Kieran Conboy, Oisin CawleyAbstract:In recent years there has been a noticeable shift in attention from those who use agile Software Development toward Lean Software Development, often labelled as a shift ''from agile to Lean''. However, the reality may not be as simple or linear as this label implies. To provide a better understanding of Lean Software Development approaches and how they are applied in agile Software Development, we have examined 30 experience reports published in past agile Software conferences in which experiences of applying Lean approaches in agile Software Development were reported. The analysis identified six types of Lean application. The results of our study show that Lean can be applied in agile processes in different manners for different purposes. Lean concepts, principles and practices are most often used for continuous agile process improvement, with the most recent introduction being the kanban approach, introducing a continuous, flow-based substitute to time-boxed agile processes.
-
Leagile Software Development
Journal of Systems and Software, 2012Co-Authors: Xiaofeng Wang, Kieran Conboy, Oisin CawleyAbstract:In recent years there has been a noticeable shift in attention from those who use agile Software Development toward Lean Software Development, often labelled as a shift "from agile to Lean". However, the reality may not be as simple or linear as this label implies. To provide a better understanding of Lean Software Development approaches and how they are applied in agile Software Development, we have examined 30 experience reports published in past agile Software conferences in which experiences of applying Lean approaches in agile Software Development were reported. The analysis identified six types of Lean application. The results of our study show that Lean can be applied in agile processes in different manners for different purposes. Lean concepts, principles and practices are most often used for continuous agile process improvement, with the most recent introduction being the kanban approach, introducing a continuous, flow-based substitute to time-boxed agile processes.