• 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.
61

Ljud i rörelse : Att framhäva ljudens berättande potential

Nohage, Jesper, Danielsson, Simon January 2018 (has links)
Med detta kandidatarbete strävar vi efter att utveckla en förståelse och ett intresse för ljuddesignens berättande funktion. Detta strävar vi efter genom att tillämpa ett rhizomatiskt perspektiv i vår designprocess samt försök till att närma oss en icke-linjär designmetodik. Det rhizomatiska perspektivet används som en källa för inspiration, en väg till att finna nya lösningar och verktyg till berättandet. Vårt prövande av ljuddesignen gjordes i en filmproduktion där vi som ljuddesigners gjorde försök till att väva in ljuddesign under hela projektets gång och arbeta proaktivt för att skapa utrymme för vår design. / With this bachelor thesis we seek to expand the understanding and interest of the narrative potential in sound design. We aim to do this by applying a rhizomatic perspective to our design process and attempt to approach a non-linear design method. The rhizomatic perspective is used as a source of inspiration, a way of finding new narrative tools and solutions. The testing of sound design was made in a film production where we, as sound designers, made attempts to weave sound design into the whole course of the project and work proactively to create space for our design.
62

Styrformers spridning och översättning : En studie om agila metoder i litteratur och i praktiken

Cengiz, Alex, Danho, Markus January 2017 (has links)
Syfte: Syftet med denna uppsats är att studera agila metoders möjligheter att spridas, och projektledares erfarenheter avseende motivering och implementering av agila metoder. Teori: Denna studie tillämpar Røviks teorier om institutionaliserade organisationsrecept. Teorin om receptens spridning har använts för att analysera om agila metoder har egenskaperna för att spridas. För att undersöka motiveringen till användning av agila metoder har motiveringsfasen använts. Därtill har införingsfasen med fokus på översättning av recept använts för att analysera implementeringen av agila metoder. Metod: En kvalitativ metod med en deduktiv ansats har använts vid denna studie då dessa ansågs vara lämpliga för att uppfylla studiens syfte. Primärdatan har samlats in genom semistrukturerade intervjuer med projektledare som valdes genom ett bekvämlighetsurval. Studien har även berikats med sekundärdata i form av konceptlitteratur om agila metoder. Slutsatser: Utifrån den valda teorin förefaller spridningsmöjligheterna för agila metoder vara svag. Projektledarnas berättelser om implementering av agila metoder visar på att metoderna har anpassats, översatts utifrån projektens förutsättningar. De metoder som har använts och kombinerats är Scrum och Kanban. Begreppen iteration, kommunikation, kunden och flexibilitet var återkommande argument för användning av metoderna. / Purpose: The purpose of this paper is to study the diffusion possibilities of agile methods, and project managers' experiences regarding the motivation and implementation of agile methods. Theory: The following study has been done using Røvik's theories of institutionalized organization recipes. The theory of the diffusion of recipes has been used to analyze whether agile methods have the properties in order to spread. To investigate the motivation for using agile methods, the motivation phase has been used. In addition, the adoption phase with focus on translation of recipes has been used to analyze the implementation of agile methods. Method: A qualitative method with a deductive approach has been used in this study, as these were considered appropriate for the purpose of the study. The primary data has been collected through semi-structured interviews with project managers chosen through a convenience sample. The study has also been enriched with secondary data in the form of conceptual literature on agile methods. Conclusions: Based on the chosen theory, the possibilities for diffusion of agile methods appear to be weak. The stories told by the project managers regarding the implementation of agile methods show that the methods have been adapted, translated according to the circumstances of the projects. The methods that have been used and combined are Scrum and Kanban. The concepts of iteration, communication, customer and flexibility were recurring arguments for using the methods.
63

Agilt - men agilt nog?

Mählberg, Esbjörn January 2011 (has links)
This paper aims to investigate whether a small organization with small development teams can find a value in leaving a functioning development process to follow a formal systems development methodology, if these organizations can find support in an agile systems development method and in such case the method needs to be adjusted according to the organizations unique conditions. A traditional plan-driven system development methodology includes a number of phases that are carried out sequentially and a completed phase can basically not be resumed. All requirements are specified at the beginning of a project and at the end of the project only one delivery of software take place. This can cause difficulties in for example dealing with changing requirements. Agile system development methods intend to deal with changing requirements and to enable continuous delivery of valuable, working software. In this paper, both the traditional plan-driven methods and agile methods will be explained. Research methodology and existing system development theories will be discussed and a company where the study has been conducted will be presented. The company's current work processes are analyzed and presented, and all collected data will be reviewed. The results of the paper shows that no initial adaptation of agile methods, Scrum in this specific case, needs to be implemented and that there is no evidence to suggest that small organizations with small development teams can not work after a formal agile methodology. Finally, a general discussion of the study will be conducted and conclusions whether the study objective has been achieved or not will be discussed. / Denna uppsats ämnar undersöka huruvida en mindre organisation med små utvecklingsteam kan finna ett värde i att lämna en fungerande utvecklingsprocess för att följa en formell systemutvecklingsmetod, ifall dessa organisationer kan hitta ett metodstöd i agila systemutvecklingsmetoder och om metoderna i så fall behöver anpassas utefter organisationens unika förutsättningar. En traditionell plandriven systemutvecklingsmetod innehåller ett antal faser som genomförs sekventiellt och en slutförd fas kan i stort sett inte återupptas. Alla krav specificeras i början av ett projekt och endast en leverans av mjukvara sker. Detta kan medföra svårigheter med att hantera till exempel förändrade krav. Agila systemutvecklingsmetoder har för avsikt att hantera förändrade krav samt möjliggöra kontinuerliga leveranser av värdefull och fungerande programvara. Under uppsatsen kommer såväl traditionella plandrivna metoder som agila metoder att förklaras närmare. Metodval för forskningen och befintliga systemutvecklingsteorier kommer att diskuteras och ett företag där studien har bedrivits kommer att presenteras. Företagets nuvarande arbetsprocess analyseras och presenteras och alla datainsamlingar kommer att gås igenom. Resultatet av uppsatsen visar på att inga initiala anpassningar av agila metoder, Scrum i det här specifika fallet, behöver genomföras och att det inte finns något som tyder på att små organisationer med små utvecklingsteam inte kan arbeta efter en formell agil metod. Slutligen kommer en allmän diskussion om studien att föras och slutsatser gällande om syftet med studien har uppnåtts kommer att diskuteras.
64

Análise da utilização de métodos ágeis no desenvolvimento de ambientes virtuais de aprendizagem: um estudo de caso do Solar 2.0 / Analysis of the use of agile methods in the development of virtual learning environments: a case study of the Solar 2.0

Torres Filho, Ari do Amaral January 2014 (has links)
TORRES FILHO, Ari do Amaral, Análise da utilização de métodos ágeis no desenvolvimento de ambientes virtuais de aprendizagem: um estudo de caso do Solar 2.0. 2014. 158 f. : Dissertação (mestrado) - Universidade Federal do Ceará, Centro de Ciências, Departamento de Computação, Fortaleza-CE, 2014. / Submitted by guaracy araujo (guaraa3355@gmail.com) on 2016-05-31T19:51:19Z No. of bitstreams: 1 2014_dis_aatorresfilho.pdf: 5052662 bytes, checksum: bbc494f5731e2ba4a447896641ee5d11 (MD5) / Approved for entry into archive by guaracy araujo (guaraa3355@gmail.com) on 2016-05-31T19:51:40Z (GMT) No. of bitstreams: 1 2014_dis_aatorresfilho.pdf: 5052662 bytes, checksum: bbc494f5731e2ba4a447896641ee5d11 (MD5) / Made available in DSpace on 2016-05-31T19:51:40Z (GMT). No. of bitstreams: 1 2014_dis_aatorresfilho.pdf: 5052662 bytes, checksum: bbc494f5731e2ba4a447896641ee5d11 (MD5) Previous issue date: 2014 / In the last two decades there has been considerable progress in the use of Information Technologies and Digital Communication in the process of teaching and learning, both in the form of classroom education as distance. In this context, the use of Virtual Learning Environments - software designed to support the courses via the Internet - is growing and access becoming increasingly diverse, ranging from desktop computers to mobile smartphones. Thus, the complexity of creating these environments becomes increasingly technical and requires Software Engineering and Project Management always better to ensure product quality and customer satisfaction generated. Given such a scenario, this paper proposes the use of Agile methodologies in the development and project management of virtual environments as a more interesting way than traditional software delivery based only on product quality, forgetting often , customer satisfaction and motivation of developers. This paper reports the adoption of agile methodologies in the development of the SOLAR AVA 2.0, showing that it is possible to succeed in both the technical level and at the organizational and personally with the adoption of agile practices in the development of AVAs that can be proven through experiments done with the satisfaction surveys with users and project developers. / Nas duas últimas décadas houve um considerável avanço no uso de Tecnologias da Informação e Comunicação Digitais no processo de ensino e aprendizagem, tanto na modalidade de Educação presencial quanto a distância. Neste contexto, o uso de Ambientes Virtuais de Aprendizagem - softwares criados para o suporte a cursos através da Internet - vêm crescendo e seu acesso se tornando cada vez mais diversificado, indo de computadores desktop a celulares smartphones. Desta forma, a complexidade de criação destes ambientes se torna cada vez maior e exige técnicas de Engenharia de Software e Gestão de Projetos cada vez melhores para garantir a qualidade do produto gerado e a satisfação do cliente. Tendo em vista tal cenário, o presente trabalho propõe o uso de Metodologias Ágeis tanto no desenvolvimento quanto na gestão de projetos de ambientes virtuais como uma solução mais interessante que a tradicional forma de criação de softwares baseada somente na qualidade do produto, esquecendo, muitas vezes, a satisfação do cliente e a motivação dos desenvolvedores
65

[en] REPORTING THE EXPERIENCE OF DEPLOYMENT OF SOFTWARE ENGINEERING BEST PRACTICES IN A HETEROGENEOUS ENVIRONMENT / [pt] RELATO DE EXPERIÊNCIA DA IMPLANTAÇÃO DE BOAS PRÁTICAS DE ENGENHARIA DE SOFTWARE EM UM AMBIENTE HETEROGÊNEO

KELLY AZEVEDO BORGES LEAL 31 January 2011 (has links)
[pt] Métodos Ágeis são estratégias recentes na Engenharia de Software (começaram a se popularizar em 2001), que surgiram com a promessa de serem flexíveis e adaptáveis - características muito importantes para lidar com constantes mudanças de requisitos em projetos. O Scrum, método ágil estudado neste trabalho, necessita de uma infraestrutura adequada para gerar benefícios ao time que o utiliza. Neste estudo, implementou-se o Scrum, com o auxílio de uma infraestrutura adequada de ferramentas e processos, em uma organização que não utilizava qualquer tipo de gerenciamento de projetos. A partir do estabelecimento de algumas metas com o apoio do modelo GQM, buscou-se a melhoria nas métricas relacionadas e os resultados estão detalhados neste presente trabalho. / [en] Agile methodology is a recent Software Engineering strategy (it became popular in 2001) that was created to be flexible and adaptable enough - characteristic very import to deal with constant requirements changes during a project lifecycle. Scrum, the agile methodology used during this study, requires an adequate infrastructure in order to offer its benefits. This study implemented Scrum and an adequate infrastructure of processes and tools to support it, inside a organization that didn’t use any kind of project management before. With the establishment of some goals using the GQM model, some improvements were expected and the results are detailed in this study.
66

Definição e gerenciamento de métricas de teste no contexto de métodos ágeis / Definition and management of testing metrics in agile methods context

André Abe Vicente 22 April 2010 (has links)
Métodos ágeis são técnicas adequadas para o desenvolvimento de software sujeito a mudanças constantes. Essas mudanças não devem afetar o cronograma, orçamento do projeto e devem assegurar o atendimento às necessidades do cliente. Diversos valores, princípios e boas práticas de desenvolvimento e de condução de projeto são aplicados em projetos ágeis com esse objetivo. Algumas dessas práticas são relacionadas a atividade de teste de software. Este trabalho teve como objetivo caracterizar a atividade de teste de software aplicada dentro de métodos de desenvolvimento ágil, buscando eliminar aspectos de teste não produtivos, identificando boas práticas e, principalmente, criando formas de acompanhar e melhorar continuamente a condução da atividade de teste. A partir da caracterização da atividade foi proposta a adoção de um conjunto de métricas para facilitar o seu acompanhamento e melhoria constante da mesma. Algumas dessas métricas de acompanhamento de testes foram implementadas na ferramenta Agile Testing Metrics Management (ATMM). O objetivo principal da ferramenta é gerenciar as iterações de desenvolvimento do projeto ágil e, também, exibir a evolução das métricas relacionadas ao código que está sendo testado e aos casos de teste desenvolvidos utilizando a ferramenta JUnit. Para validar a ferramenta e as métricas foram conduzidos estudos de casos com dois projetos de software de domínios diferentes que utilizaram métodos ágeis e testes de unidade / Agile methods are appropriate techniques for software development subject to constant changes. These changes should not affect the project schedule, budget and must ensure meeting the clients needs. Several values, principles and practices of project development and driving are applied in agile projects with this goal. Some of these practices are related to software testing activity. This study aimed at characterizing the software testing activity applied to agile development methods, trying to eliminate unproductive testing aspects, identifying good practices and especially creating ways of tracking and continuously improve the test activity. From this activity characterization, it was proposed an adoption of metrics set to facilitate the monitoring and constant improvement of the activity. Some of these testing tracking metrics were implemented in the Agile Testing Metrics Management Tool (ATMM). The main goal of this tool is to manage the iterations of agile project development and, also show the metrics evolutions regarding the code that have been tested and the test cases developed using JUnit. The tool and metrics were validated by case studies that were conducted with two software projects of different domains which used agile methods and unit testing
67

Diretrizes para desenvolvimento de linhas de produtos de software com base em Domain-Driven Design e métodos ágeis / Guidelines for developing software product lines based on Domain-Driven Design and agile methods.

Otávio Augusto Cardoso Macedo 20 February 2009 (has links)
Linhas de produtos de software (LPS) são coleções de sistemas que compartilham características comuns, desenvolvidas de forma sistemática a partir de um conjunto comum de ativos centrais. Dentre as técnicas propostas por vários autores para o desenvolvimento de LPS, dois padrões podem ser observados: o processo de desenvolvimento geralmente é sequencial e o foco do projeto (design) costuma estar em interesses técnicos, como alocação de componentes e separação em subsistemas, e não em um modelo de domínio. Embora essas práticas sejam reportadas como bem-sucedidas, um outro paradigma de desenvolvimento, baseado em métodos ágeis e em um conjunto de princípios de projeto conhecido como domain-driven design, é apresentado neste trabalho e pode produzir resultados mais satisfatórios, comparados aos métodos tradicionais. Essa hipótese é sustentada por comparações entre padrões de modelagem e por um estudo de caso feito neste trabalho / Software product lines (SPL) are collections of systems that have common features. Those systems are systematically developed from a common set of core assets. Two patterns outstand among the various techniques proposed by several authors for developing software product lines: the development process is generally sequential and the primary design concerns deal with technical issues, such as component allocation and system partitioning (into subsystems). The importance of a domain model is often neglected. Although such practices have been reported as successful, this work proposes another paradigm, which can yield more satisfactory results. This paradigm is based on agile methods and a set of design principles known as domain-driven design. This hypothesis is supported by comparing different modeling patterns and by developing a case study
68

FreeTest 2.0: uma evolução do método FreeTest para a melhoria no processo de teste de software em micro e pequenas empresas

Louzada, Jailton Alkimin 11 August 2017 (has links)
Submitted by Franciele Moreira (francielemoreyra@gmail.com) on 2017-09-11T13:42:06Z No. of bitstreams: 2 Dissertação - Jailton Alkimin Louzada - 2017.pdf: 5226619 bytes, checksum: bb291ad68acd8cf80fcb2c6c2392c596 (MD5) license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5) / Approved for entry into archive by Luciana Ferreira (lucgeral@gmail.com) on 2017-09-15T15:43:54Z (GMT) No. of bitstreams: 2 Dissertação - Jailton Alkimin Louzada - 2017.pdf: 5226619 bytes, checksum: bb291ad68acd8cf80fcb2c6c2392c596 (MD5) license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5) / Made available in DSpace on 2017-09-15T15:43:54Z (GMT). No. of bitstreams: 2 Dissertação - Jailton Alkimin Louzada - 2017.pdf: 5226619 bytes, checksum: bb291ad68acd8cf80fcb2c6c2392c596 (MD5) license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5) Previous issue date: 2017-08-11 / The Information Technology (I.T) market is growing. In the age of information, world economies have been investing more and more in the services market. Within this competitive scenario, software testing is an important component for raising the quality of software developed in Brazil and in the global competitiveness cenario. However, Small and medium-sized enterprises (SMEs) have limited resources for investments in software testing maturity processes, tools and models in their business. Faced with this, this work has as main proposal to produce an apparatus to improve the process of software testing for SMEs. Objective: As the main objectives, this study proposed a more update version of the FreeTest 1.0 process, as well as practical instructions on how to implement the activities suggested in the process, all this formatted in a new process and a wizard respectively. Methodology: In order to fulfill the objectives of this work, the FreeTest 2.0 process was created as an improvement of the FreeTest Method process, focused mainly on Agile techniques, DevOps and aligned with the SMEs ecosystem. And the FreeTest Wizard, which consists of a deployment guide that supports the implementation of the process in a didactic, dynamic and flexible way. Another contribution of this work was the creation of support tools to disseminate this knowledge and content management, in this case the creation of a web platform, distributed free of charge and in the format "as a Service". Finally, the results and conclusions can be seen in the final chapter of this work. / O mercado de Tecnologia da Informação (T.I.) é crescente. Na era da informação, as economias mundiais investem cada vez mais no mercado de Serviços. Dentro deste cenário competitivo, o teste de software é um importante componente para elevação da qualidade do software desenvolvido no Brasil e sua competitividade mundial. Contudo, as Micro e Pequenas Empresas (MPEs) possuem recursos limitados para investimentos em processos, ferramentas e modelos de maturidade de teste de software em seus negócios. Diante disto, este trabalho tem como proposta principal produzir um aparato para melhoria do processo de teste de software para MPEs. Objetivo: Como objetivos principais, este estudo propôs uma versão mais atualizada do processo FreeTest 1.0, bem como instruções práticas de como implantar as atividades sugeridas no processo, tudo isso formatado em um novo processo e um guia de implantação, respectivamente. Metodologia: Com o propósito de cumprir os objetivos almejados neste trabalho foram criados: 1) o processo FreeTest 2.0 como uma melhoria do processo do FreeTest 1.0, focado principalmente em técnicas Ágeis, DevOps e alinhado ao ecossistema das MPEs; e 2) o FreeTest Wizard, que consiste em um guia de implantação que apoia a implantação do processo de forma didática, dinâmica e flexível. Outra contribuição deste trabalho foi a criação de ferramentas de apoio para disseminação deste conhecimento e gestão dos conteúdos, neste caso, a criação de uma plataforma web distribuída de forma gratuita e no formato "as a Service". Por fim, os resultados e conclusões serão vistos no capítulo final deste trabalho.
69

Hur påverkar agila metoder kreativitet och innovationsförmåga? : En fallstudie utifrån ett litet IT-konsultföretag som arbetar enligt Scrum-metoden

Ljungman, Evelina January 2019 (has links)
Frågeställningar: Hur påverkas deltagarnas kreativitet när agila metoder används i praktiken? Hur påverkar agila arbetsmetoder innovationsförmågan? Syfte: Syftet med denna studie är att undersöka hur ett litet IT-företag arbetar med att främja kreativitet genom att arbeta enligt det agila arbetssättet, för att på så sätt kunna påverka innovationsförmågan. Metod: Denna studie baseras på en fallstudie. Företaget är ett litet IT-konsultföretag som arbetar med systemutveckling. Företaget har 15 anställda och arbetar enligt det agila arbetssättet och de har två Scrum-team. Detta arbete har sin grund i den kvalitativa metoden med influenser av ett deduktivt förhållningssätt, då studien huvudsakligen baseras på semi-strukturerade intervjuer och observationer. Slutsatser: Slutsatserna som kan dras är att det agila arbetssättet påverkar kreativiteten genom att öka deltagarnas motivation. Det agila arbetssättet påverkar kreativiteten hos de anställda, då det är fritt att plocka de uppgifter som man själv vill i varje sprint bidrar det till att det kan öka både motivationen och nyfikenheten. En annan slutsats är att det agila arbetssättet påverkar deltagarnas kreativitet då det ger de anställda en mer frihet att planera sitt arbete och ger de möjligheten att själva lösa sin arbetsuppgift på sitt sätt, genom att exempelvis testa nya tekniker. Det agila arbetssättet påverkar deltagarnas kreativitet på så sätt att det kan minska stressen utifrån för själva arbetsgruppen. Detta på grund av att det är produktägaren som har den främsta kontakten med slutkunden.Det agila arbetssättet påverkar innovationsförmågan genom att i och med att det ständigt kommer in nya arbetsuppgifter som arbetsgruppen ska lösa och då arbetsuppgifterna skiljer sig mycket åt, bidrar det till en ökad dynamik och utmaning. En intressant slutsats var att produktägarna skapade en ometveten utmaning kopplat till de anställdas arbetsuppgifter då de anställda ansåg att kravspecifikationerna som de fick var svåra att förstå. Sista slutsatsen som kan dras är att det agila arbetssättet skapade en frihet hos de anställda att själva kunna prioritera bland sina arbetsuppgifter och metoden som de ska lösas på. / Research questions: How are participants' creativity affected when agile methods are used in practice? How do agile methods affect the ability to innovate? Purpose: The purpose of this study is to investigate how a small IT company works to increase creativity by working according to the agile approach, in order to be able to affect the capacity for innovation. Method: This study is based on a case study. The company is a small IT consulting company that works with system development. The company has 15 employees and works according to the agile approach and they have two Scrum teams. This work is based on the qualitative method with influences of a deductive approach, since the study is mainly based on semi-structured interviews and observations. Conclusions: The conclusions are that the agile methods affect creativity by increasing the participants' motivation. The agile way of working affects the creativity of the employees, as it is free to pick the tasks that you want in each sprint, it contributes to increase both motivation and curiosity. Another conclusion is that the agile methods affects the participants' creativity as it gives the employees more freedom to plan their work and gives them the opportunity to solve their task in their own way, for example by testing new technologies. The agile methods affect the participants' creativity in such a way that it can reduce the stress from outside the workgroup itself. This is because it is the product owner who has the main contact with the end customer.The agile way of working affects the ability to innovate because it is constantly entering new tasks that the working group has to solve, and the tasks are very different to each other, it contributes to increased dynamism and challenge. An interesting conclusion was that the product owners created an unconscious challenge linked to the employees' tasks, as the employees felt that the requirement specifications that they received were difficult to understand. The final conclusion is that the agile methods created freedom for the employees to be able to prioritize themselves among their tasks and choose how to solve the tasks.
70

Systemförvaltning med en agil metod : En fallstudie om Scrum inom systemförvaltning

Viklund, Anton, Ahlman, Elias January 2017 (has links)
At present, the area of agile management methods is a relatively unexplored area. The purpose of this study has been to investigate how well suited agile methods are for use in IT-maintenance. This has been done by collecting material on the subject, which acted as a base for a case study. In the study, the collected material from the investigated company, external companies and observations performed at the investigated company has been analyzed against existing theory in the field. Furthermore, conclusions have been drawn from information gathered during the course of the study. Based on this survey, it can be noted that in the activities that were investigated, an implemented agile method can add value to the maintenance operation. These added values present themselves in the form of a better and clearer structure, better communication and more effective working methods. One of the biggest challenges of agile agility in management has proved to be cross-functionality in the team. In this case as well as in other theoretical cases, the lack of cross functionality has been something identified. The theoretical cases show that the introduction of an agile method helps maintenance teams to become cross-functional. In the business investigated in this study, there were only indications stating that the business had started a transition to a cross-functional team. The fact that no definitive link between agile methods and transition to cross-functionality was identified in this case is considered to be due to the fact that the agile work was at an earlier stage. In conclusion, this study shows that agile methods are well-suited for use in maintenance, but some modifications to the agile approach need to be implemented. / I dagsläget är området agila metoder inom systemförvaltning ett relativt outforskat område. Syftet med denna studie har varit att undersöka hur väl lämpade agila metoder är för en förvaltande verksamhet. Detta har gjorts genom att bakgrundsmaterial i ämnet samlats in, för att bilda en teoretisk grund för en fallstudie. I studien har det insamlade materialet från det undersökta företaget, externa företag samt egna observationer som utförts på fallföretaget analyserats gentemot existerande teori inom området, varefter egna slutsatser dragits. Utifrån studien kan det konstateras att i den verksamhet som undersökts har en implementerad agil metod tillfört värde till verksamheten. Detta i form av en bättre och tydligare struktur, bättre kommunikation och ett effektivare arbetssätt. En av de största utmaningarna med att arbeta agilt inom systemförvaltning har visat sig vara tvärfunktionalitet i teamet. I detta fall såväl som i andra teoretiska fall har avsaknaden av tvärfunktionalitet varit något som identifierats. De teoretiska fallen påvisar att införandet av en agil metod har hjälpt förvaltningsteamen att bli tvärfunktionella. I verksamheten som undersöktes uppmärksammades enbart indikationer på att verksamheten påbörjat en övergång till ett tvärfunktionellt team. Att ingen definitiv koppling mellan agila metoder och övergång till tvärfunktionalitet identifierades i detta fall anses bero på att det agila arbetet befann sig i ett tidigare skede. Avslutningsvis styrker studien att agila metoder är väl lämpade för användning inom systemförvaltning, men vissa modifikationer i det agila arbetssättet behöver genomföras.

Page generated in 0.0778 seconds