A tecnologia de agentes tem sido reconhecida como um paradigma promissor em sistemas educacionais da nova geração. Entretanto, o esforço e inflexibilidade de algumas metodologias próprias para agentesacarretam num alto custo, tempo e adaptação de escopo. Este trabalho visaavaliar alternativas de desenvolvimento de um jogo educacional médico orientado a agentes, através da aplicação de um estudo de caso, com o intuito de verificar se metodologias próprias para implementação de sistemas multiagentes trazem benefícios no resultado final da implementação do jogo, e também se os resultados alcançados na comparação de processos de desenvolvimento de cunho tradicional e ágil fazem diferença no resultado final. Desta forma, este trabalho compara três metodologias baseadas nos conceitos da Engenharia de Software através de um estudo de caso, sendo elas: O-MaSE que é uma metodologiatradicional de desenvolvimento de sistemas multiagentes e utiliza um processo de desenvolvimento tradicional; AgilePASSI que é baseada no processo de desenvolvimento ágil e específica para sistemas multiagentes; e, por último, Scrum que é uma metodologia ágil, não sendo específica para implementação de sistemas multiagentes / The agent technology has been recognized as a promising paradigm in educational systems of the new generation. However, the effort and inflexibility of some specific methodologies entail a high cost, time and adaptation scope. This work aims to validate options for developing an educational medical game oriented agents by applying an experiment in order to verify that methodologies specific to implement multi-agent systems provide benefits in the result of the implementation of the game, and also the results achieved by comparison of traditional and agile development processes makes a difference in the outcome. Thus, this paper compares three approaches based on the concepts of software engineering through an experiment, as follows: O-MaSE is a traditional methodology for the development of multi-agent systems and uses a traditional development process; AgilePASSI which is based on agile and specific development for multi-agent systems; and finally, Scrum that is an agile methodology, not specific to implementation of multi-agent systems.

The software development for mobile devices such as mobile phones, smartphones and tablets requires knowledge not only of processes but also related to software and hardware technology platforms of these devices. Continuous improvement in the performance of these platforms and the increasing demand for a variety of applications require a high competitiveness and, therefore, high levels of productivity and quality. In this scenario, agile methodologies are used and fit well to frequently changing requirements and to time to market. Among these methodologies, Scrum is one of the most accepted and used, contributing to the improvement of project management, team productivity, product quality and increasing the probability of project success. On the other hand, there is an increasing adoption of quality management methodologies such as Lean Six Sigma in Information Technology and Communication (ICT) organizations due to their proven results in improving processes development and quality of services and products developed. Methodologies such as Scrum and Lean Six Sigma have different goals, however, they can contribute together in the development of software for mobile devices. In literature, there are studies that propose the integration of agile methodologies and software quality, however, they have gaps regarding the possibility of systematic reuse of this integration, as well as in evaluating the use of these integrated methodologies. Thus, this paper proposes an evolution of an existing approach, called SLeSS, that integrates Scrum to Lean Six Sigma and has been used in the software customization for mobile phones. The evolution of this approach is to add software development in addition to customization and improve integration mechanisms initially proposed with a focus on evaluation of the practices and principles of Scrum from the use of techniques of Lean Six Sigma. This new version is applied in seven actual projects that are related to software development and customization for mobile devices and their results are also discussed in this dissertation. / O desenvolvimento de software para dispositivos mÃveis como smartphones, celulares e tablets requer conhecimento dos processos e das tecnologias relacionadas Ãs plataformas de software e de hardware desses dispositivos. A melhoria contÃnua no desempenho dessas plataformas e a demanda crescente por uma variedade de aplicaÃÃes impÃem uma alta competitividade e, por conseguinte, exigem nÃveis elevados de produtividade e de qualidade dos projetos de desenvolvimento. Nesse cenÃrio, as metodologias Ãgeis sÃo utilizadas por se adequarem bem Ãs frequentes mudanÃas de requisitos e Ãs demandas de prazo desse nicho de mercado. Dentre essas metodologias, o Scrum à uma das mais aceitas e utilizadas, contribuindo na melhoria da gestÃo de projetos, na produtividade do time, na qualidade dos produtos e no aumento da probabilidade de sucesso dos projetos. Por outro lado, hà uma crescente adoÃÃo de metodologias de gestÃo da qualidade como o Lean Six Sigma por organizaÃÃes da Ãrea de Tecnologia da InformaÃÃo e ComunicaÃÃo (TIC) devido aos seus resultados comprovados na melhoria dos processos de desenvolvimento e da qualidade dos serviÃos e dos produtos desenvolvidos. Metodologias como o Scrum e o Lean Six Sigma possuem objetivos distintos, entretanto, elas podem contribuir juntas no desenvolvimento de software para dispositivos mÃveis. Na literatura existem trabalhos que propÃem a integraÃÃo de metodologias Ãgeis e de qualidade de software, entretanto, esses trabalhos possuem lacunas no que tange a possibilidade de reuso sistemÃtico das mesmas bem como a avaliaÃÃo do uso dessas metodologias integradas. Este trabalho propÃe entÃo uma evoluÃÃo de uma abordagem jà existente, denominada SLeSS, que integra o Scrum ao Lean Six Sigma e que foi utilizada na customizaÃÃo de software para celulares. Essa evoluÃÃo visa ampliar a abordagem tanto para o desenvolvimento de software alÃm da customizaÃÃo quanto para melhorar os mecanismos de integraÃÃo inicialmente propostos com um foco na avaliaÃÃo das prÃticas e princÃpios do Scrum a partir do uso de tÃcnicas do Lean Six Sigma. Para avaliar a nova versÃo, ela à aplicada em sete projetos reais de desenvolvimento e customizaÃÃo de software para dispositivos mÃveis e seus resultados sÃo tambÃm discutidos nesta dissertaÃÃo.

Submitted by Mauricio Taves Cordeiro Coelho (mauricio.taves@gmail.com) on 2013-03-06T04:54:05Z No. of bitstreams: 1 MEX - Dissertação versão final - para submissão e impressão.pdf: 958516 bytes, checksum: 78a99a7592f57afeea670db87e854a41 (MD5) / Approved for entry into archive by Janete de Oliveira Feitosa (janete.feitosa@fgv.br) on 2013-04-09T17:43:26Z (GMT) No. of bitstreams: 1 MEX - Dissertação versão final - para submissão e impressão.pdf: 958516 bytes, checksum: 78a99a7592f57afeea670db87e854a41 (MD5) / Approved for entry into archive by Marcia Bacha (marcia.bacha@fgv.br) on 2013-04-11T11:42:55Z (GMT) No. of bitstreams: 1 MEX - Dissertação versão final - para submissão e impressão.pdf: 958516 bytes, checksum: 78a99a7592f57afeea670db87e854a41 (MD5) / Made available in DSpace on 2013-04-11T11:43:25Z (GMT). No. of bitstreams: 1 MEX - Dissertação versão final - para submissão e impressão.pdf: 958516 bytes, checksum: 78a99a7592f57afeea670db87e854a41 (MD5) Previous issue date: 2012-12-20 / The adoption of agile software development management methods has been a global trend, considering companies in the technology sector. Brazilian companies operating in this market are not detached from this tendency, since the goal of these methods is to address a common scenario to any of these organizations: dealing with the difficulty of adequately modeling the usually complex problems that are the goal of building a specific software and with the constant change of requirements that this situation represents, further enhanced by the frenetic dynamics of information dissemination in the XXI century, besides modifying a chronic perception of failure that pervades the sector, aiming to deliver quality products to its customers with maximum speed. Internal aspects such as increasing productivity and reducing rework are also part of the objectives of the adoption of these methodologies. This study aims to assess the human and cultural aspects involved and identify the convergence between the expectations of the company and employees when adopting agile management, based on field research that captured the reactions of a group of respondents to the implementation of these methods at Modulo Security Solutions, a Brazilian technology and services company, after two years of extensive internal use. The results indicate the success of the implementation, with positive reactions from employees, despite the need for addressing human aspects to adjust the model and that the negative impact of local and organizational cultures have been widely perceived. / A adoção dos métodos ágeis de gestão do desenvolvimento de software tem sido uma tendência mundial, considerando-se as empresas do setor de tecnologia. Empresas brasileiras atuando neste mercado não estão apartadas deste quadro, uma vez que o objetivo desses métodos é endereçar um cenário comum a qualquer uma dessas organizações: lidar com a dificuldade de modelar adequadamente os problemas usualmente complexos que são objetivo da construção de um software e com a mudança constante de requisitos que esta situação representa, potencializada ainda mais pela dinâmica frenética da disseminação da informação no século XXI, além de modificar um quadro crônico de fracassos e falhas no setor, visando entregar produtos de qualidade aos seus clientes com o máximo de velocidade. Aspectos internos como o aumento de produtividade e a redução de retrabalho também fazem parte dos objetivos de adoção destas metodologias. O presente estudo visa avaliar os aspectos humanos e culturais envolvidos e identificar a convergência entre as expectativas da empresa e dos empregados quando da adoção de métodos ágeis de gestão, a partir de pesquisa de campo que capturou as reações de um grupo de entrevistados à implantação desses métodos na Módulo Security Solutions, empresa brasileira de tecnologia e serviços, após dois anos de uso interno abrangente. Os resultados apontam para o sucesso da implantação, com reação positiva dos empregados, a despeito da necessidade de endereçamento de aspectos humanos para ajuste do modelo e do impacto negativo da cultura local e organizacional terem sido amplamente percebidos.

The thesis focuses on analysis and the selection of an appropriate project management tool for web based projects. The theoretical part characterizes project management, level of project management in IT environment and web based projects with their specifics. Within the web based projects, it characterizes the possibilities of development and delivery of the Web applications and the methodology used in the development -- rigorous and agile methodologies. The work focuses on the description of agile methodologies in managing software development and their usage in the management of web based projects. Procedures and ways of managing agile methodologies are reflected in the definition of requirements for functionality analyzed among the project management tools in the practical part. The practical part focuses on the description and characteristics of a sample of project management tools used in web based projects and analyzes the selection of the most appropriate one. Evaluation of project management tools is based on the level of compliance with the pre-defined functionalities and comparison of the cost of acquisition and operation for a 3 years period. The functionality of the selected project management tools is evaluated on the basis of meeting the level 8 defined areas. The cost for the project tools are evaluated in the methods of acquisition, which offers their suppliers - On-Premise, On-Demand with proprietary tools and Open Source Software tools under the GNU General Public License.

A crescente demanda por sistemas e a alta velocidade com que seus requisitos evoluem têm evidenciado que desenvolvimento de software exige flexibilidade, pois muitas decisões precisam ser tomadas durante o projeto. Além disso, as dificuldades para a produção de sistemas vão muito além das questões técnicas. Fatores estratégicos, comerciais e humanos são responsáveis por algumas das variáveis que contribuem para tornar o desenvolvimento de sistemas de software uma atividade altamente complexa. Modelos tradicionais de desenvolvimento de software propõem processos prescritivos que não consideram toda essa complexidade. Por outro lado, Métodos Ágeis de desenvolvimento de software sugerem uma abordagem mais humanística com foco na entrega rápida e constante de software com valor de negócios. Porém, para conseguir isto, é preciso escolher um conjunto de práticas de desenvolvimento adequado às características do projeto e da equipe. Desta forma, a natureza única de cada projeto e a necessidade de alta qualidade e produtividade tornam importante a busca por práticas de desenvolvimento. A partir de projetos que conduzimos usando métodos ágeis na academia e na indústria, identificamos e descrevemos 22 práticas para desenvolvimento de software que podem ser adotadas por equipes para aumentar o seu desempenho e/ou a qualidade do software. / The growing demand for systems and the high speed with which their requirements evolve has shown that software development requires flexibility because many decisions need to be taken during the project. Also, the difficulties for the production of software systems go far beyond the technical issues. Strategic, commercial and human factors are responsible for some variables that contribute to make the software development a highly complex activity. Traditional models of software development propose prescritive processes that do not consider all this complexity. On the other hand, Agile Methods of software development suggest an humanistic approach focused on fast and often business valuable software deliveries. But, in order to get it, one needs to choose an appropriated group of development practices accordingly to the project and team features. In this way, the individuality of each project and the need for better quality and productivity motivate the search for software development practices. Based on projects that we conducted by using agile methods in academic and industry environments we identified and described 22 software development practices that can be used by teams to increase their performance and/or the software quality.

Productivity improvement in the software industry is one of the major challenges facing many software development companies in this century. Most companies have adopted agile methodologies in order to profit from the benefits claimed for them. Agile methodologies are characterised by frequent software delivery, short feedback loops, quicker response to change, and problem identification earlier in the development process. The agile approach has been recognised as paving a way for companies to acquire higher software productivity, delivering good-quality and cost-effective software, enabling software development companies to respond to business challenges with their demands for high quality, high performance and high development speed in delivering the final product. For companies that adopt agile methodologies, understanding the factors that influence their teams’ software development productivity is a challenging task for management and practitioners today. In this research, an analysis is presented that identifies productivity factors that affect agile teams. It is a study of agile methods to identify common agile practices and/or values that have impact on productivity, and describes suitable metrics that could be used to measure agile team productivity. A qualitative research approach was used, and the case study was chosen as the research strategy. Two South African companies that are located in two different provinces and that adopted agile methodologies in their software development, were selected for the case studies. Qualitative content analysis was used in the research to permit subjective interpretation of factors that influence agile team productivity, and to analyse to what extent these factors affected productivity. This research has shown that an understanding of the factors that influence an agile team’s productivity gives significant insight into the way agile teams work, motivates team members to work together, and leads to uniform metrics in tracking each team’s progress. The study indicates that tracking an agile team’s work and providing adequate tools needed to execute their tasks results in improving agile team productivity. It should be recognised that using metrics to measure performance in agile teams is helpful in creating a team’s culture and trust. In this study, it was found that the factors identified in both literature and case studies affected productivity in the two companies under study, both positively and negatively. The study also found that applying the correct metrics in assessing, analysing and reviewing an agile team’s performance is important when monitoring productivity. Successful software delivery is only possible if individuals are committed to their work, are provided with the necessary tools and have access to a stable working environment. In addition, individual factors such as knowledge, skills, abilities, personalities and experience should be considered when forming agile teams. Consideration of these factors will result in grouping people that are able to work together and achieve a common goal, which is important in improving productivity. A conceptual framework for agile team productivity was proposed. The discussion of the findings is presented in more detail in this research. / School of Computing / M.Sc. (Computing)

Kravhanteringen är en av de viktigaste delarna i ett systemutvecklingsprojekt. I kravhanteringen ingår aktiviteter som att samla in krav, analysera och prioritera vilket är för att skaffa sig en så tydlig bild av det framtida resultatet som möjligt. I alla aktiviteter i kravhanteringen kommuniceras det mellan olika intressenter. Kommunikation är en vital del av kravhanteringen då projektteamet tillsammans med kunden identifierar och tar fram kund- och användarbehov genom en rad aktiviteter.Covid-19 pandemin påverkade hela världen och för att begränsa smittspridningen togs beslut om att de som kunde jobba hemifrån skulle göra det. Detta ledde till att många verksamheter fick anpassa sig efter distansarbete och kommunikation i virtuella miljöer vilket påverkade kommunikationen på olika sätt. Syftet med uppsatsen är att besvara frågan hur kravhanteringsfasen har påverkats av en omställning till distansarbete. För att samla in relevant data har kvalitativ forskningsmetod använts och semi-strukturerade intervjuer har genomförts. Den insamlade data har analyserats med hjälp av en tematisk analys där två systemutvecklingsmodeller agila metoden och vattenfallsmodellen togs upp. Resultatet av uppsatsen påvisar att alla på ett eller annat sätt påverkats av distansarbete. Det framgick att kommunikationen i kravhanteringen påverkats extra. Projektteamen försökte lösa utmaningarna genom en rad olika metoder, men lösningarna resulterade i att kravhanteringen inte påverkades resultatmässigt eller påverkat systemutvecklingsprojektet utgång. Kravhanteringen tog dock längre tid och projektteamen fick arbeta hårdare för att nå samma resultat som om det skett ansikte mot ansikte. Resultatet av studien beskriver att kommunikation i virtuell miljö bara är ett substitut i stället för att genomföra fysiska möten. / Requirements management is one of the most important parts of a system development project. Activities such as collecting requirements, analyzes and prioritizing to obtain as clear picture of the future result as possible. In all the activities in requirements management, it communicates between different stakeholders. Communication is a vital part of requirements management, as the project team together with the customer identifies and develops customer and user needs through the process. The Covid-19 pandemic affected the whole world and to limit the spread of infection, it was decided that everyone who could work from home would work from home. This led to many businesses having to adapt to teleworking and communication in virtual environments. This affected communication in different ways. The purpose of the thesis is to answer the question of how the requirements management phase has been affected by the transition to telework. To collect relevant data, qualitative research methods have been used and semi-structured interviews have been conducted. The collected data have been analyzed with the help of a thematic analysis where two system development models were taken up, the agile method and the waterfall model. The results of the essay show that everyone has been affected in one way or another by teleworking. It appeared that communication in requirements management was particularly affected. The project teams tried to solve the challenges through a number of different methods, but the solutions resulted in the requirements management not being affected in terms of results or affecting the outcome of the system development project. However, the requirements management took longer, and the project teams had to work harder to achieve the same results as if it had happened face to face. The results of the study describe that communication in a virtual environment is only a substitute for meeting face to face.

La presente tesis posee un enfoque cuantitativo no experimental de diseño correlacional cuyo objetivo general es determinar si la metodología ágil Scrum se relaciona con la satisfacción del cliente de aplicativos móviles de las principales entidades bancarias declaradas transformadoras digitales en la sección de banca minorista en Lima Metropolitana en el 2019. La metodología ágil Scrum y la satisfacción del cliente son temas de gran impacto, los cuales se desarrollan de manera constante en diversas industrias en el mundo, encontrando zonas inexploradas en cuanto al conocimiento de la relación de ambas variables. En consecuencia, podrían mejorar las metodologías de trabajo en el mundo laboral, así como la experiencia del cliente o usuario final. La investigación se realizó sobre una población de 2,371,542 personas, representados por una muestra de 383 personas, de quienes se recolectó información a través de una encuesta conformada por dos apartados, el primero se enfoca en la variable metodología ágil Scrum, estuvo compuesto por 17 preguntas y se adaptó del artículo “The Impact of Scrum on Costumer Satisfaction An Empirical Study; respecto al segundo apartado, se focalizó en la variable satisfacción del cliente, constituido por 27 preguntas y adaptadas, principalmente, de la herramienta de medición SERVQUAL. De esta manera, ambos apartados de la encuesta fueron llevados al contexto del rubro financiero y validados por jueces expertos, obteniéndose, finalmente un total de 44 preguntas de tipo Likert. Para la relación entre variables se utilizó la aplicación de la estadística no paramétrica, haciendo uso del estadístico Chi-cuadrado y la prueba estadística Rho de Spearman. Los resultados presentan r = 0,68 comprobándose que existe una relación directamente proporcional entre las variables. Asimismo, a un nivel de significancia α=0,05 se obtuvo un p = 0,000 (< 0,05) menor al nivel de significancia, demostrando la existencia significativa de una relación media entre la metodología ágil Scrum y la satisfacción del cliente, sugiriendo a los actores claves de los escenarios afines tomar en cuenta que las modificaciones de aplicaciones móviles desarrolladas con la metodología ágil Scrum impacta en la experiencia del usuario. / This thesis has a non-experimental quantitative approach of correlational design whose general objective is to determine if the Scrum methodology is related to customer satisfaction of mobile applications of the main banking entities declared digital transformers in the retail banking section in Metropolitan Lima in 2019. The Scrum methodology and customer satisfaction are high-impact topics, which are constantly being developed in various industries around the world finding unexplored areas regarding the knowledge of the relationship of both variables. Consequently, they could improve work methodologies in the world of work, as well as the client or end user experience. The research was conducted on a population of 2,371,542 people, represented by a sample of 383 people; this information was collected through a survey composed of two sections, the first one focuses on the Scrum methodology variable, it was composed of 17 questions and was adapted from the article “The Impact of Scrum on Costumer Satisfaction An Empirical Study”; regarding the second section, it focused on the client satisfaction variable, composed of 27 questions and adapted, mainly, from SERVQUAL. In this way, both sections of the survey were taken to the context of the financial sector and validated by expert judges, finally obtaining a total of 44 Likert-type questions. The application of non-parametric statistics was used for the relationship between variables making use of the Chi-square statistic and the Spearman's Rho statistical test. The results show r = 0.68 verifying that there is a directly proportional relationship between the variables. Also, the results show that for a level of significance α = 0.05, it is p = 0.000 (<0.05) lower than the significance level was obtained demonstrating the significant existence of an average relationship between the Scrum methodology and customer satisfaction, suggesting to the key actors of the related scenarios take into account that the modifications of mobile applications developed with the Scrum methodology impact the user experience. / Tesis

Denna rapport behandlar det arbete som under våren 2020 utfördes av en grupp på sju civilingenjörsstudenter i data- och mjukvaruteknik vid Linköpings universitet som en del av kursen TDDD96 – Kandidatprojekt i programvaruutveckling. Projektet utfärdades på efterfrågan av företaget Airpelago, och gick ut på att utveckla en stabil grund för ett molnbaserat videoströmningssystem. Denna rapport beskriver den färdiga produkten, förklarar de beslut som togs, beskriver vilka problem som uppstått och hur dessa lösts, samt diskuterar det slutgiltiga arbetet. Rapporten innehåller även sju individuella bidragskrivna av gruppens enskilda medlemmar / <p>Presentationen genomfördes på distans</p>

Rapporten belyser arbetet kring det kandidatarbete som utfördes av åtta studenter i kursen TDDD96 - Kandidatprojekt i programvaruutveckling på Linköpings universitet undervårterminen 2020. Uppgiften som utfördes var att utveckla en webbapplikation för att filtrera övervakningsvideor för Polismyndigheten. Resultatet av arbetet blev ett fungerandekoncepttest som släppts som öppen källkod under namnet Mycroft samt en användarmanual. Rapporten innehåller en bakgrund till projektet och projektgruppen, en teoridel sombeskriver de verktyg och utvecklingsmetoder som projektgruppen har använt samt en delsom redovisar gruppens utvecklingsmetod och andra administrativa metoder. Resultatetbeskriver den slutgiltiga produkten samt resultatet från gruppens arbetsprocesser. Rapporten avslutas med en diskussion gällande resultatet, metoden och framtiden för projektgruppen och produkten. Rapporten innehåller även åtta individuella fördjupningsarbetenfrån vardera gruppmedlem.