When adopting a microservice architecture, maintenance is needed to keep the system working. Maintenance can sometimes involve more than one team that needs to collaborate in order to fix a maintenance issue. This procedure requires coordination and correspondence between teams which can have a negative impact on the autonomy of the teams. The microservice architecture does not only introduce new benefits but also new challenges. This study creates a strategy guideline that organisations can use to address these challenges. The study highlights challenges with collaboration in maintenance and gives suggestions on strategies to use to counter the challenges. This guideline can help organisations new to the microservice architecture and help organisations to make future maintenance decisions in a microservice architecture with multiple teams. The guideline is developed using the Convergent Parallel Design and by interviewing product owners, architects, and developers in three organisations working with microservices. A survey was sent out to people working with microservices in different industries to validate the findings from the interviews. The interviews and the survey is analysed using the five steps described in the book “A Step-By-Step Guide To Qualitative Data Analysis” by O'Connor and Gibson (2003). This paper is focused on how agile teams collaborate with maintenance across microservices and does not cover teamwork within the agile team. This paper does not cover any technical aspects of microservices, such as application programming interface endpoints between services, but rather how teams work with them.

During the past decades, a substantial amount of research efforts have been made regarding making the web and digital content more accessible. However, research states that the current accessibility state globally is yet not sufficient, resulting in excluding a large group of people due to disabilities. The purpose of this study is to evaluate the current accessibility state of the prototype version of Ubisoft Connect’s chat application and how to make accessibility a natural part of a team's existing agile processes. This is performed by gathering knowledge about a team's current working processes by conducting two qualitative interviews, along with a nine-week observation, allowing us to partake in their processes when implementing changes. To evaluate the chat's current accessibility state, two of the most used usability evaluation techniques are used: heuristic evaluation and user testing. The heuristic evaluation is based on the internationally recognized standard: Web Content Accessibility Guidelines 2.1. The findings from the heuristic evaluation are implemented by the Ubisoft Connect team in the chat prototype and are later tested by 4 testers with disabilities. The result of this case study shows that heuristic evaluation and user testing should be used to complement each other since one method alone cannot create a valid accessibility state. Furthermore, it shows that agile management is the preferred method when making these changes.

With the increasing demand for high performance communication networks and the proliferation of mobile devices, significant advances in antenna design are essential. In recent years the rising demands of the mobile wireless communication industry have forced antennas to have increased performance while being limited to an ever decreasing footprint. Such design constraints have forced antenna designers to consider frequency agile antennas so that their behavior can adapt with changing system requirements or environmental conditions. Frequency agile antennas used for mobile handset applications must also be inexpensive, robust, and make use of electronic switching with reasonable DC power consumption. Previous works have addressed a number of these requirements but relatively little work has been performed on frequency agile dielectric resonator antennas (DRAs). The objective of this thesis is to investigate the use of DRAs for frequency reconfigurability. DRAs are an attractive option due to their compactness, very low losses leading to high radiation efficiencies (better than 95%) and fairly wide bandwidths compared to alternatives. DRA’s are also well suited for mobile communications since they can be placed on a ground plane and are by nature low gain antennas whose radiation patterns typically resemble those of short electric or magnetic dipoles. One way to electronically reconfigure a DRA, in the sense of altering the frequency band over which the input reflection coefficient of the antenna is below some threshold, is to partially load one face of the DRA with a conducting surface. By altering the way in which this surface connects to the groundplane on which the DRA is mounted, the DRA can be reconfigured due to changes in its mode structure. This connection was first made using several conducting tabs which resulted in a tuning range of 69% while having poor cross polarization performance. In order to address the poor cross polarization performance a second conducting surface was placed on the opposing DRA wall. This technique significantly reduced the cross polarization levels while obtaining a tuning range of 83%. The dual-wall conductively loaded DRA was then extended to include a full electronic implementation using PIN diodes and varactor diodes in order to achieve discrete and continuous tuning respectively. The two techniques both achieved discrete tuning ranges of 95% while the varactor implementation also had a continuous tuning range of 59% while both maintaining an acceptable cross polarization level.

Web analytics are used to track and examine user behavior on websites and web applications. In order to take data driven decisions companies and organizations working with the web look to web analytics to understand their users. A piece of Javascript code that collect user behavior and information is often referred to as a tag, which can be managed through a tag management system. Tag management systems can provide structure to how a website’s users’ behaviors are being measured. This study examines how a tag management system can enable web analytics of user data to be incorporated in an agile web development process at the Swedish company Dailybitsof. With a literature study, case study and interviews with professionals on the subject, a set of recommendations to enable web analytics is presented. This study suggests that a tag management system can enable web analytics to be incorporated into an agile web development process if it is implemented in combination with changes to the agile process. / Webbanalys används för att spåra och undersöka användarbeteende på hemsidor och webbapplikationer. För att ta datadrivna beslut, använder sig företag och organisationer av webbanalys för att förstå sina användare. Några rader Javascript-kod kan användas för att samla upp användarbeteende och kallas ibland för ett tag. Dessa tags kan behandlas i ett så kallad tag management-system. Tag management-system kan ge struktur över hur användarbeteendet på en hemsida spåras och analyseras. Den har uppsatsen undersöker hur ett tag management-system kan möjliggöra att data från webbanalys blir använt i en agil webbutvecklingsprocess hos det svenska företaget Dailybitsof. Med en litteraturstudie, fallstudie och intervjuer med professionella inom ämnet presenteras rekommendationer för att att möjliggöra webbanalys. Uppsatsen föreslår att ett tag management-system kan möjliggöra användandet av webbanalys i en agil webbutvecklingsprocess om det implementeras i kombination med ändringar av den agila processen.

Den här studien undersöker hinder och utmaningar som uppstår inom spelutveckling. Mer precist undersöks arbetsmetoden Scrum, som är ett agilt ramverk. Metoden som användes i studien är en kvalitativ undersökning. Semistrukturerade intervjuer genomfördes med personer som har erfarenhet inom Scrum för spelutveckling, för att identifiera deras hinder och utmaningar, men även för att ta fram lösningsförslag. Följaktligen är frågeställningen, ”Vilka hinder och utmaningar identifieras då man använder Scrum inom spelutveckling, och hur kan dessa lösas?”. Lösningsförslagen togs fram med hjälp av både intervjuobjekt och relaterad forskning. Resultatet gav att det fanns hinder och utmaningar inom fem områden. Planering av arbete, spelutvecklingens många discipliner, spelutvecklingens långa projekt, Pre-production fasen och problem som uppstår på grund av själva Scrum-ramverket. Planeringen av arbetet var ett hinder eftersom den bland annat innefattar estimering av arbete, klarkriterium, och vad som skall göras. Lösningsförslagen var att andra metoder skall användas med Scrum, bland annat för att ersätta problemen man har i utforskande faser eller när man har estetiska mål. Kortfattat så fungerar Scrum när det finns information om vad som skall göras och när det skall göras. Problematiken är att den informationen inte alltid är given inom spelutveckling / This study researches issues and challenges that arise within game development. More specific it examines the Scrum methodology, which is an agile framework.  A qualitative research method was conducted for this study. In order to identify impediments and challenges, but as well proposals for solutions, semi-structured interviews were conducted with participants who have experience from Scrum within game development. Therefore, the research question in this study is “Which issues and challenges can be identified within game development, and how could they be solved?”. The proposed solutions were constructed with help from both the interviewees and related research.  The results of the study located issues and challenges in five different areas. Planning work, the many different discipline present in game development, the long development time for game projects, the Pre-production phase, and the problems that arise from the Scrum framework itself. Planning the work was an impediment because it includes estimating the amount of work, definition of done and what to do. The proposed solutions were, to use other methods together with Scrum, for instance to replace the problems in explorative phases or when working with aesthetic goals. In short, Scrum works when there exists information about what to do and when to do it. The problem is that the information is not always available within game development.

Agile methods have been widely implemented in the industry while teaching these methods is a substantial part of Computer Science and Engineering program curricula. Evidencedriven data of agile practices, methods, and tools have been extracted based on empirical studies with students, however, there is an important need for more anecdotal evidence to confirm these findings. In order to fill this gap, this paper explores the perceptions and the applicability of the Scrum Framework in a student research team in an industrial context. Empirical data have been gathered through interviews with the case study participants combined with a survey. The analysis reveals that student experiences are mainly positive and that they can easily grasp the benefits of Scrum Framework. The challenges of implementing Scrum in such a setting mainly concern the balance between coach and self-organization, formulating accurate user stories when researching, finding the most suitable estimation method, as well as planning when conducting research. The empirical findings may potentially be extrapolated in student scrum teams or even in industrial settings. Finally, this research paper should encourage other researchers to investigate the adoption of Scrum in a student setting. / Agila metoder har implementerats i stor utsträckning inom branschen, medan undervisning i dessa metoder är en väsentlig del av utbildningarna för datavetenskap och teknik. Bevisdriven data om agila arbetssätt, metoder och verktyg har tagits fram från empiriska studier med studenter, men det finns ett viktigt behov av mer anekdotiska bevis för att bekräfta dessa resultat. För att fylla detta gap utforskar den här rapporten uppfattningarna och tillämpligheten av ramverket Scrum i ett studentforskningsteam i ett industriellt sammanhang. Empiriska data har samlats genom intervjuer med deltagarna i fallstudien i kombination med ett frågeformulär. Analysen visar att studentupplevelserna är främst positiva och att man lätt kan förstå fördelarna med Scrum. Utmaningarna med att implementera Scrum i en sådan miljö gäller främst balansen mellan coaching och självorganiserande, formulera exakta användarhistorier när man forskar, finner den mest lämpliga uppskattningsmetoden samt planerar forskningsrelaterat arbete. De empiriska fynden kan eventuellt extrapoleras i Scrumteam med studenter eller till och med i industriella miljöer. Slutligen bör detta forskningsarbete uppmuntra andra forskare att undersöka införandet av Scrum i ett studentkontext.

Can the Product Development Process at Tcom be improved by moving usability testing in-house? The interest in this question lies in the agile transformation Tcom initiated in early 2018. Once agile, the company’s interests are efficiency and increasing quality. One way of increasing the quality of their digital products is to improve the process behind it, where involving users in usability testing should be central in an iterative development process. A qualitatively driven mixed methods research approach facilitated the acquisition of the empirical data necessary to successfully answer the research question. The culture of Tcom’s usability testing was collected via a survey. The survey was complemented with the current testing process through four interviews and two observations of usability tests, one internal and one external. Parameters between the two tests were compared and weighted against each other. The main findings reveal that the internal process shows promising characteristics. It is, up to, 1/10 as expensive per participant, has a quicker call-to-test-time, facilitates transparency, and allows refinement of the process. With the main findings in hand, the conclusion points to the fact that usability testing should be composed and conducted by Tcom itself. The greatest challenge to such a change is how a usability perspective can be integrated into the Scrum methodology. / Kan produktutvecklingsprocessen på Tcom förbättras genom att flytta användbarhetstester internt? Intresset i denna fråga ligger i den agila transformation som företaget påbörjade tidigt 2018. Effektivitet och kvalitet är centrala förbättringspunkter med det agila arbetssättet. Ett sätt att öka kvaliteten på deras digitala produkter är att förbättra processen bakom, där involveringen av användare i användbarhetstester bör vara centralt i ett iterativt arbetsförlopp. En kvalitativt driven mixed methods research metod tillämpades för att förvärva den empiriska data som krävdes för att framgångsrikt besvara frågeställningen. Tcoms användbarhetstestkultur undersöktes via en enkät. Denna metod kompletterades med 4 intervjuer och 2 observationer av användbarhetstest, ett externt och ett internt. Parametrar från de två observationerna ställdes mot varandra. De centrala upptäckterna avslöjar att den interna processen uppvisar lovande egenskaper. Den är upp till en tiondel så kostsam per deltagare, har snabbare beställning-till-test-tid, tillåter transparens, och möjliggör förbättring av själva testprocessen. Med hänsyn till huvudfynden kan vi konkludera att användbarhetstest bör utformas och utföras av Tcom själva. Den största utmaningen till en sådan förändring ligger i hur ett sådant användbarhetsperspektiv ska implementeras i det agila ramverket Scrum.

In today’s globally competitive business environment, efficient product development processes are critical for companies to meet rapidly changing customer demands and preferences. Therefore, companies have looked beyond traditional linear product development processes leading to the development of new iterative processes. The new iterative and agile supporting processes have had strong success for software companies. However, how to leverage these new processes in modular hardware solutions remains unclear. This thesis analyzes the challenges of utilizing and leveraging Agile Development (AD) while maintaining a modular product strategy. This study aims to increase the understanding of how to achieve a successful coexistence between AD and modularization and thereby allowing to work increasingly agile in modular settings to decrease costs and lead times. To study this, a case study on a has been performed on a large Swedish manufacturer of modular vehicle systems. To accompany this, an abductive research approach with qualitative methods has been used, where the results are based on interviews and internal documents. The results together with the literature enable a discussion on how AD and modularization can coexist. The results can be summarized accordingly: • AD and modularization can coexist given that AD is a philosophy and mindset and modularization is product strategy; • the agile mindset and freedom have to be limited to the existing boundaries and principles set by the overall firm modular strategy; and • the ability to work agile in modular settings is disrupted when the agile team requires external involvement of additional individuals. The thesis concludes that the ability to effectively leverage AD in a modular setting depends on two aspects. First, the size and complexity of the project. Second, the product architectural knowledge within the agile team. / I dagens globala och konkurrenskraftiga företagsvärld blir produktutveckling en alltmera kritisk process för att kunna möta snabbt ändrande kundbehov. Således, eftersöker företag att utnyttja mer okonventionella och iterativa produktutvecklingsmetoder. Dessa nya agila metoder har påvisats väldigt effektiva för mjukvarubolag. Det är dock oklart hur dessa metoder kan nyttjas fördelaktigt för modulära hårdvarubolag. Denna studie analyserar utmaningarna i att använda och uttnyttja Agile Development (AD) samtidigt som man lyckas upprätthålla en modulär produktstrategi. Studien syftar till att öka förståelsen kring AD och modulariseringens samexistens, och därmed förklara hur man kan kombinera dessa för att minimera kostnader och ledtider. En fallstudie har gjort på ett svenskt tillverkande företag av modulära transportsystem. Med ett abduktivt förhållningssätt med kvalitativa metoder där data är från intervjuer och interna dokument. Resultaten tillsammans med teori möjliggör för en diskussion kring hur AD och modularisering kan samexistera. Resultaten kan sammanfattas enligt följande: • AD och modularisering kan samexistera för att AD ä ren filosofi medan modulariserig är en produktstrategi, • den agila friheten måste begränsas till de redan befintliga villkoren bestämda av företagets modulära strategi och • förmågan att arbeta agilt i en modulär kontext hämmas av när de agila teamen kräver involvering av externa individer. Studien drar slutsatsen att förmågan att effektivt nyttja AD i en modulär kontext beror på två aspekter. Först, storleken och komplexiteten av projektet. Sedan, kunskapen om produktarkitekturen i de agila teamen.

TypeScript (TS) has been growing in popularity since its release in October 2012. It is beingadopted by many tech companies who specialize in web development. However, migrating old JSprojects to TS can be challenging and time consuming which can prove problematic due to limitedtime at the developers’ disposal.The aim of this study is to find out what the benefits of using TS over JS are, and their relationto Software Sustainability. By developing a migration tool that helps with automating the migrationprocess we investigate if such a tool would bring benefits to Axis Communications AB; especially,their web developers who work with JS and TS.After the development of the artifact, a focus group consisting of six experienced web developersand one tester was invited to a workshop in order to evaluate it. The workshop consisted of threeparts: Five open questions, a demo presentation of the artifact, and an artifact evaluation basedon the system dimensions: goal, environment, structure, activity, and evolution, by using the fivepoints Likert scale.Results from the workshop allowed us to understand better the needs and the challenges faced byAxis developers during software maintenance. Furthermore, the results indicated that the artifactnot only helps with improvements in terms of code maintenance but also indirectly improves codegreenability which in itself lowers CO2 emissions as a result.Migrating JS to TS improves some aspects of code maintenance and maintainability, and ourartifact helps with the automation of that migration process. With JavaScript, companies have tobalance sustainability with greenability. Fortunately, by adding green maintenance practices andusing TypeScript it is easier to keep that stability.

There has been an increasing awareness of how organisations that have adopted new ways of working have been able to improve their productivity. The introduction of Agile in the beginning of 2000s allowed both small and large organisations to implement new methods for transforming all levels of the organisations, involving aspects such as leadership, tools, and processes. Moving towards agile practices in many ways pushed companies towards a revolution in the sense of promoting new processes and methods, which by now have become spread all over the world.The introduction of Agile has nevertheless been far from unproblematic. The organisational culture has proven to be one of the most enduring challenges, as the degree of employee understanding and involvement has a decisive impact on successful implementation during periods of significant change. Hence, in Agile Transformation, or an organisation’s journey towards continuous improvement through rapid delivery, feedback and learning in a changing business environment, leaders need constantly spread the agile philosophy in a simple and transparent matter both internally to employees and also to external stakeholders.Our study is exploratory by nature and aims to further the understanding of Agile Transformation and how Entrepreneurial Culture can have a positive impact on this transformation. To explore these issues, we employ a qualitative approach with semi-structured interviews with a team of employees in one case company. The interviews were held with upper-level managers in decision-making positions and with ownership of the change process. By exploring the employees’ opinions about adapting to Agile Transformation, and how the organisational culture has influenced and been managed in the transformation process, we present results which can be used for continued research on Agile Transformation, and particularly emphasize the importance of having an appropriate organisational culture to be able to succeed.