Dissertations / Theses on the topic 'Lean and agile software'
To see the other types of publications on this topic, follow the link: Lean and agile software.
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 dissertations / theses for your research on the topic 'Lean and agile software.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Browse dissertations / theses on a wide variety of disciplines and organise your bibliography correctly.
1
Nanduri, V. S. S. N. R. Ram. "Lean + Agile vs Seven Wastes in Software Development." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4057.
Full textAbstract:
Context: Software Process Improvement uses lean principles for eliminating wastes in the software development process. Waste is defined as anything that does not add value to the customer and product. The seven traditional wastes in software engineering are partially done work, extra process, extra features, waiting, motion, task switching and defects. Using the lean principles and practices, the wastes can be reduced or eliminated. It is important to know the lean practices that are widely used in software development and to know the practices, which captures the seven wastes. From the literature, the ability of waste reduction is theoretically discussed [2], but practically only little empirical evidence is available on ‘which practice is best capable in reducing specific kinds of waste.’ Objectives: Many software development organizations have adopted lean practices and agile practices for eliminating wastes of different kinds. Therefore, this study focuses on evaluating the effectiveness of lean practices in their ability to reduce the seven types of wastes associated with Lean Software Engineering. Methodology: The methodology that is used in this study is systematic literature review and industrial survey. In order to achieve the objective on evaluating the lean practices and agile practices in their ability to reduce the seven types of wastes that have more attention in research, a systematic literature review is conducted. Thereafter, to capture the effectiveness of lean practices in waste removal, a survey is designed to capture the perception of practitioners. Results: The systematic literature review has identified 53 relevant studies to the research topic. From these primary studies, the lean practices/principles, hybrid agile and lean practices, and the efficiency of agile practices in eliminating the seven wastes were identified. In addition to that, wastes that are captured by using lean practices; hybrid lean and agile practices were also identified. The reason for considering agile practices is that, agile and lean have similarities in eliminating the wastes and creating value to the customer [2][3]. Through the systematic literature review, it can be observed that researchers have not investigated all the seven wastes captured by lean practices. Thereafter, survey is the main contribution to this research where, the responses of 55 respondents from different countries were recorded. Most of the respondents are from India with 42% of the responses. We have asked the role of every respondent in their companies, and 19 respondents are Team leaders, 16 respondents are project managers and remaining people perform various other roles in software development. 38 respondents are from large-scale industry, which constitutes the majority part of the survey. The main contribution of the survey is identifying the ability of lean practices in eliminating different wastes. The respondents were asked to provide their level of agreement related to the effectiveness of each lean practices and agile practice in waste removal. A comparison between the results of SLR and survey reveals that there is a lot of variance in the perception of researchers and practitioners regarding the lean practices in eliminating wastes. Survey captures more wastes than SLR. From the results of survey, it was also identified that using the lean practices i.e. Kanban and VSM can eliminate most of the wastes. Kanban (41) and VSM (33) are mostly used and more efficient in industries. Conclusions: To conclude, the obtained results from this study will be quite useful for the real-time execution of lean practices. Team leaders, project managers, and organizations can adopt lean by choosing lean practices in accordance to the wastes that have to be eliminated from their software development process. This study has also identified the benefits and limitations of lean practices implemented in industry. This study helps researchers in providing necessary information that is very useful for further research in lean practices. The combinations of lean practices were also presented, which in terms one lean practice can compensate another in capturing all the seven wastes. In the survey, the additional wastes were identified when compared to SLR and this complements the literature. There is a considerable reach gap between the state of art and state of practice. It has been identified that VSM and Kanban practices have much attention in the literature. The remaining practices like Kotter and Kaizen are less concentrated in most of the research literature. From the literature, it is evident that none of the practices is capable of eliminating all the seven wastes in software development. VSM is capable of capturing wastes like waiting, extra process and motion. In addition, Kanban captures and eliminates wastes like partially done work, defects, task switching and extra features. With respect to the survey, Kanban and VSM practices are efficient in eliminating wastes. When the practitioners consider hybrid lean and agile practices, the combination of Kanban and Scrum, Scrum and VSM are efficient in eliminating wastes. The practitioners can consider the benefits of lean practices that are identified in this research.V S S N R Ram Nanduri vssnrram@gmail.com
2
Petersen, Kai. "Implementing Lean and Agile Software Development in Industry." Doctoral thesis, Karlskrona : Blekinge Institute of Technology, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-00465.
Full textAbstract:
Background: The software market is becoming more dynamic which can be seen in frequently changing customer needs. Hence, software companies need to be able to quickly respond to these changes. For software companies this means that they have to become agile with the objective of developing features with very short lead-time and of high quality. A consequence of this challenge is the appearance of agile and lean software development. Practices and principles of agile software development aim at increasing flexibility with regard to changing requirements. Lean software development aims at systematically identifying waste to focus all resources on value adding activities. Objective: The objective of the thesis is to evaluate the usefulness of agile practices in a large-scale industrial setting. In particular, with regard to agile the goal is to understand the effect of migrating from a plan-driven to an agile development approach. A positive effect would underline the usefulness of agile practices. With regard to lean software development the goal is to propose novel solutions inspired by lean manufacturing and product development, and to evaluate their usefulness in further improving agile development. Method: The primary research method used throughout the thesis is case study. As secondary methods for data collection a variety of approaches have been used, such as semi-structured interviews, workshops, study of process documentation, and use of quantitative data. Results: The agile situation was investigated through a series of case studies. The baseline situation (plan-driven development) was evaluated and the effect of the introduction of agile practices was captured, followed by an in-depth analysis of the new situation. Finally, a novel approach, Software Process Improvement through the Lean Measurement (SPI-LEAM) method, was introduced providing a comprehensive measurement approach supporting the company to manage their work in process and capacity. SPI-LEAM focuses on the overall process integrating different dimensions (requirements, maintenance, testing, etc.). When undesired behavior is observed a drill-down analysis for the individual dimensions should be possible. Therefore, we provided solutions for the main product development flow and for software maintenance. The lean solutions were evaluated through case studies.Defence September 7
3
Murray, Collin (Collin J. ). "Lean and agile software development : a case study." Thesis, Massachusetts Institute of Technology, 2008. http://hdl.handle.net/1721.1/43176.
Full textAbstract:
Thesis (S.M.)--Massachusetts Institute of Technology, System Design and Management Program, 2008."February 2008."
Includes bibliographical references (p. 89-90).
This paper looks at agile and lean development transitions for organizations that formerly used the waterfall style of development. There has been lots written about the positive aspects of agile software development and the anticipated benefits are widely touted. Through my research I became aware of significant obstacles that organizations can encounter when adopting an agile development method. The obstacles seem to be more applicable to organizations that use the waterfall development method and are compounded when legacy products exist. The intent of this thesis is to identify positive and challenging aspects for organizations that undertake a transition from waterfall development to agile development.
by Collin Murray.
S.M.
4
Mummadi, Sowrabh. "Exploratory study of Overhead in Lean/Agile Software Development." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-21802.
Full text
5
Moratilla, Temprado Enrique, and Bendito Enrique Ruz. "Lean Software Development and Agile Methodologies for a small Software development organization." Thesis, Högskolan i Borås, Institutionen Ingenjörshögskolan, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:hb:diva-20077.
Full textAbstract:
Lean Software Development is a new approach to provide a quality philosophy in software development companies. Lean offers a set of principles that helps companies to identify inefficient processes and waste. Therefore, by applying these principles, we can reduce costs, by shorting development time, incrementing productivity.In this study a software company with seven employees is analyzed. The company develops software and wants to increase its maturity and the quality of its processes. Currently, it has few documented processes. Furthermore, the company want a common way of working for every project. The challenge relies in adapting the set of principles provided by Lean to this particular case of study.We seek to analyze the current situation of the company to find out about the problems and limitations of the current way of working. After that we will state recommendations about the use of Lean combined with Agile practices such as Scrum and XP.As a result we present a proposal for implementation adapted from these philosophies to the needs and characteristics of the company.We have found that there are several ways in which the company can benefit from the implementation of Lean practices in combination with Scrum and XP. The result is a new framework that can be applied for other small software development companies in a similar situation.
6
Mehta, Naresh, and Muhammad Junaid Gill. "Agile in Multisite Software Engineering : Integration Challenges." Thesis, Blekinge Tekniska Högskola, Institutionen för industriell ekonomi, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-14892.
Full textAbstract:
Many big organizations who are in existence since before the term agile came into existence are pursuing agile transformations and trying to integrate it with their existing structure. It has been an accepted fact that agile integrations are difficult in big organizations and many of such organizations fail the transformations. This is especially true for multisite software organizations where a traditional mix of old and new ways of working ends up creating issues. The result of such failure is the implementation of a hybrid way of working which ultimately leads to lower output and higher cost for the organizations.This paper looks at the integration challenges for multisite software engineering organizations and correlates with the theoretical findings by earlier with practical findings using survey and interviews as data collection tools. This paper specifically focusses on integration challenges involving self-organizing teams, power distribution, knowledge hiding and knowledge sharing, communications and decision making. The paper also has empirical evidence that shows that there is a communication and understanding gap between the employees and management in basic understanding of agile concepts.
7
Katayama, Eduardo Teruo. "A contribuição da indústria da manufatura no desenvolvimento de software." Universidade de São Paulo, 2011. http://www.teses.usp.br/teses/disponiveis/45/45134/tde-11042012-102429/.
Full textAbstract:
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.
8
Maddila, Kalyan Chakravarthy. "Potential metrics for Agile and Lean : Systematic Literature Review and Survey." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-1916.
Full textAbstract:
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
9
Norrmalm, Thomas. "Achieving Lean Software Development : Implementation of Agile and Lean Practices in a Manufacturing-Oriented Organization." Thesis, Uppsala universitet, Avdelningen för datalogi, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-147645.
Full textAbstract:
The study reveals improvement areas in terms of lead time and quality in a traditionalsoftware development process of a large manufacturing-oriented organization, andidentifies four obstacles to the application of a Lean software development frameworkin order to achieve such improvements. The data from interviews are matched tofour predefined categories. These categories are evaluated using value streammapping and a framework of seven common improvement areas in softwaredevelopment. A large project and task tracking system indicate that lead time is a realproblem in the process. The most significant improvement area is wait time forchange approval meetings. A second prominent improvement area is the large amountof approval handshakes. At least a few of these handshakes are always approved, thusadding unnecessary lead time to the process. The four most imminent obstacles in adopting lean software development areidentified through estimating the efficiency of two in-house derivations of Scrum andKanban. The first obstacle is deep vertical but narrow horizontal expertise amongdevelopers. With some systems, there’s only one developer who knows how tomaintain the product. This makes it impossible to work as a team which is animperative principle of lean. A second obstacle is how the teams are arrangedorganizationally. They have a functional setup over three departments and threemanagers, which to some extent create a silo mentality, rendering cooperationdifficult. A third obstacle is how the teams are arranged geographically. Split over twolocations, manufacturing and headquarters, they have different customers, objectivesand a plain unfamiliarity with another that has reduced the will and opportunity tocommunicate and coordinate. A fourth obstacle is the inherent conflict between theprescriptive activities of ITIL, optimized for IT operational services, and theadaptability of agile methodologies, optimized for rapid change and empiricaldecisions. ITIL fulfills a sometimes uncalled for need to get all changes approvedthrough several layers of management. The study concludes that Lean software development is in conflict with manytraditional values of a manufacturing organization. Although lean may be prevalent inother parts of the organization, this does not necessarily include the IT function. ITstill seems to have hard time grasping the lean concepts of flow, waste and value.
10
Rodríguez, P. (Pilar). "Combining lean thinking and agile software development:how do software-intensive companies use them in practice?" Doctoral thesis, Oulun yliopisto, 2013. http://urn.fi/urn:isbn:9789526203324.
Full textAbstract:
Abstract 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, industry-leading 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 adaptationTiivistelmä Ohjelmistotuotanto kehittyy markkinoiden tarpeiden mukaisesti. Aiemmin kiisteltyjä ketteriä menetelmiä, ja nykyään myös Lean-menetelmiä sovelletaan yhä useammin ohjelmistoteollisuudessa. Lean-menetelmiin perustuva Lean-ohjelmistokehitys erottuu selkeämmin välineenä laajentaa ketterien menetelmien käyttöä. Lean on yhä monitulkintainen ohjelmistotuotannossa, joka poikkeaa teollisuustuotannosta, josta Lean on peräisin. Lean-ohjelmistokehitystä, Lean- ja ketterien menetelmien yhteensopivuutta ja niiden parasta yhdistelmää ei vielä ymmärretä riittävän hyvin. Tämä väitöskirja käsittelee Lean-menetelmien yhdistämistä ketteriin menetelmiin ohjelmistotuotannossa. Tutkimus esittää kokemusperäistä tietoa, kuinka näitä menetelmiä käytetään ohjelmisto-alan organisaatioissa. Tutkimus oli nelivaiheinen. Aluksi tutkimusmahdollisuudet kartoitettiin tutkimalla aiheeseen liittyvää kirjallisuutta. Seuraavaksi tutkittiin kyselytutkimuksen avulla Lean- ja ketterien menetelmien käyttämisen nykytilaa ja kehitystä. Kolmannessa vaiheessa tapaustutkimuksilla selvitettiin Lean- ja ketterien menetelmien yhdistämistä käytännössä. Tapaustutkimuksia tehtiin kahdessa suuressa yrityksessä, jotka olivat muuttamassa prosessejaan ketteristä menetelmistä kohti Lean-ohjelmistokehitystä. Lopuksi aiemmat tutkimusvaiheet yhdistettiin johtopäätöksiä ja vaikutusten hahmottamista varten. Tutkimuksen tulokset vahvistavat Lean- ja ketterien menetelmien yhdistämisen kiinnostavan ohjelmistotuotannonharjoittajia. Lean- ja ketterien menetelmien rajat eivät ole selkeästi määriteltyjä ohjelmistotuotannossa. Tulokset tukevat käsitystä Lean- ja ketterien menetelmien yhteensopivuudesta. Lean ohjaa yleisellä tasolla ketterien menetelmien käyttöä. Lean tuo kuitenkin myös uusia elementtejä ohjelmistotuotantoon, kuten Kanban-menetelmän, keskeneräisen työn rajoittamisen, kysyntään perustuvan ’pull’-menetelmän ja turhan työn vähentämistä tavoittelevan ’less-waste’-työkulttuurin. Lean-ajattelu myös lisää painotusta läpinäkyvyyteen ja yhteistyöhön
11
Lindblom, Mathias. "Agile Development in a Lonely Environment : How to Develop Software Using Agile Techniques Within Small-Scale Projects." Thesis, KTH, Skolan för datavetenskap och kommunikation (CSC), 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-170794.
Full textAbstract:
Most Agile Software Development methodologies are aimed towards large companies and large-scale projects. The purpose of this report was to identify, and potentially modify, Agile Development methodologies and strategies suitable for small-scale projects. Initially a comprehensive study was conducted on a few selected agile methodologies in order to find the most suitable one to be used for a loosely defined small-scale project. The result of the study led to the methodology Kanban being used experimentally on that project. The report goes through how Kanban was utilized and modified to better suit the project as well as bring forward interesting details regarding the outcome of the actual project. The produced methodology, with Kanban at its core, can especially be of use for small IT companies looking for an agile methodology fitting their project(s). It could also be used to further develop alternative variants of the agile methodology Kanban with focus on small-scale projects.De flesta agila utvecklingsmetodiker riktar sig mot storskaliga projekt och företag. Syftet med denna rapport var att identifiera lämpliga agila utvecklingsmetodiker och strategier för småskaliga projekt. Inledningsvis genomfördes en omfattande studie av ett fåtal agila metodiker med målet att hitta den mest lämpliga för ett löst definierat småskaligt projekt. Resultat av studien ledde till att metodiken Kanban experimenterades med och användes för projektet. Rapporten går igenom hur Kanban nyttjades och modifierades för att bättre passa projektet i fråga. Den framtagna metodiken, med Kanban som grund, kan vara speciellt användbar för mindre IT-företag som letar efter en agil metodik som passar deras projekt. Den skulle även kunna användas för att vidareutveckla alternativa agila Kanban-metodiker för småskaliga projekt.
12
Islam, Mohammad Shahidul, and Sentayehu Tura. "Exploring the difference between Agile and Lean:A stakeholder perspective." Thesis, Uppsala universitet, Informationssystem, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-202724.
Full textAbstract:
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.
13
Laanti, M. (Maarit). "Agile Methods in large-scale software development organizations:applicability and model for adoption." Doctoral thesis, Oulun yliopisto, 2013. http://urn.fi/urn:isbn:9789526200347.
Full textAbstract:
Abstract Agile methods have proven to be beneficial in small organizations, and there has also been growing interest in using these methods in large organizations. This dissertation analyzes what agility and agile development are and creates a framework for using those methods in large organizations. The work starts with a Concept Analysis of Agile Software Development and agile-in-large. The theoretical part also reflects the necessary background of Complex Adaptive Systems, Lean Thinking, and Learning Organizations. Then a model of an Agile Enterprise is defined and a Framework for Organizational Development and putting Agile Methods into use in large software development organizations is presented. Large development organizations consist of many levels. It is not enough to use Agile Methods on a certain level only, e.g., on the lowest level, but all levels need to change and adapt to the new way of working. Failure to do so leads to several unwanted consequences, which are described. One possible large-scale Agile Framework is described and analyzed. The usage of Agile Methods on a large scale is validated by quantitative studies. The level of success of using an Agile Framework on a large scale is dictated by how much the same framework for operation is shared within the organization, as partial transformation leads to confusion. But smaller successes can lead into organizational learning. The framework that is proposed can be used to further enhance agility. In this way large-scale agility can be seen as a never-ending series of systematic improvements of the enterprises’ Agile AspectsTiivistelmä Tämä väitöskirja tarkastelee suurten organisaatioiden tarpeisiin sopivien ketterien prosessimallien mallinnusta ja käyttöä. Ketterät menetelmät on todettu hyödyllisiksi pienissä ohjelmistoyrityksissä, joten myös isoissa yrityksissä on herännyt kiinnostus ketteriä menetelmiä kohtaan. Työ alkaa ketterien menetelmien käsiteanalyysillä, ja jatkuu määrittelemällä mitä ketteryys laajassa mittakaavassa on. Teoriaosuus käsittelee taustatiedot kompleksisista sopeutuvista järjestelmistä, lean-ajattelusta ja oppivista organisaatioista tarvittavin osin. Tämän jälkeen määritellään ketterän yrityksen käsite ja esitetään malli laajamittaiselle ketteryydelle. Suurissa kehitysorganisaatioissa on monta tasoa. Ei riitä, että ketteriä menetelmiä käytetään vain jollakin (yleensä alimmalla) tasolla, vaan kaikkien organisaation tasojen täytyy sopeutua uuteen toimintatapaan. Mikäli näin ei tapahdu, saattaa tuloksena olla joukko ei-toivottavia seurauksia, jotka on myös kuvattu tässä työssä. Työssä on esitetty ja analysoitu mahdollinen malli suuren yrityksen ketteryyden toteuttamiseksi. Ketterien menetelmien käyttö isossa yrityksessä on validoitu kvantitatiivisin menetelmin. Isoissa yrityksissä ketteristä menetelmistä saatu hyöty on sidottu siihen miten hyvin koko organisaatio pystyy noudattamaan samaa ketterää toiminnan mallia – osittainen toimintatavan muutos johtaa toimintatapojen konflikteihin. Kuitenkin myös osittaiset onnistumiset voivat johtaa organisaation oppimiseen. Esitettyä mallia voidaan käyttää kehitettäessä toimintatapaa entisestään ketterämpään suuntaan. Tällä tavalla suuren organisaation ketteryys voidaan nähdä jatkuvana sarjana systemaattisia toimintatavan parannuksia, joista jokainen johtaa entistä ketterämpään toimintatapaan
14
Cantanhede, Marco André Dias 1977. "Lean thinking em desenvolvimento de software : estudo e aplicação de ferramenta para avaliação do lean em software." [s.n.], 2014. http://repositorio.unicamp.br/jspui/handle/REPOSIP/267703.
Full textAbstract:
Orientadores: Marcos Augusto Francisco Borges, Regina Lúcia de Oliveira MoraesDissertação (mestrado) - Universidade Estadual de Campinas, Faculdade de Tecnologia
Made available in DSpace on 2018-08-24T22:28:54Z (GMT). No. of bitstreams: 1 Cantanhede_MarcoAndreDias_M.pdf: 5891395 bytes, checksum: 151886bf1ce7211aa3c33cae7ca6698a (MD5) Previous issue date: 2014
Resumo: A área de tecnologia da informação (TI) atravessou, e continua atravessando, os mesmos desafios de qualquer outra área da indústria. Desafios como: obter bons níveis de produtividades; entender e se aproximar do cliente; reduzir custos; e produzir inovação. Para gerenciar esses desafios a área de TI tem buscado novos mecanismos, por vezes criando práticas e métodos próprios, ou os trazendo de outras áreas de conhecimento. O Lean trouxe para a indústria, primeiramente a automobilística, e depois para várias outras, um novo padrão de produção e qualidade. O Lean questionou os padrões da produção em massa e trouxe novas formas para combater o desperdício, aumentar a qualidade e obter lucratividade no longo prazo. O termo Lean IT é usado para denotar o uso do Lean no combate dos desafios da indústria de TI, e o Lean Software Development é termo usado para uso do lean na área de desenvolvimento de software. O trabalho estuda e aplicada uma ferramenta de avaliação do nível de lean para a área de software, criando um procedimento para aplicação da ferramenta no Brasil. A ferramenta e o procedimento criado foram aplicados em três empresas de Desenvolvimento de Software com diferentes perfis. Os resultados demonstraram a aplicabilidade da ferramenta de avaliação do nível de lean nas empresas selecionadas, foram apontados ajustes e apresentados a necessidade de novos estudos. Também foram revistos os autores do Lean Thinking e do Lean Software Development
Abstract: The technology information (IT) industry has been facing challenges common to any other industry type. Challenges as: achieve good productive level; understand the client need; pressure for cost reductions; and innovation. IT has been searching for solution to address these challenges, sometimes creating own methods and practices, and sometimes, bringing them from other type of industries. The Lean has showed clear benefits and introduced a new standard to the automobile industry and manufacture type of business. Mass production standards were challenged by Lean creating new ways of dealing with quality and productivity. Lean has been positioned as an important alternative to deal with waste, to increate quality and expand long term profitability. The term Lean IT is used on application of Lean to address IT industry challenges, and Lean Software Development the application of lean at software development industry. The research reviews a leanness assessment tool adapted for software industry, developing an adaptation for the application at Brazil software industry. A procedure of application was created and the tool was applied at three different Software companies (enterprises). The results showed that the tool to evaluate leanness at software is applicable at the selected companies, adjustments were need and further studies are required. Lean thinking and Lean Software Development authors were also reviewed by this research work
Mestrado
Tecnologia e Inovação
Mestre em Tecnologia
15
Thota, Venkata Rama Chaitra. "Risk as a Mechanism in Self-Organizing Agile Software Development Teams." University of Cincinnati / OhioLINK, 2017. http://rave.ohiolink.edu/etdc/view?acc_num=ucin1505206458441433.
Full text
16
Katikireddy, Naga Durga Leela Praveera, and Nidhi Veereddy. "LeAgile Measurement and Metrics : A Systematic Literature Review and Case Study." Thesis, Blekinge Tekniska Högskola, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-15397.
Full textAbstract:
Context. Software engineers have been endeavouring to quantify software to obtain quantitative insights into its properties and quality since its inception. As of late, the use of Lean and Agile (LeAgile) methodologies is turning out to be progressively mainstream in the software industries. Managing software life-cycle tasks including planning, controlling and monitoring is primarily done by measurements. This is particularly valid in LeAgile organizations where these are day-to-day activities. On other words, dealing with agile development process like in any process, requires the collection of appropriate metrics to ensure visibility, inspection and adaptation as it is vital to know the effect of these methods and how product development and projects are performing. Are the goals being met? Are there any wastes? Is value being created? All of this is dependent on the ability to measure as correct and as objective as possible. Getting good metrics and interpreting them correctly is central in any product development organization. In agile approaches, the use of any metric needs to be clearly justified to decrease the amount of inefficient work done. This draws the need to discover metrics that are relevant to LeAgile methods to entail the benefits of measurement. Objectives. The main objective of this paper is to understand the current state-of-the-art and state-of-the-practice on the metrics usage in LeAgile methods. Additionally, to identify metrics that are suitable and have a high strength of evidence for their usage in the industries. Likewise, to construct a LeAgile measurement model based on the application of the metric’s context. Methods. This paper presents a two-step study; Firstly, a Systematic Literature Review (SLR) is conducted to present the state-of-the-art on using metrics in LeAgile Software Development. Second, to allow a better understanding of what measures are currently being used in collaboration between industry and academia, we have performed a case study at Telenor. Results. We found that metrics was mainly used to have an efficient flow of software development; to assess, track and improve product quality; for project planning and estimations; for project progress and tracking; to measure the teams and others. Additionally, we present the metrics that have compelling use and are worthy to be used in the industries. Conclusions. We conclude that traditional metrics or besides any metric can be used in an LeAgile context, provided they do not harm the agility of the process. This study identified 4 new metrics namely Business Value, Number of disturbance hours, Team Health check survey and Number of hours spent on IT divisions that are not present in the state-of-the-art. The gaps identified in the LeAgile measurement model built in this study can provide a roadmap for further research pertaining to the measurement model. Any of the topics identified as a means of completing the LeAgile measurement model developed in our study can be a fruitful area for future research.
17
Karvonen, T. (Teemu). "Continuous software engineering in the development of software-intensive products:towards a reference model for continuous software engineering." Doctoral thesis, Oulun yliopisto, 2017. http://urn.fi/urn:isbn:9789526216560.
Full textAbstract:
Abstract Continuous software engineering (CSE) has instigated academic debate regarding the rapid, parallel cycles of releasing software and customer experimentation. This approach, originating from Web 2.0 and the software-as-a-service domain, is widely recognised among software-intensive companies today. Earlier studies have indicated some challenges in the use of CSE, especially in the context of business-to-business and product-oriented, embedded systems development. Consequently, research must address more explicit definitions and theoretical models for analysing the prerequisites and organisational capabilities related to the use of CSE. This dissertation investigates various approaches to conducting empirical evaluations related to CSE. The study aims to improve existing models of CSE and to empirically validate them in the context of software companies. The study also aims to accumulate knowledge regarding the use of CSE, as well as its impacts. The case study method is applied for the collection and analysis of empirical data. Twenty-seven interviews are conducted at five companies. In addition, a systematic literature review is used to synthesise the empirical research on agile release engineering practices. Design science research is used to portray the model design and the evaluation process of this dissertation. Three approaches for evaluating CSE are constructed: (1) LESAT for software focuses on enterprise transformation using an organisational self-assessment approach, (2) STH+ extends the “Stairway to Heaven” model and evaluates company practices with respect to evolutionary steps towards continuous experimentation-driven development, and (3) CRUSOE defines 7 key areas and 14 diagnostic questions related to the product-intensive software development ecosystem, strategy, architecture, and organisation, as well as their continuous interdependencies. This dissertation states the relevance of CSE in the context of product-intensive software development. However, more adaptations are anticipated in practices that involve business and product development stakeholders, as well as company external stakeholdersTiivistelmä Jatkuva ohjelmistotuotanto on herättänyt keskustelua nopeasta, samanaikaisesta ohjelmistojulkaisemisesta ja asiakaskokeiluista. Toimintatapa on peräisin Web 2.0 ja software-as-a-service yhteydestä, mutta se tunnetaan nykyään yleisesti ohjelmistoja kehittävissä yrityksissä. Aiemmat tutkimukset ovat osoittaneet haasteita jatkuvan ohjelmistotuotannon käytössä. Erityisesti haasteita on havaittu yritykseltä yritykselle liiketoiminnassa ja tuotepainotteisten sulautettujen järjestelmien yhteydessä. Näin ollen on havaittu tarve tutkimuksen avulla kehittää täsmällisempiä määritelmiä ja teoreettisia malleja, joilla voidaan analysoida jatkuvan ohjelmistotuotannon käyttöön liittyviä edellytyksiä ja organisaatioiden kyvykkyyksiä. Tässä väitöskirjassa tutkitaan malleja, joilla voidaan empiirisesti arvioida jatkuvaa ohjelmistotuotantoa. Tutkimuksella pyritään parantamaan nykyisiä malleja ja arvioimaan niiden käyttöä ohjelmistoyrityksissä. Lisäksi tutkimuksella pyritään kasvattamaan tietoa jatkuvasta ohjelmistotuotannosta ja sen vaikutuksista. Tiedon keräämiseen ja analysointiin käytettiin tapaustutkimus menetelmää. Kaksikymmentäseitsemän haastattelua tehtiin viidessä yrityksessä. Lisäksi tehtiin ketterään ohjelmistojulkaisuun keskittyvä systemaattinen kirjallisuuskatsaus. Väitöskirjassa käytetään Design Science Research menetelmää kuvaamaan tutkimuksen eri vaiheita, joissa malleja suunniteltiin ja arvioitiin. Tutkimuksessa rakennettiin kolme tapaa jatkuvan ohjelmistotuotannon arvioimista varten: (1) LESAT for Software keskittyy organisaation muutoskyvykkyyden arviointiin käyttäen itsearviointimenetelmää, (2) STH+, laajentaa ”Stairway to Heaven” mallia ja arvioi yrityksen käytäntöjä eri evoluutioaskelmilla matkalla kohti kokeilupainotteista tuotekehitystä, (3) CRUSOE määrittelee seitsemän pääaluetta ja 14 kysymystä liittyen tuotekehityksen ekosysteemiin, strategiaan, arkkitehtuuriin, organisointiin sekä näiden välisiin jatkuviin riippuvuuksiin. Väitöskirja osoittaa jatkuvan ohjelmistokehityksen olevan merkityksellinen myös tuotepainotteisessa ohjelmistokehityksessä. Nähtävissä kuitenkin on, että useita nykykäytäntöjä on tarvetta muokata. Erityisesti muokkaustarvetta on tuotekehityksen ja liiketoiminnan sidosryhmiin ja yrityksen ulkoisiin sidosryhmiin liittyvissä käytännöissä
18
Dogs, Carsten, and Timo Klimmer. "An Evaluation of the Usage of Agile Core Practices : How they are used in industry and what we can learn from their usage." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2004. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4725.
Full textAbstract:
In this thesis we investigate the usage of several agile software development methods as well as the usage of certain agile core practices. By conducting a web survey, we examine what makes these practices beneficial and what tends to make them rather less suitable for certain situations. Based on the results, we finally set up some recommendations for practitioners to reflect upon and improve their own software development process. Concerning these recommendations as well as the list of the investigated practices, we hope (and are almost sure) that there are some practices or ideas contained which are worth at least thinking about. The main findings of this thesis are: - Agile software development methods have already entered the professional market but they are still no cure-all. In many cases they also produce only middle-quality software. Nevertheless, there is – even if only little – evidence that at least XP projects meet the requirements of the customer better than traditional, non-agile methods. - For a successful software development project it is important that it has a suitable requirements engineering process, that the produced software is tested sufficiently (using automated regression testing among other types of testing), that there is a good communication between the customer and the developer side, that the risks of the project are considered, that the pros and cons of practices are considered and that processes are improved continuously. - Besides, it is important to consider the whole context when implementing a certain practice. For some contexts, certain practices do not fit for their purpose and this has to be realized. However, certain shortcomings of a specific practice might be reduced or even eliminated if implemented in combination with other practices.
19
Ahmad, M. O. (Muhammad Ovais). "Exploring Kanban in software engineering." Doctoral thesis, Oulun yliopisto, 2016. http://urn.fi/urn:isbn:9789526214085.
Full textAbstract:
Abstract To gain competitive advantage and thrive in the market, companies have introduced Kanban in software development. Kanban has been used in the manufacturing industry for over six decades. In the software engineering domain, Kanban was introduced in 2004 to increase flexibility in coping with dynamic requirements, bring visibility to workflow and related tasks, improve communication, and promote the pull system. However, the existing scientific literature lacks empirical evidence of the use of Kanban in software companies. This doctoral thesis aims to improve the understanding of the use of Kanban in software engineering. The research was performed in two phases: 1) analysis of scientific literature on Kanban in software engineering and industrial engineering and 2) investigation of Kanban implementation trends in software companies. The data was collected through systematic literature reviews, survey and semi-structured interviews. The results were synthesized to draw conclusions and outline implications for research and practice. The results indicate growing interest in the use of Kanban in software companies. The findings suggest that Kanban is applicable to software development, software maintenance, and portfolio management in software companies. Kanban brings visibility to task and offering status, limits work in progress at any given time gives people greater control over their work and limit task switching. Although Kanban offers several benefits, as reported in this dissertation, the findings show that software companies find it challenging to implement Kanban incrementallyTiivistelmä Ohjelmistoteollisuudessa Kanbanin käyttö on yleistynyt vuodesta 2004 alkaen. Sillä pyritään tuomaan joustavuutta muuttuvien vaatimusten hallintaan, tuomaan näkyvyyttä työnkulkuun ja toisiinsa liittyviin tehtäviin, parantamaan kommunikaatiota sekä edistämään imuohjauksen hyödyntämistä. Kanbania on käytetty valmistavassa teollisuudessa jo yli kuuden vuosikymmenen ajan. Olemassa olevassa tieteellisessä kirjallisuudessa on kuitenkin esitetty hyvin vähän empiirisiä tutkimustuloksia Kanbanin käytöstä ohjelmistoyrityksissä. Väitöskirjan tavoitteena on parantaa ymmärrystä Kanbanin käytöstä ohjelmistotuotannossa. Tutkimus toteutettiin kahdessa vaiheessa: 1) Kirjallisuusanalyysi Kanbanin käytöstä ohjelmistotuotannossa ja tuotantotekniikassa ja 2) Empiirinen tutkimus Kanbanin käyttöönoton trendeistä ohjelmistoyrityksissä. Tutkimusaineisto kerättiin systemaattisten kirjallisuuskatsausten, kyselytutkimuksen ja puolistrukturoitujen teemahaastattelujen kautta. Tutkimustulosten synteesin pohjalta tehtiin johtopäätöksiä Kanbanin käytöstä ohjelmistotuotannossa sekä niiden merkityksestä alan tutkimukselle ja Kanbanin käytölle yrityksissä. Tutkimuksen tulokset osoittavat kasvavaa kiinnostusta Kanbanin käyttöä kohtaan ohjelmistoyrityksissä. Tulosten perusteella Kanban soveltuu käytettäväksi ohjelmistokehityksessä, ohjelmistojen ylläpidossa sekä tuoteportfolion hallinnassa. Kanban tuo näkyvyyttä ohjelmistokehitykseen, niin meneillään olevien tehtävien kuin portfoliotarjoaman osalta. Se myös auttaa rajoittamaan työtehtävien ruuhkautumista ja antaa kehittäjille paremman tavan hallita työtään rajoittamalla työtehtävien vaihtoa. Vaikka Kanbanin käytöllä on mahdollista saavuttaa väitöskirjatutkimuksessa esitettyjä hyötyjä, tulokset osoittavat, että ohjelmistoyrityksillä on haasteita Kanbanin inkrementaalisessa käyttöönotossa
20
Kaikkonen, H. (Harri). "Supporting rapid product development with agile development methodologies." Doctoral thesis, Oulun yliopisto, 2018. http://urn.fi/urn:isbn:9789526219332.
Full textAbstract:
Abstract Management of product development activities has become increasingly important, as cycle times of product development have shortened. Smaller product development projects are often conducted rapidly at companies based on customer or sales requests to answer the need for faster cycle times. However, this is often done without fully realizing the impact of the new projects on the larger project portfolio or organizational effectiveness. The main objective of this dissertation is to increase knowledge on the use of agile development methods in small, rapid product development projects, and on the implementation of a rapid product development model. The dissertation is formulated as a qualitative, inductive study based on the research results of four original publications and a summary combining the results. The results of the dissertation show that it is beneficial to separate a rapid product development process for certain types of customer- or sales-initiated projects. A new rapid development model with principles and guidelines is introduced to help organizations facilitate this separation. The implementation of the model can be supported with agile development practices, of which self-managing teams are studied in more detail. There is significant overlap between case companies’ perceived success factors for rapid development and self-management. The results imply that a functional rapid development model can be utilized as a strategic asset at companies. The results also provide empirical evidence that agile development practices can be utilized in product development. In addition to providing empirical evidence in scientific discussion about combining product development and agile software development practices, the results can be used to create better definitions of product development processes in generalTiivistelmä Tuotekehityksen johtamisesta ja hallinnasta on tullut entistä haastavampaa ja tärkeämpää, kun tuotekehitysprojektien läpimenoajat ovat lyhentyneet. Yritykset tekevät kasvamassa määrin lyhyitä tuotekehitysprojekteja asiakaspyyntöjen tai myynnin aloitteesta vastatakseen markkinoiden vaatimuksiin nopeasta kehityksestä. Tällaisten nopeiden tuotekehitysprojektien käynnistäminen ja toteutus tehdään usein ymmärtämättä yksittäisen projektin vaikutusta koko projektiportfolioon tai organisaation tehokkuuteen. Tämän väitöskirjan päätavoitteena on tutkia ohjelmistokehityksestä tunnettujen ketterien kehitysmenetelmien käyttöä nopeissa tuotekehitysprojekteissa ja uudenlaisen nopean tuotekehityksen mallin käyttöönotossa. Tutkimus on tehty laadullisena ja induktiivisena tutkimuksena perustuen neljään itsenäiseen tutkimusartikkeliin ja näiden tulokset kokoavaan kokoelmaosaan. Tutkimus osoittaa, että yrityksille on hyödyllistä erottaa erillinen prosessi tietyntyyppisille nopeille tuotekehitysprojekteille. Tutkimuksen tuloksena esitellään malli, joka tukee tätä erottamista periaatteiden ja ohjeiden avulla. Tätä mallia pystytään tukemaan ketterillä kehitysmenetelmillä, joihin liittyen on erityisesti tutkittu itseohjautuvia kehitystiimejä. Case-yritysten havainnoimilla nopean tuotekehityksen menestystekijöillä ja itseohjautuvien tiimien ominaisuuksilla on havaittavissa suurta päällekkäisyyttä. Tulokset osoittavat, että hyvin käytetty ja määritetty nopean tuotekehityksen malli voi olla strateginen kilpailuetu yrityksille. Tulokset lisäävät myös empiiristä tietoa ketterien menetelmien käytöstä tuotekehityksessä ja hyödyntävät siten ajankohtaista tieteellistä keskustelua. Tuloksia voidaan myös hyödyntää muiden tuotekehitysprosessien käyttötarkoituksen tarkempaan määrittämiseen
21
Jlassi, Sabrina. "Agile project management: analisi del framework e della sua applicazione in GetConnected S.r.l." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2021.
Find full textAbstract:
Per Agile Project Management si intende un insieme di metodologie che puntano ad ottimizzare i processi interni delle aziende che le adottano. Tali metodologie si basano sui principi definiti da Agile, ovvero una serie di approcci che si pongono come obiettivo quello di soddisfare il cliente tramite rilasci continui di un prodotto funzionante e per ognuno di essi è possibile trarre un vantaggio competitivo. Si tratta di una metodologia incrementale e iterativa che mette al primo posto la capacità di saper rispondere ai cambiamenti in modo immediato, senza intaccare il livello di produttività.
I principali framework che si basano e ampliano i principi della metodologia Agile sono: Scrum, Extreme Programming e Lean Software Development. L'obiettivo della tesi è quello di analizzare le caratteristiche principali sia dell'Agile Project Management e sia dei framework che ad esso si ispirano. Quest'analisi è stata svolta per poter per descrivere al meglio l'applicazione delle metodologie a livello pratico, avvenuta durante l'esperienza di tirocinio presso l'azienda GetConnected S.r.l. Essa sponsorizza l'agilità sia al suo interno sia offrendo servizi ai clienti per poter introdurre Agile nei propri processi. Infatti, la seconda parte della tesi punta ad analizzare le pratiche agili utilizzate nello sviluppo di un progetto che ha avuto come obiettivo la customizzazione di Jira Software - prodotto della suite Atlassian - sulla base delle esigenze esposte dal cliente.
22
Sabar, Suneel. "Software Process Improvement and Lifecycle Models in Automotive Industry." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-69640.
Full textAbstract:
The quality of a product depends on the quality of the underlying process is a well known fact. Software development organizations have been struggling to decrease their cost, increase their ROI, reduce time-to-market, and enhance the quality of their products. This all depends upon the improvement in the processes they are following inside their organizations. A number of software process improvement models exist in market, e.g., CMMI, SPICE and Automotive SPICE. But before an organization can improve its development and management processes, it is very important to know whether it is following the right processes. There exist a number of software development process models, mainly categorized into Traditional and Agile, which provide the step-by-step guidance to develop and manage the software projects.The current thesis presents a study of software process improvement models in automotive industry, their weaknesses and strengths and presents a comparison of how do they relate to each other. This thesis also explores some software development models which are more famous in automotive industry, and the applicability of process improvement models in conjunction with the Agile software development models. A case study was performed at an automotive software supplier organization to investigate the experience of combining Agile practices with organization’s company-tailored software development model that was incorporating Automotive SPICE standards.
23
Mikula, Jan. "Návrh metodiky vývoje softwaru se zaměřením na oblast UX." Master's thesis, Vysoká škola ekonomická v Praze, 2013. http://www.nusl.cz/ntk/nusl-197005.
Full textAbstract:
The main objective of this work is to propose a software development methodology which will reflect both issues -- design of User Experience (UX) and its implementation. The second objective is to compare the current software development methodologies. The third objective is to describe the work environment and the principles of that environment to fully implement this methodology. The fourth objective is to test the methodology in practice and validate its performance on my own startup. The fifth objective is to analyze companies which are focusing on similar product as my startup and their approach to UX development. First I will take look at waterfall methodology and then at modern agile methodologies such as Scrum, Kanban and Lean management, which are now becoming standard in software development. I will describe issues with the integration of UX into software development. The next section will introduce my own methodology, which is based on Scrum. The methodology consists of general principles of Lean and Agile management and the management, which is sometimes called "freedom at work". Then I will use the proposed methodology on my own startup project and will evaluate its use in practice. In last part I will analyze development process with focus on UX in projects Medium and Facebook. Thesis combines knowledge from Lean and agile management, economy and cognitive science to show the way to succeed in today services with great UX.
24
Filho, Dairton Luiz Bassi. "Experiências com desenvolvimento ágil." Universidade de São Paulo, 2008. http://www.teses.usp.br/teses/disponiveis/45/45134/tde-06072008-203515/.
Full textAbstract:
A crescente demanda por sistemas e a alta velocidade com que seus requisitos evoluem têm evidenciado que desenvolvimento de software exige flexibilidade, pois muitas decisões precisam ser tomadas durante o projeto. Além disso, as dificuldades para a produção de sistemas vão muito além das questões técnicas. Fatores estratégicos, comerciais e humanos são responsáveis por algumas das variáveis que contribuem para tornar o desenvolvimento de sistemas de software uma atividade altamente complexa. Modelos tradicionais de desenvolvimento de software propõem processos prescritivos que não consideram toda essa complexidade. Por outro lado, Métodos Ágeis de desenvolvimento de software sugerem uma abordagem mais humanística com foco na entrega rápida e constante de software com valor de negócios. Porém, para conseguir isto, é preciso escolher um conjunto de práticas de desenvolvimento adequado às características do projeto e da equipe. Desta forma, a natureza única de cada projeto e a necessidade de alta qualidade e produtividade tornam importante a busca por práticas de desenvolvimento. A partir de projetos que conduzimos usando métodos ágeis na academia e na indústria, identificamos e descrevemos 22 práticas para desenvolvimento de software que podem ser adotadas por equipes para aumentar o seu desempenho e/ou a qualidade do software.The growing demand for systems and the high speed with which their requirements evolve has shown that software development requires flexibility because many decisions need to be taken during the project. Also, the difficulties for the production of software systems go far beyond the technical issues. Strategic, commercial and human factors are responsible for some variables that contribute to make the software development a highly complex activity. Traditional models of software development propose prescritive processes that do not consider all this complexity. On the other hand, Agile Methods of software development suggest an humanistic approach focused on fast and often business valuable software deliveries. But, in order to get it, one needs to choose an appropriated group of development practices accordingly to the project and team features. In this way, the individuality of each project and the need for better quality and productivity motivate the search for software development practices. Based on projects that we conducted by using agile methods in academic and industry environments we identified and described 22 software development practices that can be used by teams to increase their performance and/or the software quality.
25
Ferreira, Nuno Augusto Simões. "Metodologia DevOps e suas mais valias para as organizações." Master's thesis, Universidade de Aveiro, 2016. http://hdl.handle.net/10773/21560.
Full textAbstract:
Mestrado em Engenharia e Gestão IndustrialNum mundo em constante mudança, onde a tecnologia assume cada vez mais um papel central nas nossas vidas, as organizações são constantemente desafiadas a adaptarem-se de forma cada vez mais rápida e precisa às alterações de mercado. No presente contexto a metodologia DevOps surge, assumindo-se como “upgrade” à metodologia Agile já existente e colocando o foco na criação mais rápida e eficiente de valor acrescentado para o negócio das organizações, ao longo de todo o ciclo de desenvolvimento. Assim, o presente estudo procura elaborar uma revisão bibliográfica do seu conceito, apresentar as suas linhas de orientação, bem como confrontar as mais-valias para as organizações citadas com as encontradas em 18 casos de estudo da aplicação de soluções no âmbito da metodologia. O objetivo final prende-se com a compreensão teórica da metodologia e do modo como esta pode ajudar as organizações a competir neste mundo cada vez mais rápido e complexo
In a constant change world, where technology assumes a greater role on our life, the organizations are been always challenged to a faster and precise adaptation. On this context the DevOps methodology also assumes itself as an Agile upgrade, looking to create value faster and efficient to the business through the development life cycle. The scope of this study is to present a bibliographic revision of its concept, its guidelines and try to understand if the benefits of its implementation reported in 18 case studies are coincident with those identified on the bibliographic revision. The final goal is to theoretically understand its concept and its real value for the organizations to compete in this faster and complex world
26
Franco, Eduardo Ferreira. "Um modelo de gerenciamento de projetos baseado nas metodologias ágeis de desenvolvimento de software e nos princípios da produção enxuta." Universidade de São Paulo, 2007. http://www.teses.usp.br/teses/disponiveis/3/3141/tde-09012008-155823/.
Full textAbstract:
Procurando obter ganhos sustentáveis de produtividade e qualidade no desenvolvimento de software, diversos modelos, formas de organização do trabalho e abordagens inovadoras foram desenvolvidos para auxiliar os gerentes de projeto. O presente trabalho propõe um modelo de gerenciamento de projetos, baseado nas metodologias ágeis de desenvolvimento de software (Extreme Programming e o Scrum), e nos princípios e valores do pensamento enxuto, originado na manufatura automobilística japonesa. Após a proposição do modelo, ele é aplicado em um estudo de caso, avaliando os resultados obtidos na combinação entre as metodologias ágeis e nos princípios e valores da produção enxuta. Em seguida, este modelo é analisado qualitativamente com o intuito de determinar suas vantagens de utilização e seu escopo de aplicação. Para tanto, recorreu-se a uma avaliação do modelo proposto e o tradicional modelo cascata, ainda amplamente adotado no setor de software, e mapeando como este modelo contorna os problemas apontados na literatura, advindos da utilização do modelo cascata.Looking for sustainable gains in productivity and quality in the development of software, several models, forms of work organization and innovative approaches were developed to support software development managers. The present work proposes a model of project management, based on agile software development methodologies (Extreme Programming and Scrum) and on lean principles and values borrowed from the Japanese automobile manufacturing. After describing the proposed model, it is applied in a case study, describing the results of combining the agile software development methodologies with the lean production principles and values. After this, the model is qualitatively analyzed to determine its advantages and its scope of application. For this, the proposed model is evaluated with the traditional waterfall model - until now widely adopted in the software industry - and mapping how it addresses problems, cited in the literature, derived from the use of the waterfall model.
27
Cunha, Thiago Ferraz Vieira da. "SLESS 2.0: an evolution of the Scrum and Lean Six Sigma integration approah for mobile applications." Universidade Federal do CearÃ, 2014. http://www.teses.ufc.br/tde_busca/arquivo.php?codArquivo=14240.
Full textAbstract:
The software development for mobile devices such as mobile phones, smartphones and tablets requires knowledge not only of processes but also related to software and hardware technology platforms of these devices. Continuous improvement in the performance of these platforms and the increasing demand for a variety of applications require a high competitiveness and, therefore, high levels of productivity and quality. In this scenario, agile methodologies are used and fit well to frequently changing requirements and to time to market. Among these methodologies, Scrum is one of the most accepted and used, contributing to the improvement of project management, team productivity, product quality and increasing the probability of project success. On the other hand, there is an increasing adoption of quality management methodologies such as Lean Six Sigma in Information Technology and Communication (ICT) organizations due to their proven results in improving processes development and quality of services and products developed. Methodologies such as Scrum and Lean Six Sigma have different goals, however, they can contribute together in the development of software for mobile devices. In literature, there are studies that propose the integration of agile methodologies and software quality, however, they have gaps regarding the possibility of systematic reuse of this integration, as well as in evaluating the use of these integrated methodologies. Thus, this paper proposes an evolution of an existing approach, called SLeSS, that integrates Scrum to Lean Six Sigma and has been used in the software customization for mobile phones. The evolution of this approach is to add software development in addition to customization and improve integration mechanisms initially proposed with a focus on evaluation of the practices and principles of Scrum from the use of techniques of Lean Six Sigma. This new version is applied in seven actual projects that are related to software development and customization for mobile devices and their results are also discussed in this dissertation.O desenvolvimento de software para dispositivos mÃveis como smartphones, celulares e tablets requer conhecimento dos processos e das tecnologias relacionadas Ãs plataformas de software e de hardware desses dispositivos. A melhoria contÃnua no desempenho dessas plataformas e a demanda crescente por uma variedade de aplicaÃÃes impÃem uma alta competitividade e, por conseguinte, exigem nÃveis elevados de produtividade e de qualidade dos projetos de desenvolvimento. Nesse cenÃrio, as metodologias Ãgeis sÃo utilizadas por se adequarem bem Ãs frequentes mudanÃas de requisitos e Ãs demandas de prazo desse nicho de mercado. Dentre essas metodologias, o Scrum à uma das mais aceitas e utilizadas, contribuindo na melhoria da gestÃo de projetos, na produtividade do time, na qualidade dos produtos e no aumento da probabilidade de sucesso dos projetos. Por outro lado, hà uma crescente adoÃÃo de metodologias de gestÃo da qualidade como o Lean Six Sigma por organizaÃÃes da Ãrea de Tecnologia da InformaÃÃo e ComunicaÃÃo (TIC) devido aos seus resultados comprovados na melhoria dos processos de desenvolvimento e da qualidade dos serviÃos e dos produtos desenvolvidos. Metodologias como o Scrum e o Lean Six Sigma possuem objetivos distintos, entretanto, elas podem contribuir juntas no desenvolvimento de software para dispositivos mÃveis. Na literatura existem trabalhos que propÃem a integraÃÃo de metodologias Ãgeis e de qualidade de software, entretanto, esses trabalhos possuem lacunas no que tange a possibilidade de reuso sistemÃtico das mesmas bem como a avaliaÃÃo do uso dessas metodologias integradas. Este trabalho propÃe entÃo uma evoluÃÃo de uma abordagem jà existente, denominada SLeSS, que integra o Scrum ao Lean Six Sigma e que foi utilizada na customizaÃÃo de software para celulares. Essa evoluÃÃo visa ampliar a abordagem tanto para o desenvolvimento de software alÃm da customizaÃÃo quanto para melhorar os mecanismos de integraÃÃo inicialmente propostos com um foco na avaliaÃÃo das prÃticas e princÃpios do Scrum a partir do uso de tÃcnicas do Lean Six Sigma. Para avaliar a nova versÃo, ela à aplicada em sete projetos reais de desenvolvimento e customizaÃÃo de software para dispositivos mÃveis e seus resultados sÃo tambÃm discutidos nesta dissertaÃÃo.
28
Hefnerová, Lucie. "Kanban a možnosti jeho využití v bankovním prostředí." Master's thesis, Vysoká škola ekonomická v Praze, 2013. http://www.nusl.cz/ntk/nusl-193869.
Full textAbstract:
The main goal of this diploma thesis is to investigate the possibilities of the usage of Kanban system within a banking environment. To achieve this goal, the history, advantages, disadvantages and main areas of its usage are analyzed and described. Another goal of this thesis is to define the suitable terminology for Czech environment and to inspect the extent to which the concept of Kanban is compatible with the existing approaches and methodologies to project management. The market analysis of available software tools to support the concept of Kanban is performed (criteria definition, evaluation and final comparision). Based on all the previously described outputs a methodology to implement Kanban in banking environment is designed.This methodology is then used in the final chapter of the thesis -- the case study from an international bank, providing middle management with a step by step guide to successfuly implement Kanban system.
29
Johansson, Katrin. "Agile Software Development." Thesis, Linköpings universitet, Institutionen för teknik och naturvetenskap, 2005. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-97920.
Full textAbstract:
Systemutvecklingsföretag är på väg in i en turbulent period. Globaliseringen ger en total konkurrens som kräver snabba anpassningar. Detta ställer krav på reaktionssnabbhet. En framtid där vi slipper ogenomträngliga lösningar ligger nu inom räckhåll. Ett nytt synsätt har börjat ta form och konkurrerar nu ut den gamla, processorienterade synen på systemutveckling. Testdriven utveckling, refactoring och par-programmering är inslag i denna nya mera lättrörliga utvecklingsmetodiken. Detta synsätt går under namnet Agile Software Development. Den studie jag genomfört och som denna uppsats är resultatet av, syftar till att ta reda på hur systemutveckling enligt synsättet agile fungerar i verkligheten och vad det betyder för aktiva systemutvecklare. Resultatet av studien är baserad på en kvalitativ undersökning, i form av intervjuer, som gjorts med tretton systemutvecklare på olika företag runt om i Sverige. Resultatet visar att genom att utveckla mjukvara med en agilemetod, får man en snabbare utvecklingscykel med fokus på störts affärsnytta först. Det ger mer funktioner med högre kvalitet till lägre kostnad. Resultatet visar också att man har en flexiblare syn på utvecklingen och en attityd som välkomnar förändringar när helst dom dyker upp. Ett arbetssätt där förändringar är en del av planeringen.
30
Saarnak, Stefan, and Björn Gustafsson. "A comparison of lifecycles : Agile software processes vs. projects in non-Agile software companies." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2003. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3251.
Full textAbstract:
In the software industry a number of different software processes has been used throughout the years to address known problems with software development, despite their intention complains has been raised that some of these are too bureaucratic. The Agile Alliance was formed in 2001 and aimed to solve this problem, they developed a manifesto and twelve principles which are supported by all Agile software processes. The purpose with the manifesto and its principles is to uncover better ways of developing software and these are by many intercessors of Agile seen as common sense and not completely new ideas. The aim with this master thesis is to answer the question if companies that explicitly claim that they do not use any Agile software process are already applying some of these ideas since they are thought of as obvious and common sense. The comparison in this thesis is performed between the project lifecycles used in specific projects by five non-Agile software companies and four identified lifecycle characteristics and two more general characteristics of the Agile software processes Extreme Programming (XP) and Dynamic Systems Development Method (DSDM). The result from the analysis of these interviews has shown that it is very difficult to decide if a software company really is working as described by XP or DSDM, this is due to that many different factors affect the final outcome. For example type of project and is the software company using different software processes for different kinds of projects. Since we just covered specific projects we were only able to conclude with absolute certainty actions that really were performed in just these projects. The project lifecycles of these software companies had some similarities with the above mentioned Agile software processes, but as a whole the analysis showed that they are quite different due to that two very important characteristics according to us, namely iterative development and frequent releases, were not applied by any of the software companies and that their project phases differed tremendously compared to XP and DSDM. Our common sense hypothesis for Agile software development was shown in this investigation to be incorrect since important activities were not performed by any of the software companies. Instead of using an iterative approach with frequent releases they all followed sequential waterfall like software processes.
31
Dumpala, Prasanth. "Software development through agile way." Thesis, University West, Department of Technology, Mathematics and Computer Science, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:hv:diva-568.
Full textAbstract:
This research paper discusses the software development through agile approaches. In which we see that most of the time, agile approaches cannot use for all type of projects. But this paper is exploring the new ideas that how we can use the agile methodologies with the help of traditional approach and PSP/TSP/Software CMMI. So, the over all paper is giving the whole idea, that we can develop any type of software projects through the new agile methodology guidelines which we are describing here. As well as for solving this paper we adopted different ways in which we focused on literature study & also published research paper on agile methodology. In addition, we did this work on the base of hybrid ideology where we combined the best ways of different approaches and achieved our goals.. Where we proved that by the combination of these approaches, we can manage our projects as well as team personals in the organization successfully. And this concept for team management comes from PSP/TSP and Software CMMI. The benefit for management of this is also to get our projects with agility and personnel's training for project management.
32
Abbas, Noura. "Software quality and governance in agile software development." Thesis, University of Southampton, 2009. https://eprints.soton.ac.uk/158357/.
Full textAbstract:
Looking at software engineering from a historical perspective, we can see how software development methodologies have evolved over the past 50 years. Using the right software development methodology with the right settings has always been a challenge. Therefore, there has always been a need for empirical evidence about what worked well and what did not, and what factors affect the different variables of the development process. Probably the most noticeable change to software development methodology in the last 15 years has been the introduction of the word “agile”. As any area matures, there is a need to understand its components and relations, as well as the need of empirical evidence about how well agile methods work in real life settings. In this thesis, we empirically investigate the impact of agile methods on different aspects of quality including product quality, process quality and stakeholders’ satisfaction as well as the different factors that affect these aspects. Quantitative and qualitative research methods were used for this research, including semi-structured interviews and surveys. Quality was studied in two projects that used agile software development. The empirical study showed that both projects were successful with multiple releases, and with improved product quality and stakeholders’ satisfaction. The data analysis produced a list of 13 refined grounded hypotheses out of which 5 were supported throughout the research. One project was studied in-depth by collecting quantitative data about the process used via a newly designed iteration monitor. The iteration monitor was used by the team over three iterations and it helped identify issues and trends within the team in order to improve the process in the following iterations. Data about other organisations collected via surveys was used to generalise the obtained results. A variety of statistical analysis techniques were applied and these suggested that when agile methods have a good impact on quality they also has a good impact on productivity and satisfaction, also when agile methods had good impact on the previous aspects they reduced cost. More importantly, the analysis clustered 58 agile practices into 15 factors including incremental and iterative development, agile quality assurance, and communication. These factors can be used as a guide for agile process improvement. The previous results raised questions about agile project governance, and to answer these questions the agile projects governance survey was conducted. This survey collected 129 responses, and its statistically significant results suggested that: retrospectives are more effective when applied properly as they had more impact when the whole team participated and comments were recorded, that organisation size has a negative relationship with success, and that good practices are related together as when a team does one aspect well, they do all aspects well. Finally, the research results supported the hypotheses: agile software development can produce good quality software, achieve stakeholders’ satisfaction, motivate teams, assures quick and effective response to stakeholder’s requests, and it goes in stages, matures, and improves over time.
33
Asbjørnslett, Bjørn Egil. "Project supply chain management : From agile to lean." Doctoral thesis, Norwegian University of Science and Technology, Department of Productions and Quality Engineering, 2003. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-339.
Full textAbstract:
More than forty years has passed since the start of the North Sea oil and gas developments. On the managerial side of the projects there have been large cost overruns, project planning and control measures developed to avoid these, initiatives to improve the industry’s competitiveness in the North Sea, as well as measures to improve the supply chains contribution in the projects. We have seen a focus first and foremost on the CAPEX side of the projects, which still is the public measure of a ‘project’s’ success as seen in medias coverage. However, the operation side of the project has been given extended focus, especially through life-cycle cost measures, and life cycle value measures trying to balance out the CAPEX, OPEX and income sides of the project to obtain the most commercial value enhancement from each project. At the same time there has been an increasing focus on the core business among the project demand and supply chain actors in this industry as in most other industries.
Our belief is that this necessitates an enhanced focus on the project demand and supply chains of the industry, both for the projects development and operations phases. A question is whether the project demand and supply chain developments are approached appropriately according to the characteristics of the industry’s project context?
34
Louis, Harriet. "Towards agile requirement engineering." Thesis, Stellenbosch : Stellenbosch University, 2015. http://hdl.handle.net/10019.1/97337.
Full textAbstract:
Thesis (MBA)--Stellenbosch University, 2015.ENGLISH ABSTRACT: Software development is a relatively young science and involves certain tools, techniques, documentation aids and processes that are applied to deliver a software project. As hardware, software and business needs advanced, so did the processes used in managing software development. It is a dynamic and complex process and each development environment or project has its own unique characteristics. For this reason the methodologies followed during the development process is very often debated. Software development teams have a wide array of methodologies to choose from. The development team usually decides what the key success factors are to deliver a software product, and then examines each one within the framework of a list of potential methodologies. This way the team can compare which methodology would best suit their needs. Factors used to evaluate which methodology to follow, includes the size of the project team, rate of expected changes, the primary goal of the project, how requirements will be managed, communication structures that will be followed, the nature of the relationship with the customer, and the organisational culture in the customer organisation. This research report takes a comparative look at Waterfall methods versus Agile methods.
35
Stone, Thomas W. "Lean Accounting Comes to Lean Software Development." Diss., Temple University Libraries, 2018. http://cdm16002.contentdm.oclc.org/cdm/ref/collection/p245801coll10/id/497799.
Full textAbstract:
Business Administration/AccountingD.B.A.
I argue that lean software development firms become more productive if they adopt and align lean managerial accounting systems with lean software development processes. I conduct two experiments on retraining and coaching of software development teams that have used lean and agile software development practices, demonstrating that these practices significantly improve productivity compared to control groups that did not receive this retraining and coaching. In a third experiment, I expand on this theme by introducing lean accounting productivity metrics to a treatment group of software developers. Team leaders actively use these metrics as quantitative “retrospectives” in team meetings to review past performance and identify areas for process improvement. Four months after these metrics are introduced, I measure their impact on the treatment group productivity and also survey the group to determine how these metrics affect employee attitudes and productivity compared to a control group that was not trained in use of these metrics for team meetings. The results indicate that introduction of lean accounting metrics does not impact employee attitudes and understanding of processes and metrics, nor does it improve productivity in the near term. Discussions with management indicate that retraining and coaching immediately improve productivity since they are directed at remedying specific operational and process issues. Using lean accounting metrics to impact team productivity and employee attitudes is more foundational and likely requires a longer period of exposure and learning. The experimental site is a large publicly traded software firm that uses lean and agile software development practices. Key Words: Lean Accounting, Training, Coaching, Software Development, Productivity
Temple University--Theses
36
Hanssen, Geir Kjetil. "From Agile Software Product Line Engineering Towards Software Ecosystems." Doctoral thesis, Norges teknisk-naturvitenskapelige universitet, Institutt for datateknikk og informasjonsvitenskap, 2010. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-11890.
Full textAbstract:
Development and evolution of software products is a challenging endeavor and a significant subfield of software engineering. One of the commonly applied approaches to control and manage this process is software product line engineering (SPLE). There exist a few process frameworks where the development of lines of related software products is basically a sum of two processes: the development of reusable assets and the rapid construction of software applications using predeveloped assets. Agile software development (ASD) is another major paradigm, which also has been widely adopted by the industry over the past decade. SPLE and ASD seek to achieve the same goal i.e. rapid and efficient construction of software. However, the former emphasizes extensive up-front investment in the development of assets for later re-use in contrast to ASD, which emphasizes a reactive approach, avoiding up-front planning and development Even though these two approaches may seem to oppose each other, the industry has lately showed great interest in combining them both, aiming to cover the weaknesses of the one with the strengths of the other. In combination with the overall shift in the software industry from closed systems mindset towards open systems, the uptake of some ASD principles (for example active customer engagement, incremental and iterative development, and open information flows) in product line organizations may contribute to the emergence of more flexible software ecosystems. This thesis presents a longitudinal study of a software product line organization, which has adopted an adapted ASD methodology in an SPLE context and to a large extent has successful in gaining benefits from both approaches, developing towards more open yet controlled processes. Data have been collected over a period of approximately five years following the progression from a strictly waterfall oriented approach, via the adoption of the agile method Evo, up to the current combined agile software product line engineering approach. The following research questions have been addressed in this thesis: RQ1: How can software product line engineering and agile software development be combined? RQ2: How does a software ecosystem shape? The main contributions of this work are: C 1. Through a longitudinal study of a software product line organization we provide detailed insight into an industrial case and how they have changed over time. C 2. We have illustrated some of the details of how SPLE and ASD can be combined in practical terms. We describe the current organization, their product line and their agile software product line engineering process. C 3. We have illustrated how the incorporation of some of the central agile principles has enabled a closer cooperation with external actors. C 4. We have explained the emergence and mode of operation of a software ecosystem, and provided a conceptual model of software ecosystems based on our findings. C 5. We have proposed a theory of software ecosystems, rooted in socio-technical theory and the concept of organizational ecology.
37
Svetinovic, Davor. "Agile Architecture Recovery." Thesis, University of Waterloo, 2002. http://hdl.handle.net/10012/1065.
Full textAbstract:
Many software development projects start with an existing code base that has to be tightly integrated into a new system. In order to make a robust system that will achieve the desired business goals, developers must be able to understand the architecture of the old code base and its rationale. This thesis presents a lightweight approach for the recovery of software architecture. The main goal of the approach is to provide an efficient way for architecture recovery that works on small to mid-sized software systems, and gives a useful starting point on large ones. The emphasis of the process is on the use of well established development techniques and tools, in order to minimize adoption costs and maximize the return on investment.
38
Jalali, Samireh. "Efficient Software Development Through Agile Methods." Licentiate thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-00528.
Full textAbstract:
Context: Distributed teams characterize Global Software Engineering (GSE). GSE stakeholders are from different cultures, geographic places and potentially time zones. These conditions have significant consequences on communication, coordination and control of software projects. Given these constraints, distributed teams need to highly rely on each other. Trust is the glue that holds them together and enables more open communication, which increases their performance and quality of delivered products. Simultaneously, in striving for more efficient software development approaches, Agile values and principles were formulated. Agile methods encourage establishing close collaboration between customers and developers, continuous requirements gathering and frequent face-to-face communications. Objective: The major objective of the research is to study efficient software development approaches particularly in (globally) distributed settings. Thus, the dynamics of trust in GSE are investigated for bringing useful trust improvement suggestions to project managers. Furthermore, Agile practices that have been efficiently applied in GSE are identified through two different systematic literature review approaches (i.e. systematic literature review and backward snowballing). The differences identified in the use of Agile practices lead to a need to better understand and assess Agility. Method: The research methods, include systematic literature reviews and case studies, are applied in different empirical cases. Then, a variety of secondary data collection methods are utilized such as semi-structured interviews, questionnaires, open discussions and presentations. Result: Achieving trust was realized to be crucial and the success factor for trust was the “awareness” of particular GSE challenges, which shall be communicated properly to all distributed team members and proper actions shall be taken to address them. Besides, the literature indicated several successful combinations of Agile and GSE. However, despite utilizing two different literature search methods the identified patterns were similar. The most common practices were “standup meetings” and “sprints/iterations”. Nevertheless, the current literature reports “Agile” as a general term and “distributed team” as the most common team/organization setting, which motivated examining the applicability of existing Agile assessment tools in an industrial setting. We found one of the studied tools sufficiently applicable in the context of the case organization. Conclusions: Trust achievement is crucial for efficient GSE collaborations regardless of the applied software development approach. Although Agile promotes trust among team members, it was formulated without considering teams’ distribution. Hence, combining Agile and GSE is challenging. The literature contains several successful cases of implementing Agile in GSE while practitioners and researchers are not yet consistent regarding their perception of Agile practices and documenting them. Therefore, they need to collaborate closely, illustrate the practices, agree on the terminology, how to document the context, and how to profile/assess Agility. For this purpose, we examined the applicability of a set of Agile assessment tools and proposed one tool for the case organization.
39
Gurram, Chaitanya, and Srinivas Goud Bandi. "Teamwork in Distributed Agile Software Development." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5379.
Full textAbstract:
Context: Distributed software development has become a most desired way of software development. Application of agile development methodologies in distributed environments has taken a new trend in developing software due to its benefits of improved communication and collaboration. Teamwork is an important concept that agile methodologies facilitate and is one of the potential determinants of team performance which was not focused in distributed agile software development. Objectives: This research shed a light on the topic of teamwork in the context of distributed agile software development. The objectives are to identify the factors contributing teamwork of distributed agile teams along with the dependencies between the factors. And, as it is not without challenges to work with unity in a heterogeneous environment, identification of challenges related to teamwork factors of distributed agile teams along with the mitigation strategies is an another objective. Methods: A systematic literature review (SLR) was employed to identify the teamwork factors along with their dependencies and corresponding challenges and mitigation strategies of each teamwork factor from state-of-the-art literature. Quasi-gold standard method was employed as search strategy in SLR to find out the primary studies representing the objective under investigation. Further a survey was conducted with industrial practitioners working in distributed agile projects to validate the findings from state-of-the-art literature. Results: A total of 13 teamwork factors (i.e. team orientation, shared leadership, mutual performance monitoring, backup behavior, feedback, team autonomy, team learning, coordination, communication, trust, collective culture, ease of use of technology, team familiarity), a set of nine dependencies between the teamwork factors and 45 challenges and 41 mitigation strategies related to the teamwork factors were identified from state-of-the-art literature. From survey result, communication, coordination, trust and team orientation were identified as four most important teamwork factors for distributed agile teams. Out of nine dependencies, seven were supported and two were not supported by the practitioners of distributed agile projects. Additionally, nine challenges and 12 mitigation strategies were identified through survey. Conclusions: From this study, we conclude that communication is the top most important factor for successful teamwork of distributed agile teams. And, unlike its prime importance in distributed software development for getting teams work together, trust was identified with a third priority for successful teamwork of distributed agile teams. Similar to the findings of the agile teams, team autonomy was identified with least importance towards the successful teamwork of distributed agile teams. Results of dependencies show that there is need for future research to explore all the dependencies between the teamwork factors. Furthermore, there are teamwork factors with no challenges and mitigation strategies being identified in state-of-the-art literature but later, through survey it was found that practitioners are facing the challenges for that particular teamwork factor. Though, this study identified those missed challenges, due to the limited number of participants involved in the survey, we cannot conclude that these were the only challenges faced in relation to the teamwork. Hence, there is a need to have a dedicated investigation in exploring all the challenges and mitigation strategies, such that it would help the distributed agile teams in attaining the fruitful interactions between them.H.no. 5-5-289, Prashanth Nagar, Vanasthalipuram, Hyderabad-500070, Andhra Pradesh. India
40
Malik, Ahsan Nawaz & Kashif Masood. "Software Testing Process in Agile Development." Thesis, Blekinge Tekniska Högskola, Avdelningen för för interaktion och systemdesign, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4328.
Full textAbstract:
Software testing is the most important process to verify the quality of a product. Software testing in Agile development is very complex and controversial issue in literature and industry. Different people have different views about software testing in Agile methods, because most of Agile methods do not focus much on software testing activities. Agile strongly focus on the close customer collaboration, short iterations and frequent deliveries. But when it comes to software testing, then it is challenging, as Agile do not include many destructive testing practices, which are normally required for a quality product. This thesis covers the area of software testing process in Agile development. Agile development processes could be more beneficial and refined by adding testing practices and for this purpose; we proposed a concept of an independent integrated software testing team. This research also identifies the practices of Agile development in industry and the critical issues in industry while practicing Agile development. The issues of automated and manual testing, good practices in automation, and how to manage independent testing teams in Agile development are also high lightened. This report highlights every aspect of software testing process in Agile development. This research is based on literature reviews and an industrial survey.
41
Cao, Lan. "Modeling Dynamics in Agile Software Development." Digital Archive @ GSU, 2005. http://digitalarchive.gsu.edu/cis_diss/4.
Full textAbstract:
Agile software development challenges the traditional way of software development and project management. In rapidly changing environments, changing requirements and tight schedule constraints require software developers to take a different approach toward the process of software development. However, beyond a few case studies, surveys and studies focused on specific practices such as pair programming, the effectiveness and applicability of agile methods have not been established adequately. The objective of my research is to improve the understanding of and gain insights into these issues. For this purpose, I develop a system dynamic simulation model that considers the complex interdependencies among the variety of practices used in agile development. The model is developed on the basis of an extensive review of the literature as well as quantitative and qualitative data collected from real projects in seven organizations. The development of the model was guided by dynamic hypotheses on customer involvement, refactoring and quality of design. The model was refined and validated using data from independent projects. The model helps in answering important questions on the impact of customer behavior, cost of making changes and economics of pair programming. Experimentation with the model suggests that the cost of change is not constant; instead, its value changes cyclically and increases towards the later phase of development. Also, the results of simulation show that with no pair programming, fewer tasks are delivered and it costs more to deliver a task when compared to development with pair programming. Further, customer behavior has a major impact on project performance. The quality of customer feedback is found to be very critical to the successful of an agile software development project. The primary contribution of this research is the simulation model of agile software development that can be used a tool to examine the impact of agile practices and management policies on critical project variables including project scope, schedule, and cost. This research provides a mechanism to study agile development as a dynamic system of practices rather than using a static view and in isolation. The results from this study are expected to be of significant interest to practitioners of agile methods by providing them a simulation environment to examine the impact of their practices, procedures and management policies.
42
Ehlers, Kobus. "Agile software development as managed sensemaking." Thesis, Stellenbosch : University of Stellenbosch, 2011. http://hdl.handle.net/10019.1/6455.
Full textAbstract:
Thesis (MPhil (Information Science))--University of Stellenbosch, 2011.ENGLISH ABSTRACT: The environment in which all organisations currently operate is undoubtably dynamic. Regardless of the nature, size or geographical location of business, companies are being forced to cope with a rapidly changing world and increasing levels of unpredictability. This thesis tracks the history of software development methodologies leading up to agile development (chapter 2). Agile development has appeared in response to the limitations of traditional development approaches and evolved to address the particular demands of a changing world (chapter 3). The theory of sensemaking is used to gain insight into the functioning of agile development. Sensemaking is introduced and a working definition of this concept is formulated (chapter 4). This research does not argue that agile development is the same as sensemaking, but rather that it can be better understood through sensemaking. Agile development can be seen as a type of sensemaking, but sensemaking is also a generic, universal cognitive ability. The structure and design of agile development is well aligned with sensemaking, and one can understand its nature and the type of management needed to support agile development better from this perspective. In fact, agile development directly supports and facilitates several important elements of the sensemaking process. For successful sensemaking to occur, certain organisational conditions need to be present. The term "managed sensemaking" is introduced to expand this notion. After performing an analysis of agile development (chapter 5), certain pertinent implications and challenges facing organisations are considered (chapter 6). By framing these implications in terms of sensemaking, practical management suggestions can be provided based on a good fit between the problem that agile development is meant to solve and the cognitive requirements of the process leading to a solution. The research conducted in this process opens the door to further research opportunities (chapter 7) and allows for the application of sensemaking in the context of software development methodologies. This study provides insight into the prevalence and functioning of agile methodologies, in software engineering contexts, by leveraging the theory of sensemaking to provide an explanation for the underlying worldview and processes constituting this approach.
AFRIKAANSE OPSOMMING: Die omgewing waarin alle organisasies tans funksioneer in ongetwyfeld dinamies. Maatskappye word genoop om die uitdagings van 'n vinnig-veranderende wêreld die hoof te bied, ongeag die aard, grootte of geografiese ligging van die besigheid. Hierdie tesis volg die geskiedenis van sagteware-ontwikkelingsmetodologiee tot by agile development (hoofstuk 2). Agile development het verskyn as 'n reaksie op die beperkings van tradisionele ontwikkelingsbenaderings en evolueer om aan te pas by huidige uitdagings (hoofstuk 3). Die teorie van sensemaking word gebruik om insig te verkry in die funksionering van agile development. Sensemaking word ingelei en 'n werksdefinisie word geformuleer (hoofstuk 4). Hierdie navorsing argumenteer nie dat agile development dieselfde is as sensemaking nie, maar eerder dat dit beter verstaan kan word deur sensemaking. Agile development kan wel gesien word as 'n tipe sensemaking, maar sensemaking is ook 'n generiese, universele kognitiewe vermoe. Die struktuur en ontwerp van agile development is goed belyn met sensemaking, en 'n mens kan die aard daarvan en tipe bestuur benodig om agile develop- ment te ondersteun beter verstaan vanuit hierdie perspektief. Tewens, agile development ondersteun en fasiliteer verskeie belangrike elemente van die sensemaking proses direk. Vir suksesvolle sensemaking om plaas te vind, word sekere organisatoriese toestande benodig. Die term "managed sensemaking" word ingelei om hierdie idee uit te brei. Na 'n analise van agile development (hoofstuk 5) word sekere dwingende implikasies en uitdagings, wat organisasies in die gesig staar, oorweeg (hoofstuk 6). Deur hierdie implikasies te plaas in sensemaking-terme kan praktiese bestuursvoorstelle aangebied word, gegrond op 'n goeie passing tussen die probleem wat agile development probeer aanspreek en die kognitiewe vereistes van die proses wat lei na 'n oplossing. Die navorsing wat onderneem is in hierdie proses ontsluit moontlikhede vir verdere studies (hoofstuk 7) en skep die moontlikheid vir die toepassing van sensemaking in die konteks van sagtewareontwikkelingsmetodologiee. Hierdie studie bied insig in die voorkoms en funksionering van agile methodologies in sagteware-ingenieurwese omgewings deur die teorie van sensemaking te hefboom om 'n verduideliking vir die onderliggende wereldbeeld en prosesse aan te bied.
43
Rantanen, E. (Eetu). "Requirements engineering in agile software projects." Bachelor's thesis, University of Oulu, 2017. http://urn.fi/URN:NBN:fi:oulu-201705091721.
Full textAbstract:
Many software projects are failed due to the delivery decisions that were made without adequate requirements information. In addition, the project management process including agile-oriented requirement management process has been identified as one of the four success factors in the agile software projects. Having the clear rules for requirements engineering is, therefore, an important thing for agile software projects from their success point of view. In this study, the objective is to analyze agile requirements engineering and to find out practices that are used in it. The goal is to define a continuous process to identify customer needs and translate them into software requirements in the agile software development. This goal is going to be achieved by a systematic literature review on the agile requirements engineering. For the agile software development and the traditional requirements engineering, the theory has been gathered from some basic books of the theme. The primary research question for this study is: How the customer needs will be translated into requirements in the agile software project as a continuous process? There are also two secondary research questions: 1. What are the customer needs and how can they be identified? 2. What kind of practices are used in the agile requirements engineering? Generally, the requirements engineering process includes four separate steps. First, the business usefulness of the system should be evaluated (feasibility study). After that, the requirements are discovered (elicitation and analysis)and converted into some standard form (specification). Last phase includes checking that the requirements define the system as customer wants (validation). Agile requirements engineering includes four major practices. The high-level interaction between the development team and the customer, iterative approach for the requirements engineering, prioritizing the requirements based on their business value for the customer, and eliciting also the non-functional requirements. In addition, the documentation of requirements is minimalistic in agile approaches. Results of this study can generally be applied and the model created can be utilized as a guideline when doing requirements engineering in the agile software projectsMonet ohjelmistoprojektit epäonnistuvat, koska tieto vaatimuksista on riittämätöntä toimituspäätöksiä tehdessä. Lisäksi projektinhallinnan prosessi, johon sisältyy ketterä vaatimustenhallinnan prosessi, on tunnistettu yhdeksi neljästä ketterien ohjelmistoprojektien menestystekijästä. Tämän takia ketterien ohjelmistoprojektien onnistumiseksi on tärkeää, että vaatimusmäärittelylle on selkeät ohjeet. Tämän tutkimuksen tarkoituksena on analysoida ketterää vaatimusmäärittelyä ja löytää siinä yleisesti käytettyjä tapoja. Tavoitteena on määrittää jatkuva prosessi, jossa asiakkaan tarpeet tunnistetaan ja käännetään ohjelmiston vaatimuksiksi ketterässä ohjelmistokehityksessä. Tavoitteeseen pyritään tekemällä systemaattinen kirjallisuuskatsaus ketterään vaatimusmäärittelyyn. Ketterää ohjelmistokehitystä sekä perinteistä vaatimusmäärittelyä käsitellään muutaman perusteoksen pohjalta. Tutkimuksen ylätason tutkimuskysymys on: Kuinka asiakkaan tarpeet käännetään vaatimuksiksi jatkuvana prosessina ketterissä ohjelmistoprojekteissa? Lisäksi tutkimuksella on kaksi alatason tutkimuskysymystä: 1. Mitä asiakkaan tarpeet ovat ja kuinka ne tunnistetaan? 2. Minkälaisia tapoja ketterässä vaatimusmäärittelyssä käytetään? Yleinen vaatimusmäärittelyprosessi sisältää neljä vaihetta. Ensin arvioidaan järjestelmän liiketoiminnallinen tarpeellisuus (kannattavuusselvitys). Tämän jälkeen etsitään vaatimuksia (selvitys ja analyysi) ja käännetään ne johonkin standardimuotoon (spesifikaatio). Viimeisessä vaiheessa tarkistetaan, että vaatimukset määrittävät järjestelmän juuri asiakkaan haluamalla tavalla (validointi). Ketterässä vaatimusmäärittelyssä on neljä yleistä käytäntöä. Korkean tason kanssakäyminen asiakkaan ja kehitystiimin välillä, iteratiivinen eli toistava lähestymistapa vaatimusmäärittelyyn, vaatimusten priorisointi perustuen asiakkaalle syntyvään arvoon ja myös ei-funktionaalisten vaatimusten tunnistus. Lisäksi voidaan sanoa, että vaatimusten dokumentointi ketterissä menetelmissä on vähäistä. Tämän tutkimuksen tuloksia voidaan yleisesti ottaen hyödyntää ja kehitettyä mallia voidaan käyttää vaatimusmäärittelyn ohjenuorana ketterissä ohjelmistoprojekteissa
44
Flaten, Kayla. "The Progression of Agile Software Development." Scholarship @ Claremont, 2017. http://scholarship.claremont.edu/cmc_theses/1717.
Full textAbstract:
This paper examines the use of Agile Software Development in the technology industry and how it came to be one of the leading models used in project management. By investigating the software development methods used in the late 1900s, it becomes clear where the system needed improvement in order to improve the efficiency in developing products. In investigating the Agile Manifesto, new and essential components are introduced that become vital in successfully producing a product. From this, it is easier to understand why Agile is so commonly used in the software development industry and how it became so effective.
45
Odzaly, Edzreena Edza. "Managing software risk in agile projects." Thesis, Queen's University Belfast, 2015. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.696155.
Full textAbstract:
Risk management in software engineering has become a recognized project management practice but it seems that not all companies are systematically applying it. At the same time, agile methods have become popular, partly because proponents claim that agile methods implicitly reduce risks due to for example, more frequent and earlier feedback, shorter periods of development time and easier prediction of cost. Therefore, there is a need to investigate how risk management can be usable in iterative and evolutionary software development processes. This research work aims to answer this need by building an appropriate and realistic model of risk management and to support this with a tool for managing risk in agile projects. The approach can be characterized as lightweight risk management which provides the needs of risk management but limits the human effort expended. This is achieved by using software agents to carry out risk identification, risk assessment and risk monitoring, the agents making use of data collected from the project environment. This thesis describes a new solution approach supported by an Agile Risk Tool (ART) which includes a model of the risk environment and support for risk management in agile development environments. In the approach used, the project manager has to define these elements: project goals, problem scenarios, consequences, risk indicators, project environment data as well as specifying risk rules using a predefined 'Rule template'. Therefore risk can be explicitly managed in the early phase of the project, leaving the designated software agents to monitor the rest. The ART model and tool support is evaluated using two case studies, both from student projects. Evidence is therefore provided for the feasibility and applicability of the approach. Overall, the research contributes a new method for risk management in agile software processes, the necessary tool support to demonstrate the method in practice as well as providing evidence to support the efficacy of the approach. In addition, an example is given of the use of software agents as a potential means to reduce the burden of risk management in software projects.
46
Custódio, Pedro Miguel Caiado. "Scrum para lean : como tornar o scrum mais lean." Master's thesis, Instituto Superior de Economia e Gestão, 2015. http://hdl.handle.net/10400.5/10342.
Full textAbstract:
Mestrado em Gestão de ProjetosA aplicação do conceitos lean na gestão de projetos de desenvolvimento de software tem vindo a despertar cada vez mais o interesse dos gestores de projeto, dadas as evidências apresentadas na literatura de como estes conceitos conseguem aumentar o desempenho dos projetos, reduzindo custos, ao mesmo tempo que geram mais valor para os clientes. As experiências que reportam a aplicação destes conceitos, comparam a aplicação do lean com as metodologias ágeis de gestão de projetos de software, denominadas como agile, indicando as suas limitações e como o lean pode contribuir para a eliminação ou redução das mesmas. Este estudo trás uma abordagem diferente dado que a investigação foca-se em como a aplicação dos conceitos lean consegue contribuir para a evolução de uma metodologia ágil de gestão específica, o Scrum. Para tal, foram identificados quais os princípios e conceitos que atualmente os praticantes de Scrum já aplicam, e com que resultados. Com a análise dos resultados obtidos conclui-se que há conceitos lean que, quando corretamente aplicados, conseguem contribuir positivamente para a evolução do Scrum.
The application of lean concepts in software development project management has been increasingly arouse the interest of project managers, given the evidence presented in literature that show how these concepts can increase projects performance, reducing costs at the same time that generate more value for customers. The experiences that report on the application of these concepts, compare the application of lean with Agile project management, presenting their limitations and how lean can help to eliminate or reduce them. This study brings a different approach as the research focuses on how the application of lean concepts can contribute to the evolution of one specific agile methodology, Scrum. To do this, the principles and concepts that Scrum practitioners currently apply and with what results were identified. The results analysis shows that there are lean concepts that, when properly applied, can contribute positively to the evolution of Scrum.
47
Lyngman, Daniel, and Martin Talls. "Lean och Agile : En jämförelse inom IT och produktion." Thesis, KTH, Industriell produktion, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-90957.
Full textAbstract:
Lean och Agile är två arbetsmetodsfilsofier utvecklade från produktion respektive IT. Denna rapport ämnar besvara hur dessa är relaterade och om filosofierna med fördel kananvändas inom motstående område. En teoretisk litteraturstudie har genomförts med sökningar i databaser efter relateradforskning. Detta gav en god inblick om de både områdena var för sig och även omanvändandet av Lean inom IT. Däremot saknades information om Agile inom produktion. En empirisk studie bestående av tre intervjuer med konsulter som hjälper företag införa Lean och Agile hos företag gav en djupare förståelse. Speciellt diskuterades även hur Agile skulle kunna användas inom produktion. Det visade sig att ett Leant företag automatiskt blir ett Agilt företag och att Lean förklarar varför Agile fungerar. Agile ryms inom Lean. Att Lean används framgångsrikt inom IT framgick i litteraturstudien och förklaras av att Lean som filosofi inte är inskränkt till produktion utan lätt kan anpassas inom andraområden. Inom produktion fungerar inte det Agila kortsiktiga synsättet på grund av skillnaderna i produkterna. Företag som använder Lean kommer fortsätta med detta så länge de ser förbättringar, alltså kommer inte Agile provas inom produktion. Däremot skulle vissa detaljer inom Agile kunna användas inom produktion.
48
Le, D. (Dat). "Agile practices adoption with Lean in growing entrepreneur companies." Master's thesis, University of Oulu, 2019. http://jultika.oulu.fi/Record/nbnfioulu-201905101711.
Full textAbstract:
Abstract. There are three popular terms in the software development industry recently, they are Agile, Lean and Entrepreneurs. Agile is an approach in which requirements and solutions for the products evolve through short cycles. Entrepreneur can be defined as the process of designing, launching and running a new business based on potential opportunities and often is a small business. In recent years, entrepreneurs firms follow Lean concepts in Information Technology industry are trying to adopt Agile methodologies because they believe it helps them to avoid failures and grow faster. However, when growing they often face problems to maintain the agility which they have when they were smaller.
The aim of this study is to find out approaches and lessons which can be used to adopt Agile practices in young expanding firms. In addition, those methods were compared to those from large-scale Agile frameworks to give conclusions on adoption approaches.
Three interviews were conducted with the high-level managers of target case companies and two of them based in Oulu, Finland and one located in Hanoi, Vietnam. All of the companies which joined the research are working software development area but each of them has a different pathway and side services. They also share are similar numbers of employees above 9 and smaller than 30, which is the reason that they were chosen. Another reason for this selection is that all of them called themselves a Lean start-up or following core concepts of it. On another hand, large-scale Agile frameworks were introduced as an approach for big organizations to adopt Agile practices. In this research, lessons from those frameworks were proposed as suggestions and a new point of view for maintaining agility.
The results of the research can be concluded that focusing on customer requirements, forming small Agile teams and giving more freedom to members are three practices that companies in the interview are using. Furthermore, from designed frameworks, it showed that having dynamic teams, enhancing the value of each iteration and improving the training process are ways to improve the adoption process in large firms.
49
Álvarez, Carlos García. "Overcoming the Limitations of Agile Software Development and Software Architecture." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-6120.
Full textAbstract:
Context. Agile Software Development has provided a new concept of Software Development based in adaptation to changes, quick decisions, low high-level design and frequent deliveries. However, this approach ignores the value that Software Architecture provides in the long term for increasing the speed in delivery working software, which may have catastrophic consequences in the long term. Objectives. In this study, the combination of these two philosophies of Software Development is investigated. Firstly, the concept of Software Architecture in Agile Projects; then, the major challenges faced concerning Software Architecture in Agile Projects, the practices and approaches that can be used to overcome these challenges and the effects that these practices may cause on the project. Methods. The research methodologies used in this study are Systematic Literature Review for gathering the highest amount possible of contributions available in the Literature at this respect, and also the conduction of Semi-Structured Interviews with Agile Practitioners, in order to obtain empirical knowledge on the problem and support or deny the SLR findings. Results. The results of the Thesis are a unified description of the concept of Software Architecture in Agile Projects, and a collection of challenges found in agile projects, practices that overcome them and a relation of effects observed. Considering the most frequent practices/approaches followed and the empirical support, it is enabled a discussion on how to combine Software Architecture and Agile Projects. Conclusions. The main conclusion is that there is not a definite solution to this question; this is due to the relevance of the context (team, project, customer, etc.) that recommends the evaluation of each situation before deciding the best way to proceed. However, there are common trends on the best-recommended practices to integrate these two concepts. Finally, it is required more empirical work on the issue, the conduction of controlled experiments that allows to quantify the success or failure of the practices implemented would be most helpful in order to create a body of knowledge that enables the application of certain practices under certain conditions.
50
Usta, Ahsen Serkan. "Tool Support For Distributed Agile Software Development." Master's thesis, METU, 2006. http://etd.lib.metu.edu.tr/upload/12607156/index.pdf.
Full textAbstract:
Agile Software Development has gained popularity with their people
centric view and their common practices for developing software in
today&rsquos volatile business world where change on requirements is unavoidable. However
the efficiency of the project depends on the communication and the collaboration of the team, which are supported by the co-location of the team. But in some cases colocation of the team cannot be realized, thus agile processes should also support distributed teams. This point was observed by Kircher, Jain, Corsaro, and Levine [31] and they suggested Distributed eXtreme Programming (DXP) after they prepared a study using offthe- shelf software products in order to replace the effect of face-toface communication on the efficiency of the application of agile processes with the aid gathered from tool support. In this study some available tool support for distributed agile software development is investigated and a tool is developed and presented in order to support software configuration management as well as increasing collaboration and communication of the team. The tool is then evaluated from a user&rsquo
s perspective and it is compared with some available software configuration management tools.