• Refine Query
  • Source
  • Publication year
  • to
  • Language
  • 10
  • 3
  • 2
  • 1
  • Tagged with
  • 16
  • 16
  • 16
  • 10
  • 6
  • 6
  • 5
  • 4
  • 3
  • 3
  • 3
  • 3
  • 3
  • 3
  • 3
  • About
  • The Global ETD Search service is a free service for researchers to find electronic theses and dissertations. This service is provided by the Networked Digital Library of Theses and Dissertations.
    Our metadata is collected from universities around the world. If you manage a university/consortium/country archive and want to be added, details can be found on the NDLTD website.
1

Exploring the difference between Agile and Lean:A stakeholder perspective

Islam, Mohammad Shahidul, Tura, Sentayehu January 2013 (has links)
In this thesis, we have identified the difference between Agile and Lean methodsbased on stakeholder’s perspectives. To achieve the goal we have dealwith only Agile and Lean principles. In addition, in order to identify thestakeholders from Agile and Lean principles we have used the relevant practicesfrom both sides. As the principles of Agile manifesto are directly followedby most of the organizations, we have also used Agile principles directlyin this research. On the other hand lean methods have no pure principles,as a result we have used the most common and popular lean principlesderived from different authors. We have only considered the mostrelevant principles that might be useful in software development. To achievea stronger result of this thesis we have also considered stakeholder theory.Moreover we have identified the stakeholder’s involvement with Agile/Leanprinciples and stakeholder theory.
2

LUT : En metod för systemutveckling med lean software development / LUT : A method for system development with lean software development

Björklund, Patrik January 2011 (has links)
Traditionell systemutveckling präglas ofta av långa utvecklingsprocesser och en oförmåga attmöta förändrade behov från kunden. Problematik med buggar i mjukvaran och förskjutnadeadlines uppstår kontinuerligt och leder till högre kostnader för företag.För att komma till rätta med dessa problem behövs en systemutvecklingsprocess som belyserproblem direkt när de uppstår och därmed tvingar de inblandade till reflektion över processensom skapar problemen vilket belyser de verkliga bakomliggande orsakerna. Låg kvalitet påmjukvara är ofta ett symptom på djupare organisatoriska problemEtt synsätt som syftar till att möta dessa problem är lean software development. Synsättet harinspirerats av lean production som är en beskrivning av The Toyota Production system vilketi sin tur är det arbetssätt som har tillämpats av Toyota under flera decennier i den traditionellatillverkningen.Mary och Tom Poppendieck har beskrivit sju principer och 22 tankeverktyg som kananvändas för att skapa en metod för lean software development. Studien visar vilka styrkoroch problem som lean software development och lean production beskriver generellt samtvilka styrkor och problem som finns avseende beskrivning av Poppendieck's principer ochtankeverktyg i synnerhet. Detta visar den förbättring som behöver göras av principerna ochtankeverktygen för att de ska kunna användas som underlag för en metod för lean softwaredevelopment samt hur denna metod ser ut konkret.Studiens resultat är en metod för lean software development baserad på Poppendieck &Poppendieck’s principer och tankeverktyg vid namn LUT – Lean systemUTveckling. / Program: Kandidatutbildning i informatik
3

A contribuição da indústria da manufatura no desenvolvimento de software / The contribution of manufacturing industry in software development

Eduardo Teruo Katayama 20 October 2011 (has links)
Os Métodos Ágeis surgiram no final da década de 90, como uma alternativa aos métodos prescritivos de desenvolvimento de software. Eles propõem uma nova abordagem de desenvolvimento, eliminando gastos com documentação excessiva e burocrática, enfatizando a interação entre as pessoas e as atividades que efetivamente trazem valor ao cliente. Nos últimos anos, diversos princípios e práticas baseados na indústria de manufatura foram incorporadas pelos Métodos Ágeis de desenvolvimento de software. Um dos princípios absorvidos é o de melhorar a eficácia de uma organização através de melhorias globais. Embora este princípio seja bem difundido nos Métodos Ágeis, utilizá-lo não é uma tarefa fácil. Nem sempre é fácil ter uma visão global do processo de desenvolvimento. Além disso, para realizar melhorias globais é necessário descobrir a causa para possíveis problemas, o que também pode ser uma tarefa difícil. Esse trabalho investiga duas abordagens da indústria de manufatura que enxergam uma organização como um sistema no qual todas as partes são inter-relacionadas. Com base nelas, três abordagens de desenvolvimento de software existentes são analisadas. Finalmente, um estudo comparativo foi feito para avaliar as principais características dos métodos de desenvolvimento estudados. Esse estudo estende o trabalho feito por Abrahamssom et al., no livro Agile Software Development: Current Research and Future Directions, avaliando o desempenho dos métodos seguindo o arcabouço proposto pelos mesmos autores. / Agile methods appeared in the late 90\'s as an alternative approach to the classic prescriptive planning approaches to software development. They propose a new style of development, eliminating excessive and bureaucratic documentation, and emphasizing the interactions between people collaborating to achieve high productivity and deliver high-quality software. In the last few years, several principles and practices based on the manufacturing industry were incorporated by Agile software development. One of the principles absorbed is to improve the effectiveness of an organization through an overall improvement. Although this principle is quite widespread in Agile Methods, using it is not an easy task. It is not easy to get the big picture of the development process. Moreover, to achieve overall improvements is necessary to discover the cause of possible problems, which can also be a difficult task. This work investigates two approaches in the manufacturing industry that shares the assumption that the whole organization is focused on overall throughput, not on micro-optimization. Based on then, three approaches to existing software development are analyzed. Finally, a comparative study was done to assess the main characteristics of the studied methods. This study extends the work done by Abrahamssom et al. In the book Agile Software Development: Current Research and Future Directions, evaluating the performance of the methods following the framework proposed by the same authors.
4

A contribuição da indústria da manufatura no desenvolvimento de software / The contribution of manufacturing industry in software development

Katayama, Eduardo Teruo 20 October 2011 (has links)
Os Métodos Ágeis surgiram no final da década de 90, como uma alternativa aos métodos prescritivos de desenvolvimento de software. Eles propõem uma nova abordagem de desenvolvimento, eliminando gastos com documentação excessiva e burocrática, enfatizando a interação entre as pessoas e as atividades que efetivamente trazem valor ao cliente. Nos últimos anos, diversos princípios e práticas baseados na indústria de manufatura foram incorporadas pelos Métodos Ágeis de desenvolvimento de software. Um dos princípios absorvidos é o de melhorar a eficácia de uma organização através de melhorias globais. Embora este princípio seja bem difundido nos Métodos Ágeis, utilizá-lo não é uma tarefa fácil. Nem sempre é fácil ter uma visão global do processo de desenvolvimento. Além disso, para realizar melhorias globais é necessário descobrir a causa para possíveis problemas, o que também pode ser uma tarefa difícil. Esse trabalho investiga duas abordagens da indústria de manufatura que enxergam uma organização como um sistema no qual todas as partes são inter-relacionadas. Com base nelas, três abordagens de desenvolvimento de software existentes são analisadas. Finalmente, um estudo comparativo foi feito para avaliar as principais características dos métodos de desenvolvimento estudados. Esse estudo estende o trabalho feito por Abrahamssom et al., no livro Agile Software Development: Current Research and Future Directions, avaliando o desempenho dos métodos seguindo o arcabouço proposto pelos mesmos autores. / Agile methods appeared in the late 90\'s as an alternative approach to the classic prescriptive planning approaches to software development. They propose a new style of development, eliminating excessive and bureaucratic documentation, and emphasizing the interactions between people collaborating to achieve high productivity and deliver high-quality software. In the last few years, several principles and practices based on the manufacturing industry were incorporated by Agile software development. One of the principles absorbed is to improve the effectiveness of an organization through an overall improvement. Although this principle is quite widespread in Agile Methods, using it is not an easy task. It is not easy to get the big picture of the development process. Moreover, to achieve overall improvements is necessary to discover the cause of possible problems, which can also be a difficult task. This work investigates two approaches in the manufacturing industry that shares the assumption that the whole organization is focused on overall throughput, not on micro-optimization. Based on then, three approaches to existing software development are analyzed. Finally, a comparative study was done to assess the main characteristics of the studied methods. This study extends the work done by Abrahamssom et al. In the book Agile Software Development: Current Research and Future Directions, evaluating the performance of the methods following the framework proposed by the same authors.
5

Lean software development v testovacím týmu / Lean software development in testing team

Chodura, Ondřej January 2012 (has links)
This diploma thesis describes the position of software testing according to Lean software development approach and its appliacation in testing team. At first. Lean concept is introduced with its basic principles, then the thesis focuses on the position of testing in the Lean software development itself. At the beginning this thesis deals with agile approach to development and software testing position in Lean software development. This concept defines several principles, which should be followed by testing teams. These principles and its general application in testing teams are subsequently explained. The second part is devoted to Lean software development in a real company. I am working as a tester and I already know the development and testing processes -- that's why one of my goals is to apply this approach to our testing team. Firstly the default situation in our company is introduced. Used technics and types of used testing tools are listed together with procedures and also the disadvantages and troubles, which occurred during the original testing process. Then the following parts are devoted to Lean software development principles application in our testing team followed with description of improvements and advantages delivered by the principles.
6

The Right Way to do IT : Waste Identification and Reduction at Software Providers - a Case Study at Infor M3

Johansson, Adam, Ryen, Jonathan January 2017 (has links)
When delivering Software as a Service (SaaS), increased challenges regarding responsiveness and flexibility are introduced to software providers. In order to address these challenges and attain customer satisfaction, the Lean Software Development principle Eliminate waste can be applied. One organization that has recognized the potential of applying the Eliminate waste principle when developing software is the Integration & BI unit of the Enterprise Resource Planning system provider Infor M3. However, the implementation of the Eliminate waste principle at the Integration & BI unit’s five teams is still in an early stage. Consequently, the intended purpose of the thesis was to identify waste and suggest approaches to reduce waste at the case organization, Infor M3 Integration & BI. In order to collect the in-depth knowledge required, the thesis utilized a qualitative case study methodology, whereby a literature review, interviews and observations were conducted. The literature review created a foundation of knowledge regarding waste in software development, that subsequent culminated as a basis for the analysis and recommendations. It could be concluded that the subject of waste identification and reduction in software development is in an early stage, largely driven by practitioners, with few verifying studies that support the subject’s applicability. However, by utilizing a waste categorization model various wastes could be identified at all of Integration & BI’s teams during the interviews, whereupon Partially done work, Delays, Task switching and Relearning was considered as the most prominent wastes. Moreover, it could be established that one team had developed successful approaches that eliminates much of the team’s waste whilst the other teams’ approaches were generally deficient. In order to more successfully reduce waste, the Integration & BI unit is suggested to create awareness of the concept of waste within the unit. The teams need a common definition and an increased understanding of waste in order to reach this awareness. Additionally, the unit is suggested to use more comprehensive indicators, like cumulative flow diagram, in order to facilitate identification and root-cause analysis of waste. Lastly, the unit is recommended to reduce waste by continuous improvements with activities structured as a PDSA-cycle. / Programvaruföretag som levererar Software as a Service (SaaS) står inför ökade utmaningar med avseende på receptivitet och flexibilitet. För att bemöta dessa utmaningar och uppnå hög kundnöjdhet kan Lean Software Development principen Eliminera slöseri appliceras. En organisation som har insett potentialen av att tillämpa principen Eliminera slöseri vid utveckling av programvara är enheten Integration & BI hos affärssystemleverantören Infor M3. Implementeringen av principen vid enhetens fem utvecklingslag är emellertid fortfarande i ett tidigt skede. Avsikten med examensarbetet var således att identifiera slöseri och föreslå tillvägagångssätt för att minska slöseri hos fallorganisationen, Infor M3 Integration & BI. För att samla in en djup förståelse om ämnet och fallföretaget utnyttjade examensarbetet en kvalitativ fallstudiemetodik, där en litteraturstudie, intervjuer och observationer genomfördes. Litteraturstudien skapade kunskap angående slöseri inom mjukvaruutveckling, vilken senare skapade en grund för både analys och rekommendationer. Slutsatsen att ämnet rörande identifiering och minimering av slöseri inom mjukvaruutveckling är i ett tidigt skede kunde göras i och med att ämnet i stor utsträckning drivs av yrkesutövare och inte av akademin. Dessutom finns det få vetenskapliga studier som verifierar ämnets applicerbarhet. Genom att använda en modell för att kategorisera olika slöseri inom mjukvaruutveckling kunde dock olika typer av slöseri identifieras hos samtliga av Integration & BIs utvecklingslag, varpå delvist gjort arbete, förseningar, uppgiftsbyte och återinlärning betraktades som de mest framträdande. Dessutom kunde det fastställas att ett av utvecklingslagen etablerat framgångsrika tillvägagångssätt för att eliminera slöseri under tiden de andra utvecklingslagens metoder generellt var bristfälliga. För att mer framgångsrikt minska slöseri, föreslås enheten Integration & BI att använda en gemensam definition och öka förståelsen om konceptet slöseri för att skapa en medvetenhet inom enheten. Dessutom rekommenderas enheten att använda mer omfattande indikatorer så som kumulativt flödesschema för att underlätta identifiering och rotorsaksanalys av slöseri. Slutligen föreslås enheten att eliminera slöseri genom ständiga förbättringar med aktiviteter strukturerade efter PDSA-cykeln.
7

Waste in Lean Software Development : A Root Cause Analysis / Waste in Lean Software Development : A Root Cause Analysis

Medidi, Prasadbabu January 2015 (has links)
Context: Removal of wastes is a crucial area in lean software development. It has been found that there was little evidence on root causes of wastes in lean software development. Root causes from the state of practice had not being investigated. Furthermore, relations between wastes were now successfully exposed through root cause identifications process. Objectives: The objective of this study was to perform an in-depth investigation to identify causes which lead to wastes in Lean software development process in the context of medium to large software development. To this end, researcher also identified relationships that exist between wastes. Methods: The researcher conducted Literature review to look for evidence on waste related activities offered in peer-reviewed literature. Furthermore, the author conducted seven semi-structured interviews and used Grounded Theory method for both literature and interview data analysis. Results: The researcher identified three categories of factors of wastes. Namely, Technical, Non-technical and Global software product development. In the technical category, factors relating to different technical aspects to build a product such as required resource issues, solving complexity issues among others were identified. Similarly, factors relating to people knowledge, management issues as well as factors that bothered on communication, coordination and temporal distance were identified as non-technical and global software product development respectively. For all seven kinds of wastes the root causes were identified. / 0046734784551
8

Projektledning inom Lean IT / Project management within Lean IT

Pettersson, Anton, Bredberg, Christoffer January 2011 (has links)
Inom IT-branschen läggs det mycket resurser på att effektivisera arbetssätt, och att hitta det optimala sättet att styra och leda projekt är en ständig utmaning. Dagens IT-organisationer befinner sig även i en situation där marknaden ställer krav på minskade kostnader men samtidigt en högre nivå av support och service. Utifrån detta har det genererats en uppsjö olika arbetssätt och tillhörande verktyg som alla har som mål att strukturera eller effektivisera systemutvecklingsprocessen. Ett av dessa arbetssätt är Lean IT som hämtar sina grunder från det väl beprövade produktionssystemet Lean Manufacturing.Inom systemutvecklingsbranschen arbetas det ofta i projektform och att ha en bra projektledning är ofta en av faktorerna bakom ett lyckat projekt. För att en projektledare ska kunna leda projektet till framgång krävs det att denne har en bra uppfattning om arbetssättet inom organisationen och projektgruppen. Denna rapport fokuserar därför på om en projektledares arbetsuppgifter inom Lean IT förändras gentemot ett mer traditionellt arbetssätt, och i så fall hur projektledarens arbetsuppgifter ser ut inom Lean IT. Informationen i studien har samlats ihop genom intervjuer med ett flertal kontaktpersoner på tre olika företag som alla inkorporerar Lean IT i sina arbetssätt, samt via deltagande observation på ett mikroföretag inom systemutvecklingsbranschen i Borås.Genom att jämföra insamlad data om en projektledares arbetsuppgifter i Lean IT-projekt med den traditionella projektledarens arbetsuppgifter som dessa är beskrivna i litteratur, har ett antal skillnader påvisats. Lean IT förespråkar ett mycket närmare samarbete mellan projektgruppen och projektledaren och en mer intensiv involvering i projekt från projektledarens sida, och detta visar sig i rapporten överensstämma med hur de studerade företagen har använt Lean IT i praktiken. Dessutom konstateras det att projektledning inom Lean IT på många nivåer är starkt relaterad till traditionell projektledning. Istället för att ha resulterat i helt nya arbetsuppgifter grundar sig snarare projektledning inom Lean IT i den traditionella projektledningen och därifrån vidareutvecklat sättet att arbeta på. / Program: Systemarkitekturutbildningen
9

Potential metrics for Agile and Lean : Systematic Literature Review and Survey

Maddila, Kalyan Chakravarthy January 2015 (has links)
Context: Despite continuously increasing importance of Agile and Lean in software development, the number of studies that investigate on use of metrics relevant to Agile or Lean are limited and yet few studies implements was unclear. Unclear is which are the prominent metrics that are useful in industries, and their purpose of usage. Objectives: Main goal of this study is to find the metrics useful in Agile and Lean practicing industries; that are evaluated in industries by systematically identifying all the metrics from empirical evidence found in Literature as well as verifying which of them are prominently being used in industries. In addition, the purpose of using these metrics in industries are reported, and causes for dissatisfaction on use of some of the identified metrics among surveyed companies are investigated and reported. Methods: Two research methodologies are used; Systematic Literature Review (SLR) and Industrial Survey. SLR is performed using snowballing as search approach to select primary studies. SLR is used to identify all the metrics that are useful for Agile and Lean software development. Rigor and relevance analysis is performed to assess the quality of the resulted primary studies. Industrial survey was conducted in order to verify and extend the empirical evidence exists in Literature regarding metrics by finding which of them are more prominently being used. Moreover causes for dissatisfaction over outcome of metrics use for process improvements were observed by performing comparative analysis between unsatisfied respondents results and satisfied respondents results. Results: In total 20 metrics were identified from the studies having high rigor and high relevance. Moreover 11 out of these 20 metrics were identified to be prominently being used in industries using survey and other 9 metrics are found useful for Agile or Lean methods but need more awareness. Evidence from both SLR and survey shows that most of these identified or potential metrics are used for time associated purposes which are predictability, tracking, forecasting or planning, and very little evidence found for metrics that are being used directly for quality purpose. It was observed that some of the surveyed respondents who answered not satisfied with the metrics being used are not aware of the potential benefits these metrics can offer in Agile or Lean settings. Conclusion: Evidence from both SLR and survey shows that the identified 20 metrics are very important and useful for Agile or Lean methods. 11 out of these 20 metrics are prominently being used by industries and evidence shows for other 9 metrics are also useful for Agile but needs more awareness for industries to realize their potential benefits in large scale. Also, more evidence is found for metrics that are used for time related purposes which are being dominant and important in industries than quality focused metrics. Therefore, it is important for industries not only to know which metrics are appropriate for Agile or Lean but also to have a deep understating of metrics behaviors. This will help to realize the level predictability these metric’s offer in order to make right assumptions or planning. / Mobile no: (+46)-723110118
10

A Systematic Literature Review and Industrial Evaluation of Incorporating Lean Methodologies in Software Engineering / A Systematic Literature Review and Industrial Evaluation of Incorporating Lean Methodologies in Software Engineering

Dwivedula, Chaitanya, Choday, Anusha January 2014 (has links)
Context: Over the recent years, ‘Lean Software Development’ (LSD) has been emerging as a significant practice in the Software Industry. The inherent nature of ‘Lean’ to efficiently handle frequently changing customer needs by minimizing ‘Waste’ is a major success factor in practicing it in the context of ‘Software Engineering’. In simple words, Lean Software Development is the true translation of Lean Manufacturing and Lean IT principles to Software Engineering. This work presents an in-depth analysis on the implication of lean methodologies from both ‘State of Art’ and ‘State of Practice’ in the context of Software Engineering. Objectives: The prime objective of the study is to investigate what methodologies were considered & adopted under lean philosophy and to present relevant evidence on the implication of lean methodologies in reference to what defines ‘lean’ in Software Engineering. An extensive literature review was aimed to find the existing challenging factors that negatively influenced the success of software projects and the respective lean mitigation methodologies that were employed by various software organizations to appease their negative impact. Industrial interviews were conducted by interviewing lean experts, with a motive to find the current state of lean implementation in software industry. The outcomes from the systematic literature review (State of Art) and the industry (State of Practice) are comparatively analysed to explore the similarities and differences on the state of lean implication. Finally, a set of guidelines are recommended that would benefit an Industrial Practitioner/Stakeholder/Academic Researcher in practicing the appropriate lean methodology in the context of software engineering. Methods: We conducted a ‘Systematic literature review’ (SLR) by systematically analyzing relevant studies and then interviewed industrial experts to validate our findings. The systematic literature review was conducted according to the guidelines proposed by Dr. Barbara Kitchenham stated in ‘Guidelines for performing Systematic Literature Reviews’ article. The thorough review helped us in identifying various challenging factors that negatively influenced the success of software projects and the respective lean mitigation methodologies that were practiced in the context of software engineering. The associated benefits of practicing the lean methodologies are also presented. The extensive review included peer reviewed articles from electronic databases such as IEEE Explore, Inspec, Scopus and ISI. In addition to this, we conducted snowball sampling on the references of the selected articles to avoid the potential risk of losing relevant and valuable information. Also, other potential sources of information such as books, theses/dissertations, white papers and website/blog articles are included as a part of Grey Literature. In this study, the articles related to the implication of lean methodologies in the context of software engineering were considered. The review included 72 primary studies published between 1993 and 2012. The primary studies were selected based on the following criteria: If they presented the challenging factors that negatively influenced the success of software projects. If they depicted the implication of lean mitigation methodologies (Tool/ Technique/ Method/ Process/ Practice/ Principle) that appeased the negative impact of the identified challenging factors that hampered the success of software projects. If they depicted the implication of lean methodologies (Tool/ Technique/ Method/ Process/ Practice/ Principle) in general or for a specific development/ Management/ Maintenance improvement activities that lead to the success of software projects in the context of software engineering. If they presented the benefits of practicing lean methodologies in the context of software engineering. The study quality assessment was done based on the quality criteria defined in the ‘Quality assessment criteria checklist’. The data such as Article ID, Article Title, Literature type (Peer- reviewed, Non-peer reviewed), Context of validation of the lean methodology (Industry/Academia), Subjects considered for the study (Researchers/students, Industrial practitioners), Type of article publication (Conference/ Journal/ Books/ Thesis Reports/ Doctoral dissertations/ Other), Research method used in the study (Case Study/ Experiment/ Experience Report/ Not stated/ Secondary Data Analysis/ Literature Review), Context of conducting the research (Industry/ Academia/ Not stated/ Both), Context of validation of the study (Strong/ Medium/ Weak), Publication date & year, Source of the publication, are extracted as a part of Quantitative analysis. The secondary data analysis for both ‘State of Art’ (Systematic literature review) and ‘State of Practice’ (Industry) was carried by performing a generic data analysis designed to answer our research questions. The more specific data such as the challenging factors that negatively influenced the success of software projects, the type of lean contribution presented i.e., the methodology being a Tool, Technique, Practice, Principal, Process or a Method, along with the benefits associated on their implication that helped us to answer our research questions are extracted as a part of qualitative analysis from the selected studies. The industrial interviews were conducted by interviewing potential lean experts who had decent experience in lean software development, to find the current state of lean implication in the software industry. In the end, a comparative analysis was performed to clearly understand the state of convergence and divergence between the results from extensive literature review and the industry with respect to the implication of lean methodologies in the context of software engineering. Results: A total of 72 primary articles were selected for data extraction. 56 articles were selected from the electronic databases that clearly depicted lean implementation in the context of software engineering. 9 articles were selected by conducting snowball sampling i.e. by scrutinizing the references of the selected primary studies and finally the grey literature resulted in 7 articles. Most of the articles discussed about lean implication in the context of software engineering. The depicted lean methodologies were validated in either Industry or Academia. A few articles depicted regarding lean principles and their benefits in the context of software engineering. Most of the selected articles in our study were peer- reviewed. Peer reviewing is a process of evaluating one’s work or performance by an expert in the same field in order to maintain or enhance the quality of work or performance in the particular field. This indicates that the articles considered for data extraction have been reviewed by potential experts in the research domain. Conclusions: This study provided a deeper insight into lean implication in the context of software engineering. The aim of the thesis is to find the challenging factors that negatively influenced the success of software projects. A total of 54 challenges were identified from the literature review. The 72 primary articles selected from various resources yielded 53 lean methodologies. The lean methodologies were grouped into Principles, practices, tools and methods. Mapping between the identified challenges and the mitigation lean methodologies is presented. Industrial interviews were conducted to find the current state of lean implication in software engineering. A total of 30 challenges were identified from the industry. A total of 40 lean methodologies were identified from the interviews. Comparative analysis was done to find the common challenges and mitigation lean methodologies between the State of art and State of practice. Based on the analysis a set of guidelines are presented at the end of the document. The guidelines benefit an industrial practitioner in practicing the appropriate lean methodology. Keywords: Lean Methodology, Lean software development, lean software management, lean software engineering, Systematic literature review, literature review. / Context: Over the recent years, ‘Lean Software Development’ (LSD) has been emerging as a significant practice in the Software Industry. The inherent nature of ‘Lean’ to efficiently handle frequently changing customer needs by minimizing ‘Waste’ is a major success factor in practicing it in the context of ‘Software Engineering’. In simple words, Lean Software Development is the true translation of Lean Manufacturing and Lean IT principles to Software Engineering. This work presents an in-depth analysis on the implication of lean methodologies from both ‘State of Art’ and ‘State of Practice’ in the context of Software Engineering. Objectives: The prime objective of the study is to investigate what methodologies were considered & adopted under lean philosophy and to present relevant evidence on the implication of lean methodologies in reference to what defines ‘lean’ in Software Engineering. An extensive literature review was aimed to find the existing challenging factors that negatively influenced the success of software projects and the respective lean mitigation methodologies that were employed by various software organizations to appease their negative impact. Industrial interviews were conducted by interviewing lean experts, with a motive to find the current state of lean implementation in software industry. The outcomes from the systematic literature review (State of Art) and the industry (State of Practice) are comparatively analysed to explore the similarities and differences on the state of lean implication. Finally, a set of guidelines are recommended that would benefit an Industrial Practitioner/Stakeholder/Academic Researcher in practicing the appropriate lean methodology in the context of software engineering. Methods: We conducted a ‘Systematic literature review’ (SLR) by systematically analyzing relevant studies and then interviewed industrial experts to validate our findings. The systematic literature review was conducted according to the guidelines proposed by Dr. Barbara Kitchenham stated in ‘Guidelines for performing Systematic Literature Reviews’ article. The thorough review helped us in identifying various challenging factors that negatively influenced the success of software projects and the respective lean mitigation methodologies that were practiced in the context of software engineering. The associated benefits of practicing the lean methodologies are also presented. The extensive review included peer reviewed articles from electronic databases such as IEEE Explore, Inspec, Scopus and ISI. In addition to this, we conducted snowball sampling on the references of the selected articles to avoid the potential risk of losing relevant and valuable information. Also, other potential sources of information such as books, theses/dissertations, white papers and website/blog articles are included as a part of Grey Literature. In this study, the articles related to the implication of lean methodologies in the context of software engineering were considered. The review included 72 primary studies published between 1993 and 2012. The primary studies were selected based on the following criteria: If they presented the challenging factors that negatively influenced the success of software projects. If they depicted the implication of lean mitigation methodologies (Tool/ Technique/ Method/ Process/ Practice/ Principle) that appeased the negative impact of the identified challenging factors that hampered the success of software projects. If they depicted the implication of lean methodologies (Tool/ Technique/ Method/ Process/ Practice/ Principle) in general or for a specific development/ Management/ Maintenance improvement activities that lead to the success of software projects in the context of software engineering. If they presented the benefits of practicing lean methodologies in the context of software engineering. The study quality assessment was done based on the quality criteria defined in the ‘Quality assessment criteria checklist’. The data such as Article ID, Article Title, Literature type (Peer- reviewed, Non-peer reviewed), Context of validation of the lean methodology (Industry/Academia), Subjects considered for the study (Researchers/students, Industrial practitioners), Type of article publication (Conference/ Journal/ Books/ Thesis Reports/ Doctoral dissertations/ Other), Research method used in the study (Case Study/ Experiment/ Experience Report/ Not stated/ Secondary Data Analysis/ Literature Review), Context of conducting the research (Industry/ Academia/ Not stated/ Both), Context of validation of the study (Strong/ Medium/ Weak), Publication date & year, Source of the publication, are extracted as a part of Quantitative analysis. The secondary data analysis for both ‘State of Art’ (Systematic literature review) and ‘State of Practice’ (Industry) was carried by performing a generic data analysis designed to answer our research questions. The more specific data such as the challenging factors that negatively influenced the success of software projects, the type of lean contribution presented i.e., the methodology being a Tool, Technique, Practice, Principal, Process or a Method, along with the benefits associated on their implication that helped us to answer our research questions are extracted as a part of qualitative analysis from the selected studies. The industrial interviews were conducted by interviewing potential lean experts who had decent experience in lean software development, to find the current state of lean implication in the software industry. In the end, a comparative analysis was performed to clearly understand the state of convergence and divergence between the results from extensive literature review and the industry with respect to the implication of lean methodologies in the context of software engineering. Results: A total of 72 primary articles were selected for data extraction. 56 articles were selected from the electronic databases that clearly depicted lean implementation in the context of software engineering. 9 articles were selected by conducting snowball sampling i.e. by scrutinizing the references of the selected primary studies and finally the grey literature resulted in 7 articles. Most of the articles discussed about lean implication in the context of software engineering. The depicted lean methodologies were validated in either Industry or Academia. A few articles depicted regarding lean principles and their benefits in the context of software engineering. Most of the selected articles in our study were peer- reviewed. Peer reviewing is a process of evaluating one’s work or performance by an expert in the same field in order to maintain or enhance the quality of work or performance in the particular field. This indicates that the articles considered for data extraction have been reviewed by potential experts in the research domain. Conclusions: This study provided a deeper insight into lean implication in the context of software engineering. The aim of the thesis is to find the challenging factors that negatively influenced the success of software projects. A total of 54 challenges were identified from the literature review. The 72 primary articles selected from various resources yielded 53 lean methodologies. The lean methodologies were grouped into Principles, practices, tools and methods. Mapping between the identified challenges and the mitigation lean methodologies is presented. Industrial interviews were conducted to find the current state of lean implication in software engineering. A total of 30 challenges were identified from the industry. A total of 40 lean methodologies were identified from the interviews. Comparative analysis was done to find the common challenges and mitigation lean methodologies between the State of art and State of practice. Based on the analysis a set of guidelines are presented at the end of the document. The guidelines benefit an industrial practitioner in practicing the appropriate lean methodology. Keywords: Lean Methodology, Lean software development, lean software management, lean software engineering, Systematic literature review, literature review. / 0091-8375920473

Page generated in 0.1511 seconds