Compared to traditional project management methods, agile methods are new. The use of project work keeps increasing, including the number of projects, with varying characteristics. In a world with a growing speed of change and with growing demands, there’s a need for adjustment, something which agile methods offer. However, agile methods are not suitable for all types of projects. The aim of the study was to broaden the understanding of what motivates implementation and usage of agile methods in projects and operations, challenges and advantages that can emerge through implementation and usage of agile methods, and if expectations of agile methods were confirmed. The study was qualitative and was made through semi-structured interviews, which were recorded and later transcribed. Collected data was analyzed based on thematic qualitative analysis. A total of three analyses were made - one per research question. All together the three analyses resulted in a total of thirteen themes. Motives for working agile varied, whereas primary motives for implementing and working with agile methods were increased efficiency, increased participation, and increased visualization of work. During on-going implementation, knowledge and training was crucial, including management, employees and customers. Agile methods were adjusted to reality and operations. Customers wanted to take part in working with agile methods, while their knowledge was inadequate. Expectations that existed before the implementation were confirmed. Agile methods hold what it promises.

Information Security nowadays is becoming a very popular subject of discussion among both academics and organizations. Proper Data Governance is the first step to an effective Information Security policy. As a consequence, more and more organizations are now switching their approach to data, considering them as assets, in order to get as much value as possible out of it. Living in an IT-driven world makes a lot of researchers to approach Data Governance by borrowing IT Governance frameworks.The aim of this thesis is to contribute to this research by doing an Action Research in a big Financial Institution in the Netherlands that is currently releasing a Data Lake where all the data will be gathered and stored in a secure way. During this research a framework on implementing a proper Data Governance into the Data Lake is introduced.The results were promising and indicate that under specific circumstances, this framework could be very beneficial not only for this specific institution, but for every organisation that would like to avoid confusions and apply Data Governance into their tasks. / <p>Validerat; 20151222 (global_studentproject_submitter)</p>

Métodos ágeis foram criados para sanar fraquezas reais e perceptíveis dos métodos tradicionais de desenvolvimento de software. Devido à pressão na entrega de produtos de software dentro do prazo, muitas vezes requisitos de segurança são pouco mensurados ou até deixados de lado. Durante o desenvolvimento ágil de software é importante detectar possíveis vulnerabilidades. Esta dissertação descreve um survey aplicado a membros de equipes de desenvolvimento de software que aplicam métodos ágeis. Para tanto, foram identificados por meio da rede de profissionais LinkedIn 110 membros de equipes ágeis que implantaram, estão em processo de implantação ou ainda irão implantar técnicas e ferramentas para detecção de vulnerabilidades. Além disso, foram entrevistados nove gerentes de equipes ágeis. O questionário e o roteiro da entrevista foram baseados em três conhecidos processos de desenvolvimento de software seguro, a saber, Processo de McGraw, OWASP CLASP e as atividades de Howard e Lipner. A coleta de dados se deu por meio de questionários e entrevistas. A análise dos resultados utilizou técnicas de estatística descritiva e análise de conteúdo. Elas indicaram os métodos ágeis mais utilizados, o uso atual das técnicas e ferramentas, as aptidões, os interesses e as necessidades em treinamento em técnicas e ferramenta para detecção de vulnerabilidades. Além disso, os benefícios obtidos com a implantação das técnicas e ferramentas, as motivações, as estratégias, as dificuldades, as limitações e as lições aprendidas foram identificadas. Os resultados indicam que existe motivação para a implantação de segurança, mas ainda não se dá atenção especial à detecção de vulnerabilidades nas equipes ágeis cujos membros participaram do survey / Agile methods were created to address real and perceived weaknesses of traditional software development methods. Due to the pressure to delivery software products on time, security requirements are often poorly addressed or even neglected. During agile software development it is important to detect possible vulnerabilities. This dissertation describes a survey applied to members of software development teams who apply agile methods. Thus, 110 members of agile teams were identified through LinkedIns network of professionals who deployed, are in the process of being deployed or will still implement techniques and tools for vulnerability detection techniques and tools were identified. The questionnaire was based on three known safe software development processes, namely, the McGraw Process, OWASP CLASP, and the activities of Howard and Lipner. Data were collected through questionnaires and interviews. The analysis of the results used techniques of descriptive statistics and content analysis. They indicated the most widely used agile methods, the current use of techniques and tools, the skills, interests and training needs of agile teams in vulnerability detection techniques and tools. In addition, the benefits of implementing the techniques and tools, the motivations, the strategies, the difficulties, the limitations and the lessons learned were identified. The results suggest that special attention is still not given to detection of vulnerabilities in the agile teams whose members participated in the survey

This study aims through a qualitative approach to study how agile methods are practised in a Swedish bank. The aim of the study is to understand the motives behind the choice to implement the agile methods, how the change process has been practised and finally what effects it gives to the employees in the company. Interviews with both the employees and the management of the bank has led to an understanding of their different views on the agile way of working through their individual experiences. Observations has visualised how the method is practiced, which contributed to a wider perspective. As analytical tools, theoretical concepts such as organizational recipes, the stakeholder model, process change, resistance, cynefin, human relations and efficiency are used. The result of the study shows that there has been both internal and external factors as the basis for the implementation of agile methods. The bank has intended for the change process to be agile with constant improvement as a goal. Uncertainty is an effect of the agile methods and is explained by a difficulty in applying the method throughout the business. The primary effect is increased efficiency, which is the management's main goal. How it affects the employees positively is through increased well-being for those motivated by the agile way of working and negative for those who is not. The study's conclusion is that it is difficult to implement a working method that generates positive effects for all employees. / Denna uppsats studerar, genom ett kvalitativt angreppssätt, hur agila metoder som arbetssätt tillämpas på en bank. Syftet med studien är att förstå motivet bakom att implementera metoderna, hur förändringsprocessen har genomförts och vilka effekter det ger på de anställda i företaget. Intervjuer av både medarbetare och ledning har genomförts och deras individuella erfarenheter har genererat i en förståelse för att det finns olika uppfattningar om arbetssättet. Observationer har synliggjort hur arbetssättet praktiseras, vilket har bidragit till ett större helhetsperspektiv. Som analysverktyg används teoretiska begrepp som organisationsrecept, intressentmodellen, processförändring, motstånd, cynefin, human relations och effektivitet. Studiens resultat visar på att både interna och externa faktorer utgjort motiv till implementeringen av agila metoder. Banken har ämnat genomföra förändringsprocessen agilt med ständig förbättring som mål. Osäkerhet är en effekt av implementationen och kan förklaras av en svårighet att tillämpa metoden i hela verksamheten. Den största effekten av arbetssättet är ökad effektivitet, vilket är ledningens främsta mål. Hur det påverkar de anställda positivt är genom ökad trivsel för de som motiveras av arbetssättet och negativt för de som inte gör det. Studiens slutsats pekar på svårigheten att implementera ett arbetssätt som genererar positiva effekter för samtliga anställda.

[pt] O trabalho a seguir apresenta uma proposta de metodologia de gerência de projetos de software aderente a pequenos projetos e fortemente inspirada em metodologias já consagradas como Unified Process e eXtreme Programming. O objetivo é prover um processo ágil, adaptável porém prescritivo. Chegaremos a um processo de fácil implantação e controle e menos dependente da qualidade técnica da equipe de desenvolvimento. A seguir, será apresentado um estudo de caso conduzido em ambiente real, por uma equipe de um pequeno empreendimento que consiste no relato do processo de amadurecimento e implantação do processo proposto, com uma análise do trabalho de implantação de processos de desenvolvimento em empreendimentos emergentes na área de TI. / [en] The following work presents a proposal of software project management methodology applicable to small projects and strongly inspired by already well established methodologies such as the Unified Process and eXtreme Programming. The objective of this proposal is to provide an agile process that is adaptable yet prescriptive. Through this one plans to arrive at a process of easy implementation and control, and less dependent on the technical quality of the development team. Subsequently, a case study will be presented that was conducted in a real environment, on a small enterprise development team. It consists of a report on the maturing and implementation of the proposed process and an analysis of the work of implementing development procedures in emerging enterprises in the IT area.

Este trabalho descreve a definição e institucionalização de um processo de engenharia de requisitos que está em conformidade com as áreas de processo do CMMI (Capability Maturity Model) de Gerência de Requisitos e Desenvolvimento de Requisitos e cujos componentes (atividades, papéis, produtos de trabalho) são baseados em RUP (Rational Unified Process). A principal contribuição deste estudo é a definição de um processo de engenharia de requisitos baseado em abordagens de desenvolvimento diferenciadas, que foi implantado em uma organização específica, com foco em praticidade, eficiência e retorno do investimento. A implantação do processo em projetos reais permitiu sua experimentação, avaliação e refinamento, validando as alternativas de integração utilizadas para empregar as abordagens de desenvolvimento escolhidas. Complementando o processo proposto, como decorrência do foco em eficiência, são consideradas possibilidades de emprego de práticas de métodos ágeis na execução do processo, com o intuito de aumentar a produtividade do mesmo, sustentando sua garantia de qualidade. O processo proposto é descrito, do método de concepção aos passos envolvidos e artefatos gerados em cada atividade. Também são comentadas as etapas e áreas de trabalho envolvidas na institucionalização do trabalho. / This research depicts the definition and institutionalization of a requirements engineering process which is in conformance to CMMI (Capability Maturity Model) Requirements Management and Requirements Development process areas. The proposed process components (activities, roles, work products) are based on Rational Unified Process (RUP) process framework. The proposed process main contribution is the definition of a requirements engineering process, leveraging such diverse development approaches, which was implemented in a specific organization, focusing on practicality, efficiency and return on investment. Implementing such process in real projects has promoted its experimentation, evaluation and refinement, validating the integration alternatives used to bring together the chosen development approaches. The possibility of employing agile methods practices through the process execution is discussed, aiming at increasing the process productivity, while assuring product quality. The proposed process details are described, from method conception to each activity steps and generated artifacts. The process institutionalization phases and work areas are also commented.

Este trabalho descreve a definição e institucionalização de um processo de engenharia de requisitos que está em conformidade com as áreas de processo do CMMI (Capability Maturity Model) de Gerência de Requisitos e Desenvolvimento de Requisitos e cujos componentes (atividades, papéis, produtos de trabalho) são baseados em RUP (Rational Unified Process). A principal contribuição deste estudo é a definição de um processo de engenharia de requisitos baseado em abordagens de desenvolvimento diferenciadas, que foi implantado em uma organização específica, com foco em praticidade, eficiência e retorno do investimento. A implantação do processo em projetos reais permitiu sua experimentação, avaliação e refinamento, validando as alternativas de integração utilizadas para empregar as abordagens de desenvolvimento escolhidas. Complementando o processo proposto, como decorrência do foco em eficiência, são consideradas possibilidades de emprego de práticas de métodos ágeis na execução do processo, com o intuito de aumentar a produtividade do mesmo, sustentando sua garantia de qualidade. O processo proposto é descrito, do método de concepção aos passos envolvidos e artefatos gerados em cada atividade. Também são comentadas as etapas e áreas de trabalho envolvidas na institucionalização do trabalho. / This research depicts the definition and institutionalization of a requirements engineering process which is in conformance to CMMI (Capability Maturity Model) Requirements Management and Requirements Development process areas. The proposed process components (activities, roles, work products) are based on Rational Unified Process (RUP) process framework. The proposed process main contribution is the definition of a requirements engineering process, leveraging such diverse development approaches, which was implemented in a specific organization, focusing on practicality, efficiency and return on investment. Implementing such process in real projects has promoted its experimentation, evaluation and refinement, validating the integration alternatives used to bring together the chosen development approaches. The possibility of employing agile methods practices through the process execution is discussed, aiming at increasing the process productivity, while assuring product quality. The proposed process details are described, from method conception to each activity steps and generated artifacts. The process institutionalization phases and work areas are also commented.

Made available in DSpace on 2016-06-02T19:07:10Z (GMT). No. of bitstreams: 1 FERRAZ_JUNIOR_Wilton_2015.pdf: 16420702 bytes, checksum: 618d7c194c6a9fff0f67ef9767ad5f99 (MD5) Previous issue date: 2015-06-29 / This work aims to develop a novel method to design educational games, following Extreme Programming and Scrum Agile Methods and screenplays under the dilemmas and mechanical game re-guise concepts, which are already widely accepted in the literature. Workshops using the proposed method were conducted in order to identify the demands of educators and students from elementary and middle school and also the viability in the implementation of the method as a support tool to the teaching process. The validation results and the method acceptance were evaluated by statistical tests, which are also widely explored in the literature for similar samples. The final remarks show the successful methods evolution and their validation results under the considered classrooms context. / Este trabalho tem por objetivo desenvolver um novo método para a produção de jogos educativos, baseado nos métodos ágeis Scrum e Extreme Programming, além de utilizar conceitos de produção de roteiros baseados em dilemas e utilização de técnicas de rerroupagem de mecânicas de jogos já existentes e amplamente aceitas pela literatura. Foram realizadas oficinas, que utilizaram versões do método proposto, para identificar as demandas de professores e alunos do ensino médio e fundamental, e verificar qual delas apresentavam viabilidade de implantação como ferramenta de apoio ao processo de ensino-aprendizagem. Os resultados obtidos, tanto em relação à aceitação do método e como em relação à melhora dos indicadores de aprendizagem dos conceitos apresentados durante as oficinas, foram analisados utilizando testes estatísticos específicos, amplamente explorados na literatura. Os resultados dos testes permitiram o aprimoramento e a validação do método proposto dentro do contexto de sala de aula.

Submitted by Alison Vanceto (alison-vanceto@hotmail.com) on 2016-09-30T12:23:06Z No. of bitstreams: 1 DissECSS.pdf: 2536269 bytes, checksum: a856f5027d19c2aaadf2834a69af7ff4 (MD5) / Approved for entry into archive by Ronildo Prado (ronisp@ufscar.br) on 2016-09-30T17:56:23Z (GMT) No. of bitstreams: 1 DissECSS.pdf: 2536269 bytes, checksum: a856f5027d19c2aaadf2834a69af7ff4 (MD5) / Approved for entry into archive by Ronildo Prado (ronisp@ufscar.br) on 2016-09-30T17:56:32Z (GMT) No. of bitstreams: 1 DissECSS.pdf: 2536269 bytes, checksum: a856f5027d19c2aaadf2834a69af7ff4 (MD5) / Made available in DSpace on 2016-09-30T18:05:54Z (GMT). No. of bitstreams: 1 DissECSS.pdf: 2536269 bytes, checksum: a856f5027d19c2aaadf2834a69af7ff4 (MD5) Previous issue date: 2015-06-01 / Conselho Nacional de Desenvolvimento Científico e Tecnológico (CNPq) / The agile methods of software development have emerged as an alternative to traditional approaches, to spend less time on documentation and more time with solving problems interactively and iteratively. In this context, the development approach Domain Driven Design (DDD) is a way of developing software in which the application design process is guided by a domain model. In conjunction with the DDD development approach, the existence of tests during the implementation of an application is required to ensure quality. Objective: This work aims to study the agile development approach Domain-Driven Design (DDD) and the software test techniques Test-Driven Development (TDD) and Behaviour-Driven Development (BDD). A case study was built to exemplify the integration of each test technique with DDD. The case study was developed with the support of the Apache Isis framework, from a well-defined domain model. Methodology: Based on the literature, the concepts of the DDD development approach and of the TDD and BDD test techniques, that provided the comparison between the techniques, and later, the implementation to illustrate this research, were extracted. The Apache Isis framework was used in this work because it allows develop DDD applications quickly. During the development of the sample system of this work, the possibility of creating an automatic generator tests and scenarios for BDD was noted. Results: A case study was created using the concepts of DDD and tests, with TDD and BDD. Furthermore, a prototype of tests and scenarios generator for software projects that use DDD, through the Apache Isis framework and tests using BDD, was developed. Conclusions: The combination of test techniques mentioned with DDD aim to boosting the development of applications, since DDD is not associate with any test technique. Writing scenarios with ubiquitous language is a great advantage to integrate DDD and BDD, because it allows a clear understanding for all involved in the project. Moreover, the creation of automatic generator speeds up the testing phase, and can detect errors that might go unnoticed or only be found as the project evolved. / Os métodos ágeis de desenvolvimento de software surgiram como uma alternativa às abordagens tradicionais, com o intuito de despender menos tempo com documentação e mais com a resolução de problemas de forma interativa e iterativa. Neste contexto, a abordagem de desenvolvimento Domain-Driven Design (DDD) representa uma forma de desenvolver software em que o processo de design de uma aplicação é guiado pelo modelo de domínio. Em conjunto com a abordagem de desenvolvimento DDD, a existência de testes durante a implementação de uma aplicação é necessária para garantir a qualidade. Objetivo: Este trabalho teve como objetivo o estudo da abordagem ágil de desenvolvimento Domain-Driven Design (DDD) e as técnicas de teste de software Test-Driven Development (TDD) e Behaviour-Driven Development (BDD). Um estudo de caso foi construído para exemplificar a integração de cada técnica de teste com o DDD. O estudo de caso foi desenvolvido por meio do framework Apache Isis, a partir de um modelo de domínio bem definido. Metodologia: Com base na literatura foram extraídos os conceitos da abordagem de desenvolvimento DDD e das técnicas de testes TDD e BDD que proporcionaram a comparação entre as técnicas e posterior implementação para exemplificar a pesquisa. O framework Apache Isis foi utilizado neste trabalho porque permite desenvolver aplicações com DDD de forma rápida. No decorrer do desenvolvimento do sistema exemplo deste trabalho, notou-se a possibilidade da criação de um gerador automático de testes e cenários para BDD. Resultados: Foi criado um estudo de caso empregando os conceitos de DDD e testes com o TDD e com o BDD. Além disso, foi desenvolvido um protótipo de gerador de testes e cenários para projetos de software que empregam DDD, por meio do framework Apache Isis e testes utilizando BDD. Conclusões: A junção das técnicas de testes citadas com o DDD visa potencializar o desenvolvimento de aplicações, uma vez que o DDD não aborda nenhuma técnica de teste. A escrita de cenários em linguagem ubíqua é um grande diferencial ao integrar DDD e BDD, pois permite um claro entendimento a todos os envolvidos do projeto. Ademais, a criação do gerador automático agiliza a fase de testes, sendo possível detectar erros que poderiam não ser notados ou apenas serem encontrados com a evolução do projeto.

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 general. / Tiivistelmä 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.