Agile is an idea that has spread far within the corporate world and was originally designed for use in small, single- team project within IT. To this, limited is known about agile in larger settings and the purpose of this thesis is to explore the translation of agile in a large organization. Conducting an ethnographic study at SEB Pension & Försäkring we illustrate that the translation of agile imply adaption. We identify three processes of translation; (1) adaption through unifying the understanding of agile, (2) adaption through testing of agile elements, and (3) adaption through negotiations. The ethnography indicates that translation of agile in large organizations is challenging and individuals struggle to convey the essence of the idea, ending up in discussions through various interventions. Due to the popularity of agile the contributions is of value for organizations that attempts to become agile. The thesis is limited by the restricted time of conducting ethnographic studies. Further research is needed to explore the translation of agile in larger settings and to provide validity for the three processes of translation.

Ces dernières années, le secteur spatial connait des évolutions rapides (nouveaux acteurs, nouvelles technologies) qui tendent à réduire le coût des applications télécom et d’observation via des satellites défilants de plus petite taille. En particulier la réduction de la taille et du poids des antennes large bande à polarisation circulaire aux fréquences VHF-UHF constitue un enjeu majeur. Cependant la miniaturisation d’une antenne s’accompagne généralement d’une dégradation de son efficacité et de sa bande passante. Afin de contourner ce compromis, la technique d’agilité fréquentielle constitue une solution intéressante qui permet de maintenir les performances de l’antenne miniaturisée sur une sous bande qui peut être pilotée sur une excursion en fréquence plus large.L’antenne « dipôles magnéto-électriques croisées » DMEC basée sur le concept de la source de Huygens est retenue pour ces travaux. En effet, cette antenne fait partie des antennes large bande les plus compactes dont le rayonnement est uni-directionnel. Le premier objectif de cette thèse est d’étudier et de développer des techniques de miniaturisation originales de l’antenne. Le deuxième axe de recherche s’intéresse à l’agilité fréquentielle de l’antenne miniature initialement développée afin de couvrir plusieurs octaves.Plusieurs techniques de miniaturisation (repliement géométrique, ajout d’éléments discrets) se sont appuyées sur des simulations électromagnétiques, de la modélisation théorique et des expérimentations. Un prototype d’antenne compact actif dans la bande VHF est développé. L’épaisseur de l’antenne est réduite à 0,1λ. L’antenne couvre une bande passante de 94 MHz à 366 MHz avec de bande passante instantanée de 60%. Le gain maximal varie entre 5 et 10 dBic avec un taux d’ellipticité toujours inférieur à 2 dB. / These past years, the space sector is experiencing rapid growth (new players, new technologies) that tend to reduce the cost of telecom and observation applications via smaller satellites. In particular, reducing the size and weight of circularly polarized broadband antennas at VHF-UHF frequencies is a major challenge. However the miniaturization of an antenna is generally accompanied by a degradation of its efficiency and its bandwidth. In order to overcome this problem, the frequency agility technique constitutes an interesting solution to maintain the performance of the miniaturized antenna on a sub-band that can be driven on a wider frequency tuning range.The "crossed magneto-electric dipole" antenna based on the Huygens source concept is chosen for this work. Indeed, this antenna is part of the most compact broadband antennas with excellent unidirectional radiation. The first objective of this thesis is to study and develop original miniaturization techniques of the antenna. The second area of research focuses on the frequency agility of the miniature antenna initially developed to cover several octaves.Several miniaturization techniques such as geometric folding and capacitive loading were developed based on electromagnetic simulations, theoretical modeling and experiments. A frequency-reconfigurable compact VHF antenna is developed and realized. The thickness of the antenna is reduced to 0.09λ. The antenna covers a band from 94 MHz to 366 MHz thanks to only two tuning states (60% instant bandwidth for each). The broadside gain varies between 5 and 10 dBic over frequency with an axial ratio always lower than 2 dB.

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

This master thesis is focused on integration of the information system in chosen company. Master thesis describes the management processes that have been used before the information system was implemented and after the implementation. It also describes recommendations for making the processes more effective. The theoretical part of this thesis introduces the project management methodologies that are mostly used for the integration of the projects and infor-mation systems. The practical part describes the processes of the management that are used for ma-nagement of the projects before new information system is implemented. Last part describes the implementation of the information sytem and the possibilities to expand the system.

Background. DevOps is a hot topic in recent years. It emphasizes the combination of development and operation. Agile is one of the most popular development methods, but Agile mainly focused on software development part, there is no more involvement in deployment and operations. In this case, many companies consider adopting DevOps in Agile to attempt to improve the situation. Objectives. The combination of two different technologies is bound to produce some challenges, whether it is for practitioners or researchers, it is very important to find these challenges and mitigate them, so this article aims to investigate the challenges of adopting DevOps in Agile, then through the systematic literature review and survey questionnaire to determine the corresponding mitigation strategy. Then, in order to detail understand the process of adopting DevOps in Agile, we use interview to research the real process of adopting DevOps in agile. Methods. According to our research question, we used the systematic literature review(SLR), survey questionnaire and interview as our research methodology. Through literature review, we collected data of adopting DevOps in Agile, and summary the challenges and its relevant mitigation strategies. Then survey questionnaire helped us linking the content of literature to the industry, and compare their difference. Through the interview, we explored the actual process of adopting DevOps in Agile in industry, and correspond the challenges to the actual process. Results. Our study summarized the software development process of adopting DevOps based on Agile and revealed 23 challenges and corresponding mitigation strategies. The report also compares the commonalities and gaps between the results from the literature and the findings of real-life adopting of DevOps challenges and mitigation strategies. Conclusions. In this article, we introduced the challenges and corresponding mitigation strategies for adopting DevOps based on agile and summarize the corresponding software development process. The obvious challenges and mitigation strategies were divided into four categories: 1) People 2) Project 3) Process 4) Organization, after which we conducted further discussions based on the actual conditions and compared the results of systematic literature review and the results of questionnaire to detail explore their difference.

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

In this master thesis problems in a small market-driven software development company are discussed. Problems such as fast changes in the company are a result of the constantly changing market. The fast changes must be managed within the company with tailored process covering the needs like short time-to-market. Misunderstandings when managing ideas from marketing and challenging issues such as communication gaps between marketing staff and developers are discussed. These problem areas are identified by the case study through interviews of selected staff. The problems adhere from fast changes and lack of processes and structures. This paper has recommended several points influenced by agile software development with Scrum and XP. The recommendations are chosen to fit the problem areas identified by the interviews. They will work as a starting point for the company to improve the situation and to use XP and Scrum for further improvements.

Context. Scrum is one of the most common used Agile method. It is based on empiricism. Scrum only provides a framework but the detailed implementations in practice are very different. and the environment has a big influence on it. National culture is proven to have an impact on Agile methodology. The implementation of Scrum practices should be influenced by national culture as well. Objectives. This paper reveals the relationship between national culture and Scrum implementation. It explores in which aspects that national culture has an influence on the implementation of Scrum practices and how the different national culture dimensions affect the implementations. Methods. A literature review is used to build a theoretical framework. This framework includes the potential relationships between national culture and Scrum practices, which are our hypotheses. Afterward, interview is used in a company that has Scrum teams in both Sweden and China. Their implementations of Scrum practices are interviewed and analyzed based on our hypotheses. Results. A framework of deducted relationship between Hofstede’s national culture dimensions and Scrum practices is built. National culture is found to have an influence on the implementations of five Scrum practices. Conclusions. National culture is found to have an influence on Scrum implementations. National culture through power distance dimension has the most impact on implementations of no title practice, manage burn down chart practice and no interference practice. National culture differences in the aspect of individualism dimension also affect the practice like no title in teams. Uncertainty avoidance degree in different nations also has the most impact on Scrum implementation such as using burn down chart practice and time-boxed dimensions. Moreover, influence from national culture in China makes the Scrum implementations more consistency than the influence from national culture in Sweden.

In the rapidly changing market of today, companies need to be responsive and react quickly to changes in both their competitors’ behaviour but also to changes in their own technical environment. In this thesis I have examined the agile characteristics of a number of companies in Stockholm, with focus on three agile concepts; Scrum, eXtreme Programming and Test Driven Development. The work started off by a prestudy, in which I have identified the criteria that a company needs to fulfil in order to be considered agile. This resulted in four main categories of characteristics; Quality, Flexibility, Communication and Competence. After doing the prestudy, these characteristics were investigated through a combination of a quantitative study and a case study. While the results mostly lean towards agile behaviour rather than non agile, it was shown that a lot of work still remains, for instance regarding improvements in the communications area, and also in the way these companies apply the agile methodologies examined. / Inom dagens snabba marknad behöver företag kunna reagera snabbt och effektivt på förändringar i både sina konkurrenters beteende, men också på förändringar i sin egen tekniska miljö. I den här uppsatsen har jag undersökt de agila attributen hos ett antal företag i Stockholm, med fokus på tre agila koncept; Scrum, eXtreme Programming och Test Driven Development. Arbetet inleddes med en förstudie, där jag identifierade de kriterium ett företag behöver uppfylla för att kunna anses vara agilt. Detta resulterade i fyra kategorier av attribut; Kvalitet, Flexibilitet, Kommunikation och Kompetens. Efter förstudien undersöktes dessa attribut genom en kombination av en enkätstudie och en studie av ett enskilt företag. Resultaten lutar mestadels åt ett agilt beteende hos de undersökta företagen, men jag har också kunnat påvisa att mycket arbete återstår, exempelvis inom kommunikationsområdet, och även gällande hur de observerade företagen applicerar de tre undersökta agila koncepten.

Context. Agile software development mainly focuses on value creation, and the first principle of theAgile Manifesto is to deliver a valuable software to customers. In spite of the great significance of value,there are few studies investigated what value is from the perspective of industry practitioners. Objectives. In this study we perform a replication study about value definitions, usage, andmeasurements in China and make a comparative analysis with the similar study did in Sweden. Theprimary objectives of this study are to: a) identify value aspects from Chinese software organizations;b) list and describe activities to achieve or maximize the value aspects, and also with the measurements;c) find the similarities and differences between China and Sweden. Methods. The data was collected by using the semi-structured interviews from 30 participants in 20Chinese agile software development organizations. We utilized the content analysis and the Statisticsmethods to analyze the 30 data points. Results. The participants identified 18 value aspects and prioritized them, and the value aspects wereanalyzed by domains and roles. The three most important value aspects are the Delivery process w.r.t.time, Organization, and Team members; different domain focused on different value aspects; the projectmanager concerned more about the Delivery process w.r.t. time, Organization, and Team members,while the product owners focused more on Customer satisfaction. Then, we list and described theactivities to achieve or maximize the value aspects, described some methods and strategies tomeasure/assure/evaluate them. Most of the activities were related to agile practices and the mostactivities were used to achieve the Delivery process w.r.t. time. Finally, we presented the similaritiesand differences between those value results from China and Sweden, the most important difference isthat the Swedish participants put the Customer value perspective at the first place, while Chineseparticipants would like to balance the value between Customer and Internal Business. Conclusions. We concluded that: 1) the Chinese participants thought that the key success factor of asoftware product was to delivery it with high quality to customers on time; 2) the main activities toachieve value were related to agile practices, and some participants used some tools to assure projectprocess; 3) For better communications and collaborations between Chinese and Swedish softwarecompanies, we recommend: a) for Chinese companies, they need to i) concern more about Customerperspective than before; ii) understand the core concepts of agile methods and their using contexts forflexible application; iii) transfer from traditional organization architecture to project-based organizationarchitecture; b) for Swedish companies, they need to i) focus more on Internal business perspective; ii)use some tools and methods to achieve their value aspects; iii) find a suitable way to collaborate betweenagile teams and non-agile teams.