O MUX-GSE é um conjunto de equipamentos ópticos, mecânicos e eletrônicos que verifica, através de testes automáticos, uma série de requisitos funcionais e auxilia na montagem e integração da câmera multiespectral dos satélites CBERS-3&4. Estes satélites, fruto de uma parceria entre Brasil e China, são instrumentos de sensoriamento remoto, produzindo imagens da terra para estudos em diversas áreas, principalmente as relacionadas à exploração sustentável dos recursos naturais. A câmera multiespectral é a primeira do gênero projetada e produzida no Brasil e tem grande importância dentro do programa espacial brasileiro. O sucesso da câmera multiespectral está intimamente ligado ao bom funcionamento do MUX-GSE, conseqüentemente, os softwares que controlam estes equipamentos e realizam os testes automáticos precisam de alta confiabilidade. O processo de software é um conjunto estruturado, composto de modelo de desenvolvimento, atividades, métodos, ferramentas e práticas, que pode assegurar a qualidade necessária a um produto de software. A definição deste processo é o primeiro passo para a execução de um projeto complexo. O objetivo deste trabalho é a implementação de um processo que permita a construção dos aplicativos do MUX-GSE em curto espaço de tempo, com uma equipe pequena e com o nível de confiabilidade necessário. A solução proposta, detalhada no texto, é baseada nos métodos ágeis, que definem práticas simples, mas que permitem assimilar mudanças ocorridas em qualquer fase do desenvolvimento. A implementação desta metodologia permitiu a produção dos aplicativos necessários a despeito de uma série de problemas enfrentados e sem atrasos que impactassem o desenvolvimento da câmera multiespectral. Este trabalho mostra que um conjunto de técnicas relativamente simples pode ser mais adequado que aquelas tradicionalmente aplicadas na engenharia de software, mesmo em projetos complexos, cabendo à equipe de desenvolvimento a análise e seleção do melhor método. Mostra ainda que estas técnicas permitem manter ou até superar a confiabilidade obtida através de métodos tradicionais. / The MUX-GSE is a set of optical, mechanical and electronic equipments that verifies, through automatic tests, a series of functional requirements and assists during the assembly and integration phases of the satellites CBERS-3&4\'s multispectral camera. These satellites, fruit of a partnership between Brazil and China, are remote sensing instruments, producing images of the earth for studies in several areas, mainly the ones related to the sustainable exploitation of natural resources. The multispectral camera is the first of its gender fully projected and produced in Brazil and is of great importance for the brazilian space program. The success of the multispectral camera is intimately related to the good operation of the MUX-GSE, therefore, the necessity of reliable software to control these equipments and to accomplish the automatic tests. The software process is a structured set composed of development model, activities, methods, tools and practices, that can assure the necessary quality to a software product. The definition of this process is the first step in the execution of a complex project. The objective of this work is to implement a process that allows the construction of the MUX-GSE\'s software in short term, by a small team and with the required reliability level. The proposed solution, detailed in the text, is based on agile methods, which define simple practices, but that allow to assimilate changes in any development stage. The implementation of this methodology provided means to produce the necessary applications, in spite of several faced problems, without delays that could possibly prejudice the multispectral camera development schedule. This work shows that relatively simples techniques can be more appropriate than those traditionally applied in software engineering, even in complex projects, being the development team on charge of the analysis and decision of the most suitable development method. It also shows that the employed technique can reach, or even surpass, the software reliability achieved through traditional methods.

Este trabalho analisa os principais métodos ágeis utilizados em empresas startup, como scrum, extreme programming, kanban e lean, isolando suas práticas e mapeando-as no Kernel do SEMAT para escolher os elementos essenciais da engenharia de software que estão relacionados a cada prática de forma independente. Foram identificadas 34 práticas que foram reduzidas a um conjunto de 26 pelas similaridades. Um questionário foi desenvolvido e aplicado no ambiente de startups de software para a avaliação do grau de utilização de cada determinada prática. Através das respostas obtidas foi possível a identificação de um subconjunto de práticas com utilização acima de 60% onde todos os elementos essenciais da engenharia de software são atendidos, formando um conjunto mínimo de práticas capazes de sustentar este tipo específico de ambiente. / This work analyses the main agile methods used in startup companies such as scrum, extreme programming, kanban and lean, isolating their practices and mapping them on SEMAT Kernel to choose the essential elements of software engineering that are related to each practice independently. 34 practices were identified and reduced to a set of 26 by similarities. A questionnaire was developed and implemented in software startups environment to evaluate the usage degree of each particular practce. Through the responses obtained it was possible to identify a subset adopted by more than 60% of respondents where all the essential elements of software engineering are met, forming a minimum set of practices capable of sustaining this specific type of environment.

O MUX-GSE é um conjunto de equipamentos ópticos, mecânicos e eletrônicos que verifica, através de testes automáticos, uma série de requisitos funcionais e auxilia na montagem e integração da câmera multiespectral dos satélites CBERS-3&4. Estes satélites, fruto de uma parceria entre Brasil e China, são instrumentos de sensoriamento remoto, produzindo imagens da terra para estudos em diversas áreas, principalmente as relacionadas à exploração sustentável dos recursos naturais. A câmera multiespectral é a primeira do gênero projetada e produzida no Brasil e tem grande importância dentro do programa espacial brasileiro. O sucesso da câmera multiespectral está intimamente ligado ao bom funcionamento do MUX-GSE, conseqüentemente, os softwares que controlam estes equipamentos e realizam os testes automáticos precisam de alta confiabilidade. O processo de software é um conjunto estruturado, composto de modelo de desenvolvimento, atividades, métodos, ferramentas e práticas, que pode assegurar a qualidade necessária a um produto de software. A definição deste processo é o primeiro passo para a execução de um projeto complexo. O objetivo deste trabalho é a implementação de um processo que permita a construção dos aplicativos do MUX-GSE em curto espaço de tempo, com uma equipe pequena e com o nível de confiabilidade necessário. A solução proposta, detalhada no texto, é baseada nos métodos ágeis, que definem práticas simples, mas que permitem assimilar mudanças ocorridas em qualquer fase do desenvolvimento. A implementação desta metodologia permitiu a produção dos aplicativos necessários a despeito de uma série de problemas enfrentados e sem atrasos que impactassem o desenvolvimento da câmera multiespectral. Este trabalho mostra que um conjunto de técnicas relativamente simples pode ser mais adequado que aquelas tradicionalmente aplicadas na engenharia de software, mesmo em projetos complexos, cabendo à equipe de desenvolvimento a análise e seleção do melhor método. Mostra ainda que estas técnicas permitem manter ou até superar a confiabilidade obtida através de métodos tradicionais. / The MUX-GSE is a set of optical, mechanical and electronic equipments that verifies, through automatic tests, a series of functional requirements and assists during the assembly and integration phases of the satellites CBERS-3&4\'s multispectral camera. These satellites, fruit of a partnership between Brazil and China, are remote sensing instruments, producing images of the earth for studies in several areas, mainly the ones related to the sustainable exploitation of natural resources. The multispectral camera is the first of its gender fully projected and produced in Brazil and is of great importance for the brazilian space program. The success of the multispectral camera is intimately related to the good operation of the MUX-GSE, therefore, the necessity of reliable software to control these equipments and to accomplish the automatic tests. The software process is a structured set composed of development model, activities, methods, tools and practices, that can assure the necessary quality to a software product. The definition of this process is the first step in the execution of a complex project. The objective of this work is to implement a process that allows the construction of the MUX-GSE\'s software in short term, by a small team and with the required reliability level. The proposed solution, detailed in the text, is based on agile methods, which define simple practices, but that allow to assimilate changes in any development stage. The implementation of this methodology provided means to produce the necessary applications, in spite of several faced problems, without delays that could possibly prejudice the multispectral camera development schedule. This work shows that relatively simples techniques can be more appropriate than those traditionally applied in software engineering, even in complex projects, being the development team on charge of the analysis and decision of the most suitable development method. It also shows that the employed technique can reach, or even surpass, the software reliability achieved through traditional methods.

<p>In today’s fast-paced world, there is a constant demand for better and more efficient ways of doing business. Motorola in Linköping are using the agile development framework, Scrum in their software development. A certain level of quality must also be assured of the delivered goods and services. Is it possible to use Scrum and still meet the quality requirements?</p><p>This Master Thesis is performed to investigate if it is possible to achieve a quality certificate from TL 9000, the telecom industry extension of ISO 9000, when using the agile development framework Scrum. The investigation consists of interviews and observations at Motorola, Linköping, along with literature studies about quality systems and agile development.</p><p>The conclusion is that it is possible to meet the TL 9000 requirements when using Scrum, under the condition that some additional processes are performed and that other parts of the organization also fulfills the remaining requirements. This is needed since there are requirements that are out of scope for the Scrum framework. Examples of the suggested additions are to follow the Scrum framework more strictly and to adopt a more specific definition of done.</p>

We mainly study development velocity in agile teams in this dissertation. The concept of development velocity relates to the classical problem of time estimation in software development and software development planning. Building on previous literature as well as a case study, we explore and theorize the factors that cause ‘velocity flux’, i.e. fluctuations in development velocity through studying the relationship between development velocity and the rate of incoming customer feature requests. The aim of this study is to contribute to a better understanding of what causes velocity flux in agile development, and discusses the implications of the findings for research and practical implications for agile planning. As a result, we propose nine factors that cause velocity flux, and provide some strategies to overcome them in order to make a more effective sprint planning in agile teams.

This study examines how Design principles affect the view of Usability in Agile development. This case study has been conducted together with Uppsala Municipality’s Development department. The Design principles from Användningsforum and Government Digital Service are studied together with Agile development strategy to determine the influence on Usability. This is an empirical inductive study where data is collected and analyzed so that a theory may be presented. The thesis is based on qualitative data gathered from Uppsala Municipality’s development project and focus on the experience and attitude of the developers in the department. Data is collected through interviews and observations of the team members. Data is analyzed with Grounded theory approach. From the results it is concluded that the Design principles influence members of the department's awareness and focus on Usability when work with Agile development project.

No description available.

É possível notar no trabalho diário das empresas que a pressão por diminuir o prazo de entrega dos softwares ainda é uma realidade. Neste contexto, empresas adotam técnicas de desenvolvimento ágil de software, implementando entregas constantes e estabelecendo ciclos iterativos e curtos no processo de desenvolvimento de software. Mas, se por um lado estas técnicas visam inovar e reduzir tempo de desenvolvimento, por outro, as empresas sentem-se pressionadas a adotar a forma tradicional de manter a qualidade de software. Neste ponto, o CMMI se apresenta como um modelo de maturidade de reconhecimento mundial e é classificado na abordagem tradicional por pregar grande formalismo e foco no processo. A abordagem ágil coloca que os indivíduos e suas interações têm maior importância que os processos e as ferramentas e que ser adaptável às mudanças é mais importante do que seguir a rigor o planejado. Ao integrar estes dois modelos de abordagens distintas espera-se que as práticas ágeis possam ajudar organizações maduras a se tornarem mais flexíveis. Com o intuito de averiguar esta integração, utilizou-se o método de pesquisa de estudo de caso, de modo a se aprofundar nas empresas que possuem certificação CMMI e decidiram adotar o modelo de desenvolvimento ágil. O objetivo é levantar como estas empresas resolveram os pontos de conflito da abordagem tradicional e ágil, de modo a se tornarem mais eficazes. O estudo ainda contém um quadro de integração CMMI versus desenvolvimento ágil de modo a elencar os pontos que merecem maior atenção e esforço de adaptação, visando a concretização da integração. / It\'s possible to notice in the daily work of companies that pressure by decreasing the delivery of software is still a reality. It is in this context that companies adopt the techniques of agile software development, implementing and establishing constant deliveries and short iterative cycles in the process of software development. But if on the one hand these techniques aim to innovate and reduce development time, on the other, companies feel pressured to adopt the traditional way of maintaining the quality of software. At this point, the CMMI is presented as maturity model worldwide recognition, classified in the traditional approach for preaching extensive formalism and focus on the process, as the agile approach puts individuals and their interactions is more important than processes and tools, where being adaptable changes is more important than following the strict what was planned. By integrating these two models of different approaches, it is expected that agile practices can help organizations mature to become more flexible. In order to investigate this integration is that this study uses the research method of case study so as to deepen the companies that have decided to adopt CMMI and agile development model. The goal is to raise as these companies solved the trouble spots of the traditional approach and agile in order to become more effective. The study also contain a framework for integrating CMMI vs. Agile development in order to list the points that deserve more attention and effort to adapt in order to achieve integration.

Quality assurance activities, in software development, are the backbone of whole project. These activities are not only responsible of product quality, but also for process quality. In conventional software development QA is a separate group of QA experts. As the trends of software development moved towards agile development, QA activities also got changed. In agile development most of these activities are performed by developers. Close people collaboration, onsite customer and Test Driven Development are the approaches in agile development to achieve better product quality. In this thesis we have presented the philosophical as well as practical angle QA in agile development. Mindset of agile development revolves around product quality but there is much work to be done to impart quality of process in agile development to get it standardized and more organized. QA activities remain centric and focused to testing. Practices like SPI and following some standards are lacking in agile methodologies. In this thesis we have proposed to inject an extra layer of QA in agile projects. Purpose of injecting and extra layer, is to use the knowledge of QA experts to achieve quality in development process that will result in higher level of product quality.

Software testing is the most important process to verify the quality of a product. Software testing in Agile development is very complex and controversial issue in literature and industry. Different people have different views about software testing in Agile methods, because most of Agile methods do not focus much on software testing activities. Agile strongly focus on the close customer collaboration, short iterations and frequent deliveries. But when it comes to software testing, then it is challenging, as Agile do not include many destructive testing practices, which are normally required for a quality product. This thesis covers the area of software testing process in Agile development. Agile development processes could be more beneficial and refined by adding testing practices and for this purpose; we proposed a concept of an independent integrated software testing team. This research also identifies the practices of Agile development in industry and the critical issues in industry while practicing Agile development. The issues of automated and manual testing, good practices in automation, and how to manage independent testing teams in Agile development are also high lightened. This report highlights every aspect of software testing process in Agile development. This research is based on literature reviews and an industrial survey.