Lean Software Development Theory Validation in Terms of Cost-Reduction and Quality- Improvement
Total Page:16
File Type:pdf, Size:1020Kb
View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Göteborgs universitets publikationer - e-publicering och e-arkiv Lean Software Development Theory validation in terms of cost-reduction and quality- improvement Bachelor of Science Thesis in Software Engineering and Management Christos Svitis University of Gothenburg Chalmers University of Technology Department of Computer Science and Engineering Göteborg, Sweden, July 2013 The Author grants to Chalmers University of Technology and University of Gothenburg the non-exclusive right to publish the Work electronically and in a non-commercial purpose make it accessible on the Internet. The Author warrants that he/she is the author to the Work, and warrants that the Work does not contain text, pictures or other material that violates copyright law. The Author shall, when transferring the rights of the Work to a third party (for example a publisher or a company), acknowledge the third party about this agreement. If the Author has signed a copyright agreement with a third party regarding the Work, the Author warrants hereby that he/she has obtained any necessary permission from this third party to let Chalmers University of Technology and University of Gothenburg store the Work electronically and make it accessible on the Internet. Lean Software Development Theory validation in terms of cost-reduction and quality-improvement Christos Svitis © Christos Svitis, July 2013. Examiner: Lars Pareto University of Gothenburg Chalmers University of Technology Department of Computer Science and Engineering SE-412 96 Göteborg Sweden Telephone + 46 (0)31-772 1000 Department of Computer Science and Engineering Göteborg, Sweden, July 2013 Abstract System [2], and have been successfully applied in many manufacturing and product development organizations. The pace of change in software development industry During the last few years, Lean develop-ment has also remains at high. People continue to push the boundaries become popular within the software industry. Its of known techniques and practices in an effort to develop popularity is due to its effectiveness in identifying and software as efficiently and effectively as possible. Lean eliminating waste, and quickly responding to changing software development has emerged as an alternative to customer and market demands. comprehensive methods designed primarily for very large projects. Key objective of Lean is fast development and 1.2. Purpose delivery of a high quality system at a relatively low investment cost. In this study, an investigation on Lean’s There is a growing body of literature on Lean software validity was conducted, by examining several organiza- development, with Poppendiecks’ book [3] being the tions which have been developing software according to “cornerstone” of Lean’s theory. Mary and Tom Poppen- Lean’s thinking. The outcome of this research was the dieck tailored the principles of Toyota’s production validation of the cost-effectiveness of Lean and of its process [1] to fit in the software engineering domain, and impact on the quality of a software system. introduced Lean as a software development process. Thereafter, influenced by their work [3] [4], a large body Keywords: Lean software development, cost-reduction, quality- of knowledge on Lean has become available. Several improvement, validation researchers have discussed advantages and disadvantages of Lean in relation to more traditional software develop- ment processes [5] [6], while others have focused on 1. Introduction identifying limitations and problems associated with Lean implementations [7] [8]. However, despite the This section gives a brief overview of the subject and variety of literature about Lean software development, theme of this study. It presents the background and the one that confirms its functionality is hard to be found. problem domain of the topic under study, and describes The purpose of this study is to assess the applicability the purpose of this thesis together with a definition of the of Lean’s theory in real situations. In other words, to research questions. investigate if Lean in practice has the results that the theory promises (similarities and differences between 1.1. Background Lean ‘in theory’ and ‘in practice’). The research was divided in two phases. Every software development organization is using a The first phase was an exploration of Lean’s theory process for the development of its products. In most and its thinking principles. This was done by reading cases, the process is adapted to each organization’s size, existing literature – especially the ones by Poppendieck resources, and needs, but the core characteristics are [3] [4] – on Lean’s theory. That helped in obtaining a based on one (or more than one) of the “standard” deeper understanding of the theoretical assumptions of development methodologies. “A system development Lean and of its seven principles. In this, the cost- and methodology refers to the framework that is used to quality-related principles/aspects of Lean were of prima- structure, plan, and control the process of developing an ry interest, and hence focus was put on these. The know- information system.” [1] However, statistics have shown ledge gained from this phase, formed the theoretical that large number of software projects does not meet their “ground” for the qualitative analysis of the second phase. expectations in terms of functionality, cost, or delivery The second – and most crucial – phase was to validate schedule [29]. This is mainly owed to the “rigidity” of the theoretical findings by comparing them with results the traditional development processes, and their inability from Lean implementations. Data regarding results of to effectively deal with the various challenges of today’s Lean’s implementations was collected in a series of software industry. Therefore, more and more companies interviews and a case study review from various are looking for better alternatives to improve the software organizations that have implemented Lean as their quality, reduce the development cost, and meet the development process. The results from the case study market demands and customer satisfaction. Lean review and the interviews were used to validate if Lean’s software development emerged as an alternative to theory is successful in real world applications, and the document-driven, rigorous traditional development success rate thereof. approaches. Lean’s philosophy is reducing the develop- ment time by removing all nonvalue-adding wastes. Lean thinking principles are based on the Toyota Production 1.3. Research Questions It is accepted as true that Lean was first introduced in Japan - mainly in Toyota Production System - but history In order to address the above objectives, two sets of also shows that Henry Ford had been applying parts of research questions were formulated to drive through the Lean in the year 1920. “One of the most noteworthy research process. As Creswell [9] describes, the research accomplishments in keeping the price of Ford products questions serve to narrow and focus the purpose of the low is the gradual shortening of the production cycle. study. The longer an article is in the process of manufacture and the more it is moved about, the greater is its ultimate Research questions of phase 1 (literature review): cost.” [10] How can Lean software development (theoretically) In the end of 19th century, the concept of Lean produ- reduce the cost of a software product? ction started with a need of mass production system. How can Lean software development (theoretically) Frederick Winslow Taylor on his time first thought about improve the quality of a software product? the high production system known as mass production, and it was presented in his book “The principles of Having these questions in mind during the review of Scientific Management” [11]. related books/articles, helped in identifying the After the Second World War, an engineer from Toyota theoretical aspects of Lean related to cost-reduction and named Eiji Toyoda visited the Ford Plant. He noticed that quality-improvement. This gave a deeper knowledge and everything was functioning smoothly, but there were understanding of Lean’s theory and of its thinking princi- wastes in essence but not in concept [12]. Eiji Toyoda ples, and set the theoretical basis of the second phase. observed waste everywhere in Ford’s process. After- wards, Eiji Toyoda with Taiichi Ohno (a production Research questions of phase 2 (interviews & case study manager from Toyota) recognized that Ford production review): system was not going to work for Japan, due to, but not Can Lean software development (in practice) reduce limited to, Japan’s infrastructure. They started to improve the cost of a software product, and how? Ford’s production system, in order to make it applicable Can Lean software development (in practice) for them [13]. Afterwards, Toyota developed the process, improve the quality of a software product, and how? which is now known as Toyota Production System. Taiichi Ohno explained the concept as “All we are doing The answer to these questions was the outcome of the is looking at the timeline from the moment the customer comparison between the theoretical assumptions of Lean gives us an order to the point when we collect the cash. and the results of the data analysis, and is being present- And we are reducing the timeline by removing the non- ed in Sections 5 & 6. value added wastes.” [14] Toyota changed the system and did continued improvements; however, it took almost 1.4. Document Outline 30 years for Taiichi Ohno to make it perfect for Toyota and make it as it is today. The paper is structured as follows: Section 2 gives an Lean Production System is mainly described in the overview of the theoretical frameworks used in this study book “The Machine that Changed the World” by James (Lean software development theory). Section 3 describes Womack, Daniel Jones, and Daniel Roos [12]. In that the research design and methodology used in this study, book, the authors mention that Lean Production System while in Section 4 the results of the study are presented.