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.

Titel: Agilt ledarskap – Ett sätt att leda en organisation med medarbetaren i centrum. Författare: Anna Hillerbratt, Victor Fors & Sara Sandén Institution: Linnéuniversitetet, Ekonomihögskolan. Program: Human Resource Management. Kurs: Företagsekonomi III – Organisation, Kandidatuppsats. Handledare: Olle Duhlin Examinator: Mikael Lundgren Syfte: Syftet med denna studie är att genom tolkning och värdering av organisationers beteenden skapa en uppfattning av det agila ledarskapet. Syftet är även att förstå om och hur det agila ledarskapet kan appliceras på organisationer oavsett om agila metoder används eller ej. Studien är intressant för studenter och ledare men även individer vilka är intresserade av hur ledarskap kan komma att se ut i förhållande till framtidens organisationer. Metod: En fallstudie som behandlar agilt ledarskap ur ett organisationsperspektiv. Studien har genomförts med en kvalitativ forskningsstrategi och en induktiv metod. Slutsats: Vi har genom tidigare forskning av det agila uppfattat att fokus initialt legat på den praktiska tillämpningen av agila metoder, och att det saknades en ledarskapsteori baserad på de två huvudsyftena i det agila synsättet. Resultatet av studien är därför den egenutvecklade VAS-modellen, Vilja, Anpassning, Samarbete. Modellens värdegrund är: Med de anställdas utveckling i centrum skapar vi tillsammans en attraktiv arbetsplats och en lönsam organisation, en organisation som kan säkerställa frekvent leverans av kvalitet och på så sätt tillgodose kundens behov samt vara lyhörd för förändring. Nyckelord: Agil, agilt synsätt, ledarskap, självstyrande team, kommunikation, motivation, flexibilitet. / Title: Agile leadership – a way to lead an organization with the employee as the main focus. Authors: Anna Hillerbratt, Victor Fors & Sara Sandén Institution: Linnaeus University, School of Business and Economics. Program: Human Resource Management. Course: Business Administration III – Organization, Supervisor: Olle Duhlin Examiner: Mikael Lundgren Purpose: The purpose of this study is to create an understanding of agile leadership through the interpretation and valuation of organizational behaviors. The purpose is also to understand if and how agile leadership can be applied to organizations regardless of whether or not agile methods are used. The study is interesting for students and leaders, but also individuals who are interested in how leadership can develop in relation to future organizations. Methodology: A case study that adresses agile leadership from an organizational perspective. The study was conducted with a qualitative method and an inductive approach. Conclusions: We have, through previous research, perceived that the focus of the agile methodologies initially was based on the practical application of agile methods and that there was no leadership theory based on the two main purposes of the agile approach. The results of the study is therefore a self-developed VAS-model. The basic principle of the model is: With the employees as the main focus we create an attractive workplace and a profitable organization, an organization that ensures frequent delivery of quality, thus meeting customer needs and being responsive to change. Key words: agile, agile approach, leadership, self-organizing teams, communication, motivation, flexibility.

Bakgrund: Den agila projektmodellen har under de senaste två decennierna vuxit fram som en utmanare till den traditionella vattenfallsmodellen. En av de stora skillnaderna mellan projektmodellerna är att i det agila arbetssättet involveras kunden kontinuerligt. Frågan är vad som då händer med överlämningen av den sista versionen av produkten, när utvecklingen är färdig? Samtidigt har bankbranschen på senare år utmanats av nya aktörer vilka profilerar sig som just digitala och IT-inriktade, och både dessa moderna banker såväl som de traditionella storbankerna har anammat det agila arbetssättet för att kunna konkurrera om kundernas uppmärksamhet. Dessa banker arbetar inte agilt till lika hög grad, och frågan är om överlämningen påverkas av det? Syfte: Syftet med studien är att öka förståelsen för hur överlämningen av det slutliga projektresultatet i agila projekt ser ut på svenska banker. Vidare ska studien undersöka om den skiljer sig mellan banker med olika agil mognad samt vilka konsekvenser som kan uppkomma i samband med överlämningen. Genomförande: Studien är genomförd som en flerfallstudie där två fall - storbanker och nischbanker, undersöks. Vidare har en fenomenologisk ansats och ett kvalitativt angreppssätt använts. Empirin har samlats in genom ett målstyrt urval varpå semistrukturerade intervjuer har genomförts med tio projektledare. Slutsats: Studien resulterar i slutsatsen att en överlämning av en slutlig produkt i agila projekt inte genomförs på ett formellt sätt, till skillnad från vad teorin tidigare har antytt. I synnerhet lämnar aldrig ansvaret för produkten någonsin det team som har utvecklat den. Vidare visar studien att storbanker arbetar med en lägre grad av agil mognad än vad nischbanker gör, men att detta inte påverkar hur överlämningen ser ut. Slutligen bidrar studien till insikter om konsekvenser kring att överlämningen inte existerar på ett formellt sätt. Detta leder till en reflektion kring att organisationer behöver anpassa sin agila projektmetodik till sin egen kontext. Projektledare generellt bör dessutom fundera över hur organisationens arbetssätt påverkar organisationen i stort samt vara medveten om de konsekvenser som dyker upp vid förändringar i arbetssättet. / Background: During the last two decades, the agile project methodology has grown as a competitor to the more traditional waterfall methodology. One of the biggest differences is, with an agile methodology the customer is involved throughout the project. But what happens in the final handover, when the development is finished? At the same time, the Swedish banking industry has been challenged by new actors whom profile themselves as digital focused and IT centred. Both types of banks have developed an agile way of working to be able to compete about the customers. However, the two types of banks does not work agile with the same maturity, and we wonder if the handover is affected by that? Purpose: The purpose of the study is to increase the understanding of what the handover of the final product in agile projects at Swedish banks looks like. Further, the study will examine if the handover differ between banks with different agile maturity, and which consequences that may arise in connection to the handover. Completion: The study was conducted as a multiple-case study in which two cases - traditional banks and specialised banks were examined. Further, a phenomenological and a qualitative approach has been used. The empirical data has been conducted through a targeted selection, where semi-structured interviews have been held with ten project leaders. Conclusion: The study concludes that the handover of the final product in agile projects does not exist in the formal way previous research has suggested. Specifically, the responsibility of the product does never leave the team developing it. Further, the study show traditional banks work with a lower degree of agile maturity in comparison to specialised banks. However, this does not affect the characteristics of the handover. Finally, the study contributes to insights about the consequences of the handover not being as formal. This contributes to a discussion about the need for organisations to be able to adapt their agile methodology to their own context. In general, project leaders also should reflect upon how their way of working affect the organisation as a whole, as well as being aware of the consequences that appears when changing the organisation’s way of working.

Submitted by Caroline Xavier (caroline.xavier@pucrs.br) on 2017-06-30T18:19:05Z No. of bitstreams: 1 DIS_GREICE_DE_CARLI_ROMAN_COMPLETO.pdf: 9835425 bytes, checksum: aa605361de91b916006af4710a54365b (MD5) / Made available in DSpace on 2017-06-30T18:19:05Z (GMT). No. of bitstreams: 1 DIS_GREICE_DE_CARLI_ROMAN_COMPLETO.pdf: 9835425 bytes, checksum: aa605361de91b916006af4710a54365b (MD5) Previous issue date: 2016-12-15 / Em fevereiro de 2001, o Manifesto ?gil foi proposto tendo como princ?pio equipes pequenas e co-localizadas. No entanto, ao longo destes 16 anos, a agilidade tamb?m foi posta em pr?tica em outros contextos, como por exemplo: equipes distribu?das e sistemas complexos, utilizando-se o termo "Desenvolvimento ?gil em Larga Escala". N?o h? uma defini??o clara e compreensiva de como a agilidade est? presente neste contexto. Assim, nosso trabalho preenche essa lacuna com o objetivo de caracterizar a agilidade no Desenvolvimento ?gil em Larga Escala. Neste trabalho, realizou-se um estudo organizado em duas fases. Na Fase 1, denominada Base Te?rica, realizamos um estudo do estado-da-arte da ?rea. Na Fase 2, denominado Estudo Emp?rico, n?s realizamos duas investiga??es: um estudo de campo em uma empresa ?gil em larga escala, para identificar o desenvolvimento durante o processo de transforma??o da empresa para esta nova abordagem e, um grupo focal, para identificar como as equipes ?geis em larga escala que v?m utilizando os m?todos ?geis o quanto se percebem em termos de aspectos de maturidade ?gil. Estes resultados contribuem para os pesquisadores e profissionais entenderem melhor como a agilidade e definida e percebida nestes grandes ambientes. O conhecimento e ?til para aqueles que querem entender como o desenvolvimento ?gil se adapta a tais ambientes e para pesquisadores com o objetivo de se aprofundar sobre o tema. / The Agile Manifesto was proposed in February 2001 having in mind small and collocated teams. However, agile has also been put in practice in other settings (e.g. large teams, distributed teams, complex systems) under the term ?Large-Scale Agile Development' (LSAD). There is no clear definition for and understanding of how agility is present in this setting. Thus, our work fills in this gap aiming to characterize agility in LSAD. We conducted a study organized in two phases. In Phase 1, named Theoretical Base, we conducted the state-of-the-art of the area. In Phase 2, named Empirical Study, we conducted two investigations: a field study in a large-scale agile company to identify how agility was developed during the transformation process of the company to this new approach, and a focus group to identify how large-scale agile teams that have been using agile for a certain while perceive themselves in terms of maturity in agile aspects. Findings contribute to researchers and professionals better understand how agility is defined and perceived in large settings. This knowledge is useful for those who want to enter the agile journey in such similar environments and for researchers aiming to further explore the topic.

Choosing the Software Development Methodology is the very first step of any project; thus,has been a hot topic among, both, practitioners and academic people. After using plandrivensoftware development methodologies software development researchers came up withthe idea of agile software development methodologies as a masterpiece. Although, failurestories of some teams brought about fading the idea that agile methodologies are thebest recipe for any kind of development project. Considering the lack of studies in helpingpractitioners to select the most appropriate agile software methodology, this study aims atprovide the software development manager with a thorough knowledge of agile methodologiesand the criteria that should be considered, while selecting one of them. A case study is used asan empirical support. / Program: Magisterutbildning i informatik

<p>Software prototyping is considered to be one of the most important tools that are used by software engineersnowadays to be able to understand the customer’s requirements, and develop software products that are efficient,reliable, and acceptable economically. Software engineers can choose any of the available prototyping approaches tobe used, based on the software that they intend to develop and how fast they would like to go during the softwaredevelopment. But generally speaking all prototyping approaches are aimed to help the engineers to understand thecustomer’s true needs, examine different software solutions and quality aspect, verification activities…etc, that mightaffect the quality of the software underdevelopment, as well as avoiding any potential development risks.A combination of several prototyping approaches, and brainstorming techniques which have fulfilled the aim of theknowledge extraction approach, have resulted in developing a prototyping approach that the engineers will use todevelop one and only one throwaway prototype to extract more knowledge than expected, in order to improve thequality of the software underdevelopment by spending more time studying it from different points of view.The knowledge extraction approach, then, was applied to the developed prototyping approach in which thedeveloped model was treated as software prototype, in order to gain more knowledge out of it. This activity hasresulted in several points of view, and improvements that were implemented to the developed model and as a resultAgile Prototyping AP, was developed. AP integrated more development approaches to the first developedprototyping model, such as: agile, documentation, software configuration management, and fractional factorialdesign, in which the main aim of developing one, and only one prototype, to help the engineers gaining moreknowledge, and reducing effort, time, and cost of development was accomplished but still developing softwareproducts with satisfying quality is done by developing an evolutionary prototyping and building throwawayprototypes on top of it.</p>

Dans le cadre du développement de logiciel, deux courants de pensée se font concurrence depuis quelques années : le développement de logiciels s'appuyant sur une modélisation plus détaillée et le développement de logiciels basé sur des méthodes agiles qui mettent l'accent sur la production de code opérationnel plutôt que sur la documentation. Chaque courant s'appuie sur ses propres principes. Diverses recherches ont été menées sur les fondements du génie logiciel plus « classique », de façon à en définir les principes. Parmi ces travaux figure la thèse de Normand Séguin, notre codirecteur. En revanche, aucune recherche n'a tenté d'étudier les fondements du développement agile de logiciel. Au début des années 2000, plusieurs grands noms du développement logiciel se sont réunis, parmi eux Cunningham, Beek, Schwaber, Sutherland et Fowler. Ces derniers ont tenté d'extraire, de leurs approches respectives, quatre valeurs et douze principes communs à tous dans le but de produire un « Manifeste agile ». Le développement agile de logiciel peut se faire à l'aide d'un ensemble de méthodes agiles. Bien que chaque méthode adhère aux valeurs et principes du manifeste, chacune met de l'avant des valeurs, des principes et des pratiques complémentaires. Ce mémoire présente les résultats d'une étude de 32 énoncés présentés comme étant des « principes agiles » répertoriés dans la littérature. La liste des principes étudiés est formée à partir des douze principes du manifeste agile, cinq principes de l'eXtreme programming (XP), six de Scrum et neuf de Dynamic System Development Method (DSDM). Notre étude est fondée sur une méthodologie analytique reposant sur une liste de critères pour vérifier si un « principe agile » correspond bien à un principe de génie logiciel. Notre analyse a permis d'identifier 19 principes qui répondent aux critères. Tous les principes retenus sont des propositions prescriptives guidant l'action dans le processus de développement de logiciel. ______________________________________________________________________________ MOTS-CLÉS DE L’AUTEUR : génie logiciel, développement agile, manifeste agile, méthodes agiles, principe, SWEBOK, eXtreme Programming, Scrum, DSDM.

Der Beruf als wesentliche Institution der Anerkennung in der modernen Gesellschaft steht im Wandel und dadurch die Anerkennungschancen und -formen der Arbeit. Fokussiert wird zunehmend Arbeit, die sich an ihrem Erfolg misst und weniger Arbeit, bei welcher die Leistung an sich im Vordergrund steht. Dadurch wird die Wertlosigkeit bestimmter Beschäftigungsgruppen gefördert sowie die De-Institutionalisierung der Anerkennung im Beruf gestärkt. Zudem entfallen durch immer flacher werdende Unternehmens-Hierarchien auch Möglichkeiten Anerkennung durch Positionssymbole auszurücken. Dies bedeutet, dass die Sichtbarmachung von Leistung und des Sich-Sichtbarmachens an Wichtigkeit gewinnt. (...)

Le secteur public est un domaine en perpétuelle mutation, de par la pression économique actuelle mais aussi du fait des progrès technologiques constants. C'est en particulier le cas des collectivités territoriales, dans lesquelles les agents du secteur public sont soumis à de fortes pressions, notamment par la nécessité d'assurer un service de qualité aux usagers tout en minimisant les coûts engagés, mais également du fait de devoir développer de nouvelles compétences pour répondre à des exigences en évolution. Les projets actuels, impliquant de multiples technologies et le besoin de travailler en synergie avec les acteurs territoriaux, sont devenus primordiaux pour la gestion des chaînes logistiques du secteur public. Le domaine du génie industriel a développé diverses méthodes pouvant répondre à ces nouveaux besoins. Ces méthodes englobent différentes théories et pratiques allant du progrès permanent à la gestion de la chaîne logistique jusqu’à la gestion de la relation client. Ces pratiques visent avant tout à améliorer la coordination et l'intégration de toutes les activités nécessaires à l'élaboration d’un produit ou un service. L’apparition de nouvelles démarches, telles que la Smart City, légitime la mise en pratique de méthodes industrielles pour la gestion de services répondant à l’intérêt général d’un territoire. Dès lors, l'objectif de ce travail a été de transposer aux collectivités territoriales des méthodes issues du génie industriel, en s’appuyant sur la démarche de la Smart City, afin de permettre une synergie entre les partenaires, tout en augmentant la productivité de l’organisation dans la fourniture de services publics plus performants. / The public sector is a domain in perpetual transformation, due to current economic pressure and constant technological progress. This is particularly the case in Urban Communities, where employees are under intense pressure, notably by the need to ensure services of high quality to their users while minimizing the costs incurred, but also because of the necessity to develop new skills to meet the new requirements of the sector. Current projects involving multiple technologies, the need to work in synergy with the territorial actors becomes essential for the management of the public sector supply chains. The field of industrial engineering has developed various methods which can address these new needs for the public sector. These methods include various theories and practices going from continuous improvement to Supply Chain Management, including customer relationship management. These practices aim above all at improving the coordination and integration of all activities necessary to the development of a product or service. The emergence of new approaches, such as the Smart City, legitimizes the application of industrial methods for the management of services answering the general interest of a territory. Consequently, the objective of this work is to adapt to the Urban Communities of the methods derived defined in industrial engineering and to integrate the approach of Smart City to improve the synergy between the partners, while increasing the productivity of the organization in the supply of more efficient public services.

Dans cette thèse, nous nous sommes intéressés à la gestion dynamique des processus métiers. L’objectif étant de permettre d’une part, une exécution robuste qui prend en compte la dynamicité des différents éléments de processus métiers. D'autre part l’objectif est aussi de gérer les processus en prenant en compte les compétences nécessaires à leurs exécutions. Ce travail de thèse s’appuie sur l’approche BPM et plus précisément à sa phase d’exécution. Dans un monde de travail turbulent et en constante évolution, on parle souvent de modèles adaptables ou adaptatifs, de modèles qui s’enrichissent à chaque exécution et ne suivent pas un modèle structuré et prédéfini tel que le cas du BPM (Business Process Management) classique. En effet, les outils d’automatisation des processus métiers actuels ont été conçus pour fournir un soutien aux acteurs impliqués pour répondre aux questions : Qu'est-ce qui doit être fait? Qui est en charge de le faire? Quand faut-il être effectué? La plupart du temps ces systèmes sont prescriptifs. Ainsi, les acteurs impliqués ne sont pas seulement supportés, ils sont forcés à effectuer les tâches dans des séquences spécifiées. De surcroit, un processus flexible c’est un processus capable de changer que les parties qui ont besoin d'être changées tout en gardant la stabilité de ses autres parties. Dans ce contexte, parmi les approche prometteuses, l’approche orientée services offre aux entreprises une modularité permettant de remplacer facilement un composant par un autre, de le réutiliser et d’étendre son objectif en lui ajoutant un autre composant. De ce fait, dans le but de supporter l’agilité des processus métiers, nous proposons une approche combinant les trois approches suivantes : l’approche BPM, la gestion des compétences et l'approche orientée service dans un environnement social supportant le travail collaboratif. / In the modern economy, creating agile business processes is one of the conditions to obtain/ maintain competitive advantage on the market. Efficient organizations need to ensure that their business processes are flexible so that these processes can easily accommodate changes in regulations and policies. Actually, the management of business processes is supported by the BPM (Business Process Management) approach. It addresses the management, transformation and improvement of organizational operations. Yet, actual BPM does not feature the means to have a continuous adaptation of their business processes and quick adjustment of their models and resources allocation to meet changing environmental conditions. In this thesis, we aim to support the agility of business processes to ensure a continuous adaptation to changes. The agility of business processes, combined with the agility of employees and that of information technology are prerequisites for achieving business agility. To support agility at IT level, we use the SOA (Service Oriented Architecture) approach. Indeed, the SOA can provide numerous benefits to the organization, enabling it to reduce complexity and increase flexibility through their reutilization and modularity features. Moreover, resources which are important assets in successful process’s implementation are widely supported with agile organization regarded as primordial factor for successful agility implementation. For this reason, we propose an approach that combines management of processes with the required skills to their execution and to better enhance the process flexibility we combine BPM with SOA in a social environment.