Today, agile development is broadly used within both small and large organizations worldwide. Transitioning to agile development in a large organization is a complex task that requires support from everyone in it. The Scaled Agile Framework (SAFe) is a framework meant to help integrate agile development within all parts of an organization. Regularly conducted assessments of how well an organization has integrated agile development can be a way to make sure the transition is happening as intended. These kinds of assessments are often called agile maturity assessments. SAFe includes such an assessment, but since the assessment is based on thoughts and reflections from members in the organization, doing the assessment can be difficult and may give unreliable results. This study aims to explore one way to support the assessment with objective data by generating visualizations of issue tracking data extracted from Jira and Github. The Inductive visual Miner, a plugin in the process mining software ProM, was used for the visualizations. A case study was conducted at the IT department of the Swedish Tax Agency. A slightly modified version of the methodology called the PM2 methodology was used to conduct the study. The modified methodology included six stages; a planning stage, a data extraction stage, a data processing stage, a mining and analysis stage, an evaluation stage and lastly, an improvement stage where an attempt was made to improve the visualizations based on the analysis and the evaluation. The planning stage was used to gain information about the work processes in the organization and what kind of data that may exist in the chosen data sources. A set of goal questions connected to the agile maturity assessment were generated, which the visualizations were expected to provide answers to. Data from six teams were then used to generate the visualizations. At first, the visualizations were explored and later evaluated in collaboration with the SCRUM-master in each team. The results in this study show that visualizations generated from issue tracking data using the Inductive visual Miner can be used to answer questions about time and order of events that are related to the agile maturity assessment within SAFe. However, additional analysis and reflections are needed to draw conclusions about the agile maturity from the information obtained from the visualizations. A set of requirements for the data used to generate this kind of visualizations is also proposed. The requirements were based on the results from all stages. / Agil utveckling används idag flitigt inom både små och stora organisationer över hela världen. Att gå över till agil utveckling i en stor organisation är en komplex uppgift som kräver stöd från alla inom den. Scaled Agile Framework (SAFe) är ett ramverk avsett att göra det lättare att integrera agil utveckling inom alla delar av en organisation. Regelbundet genomförda utvärderingar av en organisations användning av agil utveckling kan vara ett sätt att se till att övergången sker som planerat. Dessa utvärderingar kallas ofta agila mognadsmätningar. I SAFe ingår en sådan utvärdering, men eftersom utvärderingen baseras på tankar och reflektioner från medlemmar i organisationen kan det vara komplicerat att utföra utvärderingen och den kan ge icke pålitliga resultat. Syftet med denna studie är att utforska ett sätt att stödja den agila mognadsmätningen med objektiv data genom att generera visualiseringar av ärendehanteringsdata som extraherats från Jira och Github. En plugin kallad Inductive visual Miner i process mining-verktyget ProM används för denna visualisering. En fallstudie genomfördes på Skatteverkets IT-avdelning. En något modifierad version av metoden kallad PM2 -metoden användes för att genomföra studien. Den modifierade metoden inkluderade sex steg; ett planeringsskede, ett datautvinningsskede, ett databearbetningsskede, ett process mining- och analysskede, ett utvärderingsskede och slutligen ett förbättringsskede där ett försök till att förbättra visualiseringarna utifrån analysen och utvärderingen genomfördes. Planeringsstadiet användes för att få information om arbetsprocesserna i organisationen och vilken typ av data som kan finnas i de valda datakällorna. En uppsättning målfrågor kopplade till den agila mognadsmätningen formulerades. Detta var frågor som visualiseringarna förväntades ge svar på. Data från sex team användes sedan för att generera visualiseringarna. Visualiseringarna undersöktes först noggrant och utvärderades sedan i samarbete med SCRUM-mastern i varje team. Resultaten i denna studie visar att visualiseringar genererade från ärendehanteringdata med hjälp av verktyget Inductive visual Miner kan användas för att svara på frågor om tid och ordning av händelser i arbetsprocessen, som är relaterade till den agila mognadsmätningen inom SAFe. Ytterligare analyser och reflektioner behövs dock för att dra slutsatser om den agila mognaden utifrån informationen som erhålls från visualiseringarna. En uppsättning krav för den data som ska användas för att generera denna typ av visualiseringar föreslås också. Dessa krav är baserade på resultaten från alla steg i metoden.

Today’s enterprises are operating in a highly complex environment with rapid disruptions from different areas such as technology, regulations or market, all of them capable of bringing the entire industry upside down. And many large organizations are adopting agile software development methods as part of their continuous push towards higher flexibility and shorter lead times. Agility, however, introduces challenges and problems for the engineering of enterprises, yet few reports on organizational alignment in this regard are available in the literature. This problem of alignment between business/operations and IT has been around for as long as computers have been introduced to the work offices and is still today an important issue for enterprises of any kind. This thesis, therefore, tries to investigate the lack of insight or fragmented knowledge regarding organizational design or architecture of modern enterprises in both academia and industry. The purpose of this thesis is to explicate the challenges and recommendations found in research papers, industrial whitepapers and interviews in order to propose guidelines for achieving better alignment. The goal of this thesis is to provide an inventory of available researches in the area of Business and IT Alignment (BITA) and organizational science in order to help suggest a basis for future research. For this purpose, a Design Science Research (DSR) strategy has been followed in combination with a literature review accompanied by two rounds of interviews as a means for data collection and evaluation. The artefacts resulting from this thesis take the form of fifteen guidelines extracted using coding analysis from the literature review and a first round of interviews at a major Swedish vehicle manufacturing enterprise. The guidelines were subsequently evaluated in a second round of interview with an industry expert reviewing the correctness and usefulness of the guidelines. The results of the evaluation proved that guidelines were useful for both the academia and industry experts. Hence, enabling the author to claim that a tentative proposition has been achieved. / Dagens företag arbetar i en mycket komplex miljö med snabba störningar från olika områden som teknik, regler eller marknader, som alla kan vända hela branschen upp och ner. Och många stora organisationer använder sig av agila programvaruutvecklingsmetoder som en del av deras kontinuerliga tryck mot högre flexibilitet och kortare ledtider. Agilitet eller snabbfothet medför emellertid utmaningar och problem för konstruktion av organisationer, men få rapporter om organisatorisk anpassning i detta avseende finns tillgängliga i litteraturen. Detta problem med anpassningen mellan verksamhet och IT har funnits så länge datorer har introducerats på arbetsplatserna och är än idag en viktig fråga för organisationer av alla slags. Denna avhandling försöker därför undersöka bristen på insikt eller fragmenterad kunskap om organisationsdesign eller arkitektur hos moderna företag i både den akademiska världen och såväl industrin. Syftet med denna avhandling är att beskriva de utmaningarna och rekommendationerna som finns i forskningspapper, industriella vitböcker och intervjuer för att föreslå riktlinjer för bättre anpassning. Målet med denna avhandling är att tillhandahålla en inventering av tillgängliga forskningar inom området Business and IT Alignment (BITA) och organisationsvetenskap för att kunna föreslå en grund för framtida forskning. För detta ändamål har en Design Science Research (DSR) strategi följts i kombination med en litteraturstudie åtföljd av två intervjuomgångar som ett medel för datainsamling och utvärdering. Artefakterna som härrör från denna avhandling har formen av femton riktlinjer extraherade med hjälp av kodningsanalys från litteraturstudien och en första intervjuomgång hos ett stort svenskt fordonstillverkningsföretag. Riktlinjerna utvärderades därefter i en andra intervjuomgång med en branschexpert som granskade riktigheten och användbarheten av riktlinjerna. Resultaten av utvärderingen visade att riktlinjerna var användbara för både akademin och branschexperter. Därför gör det möjligt för författaren att hävda att en preliminär proposition har uppnåtts.

The number of mobile applications has increased tremendously over the last decade, thereby also having increased the importance of mobile application testing. Testing is a very crucial process in the development of a mobile application to ensure reliability and proper functionality. In an Agile/DevOps environment, test automation is an integral part in order to support the continuous integration and continuous delivery/deployment principle. There is a plethora of mobile application testing automation frameworks available in the market today. Android testing frameworks were chosen for this study because of the prevalence of Android applications in the market today. The focus of this study is the comparison of the most popular mobile application testing automation frameworks in terms of performance and capabilities in an Agile/DevOps environment. In order to achieve this, firstly, the three most popular mobile application testing automation frameworks to be used for the study were identified. Secondly, the Key Performance Indicators and capabilities to be used for comparison of the frameworks were identified. Then, test cases in a complex mobile application were designed for analysing the frameworks based on the criteria gathered. Finally, the test cases were integrated in a Continuous Integration/ Continuous Delivery pipeline to gather results and perform a more detailed comparison in an Agile/DevOps environment. From this study, Espresso turned out to be the best framework in terms of KPI analysed beating the other frameworks in all the KPIs, while Robotium was second best followed by Appium. But on the other hand, Appium was the best framework in terms of capabilities by having ability to execute the maximum number of capabilities analysed followed by Robotium while Espresso was the worst framework in this criteria. / Antalet mobilapplikationer har ökat enormt under det senaste decenniet och därmed har även vikten av mobilapplikationstest ökat. Testning är en mycket viktig process i utvecklingen av en mobilapplikation för att säkerställa tillförlitlighet och korrekt funktionalitet. I en Agile/DevOps miljö är testautomation en viktig del för att stödja principen av kontinuerlig integration och kontinuerlig leverans/driftsättning. Det finns en mängd ramverk för automatiserad testning av mobilapplikationer på marknaden idag. Testramverk för Android valdes för denna studie på grund av utbredningen av Android-applikationer på marknaden idag. Fokus för denna studie är jämförelsen av de mest populära automatiserade testramverk för mobilapplikationer med avseende på prestanda och lämplighet i en Agile/DevOps miljö. För att uppnå detta, identifierades först de tre mest populära automatiserade testramverk för mobilapplikationer som skulle användas för studien. Sedan identifierades de viktigaste resultatindikatorerna och kapaciteterna som skulle användas för att jämföra ramverken. Därefter designades testfall i en komplex mobilapplikation för att analysera ramverken baserat på de bestämda kriterierna. Slutligen integrerades testfallen i en pipeline för kontinuerlig integration /kontinuerlig leverans för att samla resultat och utföra en mer detaljerad jämförelse i en Agile/DevOps miljö. Från denna studie visade sig Espresso vara det bästa ramverket när det gäller KPI-analys, som slog de andra ramarna i alla KPI: er, medan Robotium var näst bäst följt av Appium. Men å andra sidan var Appium det bästa ramverket med avseende på kapacitet. Den hade förmågan att utföra det maximala antalet kapacitet som analyserades, följt av Robotium medan Espresso var det sämsta ramverket i dessa kriterier.

At present, the area of agile management methods is a relatively unexplored area. The purpose of this study has been to investigate how well suited agile methods are for use in IT-maintenance. This has been done by collecting material on the subject, which acted as a base for a case study. In the study, the collected material from the investigated company, external companies and observations performed at the investigated company has been analyzed against existing theory in the field. Furthermore, conclusions have been drawn from information gathered during the course of the study. Based on this survey, it can be noted that in the activities that were investigated, an implemented agile method can add value to the maintenance operation. These added values present themselves in the form of a better and clearer structure, better communication and more effective working methods. One of the biggest challenges of agile agility in management has proved to be cross-functionality in the team. In this case as well as in other theoretical cases, the lack of cross functionality has been something identified. The theoretical cases show that the introduction of an agile method helps maintenance teams to become cross-functional. In the business investigated in this study, there were only indications stating that the business had started a transition to a cross-functional team. The fact that no definitive link between agile methods and transition to cross-functionality was identified in this case is considered to be due to the fact that the agile work was at an earlier stage. In conclusion, this study shows that agile methods are well-suited for use in maintenance, but some modifications to the agile approach need to be implemented. / I dagsläget är området agila metoder inom systemförvaltning ett relativt outforskat område. Syftet med denna studie har varit att undersöka hur väl lämpade agila metoder är för en förvaltande verksamhet. Detta har gjorts genom att bakgrundsmaterial i ämnet samlats in, för att bilda en teoretisk grund för en fallstudie. I studien har det insamlade materialet från det undersökta företaget, externa företag samt egna observationer som utförts på fallföretaget analyserats gentemot existerande teori inom området, varefter egna slutsatser dragits. Utifrån studien kan det konstateras att i den verksamhet som undersökts har en implementerad agil metod tillfört värde till verksamheten. Detta i form av en bättre och tydligare struktur, bättre kommunikation och ett effektivare arbetssätt. En av de största utmaningarna med att arbeta agilt inom systemförvaltning har visat sig vara tvärfunktionalitet i teamet. I detta fall såväl som i andra teoretiska fall har avsaknaden av tvärfunktionalitet varit något som identifierats. De teoretiska fallen påvisar att införandet av en agil metod har hjälpt förvaltningsteamen att bli tvärfunktionella. I verksamheten som undersöktes uppmärksammades enbart indikationer på att verksamheten påbörjat en övergång till ett tvärfunktionellt team. Att ingen definitiv koppling mellan agila metoder och övergång till tvärfunktionalitet identifierades i detta fall anses bero på att det agila arbetet befann sig i ett tidigare skede. Avslutningsvis styrker studien att agila metoder är väl lämpade för användning inom systemförvaltning, men vissa modifikationer i det agila arbetssättet behöver genomföras.

Context. Software Project management focuses on planning and executing the activities for developing software. Agile Software Project Management helps to plan shorter iterations and frequent changes to customer requirement. Developing the process flow metrics helps to monitor the process and to tune the process for the given context. Objectives. The main objectives in the thesis are to identify process flow metrics and frameworks that are suitable for measuring the process flow in Agile projects especially projects with significant dependence on hardware components. Apart from identified metrics from the literature, we identify the impact, challenges, and advantages of using agile models with the help of productivity and process flow metrics and implement them on a test phase project and compare the productivity of agile model with waterfall model. Methods. The thesis presents a two-step study. The first step was to perform a Systematic Literature Review (SLR) and collect the metrics from the literature study that can be used for the comparison of the productivity of both the processes. The Second step was to conduct a case study at Volvo Cars to get us a better understanding the impact of the agile and how the process flow metrics can be used in real time for measuring and comparison.   Results. In the first step of SLR, 363 metrics that can be used by software teams have been identified of which 10 were suitable for the comparison of our current case study required by the second step of our thesis. In the second step, in the first iteration after the transition, an increase in productivity of 6.25% is achieved by the team following the agile process over the team following the traditional process. Several advantages and challenges faced during the transition have been identified which might have affected the achieved productivity. Conclusions. We conclude from the results achieved that metrics can be used as a tool to enhance the benefits of the Agile process. Process Flow metrics can be of good use to compare the difference of productivity between different processes and make improvements to the current processes. Use of process flow metrics increases the insight of all the team members on the progress of the project and guides them to enhance team performance and stay on track with the project schedule.

Over the last few years, DevOps has gained much attention in the IT development field. It is a new way of thinking of how developers and operators work, which aim to integrate the development, testing, and operation work efficiently. DevOps breaks down communication silos, improve collaboration and productivity by automating infrastructure deployment, workflows, continuously improving the integration and delivery process, and measuring the application performance indicators. Automation is crucial in DevOps, and a key aspect of automation is “Infrastructure as code (IaC)”. IaC allows companies to manage and maintain their infrastructure resources such as virtual machines, load balancers, firewalls, and network devices programmatically in codes instead of manual processes and procedures. As a result, companies will be able to provision and deploy these infrastructure resources consistently, increase the rate of software delivery and improve the time to market, which in turns lead to a substantial competitive advantage. Previous research call for an examination of the gained opportunities and the challenges that can be faced in implementing IaC. Understanding these challenges and opportunities and their implications allow the companies to know why IaC can be interesting for them? And what and how changes should be done to adopt IaC. This paper presents a qualitative study that aims to illustrate the opportunities and challenges in implementing Infrastructure as a code. This paper will also present how infrastructure used to be managed in physical datacenter and cloud systems, and how agile, DevOps and IaC affect the infrastructure management. Our findings show considerable benefits in adopting IaC, and some challenges might be encountered when implementing IaC. Furthermore, the study acknowledges the role of agile, cloud systems, and DevOps in facilitating the implementation of Infrastructure as a code. Keywords: DevOps, Infrastructure as a code, Automation, Infrastructure resources, agile, cloud systems / <p></p><p></p><p></p>

Frågeställningar: Hur påverkas deltagarnas kreativitet när agila metoder används i praktiken? Hur påverkar agila arbetsmetoder innovationsförmågan? Syfte: Syftet med denna studie är att undersöka hur ett litet IT-företag arbetar med att främja kreativitet genom att arbeta enligt det agila arbetssättet, för att på så sätt kunna påverka innovationsförmågan. Metod: Denna studie baseras på en fallstudie. Företaget är ett litet IT-konsultföretag som arbetar med systemutveckling. Företaget har 15 anställda och arbetar enligt det agila arbetssättet och de har två Scrum-team. Detta arbete har sin grund i den kvalitativa metoden med influenser av ett deduktivt förhållningssätt, då studien huvudsakligen baseras på semi-strukturerade intervjuer och observationer. Slutsatser: Slutsatserna som kan dras är att det agila arbetssättet påverkar kreativiteten genom att öka deltagarnas motivation. Det agila arbetssättet påverkar kreativiteten hos de anställda, då det är fritt att plocka de uppgifter som man själv vill i varje sprint bidrar det till att det kan öka både motivationen och nyfikenheten. En annan slutsats är att det agila arbetssättet påverkar deltagarnas kreativitet då det ger de anställda en mer frihet att planera sitt arbete och ger de möjligheten att själva lösa sin arbetsuppgift på sitt sätt, genom att exempelvis testa nya tekniker. Det agila arbetssättet påverkar deltagarnas kreativitet på så sätt att det kan minska stressen utifrån för själva arbetsgruppen. Detta på grund av att det är produktägaren som har den främsta kontakten med slutkunden.Det agila arbetssättet påverkar innovationsförmågan genom att i och med att det ständigt kommer in nya arbetsuppgifter som arbetsgruppen ska lösa och då arbetsuppgifterna skiljer sig mycket åt, bidrar det till en ökad dynamik och utmaning. En intressant slutsats var att produktägarna skapade en ometveten utmaning kopplat till de anställdas arbetsuppgifter då de anställda ansåg att kravspecifikationerna som de fick var svåra att förstå. Sista slutsatsen som kan dras är att det agila arbetssättet skapade en frihet hos de anställda att själva kunna prioritera bland sina arbetsuppgifter och metoden som de ska lösas på. / Research questions: How are participants' creativity affected when agile methods are used in practice? How do agile methods affect the ability to innovate? Purpose: The purpose of this study is to investigate how a small IT company works to increase creativity by working according to the agile approach, in order to be able to affect the capacity for innovation. Method: This study is based on a case study. The company is a small IT consulting company that works with system development. The company has 15 employees and works according to the agile approach and they have two Scrum teams. This work is based on the qualitative method with influences of a deductive approach, since the study is mainly based on semi-structured interviews and observations. Conclusions: The conclusions are that the agile methods affect creativity by increasing the participants' motivation. The agile way of working affects the creativity of the employees, as it is free to pick the tasks that you want in each sprint, it contributes to increase both motivation and curiosity. Another conclusion is that the agile methods affects the participants' creativity as it gives the employees more freedom to plan their work and gives them the opportunity to solve their task in their own way, for example by testing new technologies. The agile methods affect the participants' creativity in such a way that it can reduce the stress from outside the workgroup itself. This is because it is the product owner who has the main contact with the end customer.The agile way of working affects the ability to innovate because it is constantly entering new tasks that the working group has to solve, and the tasks are very different to each other, it contributes to increased dynamism and challenge. An interesting conclusion was that the product owners created an unconscious challenge linked to the employees' tasks, as the employees felt that the requirement specifications that they received were difficult to understand. The final conclusion is that the agile methods created freedom for the employees to be able to prioritize themselves among their tasks and choose how to solve the tasks.

A competência em gerenciamento de projetos (GP) é reconhecida como um fator crítico para o desenvolvimento de novos produtos e possuir sistemas de informação adequados é um quesito fundamental para apoiá-la. Há uma disponibilidade de ferramentas e em contrapartida, um número significativo de críticas à sua utilização, especialmente no caso de produtos inovadores e complexos. O trabalho tem por objetivo identificar os desafios a serem enfrentados para o desenvolvimento de ferramentas de software para apoiar práticas com esse enfoque. Empregou-se a revisão bibliográfica combinada com o estudo de caso múltiplo. Compilou-se os desafios apontados na literatura, revisando os temas: colaboração, gerenciamento ágil de projetos e softwares para gerenciamento de projetos. O resultado, organizado segundo as áreas de processo do PMI, foi comparado com problemas reais, coletados por meio do método de estudo de caso. O setor de bens de capital foi escolhido para garantir a complexidade dos projetos (número de peças do produto e presença de colaboração). A unidade de análise é o sistema de informação para gerenciamento dos projetos (SIGP) de cada empresa. Descreveu-se o SIGP e o papel dos softwares de GP, de forma a identificar os desafios e classificá-los segundo áreas de conhecimento de GP. Os instrumentos utilizados foram roteiros de entrevistas, observações e análise de documentos. Os desafios foram confrontados com o esforço da comunidade científica, identificado por meio de uma revisão bibliográfica, classificada segundo as mesmas áreas de GP. Ao final, comparam-se os desafios das empresas com a teoria e identifica-se uma lista de requisitos para o desenvolvimento de softwares na área. A análise indica também que as ferramentas de GP são utilizadas de forma restrita na indústria de bens de capital e que há discordâncias entre o esforço dos pesquisadores e necessidades dos profissionais da área. Por fim, esta pesquisa identifica como temas relevantes: a integração de dados, o desenvolvimento de funcionalidades de aquisição e de gerenciamento de interfaces, riscos, recursos e multiprojetos. / The project management competence has been recognized as a critical factor to develop new products. Information systems are a fundamental factor to support it. There is an exceptional amount of tools. In opposition there are a significant number of critics about its utilization, in special in projects like innovative and collaborative product projects. The critics pointed needs for new methods and practices to support the agile project management. This research aims to identify challenges of developing project management tool to support this approach. The method used combines a bibliographical review with a multiple case study. The literature challenges were compiled, reviewing the themes: collaboration, agile project management and project management software. The result, organized by PMI process areas, was compared with case study real problems. The capital goods (BK) sector was chosen to ensure the projects complexity (by the product and collaboration presence). The analysis unit is the project management information system (PMIS) of each company. The PMIS and the role of the project management software were described to identify the challenges and classify them according to project management areas. The data collection instruments are plan interview, non-participant observations and document analysis. The challenges were faced with the scientific community effort, identified through a literature review and classified according to the same areas of PM. Following, the challenges of companies was compared with the literature and a requirement list is identified to develop PM software. The analysis indicates that the PM tools used in the BK industry are restricted. There is a mismatch between the researcher efforts and necessities of professionals in the area. Finally, this research identifies as relevant themes: data integration, development of acquisition features, interfaces, risks, resources and multi-projects management.

Para alunos de cursos superiores de Sistemas de Informação e afins, aprender a programar computadores é fundamental. No entanto, ensinar programação por meio de métodos tradicionais tem se tornado cada vez mais desafiante devido a fatores recentes, tais como transformações na maneira de aprender das novas gerações e o surgimento de novas máquinas computacionais. Neste contexto, a aprendizagem baseada em projeto possui potencial para beneficiar a educação em programação. Há especial relevância para a abordagem Ágil de projetos, por possuir destaque no mercado de trabalho e origem atrelada ao próprio desenvolvimento de softwares. Por outro lado, foram encontrados poucos estudos de relevância internacional relatando a utilização da aprendizagem baseada em projeto ágil (APjBL) no contexto do ensino superior brasileiro. O objetivo geral desta pesquisa é analisar os benefícios de um método APjBL para os alunos de programação no ensino superior brasileiro quando comparado ao método tradicional de ensino, principalmente com relação a quatro benefícios de interesse desta pesquisa: o rendimento escolar, a motivação para aprender, a comunicação verbal e a exploração vocacional dos alunos. Nesta pesquisa empírica e de natureza aplicada, foi feita a opção pelo quase-experimento em um curso superior tecnológico de Análise e Desenvolvimento de Sistemas durante o primeiro semestre de 2018. A análise foi quali-quantitativa e os critérios de comparação foram os quatro benefícios mencionados. Como intervenção educacional APjBL, foi escolhido o método Agile Model for Projects in Computing Education (AMoPCE) e adaptado ao contexto. Participaram desta pesquisa 151 alunos e cinco professores, divididos em grupos de experimento e controle. Ao final do semestre, os alunos responderam a um questionário eletrônico sobre três benefícios: motivação para aprender, comunicação verbal e exploração vocacional. Foram coletadas as notas e as frequências dos alunos, além das percepções dos professores por meio de entrevistas individuais semiestruturadas. Dados históricos das disciplinas foram coletados para ajudar a explicar os fenômenos. Conclui-se que, no contexto geral da pesquisa, para a disciplina de conteúdo predominantemente procedural (prático), AMoPCE beneficiou a motivação extrínseca, a frequência escolar e a escuta ativa na comunicação. Para a disciplina altamente procedural, AMoPCE apresentou mais dois benefícios: motivação para aprender intrínseca e exploração vocacional intrínseca. Em suma, foi verificada uma hipótese de pesquisa, AMoPCE beneficia a motivação para aprender, na disciplina altamente procedural / To learn computer programming is an essential topic to undergraduate students at Information System and related higher education courses. However, teaching programming using traditional methods have become much more challenging due to recent reasons, like changes in the manner that the new generation is now prone to learn, and the arising of new programmable devices. The Project-Based Learn may offer potential benefits to the computer programming education, especially the Agile approach, given its origin at the software development process. And yet there were found a few relevant international studies regarding the Agile Project-Based Learn (APjBL) to cope with the computer programming education at Brazilian Information System higher education. The research leading objective was to analyze the main benefits of the APjBL teaching method when compared to the traditional teaching method, mainly the following four students benefits: academic performance, motivation to learn, verbal communication and vocational inquiry aspects. As the comparison criterion, we selected these four benefits through specific instruments adapted to this research. We also chose the Agile Model for Projects in Computing Education (AMoPCE) as the APjBL teaching method, which was originated from previous researches and that we adapted to this context. This research adopted an experimental approach via a quasi-experiment at the System Development and Analysis higher education course, during the first semester of 2018. A total of 151 students and five teachers participated in this research. By the end of the experiment, the students replied to an electronic questionnaire regarding three benefits: motivation to learn, verbal communication and vocational inquiry aspects. Five professors participated in an individual interview. Students grades and frequency and their historical data were also collected. As results, we found that for procedural (practical) content, AMoPCE presented at least the following benefits: extrinsic motivation, class frequency, and verbal communication via active listening. Even further, when the class is highly procedural, AMoPCE presents two benefits more: intrinsic motivation to learn and intrinsic vocational inquiry. In summary, the hypothesis that AMoPCE benefits the motivation was confirmed at highly procedural classes

Linhas de produtos de software (LPS) são coleções de sistemas que compartilham características comuns, desenvolvidas de forma sistemática a partir de um conjunto comum de ativos centrais. Dentre as técnicas propostas por vários autores para o desenvolvimento de LPS, dois padrões podem ser observados: o processo de desenvolvimento geralmente é sequencial e o foco do projeto (design) costuma estar em interesses técnicos, como alocação de componentes e separação em subsistemas, e não em um modelo de domínio. Embora essas práticas sejam reportadas como bem-sucedidas, um outro paradigma de desenvolvimento, baseado em métodos ágeis e em um conjunto de princípios de projeto conhecido como domain-driven design, é apresentado neste trabalho e pode produzir resultados mais satisfatórios, comparados aos métodos tradicionais. Essa hipótese é sustentada por comparações entre padrões de modelagem e por um estudo de caso feito neste trabalho / Software product lines (SPL) are collections of systems that have common features. Those systems are systematically developed from a common set of core assets. Two patterns outstand among the various techniques proposed by several authors for developing software product lines: the development process is generally sequential and the primary design concerns deal with technical issues, such as component allocation and system partitioning (into subsystems). The importance of a domain model is often neglected. Although such practices have been reported as successful, this work proposes another paradigm, which can yield more satisfactory results. This paradigm is based on agile methods and a set of design principles known as domain-driven design. This hypothesis is supported by comparing different modeling patterns and by developing a case study