Agile methodologies have become a popular and widely accepted method for managing software development. Since the inception of the Agile Manifesto over ten years ago, agile development techniques have superseded waterfall methods in many, if not most, software development organizations. Despite its apparent success, many companies have struggled with the adoption and implementation of agile, and exactly what level of adoption provides optimum agility. Agility is commonly held in the literature to be constructed of elements external to a company or project but may in fact be composed of both external and internal elements. The exact relationship of the adoption of agile development techniques and their relationship to the actual agility of a business remain unclear. A primary contributor to this uncertainty is the somewhat amorphous definition of agile itself. In academic literature, the concept is still relatively young and loosely defined. In practice, organizations have largely opted for a hybrid approach to agile, mixing its concepts and methods with existing Stage Gate or waterfall methodologies. This has made the management of agile even more complex. Crucially, there is no definition or criterion available to determine the appropriate mix of agile and waterfall processes in an embedded software development context nor is there a method to determine the impact of one against the other. These issues beg the question: how do organizations manage agility? This interpretive case study provides an empirical account of how stakeholders manage both market and process agility in an embedded systems context via a hybrid agility implementation and product genesis. As a result, we provide the notion of agile vorticity, as the point at which market and process agility collide to produce business momentum at a specific point of innovation within the agile business vortex.

Thesis--Auburn University, 2009. / Abstract. Includes bibliographical references (p. 39-41).

The thesis focuses on the issue of Agile approach Scrum in IT project management, namely the description and analysis of the current state of Agile approaches in selected company and the subsequent drafting own proposals for improvement of the management of IT projects. A literature background review deals with the basic characteristics and rules of agile approach Scrum. In the practical part of the Thesis is introduced the company Juicymo s.r.o. After a brief description of the company, the current state of agile approach to IT project management is described and analyzed. The thesis primarily described in detail cases in which the management of the company differs from the definitions and rules of Scrum. The thesis also drawn up concrete proposals on how to improve the current state of management of the selected company.

This dissertation is focused on the topic of management, development, and maintenance of web applications. Main goal of the this dissertation thesis focuses to propose economic, financial, and technically optimum solution in the manner of development, management and maintenance of web applications. As the partial goals author makes empirical analysis and comparison of existing methods, author also compares advantages and disadvantages of chosen management methodologies and suggests a new optimal solutions based on academic research and results. Secondly, form a literature review to explore the state of the topic in our and foreign literature. Thirdly, characterize conceptual materials relating to management development, maintenance and use of web applications in small business. Fourthly, assess possible solutions in the use of web applications development Lastly author makes practical test selected methods and tools. Dissertation will help to small business entrepreneurs to choose optimum solution in their business environment.

TORRES FILHO, A. A. 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 em Ciência da Computação) - Centro de Ciências, Universidade Federal do Ceará, Fortaleza, 2014. / Submitted by Daniel Eduardo Alencar da Silva (dealencar.silva@gmail.com) on 2015-01-23T20:18:36Z No. of bitstreams: 1 2014_dis_aatfilho.pdf: 5052662 bytes, checksum: bbc494f5731e2ba4a447896641ee5d11 (MD5) / Approved for entry into archive by Rocilda Sales(rocilda@ufc.br) on 2015-09-23T16:29:47Z (GMT) No. of bitstreams: 1 2014_dis_aatfilho.pdf: 5052662 bytes, checksum: bbc494f5731e2ba4a447896641ee5d11 (MD5) / Made available in DSpace on 2015-09-23T16:29:47Z (GMT). No. of bitstreams: 1 2014_dis_aatfilho.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

Dissertação (mestrado) - Universidade Federal de Santa Catarina, Centro Tecnológico. Programa de Pós-Graduação em Ciência da Computação / Made available in DSpace on 2013-06-25T19:16:21Z (GMT). No. of bitstreams: 1 311840.pdf: 1347542 bytes, checksum: 29e066295925790f3ea8feb592d26a15 (MD5) / O principal objetivo dos métodos ágeis existentes é promover o desenvolvimento eficiente de software através de práticas que priorizam a comunicação com o cliente e entregas frequentes. Cada método ágil apresenta um conjunto próprio de práticas. Com esta diversidade de práticas torna-se interessante a construção de novos processos ágeis que contemplem apenas as práticas mais adequadas a partir destes métodos. O problema, entretanto, é que a combinação de práticas de diferentes métodos ágeis não garante, necessariamente, que o novo processo definido seja ágil. Este trabalho avalia a agilidade do conjunto de práticas de um framework de práticas ágeis e busca identificar quais práticas apresentam maior harmonia quando usadas no mesmo processo. A agilidade das práticas é avaliada através dos dados de uma grande pesquisa de opinião online e a harmonia entre elas é identificada através da técnica de análise de agrupamentos. Os melhores resultados foram apresentados pelas práticas de Integração contínua, Desenvolvimento lado a lado e Testes de aceitação. A análise de agrupamentos, por sua vez, formou quatro grupos de práticas: o primeiro formado por Projeto da arquitetura do sistema e Lista de requisitos; o segundo por Desenvolvimento coletivo de código, Integração contínua, Refatoração e Testes de aceitação; o terceiro por Projeto da iteração e Modelagem geral; e o quarto por Desenvolvimento lado a lado e Reuniões diárias. / The main objective of agile methods is to promote efficient software development through practices that prioritize communication with the client and frequent deliveries. Each agile method presents its unique set of practices. This diversity of practices may lead to the definition of new agile processes that include only the more appropriate practices from these methods. The problem, however, is that combining practices from different methods does not guarantee that the resulting process can be considered agile. This work assesses the agility of a set of practices of a framework for selecting agile practices and seeks to identify which practices provide more harmony when used in the same process. The agility of the practices is evaluated using data from a large online survey and the harmony between them is identified by the technique of cluster analysis. The best results were presented by the practices of Continuous integration, Side by side development and Acceptance tests. The cluster analysis resulted in four practice groups: the first with System architectural design and Requirements list; the second with Collective code ownership, Continuous integration, Refactoring and Acceptance tests; the third with Iteration design and General modeling; and the fourth with Side by side development and Daily meetings.

Thesis Submitted in fulfilment of the requirements for the degree Master of Technology in Information Technology in the Faculty of Informatics and Design at the Cape Peninsula University of Technonlogy / The use of Information and Communication Technology (ICT) in business has evolved to such an extent that many organizations (if not all) rely on Information Technology (IT) systems to better manage their processes, get competitive advantage, improve performance (efficiency and effectiveness), provide quality services on time and most importantly to keep customers happy. This has changed the way people communicate and conduct businesses, lowering processing cost, time and improving a return on investment. Therefore, high quality software systems are essential. Organizations adopt Agile Scrum methodologies in order to develop applications that help them to obtain a return on investment quickly, to improve customer satisfaction and to maintain competitive advantage. However, the IT industry is yet to develop error-free software that meets the expected quality standards. Therefore, the aim of this study was to explore the extent to which software quality assurance measures can be understood and applied to maximize the quality of software projects developed under Scrum methodology. A qualitative research method informed by an interpretive approach was used to collect and analyse data. Following the purposive sampling technique, five Scrum teams operating in different environments and two academics from one academic institution were interviewed. Structuration Theory (ST) was then used as an analytical framework to analyse data and to improve the understanding of Scrum practices and related quality assurance (QA) processes. Drawing on the major terms of ST, the contextual terrain of the Scrum development process was mapped. It reflected that rules are important aspects of Scrum functions. However, rules are not as strictly applied as in the traditional methodologies. The developer skill, project type and size have a direct influence on the practice/s. In Scrum, rules are flexible in that they can be modified to meet the environment and conditions of the team. Equally significant are resources, most particularly, time and the human resources in the form of developers and Scrum leaders. Otherwise, unit testing, user acceptance testing, close collaboration and code reviews were perceived as the most important practices in Scrum projects. In view of the findings, recommendations can be summed up into 4 main points; (1) that to ensure quality assurance in Scrum, Scrum teams, especially team leaders, should enforce compliance to standards, regardless of time pressures and tight deadlines; (2) It seems that the practice of working with the client to test final products as a quality assurance mechanism is working for all parties. This practice is encouraged and must be maintained; (3) Code reviews must be enforced, and that organisations invest in resources including the constant training of developers; (4) Project product owners, project managers, team leaders and business analysts should regularly meet with the user to verify requirements prior to the implementation phase. Active stakeholder involvement can minimize development costs and time.

Målet med min rapport har varit att undersöka de svårigheter och problem som utvecklare på Barnebys kan ställas inför under sitt dagliga arbete. För att begränsa mig har jag valt två stora områden att undersöka, det agila arbetssättet och versions hanteringssystem. Men det viktigaste fokuset i rapporten är vilka problem som uppstår som är relaterade att man jobbar flera utvecklare på samma projekt. Så kallade teams. Rapporten avhandlar en teoretisk bakgrund till de båda ämnena och sedan så genomför jag en undersökning bland de anställda på Barnebys teknikavdelning. Undersökningen görs medhjälp av Google Forms och här finns frågor kring dessa ämnen. Rapporten tar också upp förslag på lösningar och/eller förbättringar. Rapporten avslutas med en presentation av resultatet och egna reflektioner.

Submitted by Daniella Sodre (daniella.sodre@ufpe.br) on 2015-03-10T12:07:29Z No. of bitstreams: 2 Dissertaçao Aureneia de Santana.pdf: 2151503 bytes, checksum: c59d40d61142cbc0d5badcca65289d07 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) / Made available in DSpace on 2015-03-10T12:07:29Z (GMT). No. of bitstreams: 2 Dissertaçao Aureneia de Santana.pdf: 2151503 bytes, checksum: c59d40d61142cbc0d5badcca65289d07 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Previous issue date: 2013-12-10 / Os projetos fazem parte do dia-a-dia das organizações e é bastante comum o número de demandas ser superior à capacidade da equipe disponível. Por isso, a importância de ser ter processos definidos para ajudar selecionar e priorizar aqueles projetos que são mais relevantes para a instituição. O presente trabalho apresenta uma proposta de solução para ajudar no gerenciamento das demandas recebidas pela organização, desde a solicitação, até a implantação no ambiente do cliente, com os seguintes objetivos: (1) Construir um método para definição de critérios para priorização de projetos. O método deve indicar os projetos que podem trazer mais benefícios para a organização e menor custo para a equipe de desenvolvimento, baseado em critérios definidos a partir de termos comuns utilizados no dia-a-dia da organização. (2) Propor um processo de desenvolvimento de software baseado no Framework Scrum, fazendo uso do método de priorização de projetos proposto. A avaliação do método de priorização se deu comparando os resultados obtidos com o do Método TOPSIS (Technique for Order of Preference by Similarity to Ideal Solution) e opinião de um especialista, revelando que pode ser uma ferramenta útil para o órgão, pois permite identificar previamente quais os projetos trarão mais benefícios para a organização e consequentemente devem ter mais prioridade no desenvolvimento, minimizando os riscos e fracassos nos projetos e melhor otimização da equipe de desenvolvimento.

Scoping in Software Product Lines (SPL) is the first step to identify products, features, and assets in a market segment. Traditional approaches for SPL scoping are heavyweight and upfront processes in scenarios with unpredictable changes and little resources. An incurred key challenge is handling systematically the iterativeness, adaptability, and feedback in the SPL scoping process. As a final consequence, the software industry can hamper investment in the SPL scoping. In this context, the Scrum framework, as the most popular agile approach to foster the iterativeness, adaptability, and feedbacks, can address that challenge. Previous studies have combined Scrum into some SPL activities with good results. This thesis provides a process, named of RiPLE-SCA, for SPL scoping inspired in the Scrum practices. This process bases on industrial evidence (a case study of a traditional SPL scoping), expert opinion on agile SPL (through a survey), and scientific literature about agile SPL (a systematic mapping). A feasibility study and a cross-case study carried out with two industrial partners indicated that the RiPLE-SCA is practicable and appropriate for an industrial setting as well as fosters iterativeness, adaptability, and feedbacks detecting early obsolete features and changes in domain, requirements, features, and technology. / Submitted by João Arthur Martins (joao.arthur@ufpe.br) on 2015-03-12T18:58:41Z No. of bitstreams: 2 Tese Ivonei Freitas da Silva.pdf: 9233841 bytes, checksum: 6029df71deecd12c97bd99e1787a8361 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) / Made available in DSpace on 2015-03-12T18:58:41Z (GMT). No. of bitstreams: 2 Tese Ivonei Freitas da Silva.pdf: 9233841 bytes, checksum: 6029df71deecd12c97bd99e1787a8361 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Previous issue date: 2013-10-29 / CNPq / A atividade de escopo em linhas de produto de software é o primeiro passo para identificar produtos, características e ativos de software em um segmento de mercado. As abordagens tradicionais para escopo de linhas de produto de software são processos densos e abrangentes em cenários com mudanças imprevisíveis e com poucos recursos. Um desafio chave nesse cenário é o gerenciamento sistemático da iteratividade, adaptabilidade e do feedback no processo de escopo de linhas de produto de software. Como último efeito, a indústria de software pode restringir investimentos no processo de escopo. Neste contexto, o framework Scrum, abordagem mais popular para incentivar a iteratividade, a adaptabilidade e o feedback, pode lidar com esse desafio. Estudos anteriores têm combinado Scrum com algumas atividades de linhas de produto de software obtendo bons resultados. Esta tese define um processo, denominado de RiPLE-ASC, para o escopo da linha de produtos de software inspirado nas práticas do Scrum. Este processo basea-se nas evidências da indústria (um estudo de caso real de escopo de linhas de produto usando uma abordagem tradicional), na opinião de especialistas em linhas de produto de software ágeis (através de um survey) e na literatura científica sobre linhas de produto de software ágeis (uma mapeamento sistemático). Um estudo de viabilidade e um estudo de caso “cross-case” executados com dois parceiros industriais de nosso grupo de pesquisa indicaram que o RiPLE-ASC tem aplicação prática e adequa-se em um ambiente de produção de software industrial bem como incentiva a iteratividade, adaptabilidade e o feedback detectando cedo características obsoletas e mudanças no domínio, requisitos, características e tecnologia