• Refine Query
  • Source
  • Publication year
  • to
  • Language
  • 51
  • 32
  • 28
  • 13
  • 3
  • 1
  • 1
  • 1
  • 1
  • 1
  • 1
  • Tagged with
  • 139
  • 139
  • 66
  • 54
  • 35
  • 34
  • 34
  • 32
  • 32
  • 32
  • 29
  • 29
  • 26
  • 20
  • 20
  • About
  • The Global ETD Search service is a free service for researchers to find electronic theses and dissertations. This service is provided by the Networked Digital Library of Theses and Dissertations.
    Our metadata is collected from universities around the world. If you manage a university/consortium/country archive and want to be added, details can be found on the NDLTD website.

Agile Methods (Scrum, XP) Applying into Small (Micro) Enterprise Brusiness Website Development : A case study of Dalsland Travel AB website development project

Shen, Bin January 2013 (has links)
No description available.

The agile methods : an analytical comparison of five agile methods and an investigation of their target environment : a thesis presented in partial fulfillment of the requirements for the degree of Master of Information Sciences in Information Systems at Massey University, Palmerston North, New Zealand

Strode, Diane Elizabeth Unknown Date (has links)
This study defines the systems development methodologies named agile methods and investigates the environmental conditions where agile methods are most suitable. A definition of agile methods was developed using an analytical comparativeframework to investigate five of the earliest published agile methods; Dynamic SystemsDevelopment Method, Extreme Programming, Scrum, Adaptive Software Development,and Crystal Methods. The framework decomposed each method into its componentparts; philosophy, models, techniques, tools, scope, outputs, practice, and the extent towhich the method may be adapted to a situation. Based on this analysis and a literaturereview, a theoretical model of the target environment for agile methods was developed.This theoretical model is a proposed set of organisation, people, project, technology,and domain factors that relate to the successful use of an agile method.A mixed method research methodology was used. A qualitative design, consisting ofpositivist case studies, was used to test the theoretical model. Data was gathered fromnine software development projects, both agile and non-agile, using questionnaires andinterviews of project leaders. Then cross-case analysis was carried out on each projectfactor in the theoretical model. The relationship between environmental factors andagile method usage was investigated using non-parametric quantitative data analysis.This led to a revised model of the target environment for agile methods. The empiricaldata showed that specific organisational culture factors correlate with effective use of anagile method. These include the organisational characteristics of feedback and learning,teamwork, empowerment of people, collaboration, leadership, loyalty, and a resultsorientedculture that values entrepreneurship, innovation and risk taking.This research is significant for method users, those carrying out empirical research into agile methods, and those carrying out studies of systems development methodologies.

Agila projektledningsmetoder och motivation : Varför man blir produktiv av att flytta lappar på en whiteboard / Agile project management methods and motivation : Why moving sticky notes on a whiteboard boosts productivity

Jansson, Tomas January 2015 (has links)
Agile methods for Information Systems Development (ISD) projects are claimed to encourage developers to be more flexible and efficient by means of arrangements in the development team’s physical and social environment. Research has, however, not yet answered the questions of how, why, and in what contexts agile methods work. ISD can be understood as a highly complex undertaking, which requires the developers’ creativity. The creative process is susceptible to the individual’s task motivation, which in turn is affected by the physical and social environment. In view of this, I argue that theories of motivation, such as the Self-Determination Theory, and theories of creativity could be usefully applied in such research. This study analyses Scrum, one of the most popular agile methods. Empirical data were collected through focused interviews with developers who had extensive experience of working in projects using various agile methods. Narratives of work episodes with perceived high and low motivation were analyzed in terms of motivation theory. Interview data were classified according to the type of motivation experienced and analyzed in relation to the agile method arrangement involved. The results of the investigation demonstrate how agile methods affect developers’ motivation in ways that are conducive to creative performance. The most pronounced effects are related to the individuals’ perceived work-related competence, autonomy, and sense of belonging to the team. Several agile arrangements in combination affect motivation in the positive direction, the single most influential factor being the team’s daily stand-up meetings. The agile arrangement that seems most difficult to implement without causing episodes of low motivation is the product owner role. The analytical approach taken in this study contributes to a better understanding of the aspects that are critical to the successful implementation of agile methods. / Agila metoder för systemutvecklingsprojekt syftar till att öka utvecklarnas flexibilitet och effektivitet genom arrangemang av utvecklarnas fysiska och psykosociala arbetsmiljö. Forskning om hur, varför och i vilka sammanhang agila metoder fungerar är dock ännu otillräcklig. Systemutveckling kan beskrivas som en komplex uppgift som fordrar utvecklarnas kreativitet. Individens kreativa process påverkas av individens uppgiftsmotivation, vilken i sin tur påverkas av faktorer i den fysiska och psykosociala arbetsmiljön. Mot den bakgrunden framhålls psykologisk teori om motivation, som Self-Determination Theory, och teori om kreativitet, som relevant för forskning om agila metoder. I avhandlingen analyseras Scrum, en av de mest populära agila metoderna. Empiriska data har hämtats från fokusintervjuer med utvecklare med lång erfarenhet av arbete i agila projektmiljöer. Deras berättelser om episoder med starka motivationsupplevelser har analyserats med stöd av teorin. Intervjudata har klassificerats avseende motivationstyp och i relation till inverkande agila arrangemang. Resultaten visar hur agila metoder inverkar på utvecklares motivation i avseenden med relevans för kreativa prestationer. Starkast var inverkan relaterad till utvecklarnas upplevelse av arbetsrelaterad kompetens, autonomi och samhörighet med utvecklingsteamet. Flera samverkande agila arrangemang inverkade positivt på motivationen; allra starkast inverkan hade teamets dagliga stå-upp-möte. Det agila arrangemang som var svårast att implementera utan att bidra till uppkomsten av negativt inverkande episoder var rollen produktägare. Studien bidrar med kunskap relevant för implementering av agila metoder i systemutvecklingsprojekt.

Dynamiska metoder för små systemutvecklingsprojekt

Ahmed, Reham January 2003 (has links)
<p>Litteratur inom systemutvecklingsområdet visar behov av nya snabbare systemutvecklingsmetoder. Orsaken är komplexiteten både i systemutvecklings</p><p>projekten och i organisationer, där systemutveckling sker. Nu föredras små projekt, som omfattar färre än tio deltagare och genomförs på mindre än ett år. De traditionella systemutvecklingsmetoder anses vara lämpliga för stora projekt. Det finns nya systemutvecklingsmetoder, som får benämningen dynamiska metoder, för små projekt. I detta examensarbete studeras faktorer för två dynamiska metoder som gör dem lämpliga för små projekt. De två dynamiska metoderna som kommer att studeras är Extreme Programming och en specifik dokumenterad anpassning av RUP.</p><p>Syftet med detta examensarbete är att studera metoddokumentationen för två dynamiska metoder för att reda ut i vilken utsträckning de passar för små projekt. Ett ytterligare syfte är att genom analys av andras erfarenheter om tillämpningar av de två metoderna redogöra för det som styrker argumenten om deras lämplighet för små projekt.</p><p>För att besvara frågeställningen studerades litteratur och ett antal artiklar. Två telefonintervjuer genomfördes också för att besvara en av de två delfrågorna, som tillsammans utgör frågeställningen för denna studie. Resultatet visar att den specifikt dokumenterade anpassade RUP inte följer alla aspekter för små projekt. Däremot följer Extreme Programming alla de aspekterna.</p>

Using Feature Models For Reusability In Agile Methods

Jedyk, Marcin 01 June 2011 (has links) (PDF)
The approach proposed in this thesis contributes to implementing source code reuse and re-engineering techniques for agile software development. This work includes an introduction to feature models and some of the Feature Oriented Software Development (FOSD) practices to achieve a lightweight way of retrieving source code. A Feature model created during the course of following FOSD practices serves as an additional layer of documentation which represents the problem space for the developed application. This thesis proposes linking source code with such a feature model for the purpose of identifying and retrieving code. This mechanism helps with accessing the code segment corresponding to a feature with minimal effort, thus suits agile development methods. At the moment, there is a gap between feature oriented approaches and agile methods. This thesis tries to close this gap between high-level approaches for software modelling (feature modelling) and agile methods for software development.

Agile Methods in large-scale software development organizations:applicability and model for adoption

Laanti, M. (Maarit) 08 January 2013 (has links)
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 Aspects. / Tiivistelmä 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.

Využití agilních metod při tvorbě strategických materiálů / The Application of Agile Methods in the Process of Strategic Materials

Waldhans, Marek January 2012 (has links)
This master thesis focuses on the agile methods description and their use in creating of company strategic material. The main part of this thesis consist of the SCRUM and Kanban method. The work contribution is an optimization of the document creation process. The solution proposed is implemented through the MS SharePoint server with mind mapping module and Kanban board module. Thanks to this solution, company project can be managed in a more effective, faster and higher quality way.

Agila metoder i praktiken : En fallstudie om kommunikation och motivation

Khosravi, Patricia, Thurow, Stephanie January 2018 (has links)
Agile methods have become a popular project managing method within software development (Cervone, 2011, ss. 19-20; Maximini, 2015, s. 3). Though there is an absence of studies on agile methods and motivation in employees (Dybå &amp; Dingsøyr, 2008). Furthermore, the agile manifesto (2001) explains the importance of motivated employees for the development of software.   The purpose of this study is to examine how employees in two well-known Swedish companies perceive the use and the effects of agile methods in their organization, and their internal communication. The study followed a qualitative approach to measure data collected from semi-structured interviews and includes interviews with eight developers and two agile coaches in two organizations. The theoretical framework is based on Media Richness Theory and Self-determination Theory. The selected theories help the examination why a communication channel is chosen for disseminating information and motivational factors through asking questions about their sense of autonomy, relatedness and competence.   The results show that face-to-face conversation is the efficient communication channel to disseminate information, but the most utilized channel was chat and mail to the respondents. Additionally, our respondents experience motivational factors such as the feeling of competence and relatedness as being moderately fulfilled at their workplace, though feelings of autonomy on an individual level were not fulfilled. This indicates that a complete introduction to the work method, a variation between independent and group work and face-to-face communication should be encouraged to achieve internal communication.

Zavedení agilních metod ve firmě / Application of Agile in a Company

Fotijev, Petr January 2016 (has links)
This master thesis deals with problems of information technology projects and their solutions using agile project management. Based on an analysis of the company and its projects is suggested solution using agile methods.

Padrões de testes automatizados / Automated Test Patterns

Paulo Cheque Bernardo 04 July 2011 (has links)
A qualidade dos sistemas de software é uma preocupação de todo bom projeto e muito tem se estudado para melhorar tanto a qualidade do produto final quanto do processo de desenvolvimento. Teste de Software é uma área de estudo que tem crescido significativamente nos últimos tempos, em especial a automação de testes que está cada vez mais em evidência devido à agilidade e qualidade que pode trazer para o desenvolvimento de sistemas de software. Os testes automatizados podem ser eficazes e de baixo custo de implementação e manutenção e funcionam como um bom mecanismo para controlar a qualidade de sistemas. No entanto, pouco conhecimento sobre a área e erros comuns na escrita e manutenção dos testes podem trazer dificuldades adicionais aos projetos de software. Testes automatizados de baixa qualidade não contribuem efetivamente com o controle de qualidade dos sistemas e ainda demandam muito tempo do desenvolvimento. Para evitar esses problemas, esta dissertação apresenta de forma crítica e sistemática as principais práticas, padrões e técnicas para guiar o processo da criação, manutenção e gerenciamento dos casos de testes automatizados. Inicialmente, são feitas comparações entre a automação de testes e outras práticas de controle e garantia de qualidade. Em seguida, são apresentados os problemas e soluções mais comuns durante a automação de testes, tais como questões relacionadas a tipos específicos de algoritmos, sistemas com persistência de dados, testes de interfaces de usuário e técnicas de desenvolvimento de software com testes automatizados. Para finalizar, a dissertação traz uma reflexão sobre o gerenciamento e a abordagem da automação de testes para tornar o processo mais produtivo e eficaz. / The quality of software systems is a concern of every good project and much has been studied to improve the quality of the final product and process development. Software Testing is an increasing area, especially test automation, which is in evidence due to the speed and quality that it may bring to the development of software systems. Automated tests can be effective and can have a low cost of implementation and maintenance to ensure and control the quality of the systems. However, little knowledge about the area and common errors in writing and maintaining tests may bring additional difficulties to the software projects. Low quality automated tests do not contribute effectively to quality control systems and still take a long time of development. To avoid these problems, we present critically and systematically the core practices, standards and techniques to guide the process of creation, maintenance and management of automated test cases. Initially, comparisons are made between the test automation, other control practices, and quality assurance. Next, we present the most common problems and solutions for the automation of tests, such as issues related to specific types of algorithms, systems with data persistence, testing user interfaces and techniques for software development with automated tests. Finally, this essay reflects on the management and approach to test automation to make the process more productive and effective.

Page generated in 0.1292 seconds