Att förutspå framtiden är något som är av vikt för organisationer som vill hålla sig ajour med dagens snabbt föränderliga värld. Det är viktigt för företag att befinna sig på marknaden vid rätt tidpunkt och med rätt typ av tjänst eller produkt. Organisationer tenderar att investera stora summor på uppdaterade erbjudanden på marknaden. För att organisationer ska hålla sig uppdaterade på marknaden krävs det anpassning för att möta nya förväntningar. För att kunna agera på de nya möjligheterna har agil arbetsmetod blivit ett trendigt tillvägagångssätt. En agil organisation kan effektivt ta hänsyn till förändringar i marknaden, kundbehov och teknologi. Ett annat område som har ökat i behov för företag är tjänstedesign. Behovet har uppkommit genom nya krav på ökat värde på tjänster, ökade förväntningar hos kund och digitaliseringens påverkan på tjänster. Genom att arbeta med- och studera kunden, kan företag generera kvalitativa tjänster. Det leder vidare till en ökad förmåga att hitta marknadsmöjligheter Idag saknas studier som kombinerar trendspaning med agil arbetsmetod och tjänstedesign. Genom att studera de tre ämnesområdena i den teoretiska referensramen, har studien ändamålet att generera en modell som kombinerar dem.  Syftet med studien är att identifiera dagens metoder och arbetsprocesser kring trendspaning. Vidare kommer vi lyfta fram faktorer som har betydelse vid en trendspaning. Utöver trendspaning kommer studien även att inkludera perspektiven tjänstedesign och agil arbetsmetod. Den agila metoden kommer fokusera på Scaled Agile Framework. För att slutligen ge ett förslag på hur perspektiven kan integreras med trendspaning. Syftet med studien blir slutligen ge en rekommendation på en metod kring trendspaning som ska framtidssäkra en svensk bankverksamhet.  Forskningsfrågan besvaras genom att koppla det teoretiska ramverket till 12 kvalitativa intervjuer. Teorin och empirin sammanställs i analysen för att utveckla studiens slutliga modell. Modellen besvarar forskningsfrågan: ”Hur kan en lämplig trendspaningsmetod i en svensk bankverksamhet med fokus på agil arbetsmetod och tjänstedesignmetod utformas?”. Studien bidrar till en djupare förståelse av trendspaning, agil arbetsmetod och tjänstedesign genom en djup kunskap och en koppling mellan de tre ämnesområdena och deras samband. Slutligen belyser studien vikten av en gemensam arbetsmetod, en gemensam plattform och en stegvis process på ett företag.

This thesis was done in collaboration with Volvo Cars to inspect their risk management process in light of their recent change to an agile way of working. The question was if their actual risk management differentiates from their directive and if the company could in any way improve their agile risk management. By having qualitative semi-structured interviews with employees in the IT section of the company, we got the picture that not many knew about the IT Risk Management Directive that explains the process, but they are still working within its guidelines. Other sections of the company that is still working traditionally might also benefit from changing to an agile way. However, that would depend on the size of their projects and what kind of work they do since the agile methodology is more turned towards smaller projects that can change direction quickly.

This study aims to discover and create an overview of how model-based systems engineering (MBSE) is utilized in Scaled Agile Framework (SAFe) settings. The overall goal is to identify the challenges and opportunities, the best practices and to find different publication trends that exist for this combination. The combination is interesting to investigate given that MBSE is considered to traditionally be a waterfall-based way of working, whereas SAFe is an Agile way of working. The study was executed by conducting a systematic mapping study. The results we found that were linked to the publication trends where that the number of primary studies investigating the combination of MBSE and SAFe were relatively low, and that the amount of grey literature that were found were higher than peer-reviewed primary studies. The best practices of the combination of MBSE and SAFe were identified by analyzing different methods, tools, and processes. Identified challenges and opportunities of this combination were that it provides: enhanced collaboration and communication capabilities, centralized information about the system under development, reduction of complexity, and decreased development time.

In recent years, product development organizations have started adopting agile methods beyond its intended application on software development as part of organizational aspirations to increase market responsiveness and decrease lead times. Such extended adoption of agile is now commonly known as large-scale agile transformation, yet case studies and research-based guidance on implementing agile at scale is scarce. Available literature lists several general challenges and success factors surfacing during the full course of transformation. This thesis aims to complement existing research through investigating critical factors of a large-scale transformation specifically at early stages of agile adoption. This is performed by applying Laanti's agile maturity model and Roger's innovation adoption theory to a case study of a large fintech company who recently initiated their transformation. Although many of the general challenges discovered were proven to appear even at early stages of adoption, we found four factors particularly important for early-stage adoption of large-scale agile, namely 1) having agile support tailored to team maturity, 2) involving project managers in agile coaching, 3) breaking down silo barriers and 4) developing agile customer contracts. In addition to the critical factors found, we propose an extension to Roger's adoption model in cases when external stakeholders are believed to be affected by the adoption of an innovation. Further studies on early-stage adoption of large-scale agile are required to confirm our conclusions. / Som ett led i att öka marknadsresponsivitet och minska ledtider, har det idag blivit alltmer vanligt för organisationer som utvecklar produkter att applicera agila arbetssätt utanför mjukvaruutveckling. En sådan utökad adoption av agile kallas för storskalig agile transformation. Fallstudier och forskningsbaserade råd för implementering av agile i stor skala är fortfarande få. Syftet med denna studie är att bidra till och komplettera existerande forskning genom att utforska kritiska faktorer för storskaliga agila transformationer i ett tidigt adoptionsstadie. Detta görs genom att applicera och kombinera Laanti's agila mognadsmodell och Roger's teori om innovationsadoption i en fallstudie på ett stort fintech-företag som nyligen initierade sin agila transformation. Fyra kritiska faktorer specifika för tidigaadoptionsstadier identifierades, närmare bestämt vikten av att 1) anpassa agila stödfunktioner till varje teams agila mognad, 2) involvera projektledare i agile coachning, 3) bryta ner silobarriärer mellan funktioner och 4) utveckla agila kundkontrakt. Dessutom föreslår vi en utökning av Roger's innovationsegenskaper för värdering av potentiell adoptionsframgång av innovationer som påverkar externa intressenter. Ytterligare studier på stor-skalig agil transformation i tidiga stadier krävs för att bekräfta våra slutsatser.

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.

The popularity of agile methodologies is steadily increasing. This study is an intent to balance the agile change literature with a psychological perspective and quantitative measures of an agile change made within a Swedish organization. Organizational change recipients’ beliefs (discrepancy, appropriateness, valence, efficacy, & principal support) and trust in management were measured in an online survey to see how well these variables could predict a successful agile change towards transparency. The results indicate a lack of support for several previously cited success factors in the agile literature and a need for more quantitative and research-driven literature. No support could be found for a relationship between discrepancy, appropriateness, valence, principal support, trust in management, and the outcome of a successful implementation of transparency. Efficacy was found to be a significant and robust predictor of the outcome. More research is needed to ensure the generalizability of the results.

Background: The Scaled Agile Framework®(SAFe) has been adopted by many automotive Original Equipment Manufacturers (OEMs) for scaling their agile practices. It is one of the ways to improve and accelerate their in-house software development life cycle. Most OEMs have tailored the agile framework to fit their own needs. However, with the increasing complexity of vehicles, especially in terms of embedded software and hardware development, agile release trains (ARTs) face challenges in managing requirements throughout the vehicle development life cycle. Multiple teams working on requirements, consistency of requirements, collaboration, prioritization of requirements between teams, and changing requirements are some of the challenges faced by the SAFe practicing organizations. Objectives: This thesis examines how the requirements engineering within SAFe has been practiced inone of the automotive OEMs, and the challenges its agile release trains face. It addresses the real problems of practical interest and real-life context by interacting with the teams who have been closely working with the requirements daily. It also accumulates the impacts due to the identified challenges. Methods: This study utilizes a case study methodology, which is flexible in design, exploratory, andqualitative. This choice of research method is influenced by the scope of the study, research questions, and the degree of interaction required between us and the participants to collect the data. By conducting semi-structured interviews, a large quality of data isproduced by having a higher level of interaction with participants. The collected data is then probed for newer and unexpected responses using a thematic approach, which helps to identify patterns and themes using large and complex data. Results: This thesis summarizes the requirement engineering practices and challenges faced by theagile release trains in SAFe practicing automotive industry. We approached the agile teams directly and collected the organizational and stakeholder behavior while working with therequirements and the challenges faced. Using intrinsic data analysis, the gathered interview data is understood, and the implications are listed. This study reemphasizes that agile release trains were facing many challenges, especially in the requirements engineeringarea even though the Scaled Agile Framework is practiced. Knowledge gaps, incompleteand misunderstood customer requirements, ineffective communication, fragmented tooling, inadequate management support, and inconsistent requirement engineering practiceare some of the challenges highlighted by the agile release trains.

Information is everywhere, modern life depends on information. The faster we process data and generate meaningful outcomes, the better. Any IT project produces a lot of artifacts like software code, requirement documents, financial reports, traceability metrics, status reports, and so on. With all this documentation, we are often overloaded with information that makes the picture murkier. Having the wherewithal to capture the needed key performance indicators, there is still a gap between expectation and reality. This thesis is going to fill this gap between available metrics and desired indicators. The agile software development model has been around for a long time now. Today’s organizations are bigger than ever before and are competing in a changing landscape faster than ever before. Scaled agile models have helped the industry to ramp up on the human resources front but these models have not matched the needs of software maturity. Software status gathering and presenting tools are largely waterfall or small-scale agile-centered. The core of the agile approach is value creation but there is no single universal means to measure value. Our research intention is to present a standard value proposition in agile and provide metrics that are better suited for project managers. With help from empirical data, we not only identified the soar areas but also tried to remedy major concerns. To reach our goal, we used face-to-face interviews as our research strategy to get an account of firsthand experiences with the existing KPIs and what are the challenges. Our data collection was done through interviews with domain experts or people with extended knowledge of the subject. Finally, we performed a thematic analysis of the data to find what are the common themes emerging out of the shortcomings of the existing tools and what are the common desired requirements from KPIs. We have given a generic definition of value as well as proposed some KPIs that might come in handy for the practitioners of SAFe.

Product development is more complex than ever. Industries all over the world face intensified competition, forcing firms to improve their innovation performance. This involves integrating software development to a greater extent. As an effort to cope with such progression, agile project management methodologies have been adopted. These include methodologies that are tailored to fit large organisations, made to enhance communication and speed up decision-making. Moreover, such methodologies allocate time for joint planning sessions (such as Program Increment Planning) to foster coordination between teams. The need for extensive coordinating capabilities increases with firm size and product complexity, meaning that large, multinational manufacturers with integrated software- and hardware development face the greatest challenges. With difficult coordination challenges comes a demand for prominent organisational coordination capabilities. This includes capabilities to identify dependencies between agile teams in time, to avoid delays, budget overruns, and quality issues. Hence, firms must adopt sufficient project management procedures, as well as shape organisational artefacts, processes, and culture to maximise their organisational coordination capabilities. In this project, these artefacts, processes, and the organisational culture were defined as factors. Furthermore, the project aimed at (1) – identifying factors that positively contribute to organisations’ capabilities to find inter-team dependencies, and (2) – investigating how to favour those identified factors. The research was conducted at Volvo Car Corporation, a Swedish car manufacturer that undergoes a transition towards being a large-scale agile organisation. Theories concerning coordination, communication, and knowledge management were jointly deployed to construct a state-of-the-art theoretical framework. Thereafter, the conceptual model was the guiding lens for collecting and analysing empirical evidence. Consequently, this project was able to assess 26 factors for identifying inter-team dependencies. Furthermore, several of these factors are proven to be interconnected as they fuel each other and exist in symbiosis. Thus, this project advocates that large-scale agile organisations must understand these factors and their connection to each other — that is when incorporating coordination mechanisms to better identify inter-team dependencies.

While agile development is becoming ever more popular, studies have shown that few organisations successfully transition from traditional to agile practices. One such study showed that large organisations can benefit greatly from agile methods, but evaluating agile maturity and tailoring the method to the organisation’s needs is crucial. An agile maturity model is a tool with which an organisation’s practices and their conformance to agile development is evaluated. The purpose of this study is to discover the best suited agile maturity model for large organisations and to minimise costs, resources and the subjectivity of the model’s evaluation. In this study we take a closer look at four agile maturity models, the Scaled Agile Framework Maturity Model (SAFeMM) by Turetken, Stojanov and Trienekens (2017), the Scaled Agile Maturity Model (SAMM) by Chandrasekaran (2016), the Agile Adoption Framework (AAF) by Sidky, Arthur and Bohner (2007) and the Scaled Agile Framework Business Agility Assessment (SAFeBAA) by the Scaled Agile Incorporation. By evaluating each model on their scalability, completeness, generality, precision, simplicity, usability and meaningfulness, consistency, minimum overlapping, balance and proportion of automatable measurements, the best model is chosen. Based on the evaluation criteria for the maturity models, the SAFeMM is deemed the most suitable model. It proves to be a comprehensive, well-rounded tool with persistent high scores in all criteria. In order to improve the model’s objectivity and resource needs, it is also applied in a case study at the Swedish Tax Agency, where the possibilities to automate the model are investigated. The results show that the SAFeMM can be automated to roughly 50%, with the use of process mining and software system querying. Process mining uses event logs to extract and analyse information, while software querying extracts information directly from the software systems used in an organisation. The study suggests primary sources for querying and process mining techniques and perspectives to enable and encourage future research in the area of process mining within agile development. / Agil utveckling är en mycket populär utvecklingsmetod, samtidigt visar studier att få stora organisationer lyckas med övergången från traditionella metoder direkt. Som hjälpmedel kan dessa organisationer använda så kallade agila mognadsmodeller. En agil mognadsmodell är ett verktyg som mäter hur väl en organisation och dess processer överensstämmer med agila principer. Syftet med denna studie är att undersöka vilken agil mognadsmodell som är bäst lämpad för stora organisationer och kan samtidigt minimera kostnader, resurser och subjektiviteten i mätningarna. Därför tittar denna studie på fyra agila mognadsmodeller, Scaled Agile Framework Maturity Model (SAFeMM) av Turetken, Stojanov och Trienekens (2017), Scaled Agile Maturity Model (SAMM) av Chandrasekaran (2016), Agile Adoption Framework (AAF) av Sidky, Arthur och Bohner (2007) och Scaled Agile Framework Business Agility Assessment (SAFeBAA) av Scaled Agile Incorporation. Genom att utvärdera varje modell baserat på dess skalbarhet, helhetsbild, generaliserbarhet, precision, enkelhet, användbar-het och meningfullhet, kontinuitet, minimal överlappning, balans och andel automatiserbara mätvärden, bestäms vilken modell som är bäst. Resultaten visar, att baserat på de ovannämnda kriterierna, är SAFeMM modellen den bäst lämpade för stora organisationer. Den visade sig vara särsilkt helhetstäckande, enkel att förstå och använda, med höga poäng på de flesta kriterierna. För att förbättra modellens objektivitet och resurskrav, gjordes även en fallstudie där modellen applicerades på Skatteverkets IT avdelning. Där undersöktes möjligheterna för att automatisera modellen. Resultaten visar att knappt 50% av modellen är automatiserbar genom metoder såsom process mining och software querying. Process mining, använder event loggar från mjukvarusystem för att analysera och utvinna information, medan software querying utvinnar information direkt från mjukvarusystemen. Studien presenterar förslag på utvinningskällor och process mining tekniker och metoder för sammanhanget.