Agile software development methodologies, such as Scrum, have gained tremendous popularity and proven successful in quickly delivering quality Functional Requirements (FRs). However, agile methodologies have not adequately identified, modeled, and linked Non-Functional Requirements (NFRs) with FRs in early development phases. Researchers agree that NFRs have been generally ignored in conventional methodologies, especially ignored in agile environments. This dissertation develops a conceptual framework for NFR modeling in agile processes. The proposed Non-functional Requirements Modeling for Agile Processes (NORMAP) Methodology investigated the feasibility of identifying, linking, and modeling Agile Loose Cases (ALCs) with Agile Use Cases (AUCs) and Agile Choose Cases (ACCs). AUCs are newly proposed hybrid of use cases and agile user stories. ALCs are proposed—loosely—defined agile NFRs. ACCs are proposed potential solutions (operationalizations) for ALCs. A lightweight adapted version of the NFR Framework was developed including 25 important NFRs selected out of 161 for this study. Further, an enhanced risk-driven agile requirements implementation sequence (NORPLAN) was developed and visualized as a tree-like view (NORVIEW). The NORMAP Methodology was validated through developing NORMATIC--a Java-based agile visual modeling simulation tool and two case studies. NORMATIC utilized Natural Language Processing (NLP) tools to parse requirement sentences and identify potential ALCs. The first case study utilized the Predictor Models in Software Engineering (PROMISE) dataset used in NFRs classification. NORMAP successfully parsed and classified ALCs for 529 out of 607 (87.15%) independent user requirements. The second case study utilized the European Union eProcurement System’s 26 functional requirements. NORMAP successfully parsed and classified ALCs for 50 out of 57 sentences that included possible ALCs (87.71%). Furthermore, requirements quality and project management metrics were used to calculate a risk-driven requirements implementation sequence using three priority schemes. Results showed that Riskiest-Requirements-First priority scheme planned requirements in 17 sprints--two months earlier than the Highest-Business-Value-First scheme (21 sprints) and one month earlier than the Riskiest-Requirements-Last scheme (19 sprints). Agile communities can potentially benefit from the NORMAP Methodology by utilizing a systematic and risk-driven lightweight engineering process to visually model and plan NFRs as first-class artifacts in agile environments.

This diploma thesis is focused on current situation analysis of the company with particular designed change of project management. This change is aimed to set up a Scrum agile method. Basics of Scrum agile method are explained in the first chapter of this diploma thesis. Based on the knowledge gained from analitical chapter of this thesis there are designed specific changes according Scrum principles in the last chapter.

The thesis deals with optimization of project management in a custom web development company. The theoretical part is devoted to the description of traditional and agile approaches of project management. The analytical part describes the current state of project management. The main part of the thesis consists of optimization of project management by agile SCRUM method, case study implementation and evaluation of benefits and costs of introduced change.

A Engenharia de Software é uma disciplina que tem entre seus objetivos melhorar a produtividade dos processos de desenvolvimento de software, assim como propiciar qualidade ao produto resultante desses processos. Para mensurar a qualidade dos produtos de software, foram criados modelos de qualidade, que recomendam métricas, processos e atividades que passaram a se tornar parte do dia-a-dia do desenvolvimento de projetos em empresas. Considerando outra perspectiva, a indústria de software tem adotado cada vez mais os métodos ágeis. Esses métodos foram desenvolvidos visando a entrega rápida do software, com ciclos curtos e adaptáveis de desenvolvimento, foco na comunicação direta e baixo volume de documentação. Considerando a importância do tema qualidade de software, e a baixa aderência dos modelos tradicionais de qualidade aos métodos ágeis, o objetivo deste projeto foi investigar o tema qualidade de software no contexto ágil, ou seja, estudar quais métricas de qualidade são empregadas nesse processo de desenvolvimento. Para isso foram realizados dois estudos empíricos, um estudo de caso e um survey, sobre atividades de garantia e controle de qualidade, métricas de qualidade de software, processos e ferramentas utilizadas no desenvolvimento de software. Os resultados obtidos guiaram a construção de uma ferramenta de apoio para avaliação da qualidade durante o desenvolvimento ágil de software. Os resultados dos estudos mostraram que a execução constante de atividades como revisão de código e refatoração, são fatores essenciais para garantia de qualidade nos métodos ágeis. Outro resultado encontrado foi o de que praticantes de métodos ágeis são entusiastas do processo de desenvolvimento utilizado. Eles conhecem o método e praticam com alta fidelidade os passos definidos pelo processo. É possível concluir que os métodos ágeis possuem diversas atividades como foco na garantia de qualidade de seu produto desde os estágios iniciais do desenvolvimento. A cultura ágil cria um ambiente propício para motivação e engajamento das equipes de desenvolvimento, fato que reflete positivamente na qualidade final dos produtos / One of the main objectives of Software Engineering is to improve the productivity of software development processes, as well as providing quality to the product resulting from such processes. Thus, quality models were defined to measure the software quality. Those models recommend metrics, processes and activities that became part of day-to-day on development companies. Considering another perspective, the software industry has increasingly adopted agile methods. These methods were developed considering rapid software delivery, with short and adaptable development cycles, focusing on direct communication and low volume of documentation. Considering the importance of software quality and the low compliance of agile methods to traditional quality models, this project aimed to investigate software quality in agile development environments, in other words, to research wich quality metrics are employed in these development processes. Considering this objective, two empirical studies were designed, a case study and a survey. These studies have explored themes like software quality control, software quality assurance, quality metrics, development process and development tools that are employed on software development. The results guided the construction of a tool to support the quality evaluation during the agile development. The studies results showed that the high frequency of activities such as code review and refactoring, are essential factors for assuring quality on projects using agile methods. Another result was found regarding developers behavior. Agile practitioners are enthusiasts of the development process they use. They have a high level of compliance to development process they use. It is possible to conclude that agile methods have several activities focused on the quality assurance of its own products since the initial stages of development. The agile culture creates a convenient environment that engages and motivates the development teams. This fact has a positive effect on the product quality

A adoção de metodologias ágeis tem se provado uma atividade sensível a cultura das organizações que as aplicam. Nos dez anos que se sucederam ao Agile Manifesto, projetos ágeis se desenvolveram a partir de tentativas conduzidas em situações ideais até grandes iniciativas adaptadas para as mais diversas condições. Por outro lado, a cultura organizacional tem se provado determinante na maneira que organizações abordam os desafios que se apresentam. Este trabalho tem por objetivo explorar a relação entre os pressupostos culturais básicos das organizações e práticas ágeis selecionadas. Para isso, se buscou identificar, através de revisão da literatura, pressupostos básicos significativos, práticas ágeis representativas e como se dá a interação entre esses, mapeando correlações através de uma survey. Essa se trata de um questionário respondido por funcionários da consultoria de TI ThoughtWorks a partir de sua experiência em projetos ágeis em clientes. A partir do resultado da survey foram exploradas as correlações identificadas – inclusive no que diz respeito à experiência e satisfação dos clientes com metodologias ágeis – e as observações foram validadas com consultores especialistas em métodos ágeis e em cultura organizacional. Procurou-se, assim, oferecer um mapa inicial para investigar a relação entre cultura organizacional e práticas ágeis que pode sugerir abordagens para introdução de práticas ágeis baseadas no perfil cultural da organização aonde se busca introduzi-las. / Companies adopting Agile methodologies have proven sensible to cultural differences. Ten years after the Agile Manifesto, agile projects have grown from small teams operating in specific situations to big cross-national initiatives. Organizational culture, in the other hand, is considered a determining factor in the way an organization perceives the world and interacts with it. In this paper, the relation between basic cultural assumptions of an organization will be matched up against a few selected agile practices. To achieve that, it looked into the literature to map these basic assumptions and representative agile practices, aiming to establish correlations between them through the results of a survey. This survey is a questionnaire answered by employees of the IT consultancy firm ThoughtWorks based on their experience in agile projects in client‟s organizations. Based on the survey results, some correlations were identified and analysed – including some regarding client experience and satisfaction with agile – and the observations were submitted to consultants, specialist in both agile practices and organizational culture for confirmation of the findings. It aimed to offer an initial map to investigate relations between organizational culture and agile practices looking to suggest new approaches for the introduction of agile practices based on the cultural profile of the target organization.

A adoção de metodologias ágeis tem se provado uma atividade sensível a cultura das organizações que as aplicam. Nos dez anos que se sucederam ao Agile Manifesto, projetos ágeis se desenvolveram a partir de tentativas conduzidas em situações ideais até grandes iniciativas adaptadas para as mais diversas condições. Por outro lado, a cultura organizacional tem se provado determinante na maneira que organizações abordam os desafios que se apresentam. Este trabalho tem por objetivo explorar a relação entre os pressupostos culturais básicos das organizações e práticas ágeis selecionadas. Para isso, se buscou identificar, através de revisão da literatura, pressupostos básicos significativos, práticas ágeis representativas e como se dá a interação entre esses, mapeando correlações através de uma survey. Essa se trata de um questionário respondido por funcionários da consultoria de TI ThoughtWorks a partir de sua experiência em projetos ágeis em clientes. A partir do resultado da survey foram exploradas as correlações identificadas – inclusive no que diz respeito à experiência e satisfação dos clientes com metodologias ágeis – e as observações foram validadas com consultores especialistas em métodos ágeis e em cultura organizacional. Procurou-se, assim, oferecer um mapa inicial para investigar a relação entre cultura organizacional e práticas ágeis que pode sugerir abordagens para introdução de práticas ágeis baseadas no perfil cultural da organização aonde se busca introduzi-las. / Companies adopting Agile methodologies have proven sensible to cultural differences. Ten years after the Agile Manifesto, agile projects have grown from small teams operating in specific situations to big cross-national initiatives. Organizational culture, in the other hand, is considered a determining factor in the way an organization perceives the world and interacts with it. In this paper, the relation between basic cultural assumptions of an organization will be matched up against a few selected agile practices. To achieve that, it looked into the literature to map these basic assumptions and representative agile practices, aiming to establish correlations between them through the results of a survey. This survey is a questionnaire answered by employees of the IT consultancy firm ThoughtWorks based on their experience in agile projects in client‟s organizations. Based on the survey results, some correlations were identified and analysed – including some regarding client experience and satisfaction with agile – and the observations were submitted to consultants, specialist in both agile practices and organizational culture for confirmation of the findings. It aimed to offer an initial map to investigate relations between organizational culture and agile practices looking to suggest new approaches for the introduction of agile practices based on the cultural profile of the target organization.

A Engenharia de Software é uma disciplina que tem entre seus objetivos melhorar a produtividade dos processos de desenvolvimento de software, assim como propiciar qualidade ao produto resultante desses processos. Para mensurar a qualidade dos produtos de software, foram criados modelos de qualidade, que recomendam métricas, processos e atividades que passaram a se tornar parte do dia-a-dia do desenvolvimento de projetos em empresas. Considerando outra perspectiva, a indústria de software tem adotado cada vez mais os métodos ágeis. Esses métodos foram desenvolvidos visando a entrega rápida do software, com ciclos curtos e adaptáveis de desenvolvimento, foco na comunicação direta e baixo volume de documentação. Considerando a importância do tema qualidade de software, e a baixa aderência dos modelos tradicionais de qualidade aos métodos ágeis, o objetivo deste projeto foi investigar o tema qualidade de software no contexto ágil, ou seja, estudar quais métricas de qualidade são empregadas nesse processo de desenvolvimento. Para isso foram realizados dois estudos empíricos, um estudo de caso e um survey, sobre atividades de garantia e controle de qualidade, métricas de qualidade de software, processos e ferramentas utilizadas no desenvolvimento de software. Os resultados obtidos guiaram a construção de uma ferramenta de apoio para avaliação da qualidade durante o desenvolvimento ágil de software. Os resultados dos estudos mostraram que a execução constante de atividades como revisão de código e refatoração, são fatores essenciais para garantia de qualidade nos métodos ágeis. Outro resultado encontrado foi o de que praticantes de métodos ágeis são entusiastas do processo de desenvolvimento utilizado. Eles conhecem o método e praticam com alta fidelidade os passos definidos pelo processo. É possível concluir que os métodos ágeis possuem diversas atividades como foco na garantia de qualidade de seu produto desde os estágios iniciais do desenvolvimento. A cultura ágil cria um ambiente propício para motivação e engajamento das equipes de desenvolvimento, fato que reflete positivamente na qualidade final dos produtos / One of the main objectives of Software Engineering is to improve the productivity of software development processes, as well as providing quality to the product resulting from such processes. Thus, quality models were defined to measure the software quality. Those models recommend metrics, processes and activities that became part of day-to-day on development companies. Considering another perspective, the software industry has increasingly adopted agile methods. These methods were developed considering rapid software delivery, with short and adaptable development cycles, focusing on direct communication and low volume of documentation. Considering the importance of software quality and the low compliance of agile methods to traditional quality models, this project aimed to investigate software quality in agile development environments, in other words, to research wich quality metrics are employed in these development processes. Considering this objective, two empirical studies were designed, a case study and a survey. These studies have explored themes like software quality control, software quality assurance, quality metrics, development process and development tools that are employed on software development. The results guided the construction of a tool to support the quality evaluation during the agile development. The studies results showed that the high frequency of activities such as code review and refactoring, are essential factors for assuring quality on projects using agile methods. Another result was found regarding developers behavior. Agile practitioners are enthusiasts of the development process they use. They have a high level of compliance to development process they use. It is possible to conclude that agile methods have several activities focused on the quality assurance of its own products since the initial stages of development. The agile culture creates a convenient environment that engages and motivates the development teams. This fact has a positive effect on the product quality

A adoção de metodologias ágeis tem se provado uma atividade sensível a cultura das organizações que as aplicam. Nos dez anos que se sucederam ao Agile Manifesto, projetos ágeis se desenvolveram a partir de tentativas conduzidas em situações ideais até grandes iniciativas adaptadas para as mais diversas condições. Por outro lado, a cultura organizacional tem se provado determinante na maneira que organizações abordam os desafios que se apresentam. Este trabalho tem por objetivo explorar a relação entre os pressupostos culturais básicos das organizações e práticas ágeis selecionadas. Para isso, se buscou identificar, através de revisão da literatura, pressupostos básicos significativos, práticas ágeis representativas e como se dá a interação entre esses, mapeando correlações através de uma survey. Essa se trata de um questionário respondido por funcionários da consultoria de TI ThoughtWorks a partir de sua experiência em projetos ágeis em clientes. A partir do resultado da survey foram exploradas as correlações identificadas – inclusive no que diz respeito à experiência e satisfação dos clientes com metodologias ágeis – e as observações foram validadas com consultores especialistas em métodos ágeis e em cultura organizacional. Procurou-se, assim, oferecer um mapa inicial para investigar a relação entre cultura organizacional e práticas ágeis que pode sugerir abordagens para introdução de práticas ágeis baseadas no perfil cultural da organização aonde se busca introduzi-las. / Companies adopting Agile methodologies have proven sensible to cultural differences. Ten years after the Agile Manifesto, agile projects have grown from small teams operating in specific situations to big cross-national initiatives. Organizational culture, in the other hand, is considered a determining factor in the way an organization perceives the world and interacts with it. In this paper, the relation between basic cultural assumptions of an organization will be matched up against a few selected agile practices. To achieve that, it looked into the literature to map these basic assumptions and representative agile practices, aiming to establish correlations between them through the results of a survey. This survey is a questionnaire answered by employees of the IT consultancy firm ThoughtWorks based on their experience in agile projects in client‟s organizations. Based on the survey results, some correlations were identified and analysed – including some regarding client experience and satisfaction with agile – and the observations were submitted to consultants, specialist in both agile practices and organizational culture for confirmation of the findings. It aimed to offer an initial map to investigate relations between organizational culture and agile practices looking to suggest new approaches for the introduction of agile practices based on the cultural profile of the target organization.

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.

The conceptual framework of agile software development is an ever-growing movement in the software industry. However, recent studies have shown that large, less software-focused companies, where software development is primarily used for in-house IT-solutions, struggle with giving up traditional command-control type of management. This hits hard on some of the most important principles of agile software development and in many cases this phenomenon has inevitably led to large gaps between development teams and more managerial parts of the organization. This thesis has aimed to study this gap and investigate how it affects software development teams’ ability to carry out their work. By comparing three software teams that were internally highly similar but with varying external conditions, impact on the teams’ behaviour based on their different environments was studied. The study was carried out using a multiple-case study approach with primary data sources consisting of survey gathered data from all team members and interviews with a subset of the team members. The results gathered from this study suggest that agile development teams are extremely dependent on a well-functioning interface to business related parts of an organization. Regarding teams’ ability to make decisions and being agile in their way of working, the results primarily isolate impediments with roots in an unwillingness to adhere to and lack of understanding of agile principles. In this thesis, our gathered results were also correlated with a modern framework called Flow in order to confirm its relevance regarding analyzing software development teams in large-scale environments.