The goal of this thesis is to describe the Application lifecycle management (ALM), with a focus on two aspects of this system. The aspects are: the application for the administration of requirements JIRA and the application for the administration of the testing system Testlink. The basis for this endeavor was my practical experience with the implementation of the process ALM in the company LMC. Application lifecycle management is an essential part of companies focused on management processes for software development and it can thus improve their features, from the defining stage to the installation in the production sphere. In my thesis I focus on the application JIRA, as a replacement tool for the administration of requirements and the application Testlink, which is software for the administration and test management. The result aims to conclude whether these applications fulfilled the initial representations of the company and the requirements in the ALM framework. An evaluation of the positive and negative aspects during implementation is being carried, with a look at the effective implementation into practice. I shall try to define the general areas where eventual failures can be detected during the implementation process and that should be carried in mind during the process.

The goal of master thesis "Automation of Processes in Agile Development" is research of agile metodics with a focus on development practices in the Kentico company. This thesis describes different tools used as a support of agile software development including JIRA Software and Confluence, which are used in Kentico. Important part of this thesis is analysis of the current company processes and a plan of their optimization and automation. During the implementation part a web application which displays metrics arising from analysis and optimization proposal phase is realized. This thesis also contains discussion of it's realization and possible improvements.

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.

Målet med min rapport har varit att undersöka de svårigheter och problem som utvecklare på Barnebys kan ställas inför under sitt dagliga arbete. För att begränsa mig har jag valt två stora områden att undersöka, det agila arbetssättet och versions hanteringssystem. Men det viktigaste fokuset i rapporten är vilka problem som uppstår som är relaterade att man jobbar flera utvecklare på samma projekt. Så kallade teams. Rapporten avhandlar en teoretisk bakgrund till de båda ämnena och sedan så genomför jag en undersökning bland de anställda på Barnebys teknikavdelning. Undersökningen görs medhjälp av Google Forms och här finns frågor kring dessa ämnen. Rapporten tar också upp förslag på lösningar och/eller förbättringar. Rapporten avslutas med en presentation av resultatet och egna reflektioner.

Software tools such as Build systems and project management tools are sometimes notwell designed when it comes to usability. This paper investigates the possibility of creatingcustom solutions for the three Atlassian products Jira, Confluence, and BitBucket, in orderto increase the efficiency when performing common tasks at the Atlassian administration atSaab AB. It was discovered that the main issue was performing reoccurring project-accesspermission audits, which was a very repetitive task with many manual steps involved.The solution to the issue was a Python script that, through the use of the Atlassian RESTAPI, could collect all the necessary information automatically and present it in a readablesummarized view. The amount of manual steps was significantly decreased to just a fewsteps which made a huge difference for the Atlassian administrators at Saab AB.

The goal of my master's theses was to analyze the requirements of the ITIL framework for a service desk implementation, identify specifics of SME companies and to try to scale down the ITIL implementation of a service desk to the size applicable to SME. In my practical part I'd like devise a functional model of the ITIL compliant service desk featuring Incident, Request, Change, and Problem Management processes based on the Atlassian Jira sotware. After completing the theasis I will answer a question - if it is possible to use ITIL in the SME segment.

Visualisering är en ofta förekommande metod som används vid utveckling av en ny produkt för att redan i ett tidigt stadium kunna visa den färdiga produkten i form av en prototyp eller annan digital ritning. Det är dock inte lika vanligt att visualisera själva utvecklingen av produkten eller vilken fas den befinner sig i, vilket kan leda till osäkerhet inom utvecklingsgruppen och ge det fortsatta arbetet av produkten en tvetydig bild. Projektgrupperna på företaget CGI Östersund jobbar enligt den agila systemutvecklingsmetoden Scrum där arbetet delas upp i olika delleveranser och ärenden, vilket gör det möjligt att visualisera utvecklingsprocessen. Den här undersökningen har studerat Scrum-metoden ytterligare och därefter tagit fram ett visualiseringsverktyg bestående av en REST-webbtjänst i Java och en webbklient som hämtar information från ett ärendehanteringssystem, JIRA, som företaget använder sig av. Informationen presenteras sedan i form av olika grafer beroende på vad som skall visualiseras. Verktygets funktion och konstruktion har sedan utvärderats med användbarhetstester och även jämförts med ett liknande verktyg som redan finns i den befintliga JIRA-plattformen. Användbarhetstesterna utfördes både innan och efter implementation där det första testet enbart bestod av mock-ups och det andra när verktyget hade fått ett fungerande resultat. Resultatet har visat att det fortfarande råder en del oklarhet i verktygets mer invecklade funktioner, men att helheten av de olika delsystemen är förståelig i dess användbarhet. Jämförelsen med visualiseringen i JIRA visar att liknelserna är stora och att det i nuläget finns både för- och nackdelar med att använda den här lösningen. Verktyget är i övrigt uppbyggd med moderna tekniker och står på en bra grund för vidare utveckling från företagets sida. / Visualization is a frequent method used in the development of a new product to see the finished product to an early stage in the form of a prototype or digital drawing. However, it is not as common to visualize the actual development of the product or what phase it is in, which can lead to confusion within the development team and provide further the work of the product an ambiguous picture. Project teams at the company CGI Östersund works according to the agile system development methodology Scrum where the work is divided into different partial deliveries and issues, making it possible to visualize the development process. This investigation has studied the Scrum method further and then developed a visualization tool consisting of a REST web service in Java and a web client that retrieves information from a issue tracking system, JIRA, which the company uses. The information is then presented in the form of various graphs depending on what is to be visualized. The tool's function and design has been evaluated with usability testing and also then compared with a similar tool that is already in the existing JIRA platform. Usability tests were conducted both before and after implementation, the first test consisted only of mock-ups and the second when the tool had a functioning results. The results have shown that there is still some ambiguity in the tool's more complex features, but to the whole of the various subsystems is understandable in its usability. The comparison with the visualization in JIRA shows that the parables are great and that at present there are both advantages and disadvantages of using this solution. The tool is otherwise constructed with modern techniques and stands on a good basis for further development from the company.

Byggbranschen är en konservativ bransch som länge har setts som motsträvig och traditionell. Detta har resulterat i en långsam utveckling av kommunikationsmönster och former för ledning och samverkan i branschen. En god kommunikation är en förutsättning för lyckade byggprojekt, varför det är av stort intresse att säkerställa en sådan. Denna rapport undersöker hur projekteringsbranschens kommunikation ser ut i dag och hur denna kan förbättras med hjälp av nätverksbaserade agila projektlednings- och kommunikationssystem. Den utreder även hur de i dag tillgängliga systemen anses fungera och dessa kan utveckla kommunikationen inom byggprojektering. Detta görs genom att studera hur användare av det agila projektlednings- och kommunikationssystemet Jira upplever att det fungerar och används. För att undersöka detta användes en kvalitativ metod i form av intervjuer med projektledare, BIM-samordnare och konsulter vid projekten. Denna intervjustudie kompletterades med en kvantitativ undersökning med ett internetbaserat formulär. Båda dessa studier är baserade på en inledande litteraturstudie. Genom att jämföra och analysera de två studierna har slutsatser dragits kring dagens och framtidens kommunikation. De visar att det finns en positiv inställning hos respondenterna till att använda nätverksbaserade kommunikationssystem hos respondenterna. Man kan se att kommunikationen inom byggprojektering kan förbättras och effektiviseras med hjälp av den typ av nätverksbaserade kommunikationssystem som behandlas i rapporten. Baserat på dessa resultat samt tidigare forskning kan man dra slutsatsen att detta nya kommunikationssätt kan leda till en sänkning av både kostnad och tidsåtgång vid byggprojekt. Utöver dessa frågeställningar och slutsatser har studien resulterat i ett antal rekommendationer för det företag som arbetet har skrivits för, Plan B AB. Dessa rekommendationer bildar ett underlag för en ytterligare utveckling av den Jira som används i deras nuvarande projekt vid Ångströmlaboratoriet. / The construction industry is a conservative industry that has for a long time been seen as recalcitrant and traditional, which has resulted in a slow development in business communication systems. This report covers how communication in project planning looks like today. The report also sheds light on opinions this branch of industry has of agile project leading- and communication systems. The study that was performed provided information on how the users view Jira, the agile project leading and communication system, and how it operates. To examine this a qualitative investigation was done in the form of interviews with project leaders, coordinators and consultants. To achieve a somewhat wider response group a survey was conducted through an Internet based questionnaire. The purpose of the study was to identify how coworkers in a Jirabased project feel about the program’s usefulness, if it helps or hinders productivity, if there are any possible features that need improving, and what the users think about the work environment of Jira. The result of the study was a positive opinion of both Jira as a software program and the overall change in project communication opportunities. The study also provided ideas on how to adapt Jira to the project planning branch of the construction industry. In addition, the study also resulted in suggestions on how the company can improve their usage of Jira in the case study for the thesis.

The thesis deals with basic principles of agile software development and describes their advantages compared to the traditional approach. Siemens, s.r.o in Brno uses combination of Scrum and Kanaban as part of organizational processes, therefore the thesis focuses mainly on the method Scrum, Kanban, Scrum-ban and compares these methods with each other. The thesis also analyzes the existing project and results were consulted with the representative of the Siemens company together with the proposals for improvement. JIRA plugin was designed and implemented base on our mutual agreement. This module extends the current tool for analyzing agile projects, this leads to better support of decision making in the context of agile processes. Benefits and further upgrades are consulted at the end of the thesis.

The thesis deals with module extension in currently developing project called Time Project 5. Specifically, the Phases, Notification and External Interface module. The thesis is divided into four major chapters. The first chapter introduces theoretical background consisting of backend and frontend technology description. The second chapter serves as determination of customer's expectations in form of functional and nonfunctional requirements gathering. The major focus of the third chapter is on application architecture design of both server and client side together with subcomponents design. Additionally, this chapter is complemented by the data model and Time Project 5 application design. The last, and at the same time, major chapter reveals the actual implementation of mentioned subcomponents including further necessary support features.