La question de la transition numérique est primordiale en conception architecturale. L’objectif de notre recherche est de proposer des pratiques collaboratives afin de faciliter cette transition numérique. Nous nous concentrons sur des pratiques dites « agiles » permettant d’améliorer la communication et la coordination entre architectes, ingénieurs ou encore le maître d’ouvrage. Ces pratiques doivent permettre à ces acteurs d’échanger leurs intentions architecturales et de les évaluer tout en s’assurant que leurs propositions sont satisfaisantes vis-à-vis des besoins du client. Ces pratiques consistent à remplir collaborativement un cahier d’intentions, nécessitant alors confrontations d’opinions, à jouer à un jeu de cartes obligeant tous les concepteurs à prendre la parole, à réaliser des réunions courtes et quotidiennes afin d’expliquer son avancement ou encore à être un coach dont l’objectif est de faciliter la vie de ses collaborateurs. / The question of digital transition is a key issue in architectural design. The objective of our research is to propose collaborative practices to facilitate this digital transition. We focus on so-called "agile" practices to improve communication and coordination between architects, engineers or project owner. These practices must allow these actors to exchange their architectural intentions and evaluate them while ensuring that their proposals are satisfactory concerning the client's needs. These practices consist in collaboratively filling out a book of intentions, requiring confrontations of opinions, playing a card game obliging all designers to speak out, holding short, daily meetings to explain their progress or being a coach, whose objective is to make life easier for their employees.

A crescente demanda por sistemas e a alta velocidade com que seus requisitos evoluem têm evidenciado que desenvolvimento de software exige flexibilidade, pois muitas decisões precisam ser tomadas durante o projeto. Além disso, as dificuldades para a produção de sistemas vão muito além das questões técnicas. Fatores estratégicos, comerciais e humanos são responsáveis por algumas das variáveis que contribuem para tornar o desenvolvimento de sistemas de software uma atividade altamente complexa. Modelos tradicionais de desenvolvimento de software propõem processos prescritivos que não consideram toda essa complexidade. Por outro lado, Métodos Ágeis de desenvolvimento de software sugerem uma abordagem mais humanística com foco na entrega rápida e constante de software com valor de negócios. Porém, para conseguir isto, é preciso escolher um conjunto de práticas de desenvolvimento adequado às características do projeto e da equipe. Desta forma, a natureza única de cada projeto e a necessidade de alta qualidade e produtividade tornam importante a busca por práticas de desenvolvimento. A partir de projetos que conduzimos usando métodos ágeis na academia e na indústria, identificamos e descrevemos 22 práticas para desenvolvimento de software que podem ser adotadas por equipes para aumentar o seu desempenho e/ou a qualidade do software. / The growing demand for systems and the high speed with which their requirements evolve has shown that software development requires flexibility because many decisions need to be taken during the project. Also, the difficulties for the production of software systems go far beyond the technical issues. Strategic, commercial and human factors are responsible for some variables that contribute to make the software development a highly complex activity. Traditional models of software development propose prescritive processes that do not consider all this complexity. On the other hand, Agile Methods of software development suggest an humanistic approach focused on fast and often business valuable software deliveries. But, in order to get it, one needs to choose an appropriated group of development practices accordingly to the project and team features. In this way, the individuality of each project and the need for better quality and productivity motivate the search for software development practices. Based on projects that we conducted by using agile methods in academic and industry environments we identified and described 22 software development practices that can be used by teams to increase their performance and/or the software quality.

A busca por vantagem competitiva é a realidade das empresas na atual economia global. A formação de redes de inovação representa uma forma colaborativa de desenvolver inovações e adquirir vantagem competitiva para atingir novos mercados. Nesses ambientes a gestão constitui-se em um desafio e diversas abordagens podem ser aplicadas na busca pelo sucesso. Esta pesquisa tem o objetivo de identificar e sistematizar como a abordagem de gestão ágil, fundamentada na flexibilidade e adaptabilidade, pode ser aplicada nesses ambientes. A metodologia de pesquisa compreende um estudo bibliográfico para embasamento teórico da temática proposta e uma pesquisa-ação para coletar dados em campo. A análise e discussão do cruzamento entre as evidências teóricas e os dados práticos visa propor uma modelagem de empresas para apoiar a aplicação da gestão ágil em ambientes de redes de inovação auto-organizadas. A modelagem desenvolvida foi guiada pela metodologia Enterprise Knowledge Development-Change Management Method (EKD-CMM) conforme a For Enterprise Modeling (4EM). O resultado da pesquisa identifica os benefícios e limitações observados na aplicação prática da mesma e contribui para ampliar a compreensão dos elementos envolvidos no processo de gestão de redes de inovação auto-organizadas, utilizando a abordagem ágil. / The race for competitive advantage is the business reality in today\'s global economy. Innovation networks formation is a collaborative way to develop innovations and acquire competitive advantage to reach new markets. Management is a challenge in these environments and different approaches can be applied in the pursuit of success. This research aims to identify and systematize how agile management approach, based on flexibility and adaptability, can be applied in these environments. The research methodology comprises a bibliographical study to present the theoretical background in the field of interest and one action research to data collection. The analysis and discussion of the intersection between theoretical background and field practical data aims to propose an enterprise modeling to support the application of agile management in self-organized innovation network environments. The modeling development was guided by the Enterprise Knowledge Development-Change Management Method (EKD-CMM) based on For Enterprise Modeling (4EM) methodology. The research result identifies the benefits and limitations observed in its pratical implementation and contributes to expand the understanding of the elements involved in the management process of self-organizing innovation networks using agile management approach.

In den 80er und 90er Jahren hatten große Anwendungssysteme in Unternehmen einige hundert bis tausend Anwender. Der Software-Entwicklungsprozess für diese Anwendungen war innerhalb der Unternehmen relativ klar geregelt. Fachinformatiker und Fachabteilungen standen einander dabei gegenüber. Oft wurden auch externe Fachleute und Komponentenlieferanten integriert. Entwicklungsmethoden und Werkzeuge waren auf diese Situation ausgelegt. Seit dieser Zeit haben wesentliche Veränderungen stattgefunden. Internettechnologien haben neue Klassen von Applikationen ermöglicht, die wie folgt charakterisiert werden können: - Die Applikationen sind kooperativ (unternehmensübergreifend). Nicht selten sind 20-50 oder mehr Unternehmen z. B. bei Zulieferketten beteiligt. - Eine eigene Klasse bilden mandantenfähige Systeme sowie Business-to-Consumer Systeme (B2C) bei denen sehr große Nutzerzahlen konnektiert werden. - Die Entwicklungszeiten liegen im Bereich von Monaten statt Jahren für eine erste Bereitstellung einer Basislösung. - Die Systeme werden inkrementell unter starker Anwenderbeteiligung bis hin zur Endbenutzerbeteiligung weiterentwickelt. (...)

The emergence of cloud computing is influencing how businesses develop, re-engineer, and implement critical software applications. The cloud requires developers to elevate the importance of compliance with security policies, regulations and internal engineering standards in their software development life cycles. Cloud computing and agile development methodologies are new technologies associated with new approaches in the way computing services are provisioned and development of quality software enhanced. However adoption and use of agile and cloud computing by SMMEs in South Africa is seemingly constrained by a number of technical and non-technical challenges. Using Grounded Theory and case study method this study was aimed at exploring the development of a framework for agile methodologies to promote the adoption and use of cloud computing services by SMMEs in South Africa. Data was collected through survey and in-depth interviews. Open, Axial and Selective coding was used to analyse the data. In tandem with its main objective the study, besides exploring the development of the envisaged framework, also generated and made available valuable propositions and knowledge that SMMEs in South Africa using agile development methodologies can use to work better with cloud computing services in the country without compromising on software quality. The findings of this study and the emerging insights around the development of the framework, which in itself also constitutes an important decision making tool for supporting adoption and use of cloud computing services, are a substantial contribution to knowledge and practice in the ICT field of information systems in South Africa / Information Science / D. Phil. (Information Systems)

Abstract Management of product development activities has become increasingly important, as cycle times of product development have shortened. Smaller product development projects are often conducted rapidly at companies based on customer or sales requests to answer the need for faster cycle times. However, this is often done without fully realizing the impact of the new projects on the larger project portfolio or organizational effectiveness. The main objective of this dissertation is to increase knowledge on the use of agile development methods in small, rapid product development projects, and on the implementation of a rapid product development model. The dissertation is formulated as a qualitative, inductive study based on the research results of four original publications and a summary combining the results. The results of the dissertation show that it is beneficial to separate a rapid product development process for certain types of customer- or sales-initiated projects. A new rapid development model with principles and guidelines is introduced to help organizations facilitate this separation. The implementation of the model can be supported with agile development practices, of which self-managing teams are studied in more detail. There is significant overlap between case companies’ perceived success factors for rapid development and self-management. The results imply that a functional rapid development model can be utilized as a strategic asset at companies. The results also provide empirical evidence that agile development practices can be utilized in product development. In addition to providing empirical evidence in scientific discussion about combining product development and agile software development practices, the results can be used to create better definitions of product development processes in general. / Tiivistelmä Tuotekehityksen johtamisesta ja hallinnasta on tullut entistä haastavampaa ja tärkeämpää, kun tuotekehitysprojektien läpimenoajat ovat lyhentyneet. Yritykset tekevät kasvamassa määrin lyhyitä tuotekehitysprojekteja asiakaspyyntöjen tai myynnin aloitteesta vastatakseen markkinoiden vaatimuksiin nopeasta kehityksestä. Tällaisten nopeiden tuotekehitysprojektien käynnistäminen ja toteutus tehdään usein ymmärtämättä yksittäisen projektin vaikutusta koko projektiportfolioon tai organisaation tehokkuuteen. Tämän väitöskirjan päätavoitteena on tutkia ohjelmistokehityksestä tunnettujen ketterien kehitysmenetelmien käyttöä nopeissa tuotekehitysprojekteissa ja uudenlaisen nopean tuotekehityksen mallin käyttöönotossa. Tutkimus on tehty laadullisena ja induktiivisena tutkimuksena perustuen neljään itsenäiseen tutkimusartikkeliin ja näiden tulokset kokoavaan kokoelmaosaan. Tutkimus osoittaa, että yrityksille on hyödyllistä erottaa erillinen prosessi tietyntyyppisille nopeille tuotekehitysprojekteille. Tutkimuksen tuloksena esitellään malli, joka tukee tätä erottamista periaatteiden ja ohjeiden avulla. Tätä mallia pystytään tukemaan ketterillä kehitysmenetelmillä, joihin liittyen on erityisesti tutkittu itseohjautuvia kehitystiimejä. Case-yritysten havainnoimilla nopean tuotekehityksen menestystekijöillä ja itseohjautuvien tiimien ominaisuuksilla on havaittavissa suurta päällekkäisyyttä. Tulokset osoittavat, että hyvin käytetty ja määritetty nopean tuotekehityksen malli voi olla strateginen kilpailuetu yrityksille. Tulokset lisäävät myös empiiristä tietoa ketterien menetelmien käytöstä tuotekehityksessä ja hyödyntävät siten ajankohtaista tieteellistä keskustelua. Tuloksia voidaan myös hyödyntää muiden tuotekehitysprosessien käyttötarkoituksen tarkempaan määrittämiseen.

Context: Agile methodologies are widely recognized in western countries. From past few years, its practices are being successfully adopted in global settings especially in eastern countries. Across the world, teams are following its values and principles. Are all the teams behaving in the same way? Potential difficulties related to culture arise while implementing agile practices. Due to variance in backgrounds and behaviors, social cliques and issues are likely to be formed between the team mates which become a hurdle. Objectives: The study unravels the list of relationships between the agile team behavioral characteristics and Hofstede cultural dimensions. It also explores whether Indian employees working in an agile environment possess the required behavioral characteristics which are useful for the effective functioning of a team. The other objective of this study reveals the influence of the years of experience of the agile employees on behavioral characteristics. Methods: Data collection processes include a literature review and a web survey. First, in the literature review analysis of the empirical studies from year 1999-2011 was done. The review approach helped in collecting and summarizing the data. The studies were identified from the most reliable and authentic databases that are scientifically and technically peer reviewed such as Engineering village, IEEE Xplore, ACM digital library, Springer Link and Google Scholar. A survey was conducted with 33 practitioners from various multinational organizations in India. Statistical analysis was used to analyze the data. Results: Hofstede’s cultural dimensions had noticeable influence on agile team behavioral characteristics. Although, all the enabler characteristics were not seen in Indian culture, the results clearly show that some of the cultural dimensions are enabling factors to function well in an agile team and some hinder the team effectiveness. The result from the literature review shows the list of relationships between Hofstede cultural dimensions and agile team behavioral characteristics. All team behavioral characteristics were to a certain extent demonstrated by Indian agile employees, which can be known from the survey results. It is also seen from the survey results that, team behavioral characteristics can be demonstrated more effectively by the experienced agile employees. Conclusion: From this study, we have found the relationships between Hofstede cultural dimensions and agile team behavioral characteristics. List of agile team behavioral characteristics which were followed by Indian agile employees were obtained from the survey. We conclude that Indian agile employees were able to demonstrate all the agile team behavior characteristics required for an effective functioning of a team. One more interesting thing which came into our attention, after analyzing the survey was that years of experience of agile employees do have an effect on the employees which influences the demonstration of team behavior characteristics. It was clear that demonstration of these characteristics were not only dependent on individual’s nature but also on the years of experience in agile environment. The absence of relationships which were not found through literature needs to be focused. Hence we conclude that there is a need for conducting even more in-depth surveys and reviews to investigate the unfound relationships.

Abstract Software engineering is advancing according to market needs. Consequently, software development methods that initially caused controversies such as Agile, and more recently Lean, are increasingly being adopted by the software industry. Particularly, Lean Software Development, which was initially regarded as one of the Agile methods, is acquiring an identity of its own as a means to scale Agile. However, Lean thinking is still open to interpretation in the domain of software development, which differs fundamentally from the manufacturing domain where Lean originally emerged. Specific issues such as the essence of Lean Software Development, the compatibility of Lean and Agile and the best combination of them are not properly understood. This dissertation addresses Lean thinking and its combination with Agile in the field of software development, by providing empirical evidence on how software-intensive organisations use them in practice. The research was performed in four phases. First, the relevant literature was analysed to identify research opportunities. Second, a survey strategy was used to investigate status and trends in the adoption of Agile and Lean. The third phase explored in detail how Agile and Lean are combined in practice, by conducting case studies on two large-scale, industry-leading companies that were transforming their processes from Agile Software Development into Lean Software Development. Finally, in the fourth phase, the results of the previous research phases were synthetized to draw conclusions and outline implications. The results of the study confirmed the interest of practitioners in using a combination of Agile and Lean. Unlike in manufacturing, the borders of Agile and Lean are not clearly defined in the software domain. The results provided evidence of numerous compatibilities between Agile and Lean in software development. Generally, the use of Agile methods at a prescriptive level is guided by Lean principles. However, Lean thinking also brings new practical elements to software development processes, such as Kanban, work-in-progress limits, a ‘pull’ and ‘less waste’-oriented culture and an extended emphasis on transparency and collaborative development. The results showed the fundamental importance of practices that enable quick feedback, fast learning and adaptation. / Tiivistelmä Ohjelmistotuotanto kehittyy markkinoiden tarpeiden mukaisesti. Aiemmin kiisteltyjä ketteriä menetelmiä, ja nykyään myös Lean-menetelmiä sovelletaan yhä useammin ohjelmistoteollisuudessa. Lean-menetelmiin perustuva Lean-ohjelmistokehitys erottuu selkeämmin välineenä laajentaa ketterien menetelmien käyttöä. Lean on yhä monitulkintainen ohjelmistotuotannossa, joka poikkeaa teollisuustuotannosta, josta Lean on peräisin. Lean-ohjelmistokehitystä, Lean- ja ketterien menetelmien yhteensopivuutta ja niiden parasta yhdistelmää ei vielä ymmärretä riittävän hyvin. Tämä väitöskirja käsittelee Lean-menetelmien yhdistämistä ketteriin menetelmiin ohjelmistotuotannossa. Tutkimus esittää kokemusperäistä tietoa, kuinka näitä menetelmiä käytetään ohjelmisto-alan organisaatioissa. Tutkimus oli nelivaiheinen. Aluksi tutkimusmahdollisuudet kartoitettiin tutkimalla aiheeseen liittyvää kirjallisuutta. Seuraavaksi tutkittiin kyselytutkimuksen avulla Lean- ja ketterien menetelmien käyttämisen nykytilaa ja kehitystä. Kolmannessa vaiheessa tapaustutkimuksilla selvitettiin Lean- ja ketterien menetelmien yhdistämistä käytännössä. Tapaustutkimuksia tehtiin kahdessa suuressa yrityksessä, jotka olivat muuttamassa prosessejaan ketteristä menetelmistä kohti Lean-ohjelmistokehitystä. Lopuksi aiemmat tutkimusvaiheet yhdistettiin johtopäätöksiä ja vaikutusten hahmottamista varten. Tutkimuksen tulokset vahvistavat Lean- ja ketterien menetelmien yhdistämisen kiinnostavan ohjelmistotuotannonharjoittajia. Lean- ja ketterien menetelmien rajat eivät ole selkeästi määriteltyjä ohjelmistotuotannossa. Tulokset tukevat käsitystä Lean- ja ketterien menetelmien yhteensopivuudesta. Lean ohjaa yleisellä tasolla ketterien menetelmien käyttöä. Lean tuo kuitenkin myös uusia elementtejä ohjelmistotuotantoon, kuten Kanban-menetelmän, keskeneräisen työn rajoittamisen, kysyntään perustuvan ’pull’-menetelmän ja turhan työn vähentämistä tavoittelevan ’less-waste’-työkulttuurin. Lean-ajattelu myös lisää painotusta läpinäkyvyyteen ja yhteistyöhön.

Companies are constantly challenged to maintain but also to expand their market position. According to a study it’s problematic to carry out successful IT-projects. Dependencies, coordination and long term planning are three factors which has shown are difficult to master in bigger projects. The aim with the study is to in- vestigate how these aspects work in one case, through a case study on an IT com- pany. The goal is to contribute with research to the subject of long term planning in IT-projects where agile methods usually is used today. Previous research and theories as project management, agile project management, planning methods, scaling methods, coordination methods and change management are used as a base for the study. An exploratory qualitative study has been performed at the case company, the generated result composes of interviews with personnel from the company. The result showed how the methods and theories where used in the case company mainly focusing on long-term planning and workflows. Generally, the same thoughts where shared among the personnel, but because of the open questions the responder got encouraged to elaborate and explain their opinion leading to new information and aspects even when they agreed on the topic. When analyzing the result, I show that a clear framework, implementing of sim- ple work methods and the project management were all important to be able to conduct long-term planning and handle dependencies in projects. The conclusion was to implement the scaling method SAFe but also to use coordination methods. An important aspect is to include change management processes and theories when implementing or changing something. Further studies suggest that research in this article should be carried out on more companies and studies if the imple- mentation of the agila scaling method SAFe has a positive effect in a company. / Varje dag utmanas företag för att bibehålla men även utöka deras marknadspo- sition. Enligt en studie så är det problematiskt att genomföra lyckade IT-projekt. Beroenden, koordinering och långsiktig planering är tre faktorer som det visat sig vara svårt med i större projekt. Syftet med studien är att undersöka hur dessa aspekter fungerar på ett visst fall, genom en fallstudie på ett IT-företag. Målet är att kunna bidra med forskning till ämnet gällande långsiktig planering i IT-pro- jekt där agila metoder vanligtvis idag används. Tidigare forskning och teorier som projektledning, agil projektledning, planeringsmetoder, skalningsmetoder, koordineringsmetoder samt förändringsledning ligger till grund för studien. En explorativ kvalitativ studie har genomförts på fallföretaget. Det genererade re- sultatet baseras på intervjuer med personal på företaget. Resultatet visade hur det fungerade på fallföretaget gällande långsiktig planering och arbetssätt. I stora drag framfördes liknande tankar och åsikter, men då de ställda frågorna var öppet ställda så framkom även olika nyanser och delar från de olika respon- denterna. Analysen av resultatet visade att tydligare ramverk, implementering av arbetssätt och ledning var viktiga för att kunna planera långsiktigt och han- tera beroenden. Slutsatsen som drogs var att implementera skalningsmetoden SAFe men också använda sig av koordineringsmetoder. En viktig aspekt att inte förglömma är även förändringsarbetet vid införandet eller förändring av något. För vidare forskning skulle studien kunna göras på fler företag och även en stu- die på implementeringen av den agila skalningsmetoden SAFe skulle kunna gö- ras för att se om det skulle ge en positiv effekt för företaget.

Inledning: Agila metoder är ett etablerat arbetssätt inom IT och systemutveckling som nu tagit sig in i andra sammanhang, däribland i HR-funktioner där det benämns agil HR. För att förklara hur idéer förändras när de landar i olika sammanhang brukar begreppet översättning införas, där översättning av en idé kan ta olika form beroende på det sammanhang som det hamnar i. Fält förklaras inom nyinstitutionell teori som ett område eller interaktioner inom en specifik domän. En allt vanligare företeelse idag är att fält tenderar att interagera varpå nya praktiker uppstår. Syfte: Syftet med studien är att utifrån ett nyinstitutionellt perspektiv öka förståelsen för fältinteraktioners uppkomst och deras påverkan på idéers översättning. Metod: Studien har ett nyinstitutionellt samt hermeneutisk perspektiv och har genomförts med en kvalitativ metod. En fallstudie har utförts där intervjuer har varit den primära datainsamlingsmetoden med totalt tolv medverkande. Tillsammans täcker de diskursen kring agil HR, där även sekundärdata i form av bloggar och hemsidor har använts. Slutsats: Studien visar att agil HR har uppkommit genom fältinteraktioner hos fältet IT och fältet HR. Inom denna fältinteraktion kan två arenor urskiljas vilka har olika beroenden till fältet IT, som resulterat i olika översättningar av agil HR. Olikheterna förklaras av institutionella och situationsspecifika drivkrafter i omgivningen vilka skapar olika beroenden samt maktobalanser inom arenorna. Beroendet skapas antingen via en integrationsmekanism eller som en kedjereaktion av redan existerande beroenden. / Background: Agile methods is an established approach within IT and software development that has recently appeared in other contexts, in HR-functions named Agile HR. To explain how ideas travel and land in different situations, the concept of translation is usually introduced. Translation of an idea means that an idea can take different appearance depending on the situation. Fields are explained in institutional theory as an area, or interactions within a specific domain. An increasingly common phenomena today is that fields interact and when so, new practices can emerge. Aim: The aim of the study is to, from an institutional perspective, increase the understanding of the emergence of field interaction and its impact on the translation of ideas. Methodology: The study has taken an institutional and hermeneutic perspective and has been conducted with a qualitative method. A case study has been completed where interviews have been the primary method of data collection, with twelve participants in total. Together they cover the discourse about Agile HR. Secondary data from blogs and webpages have also been used. Conclusion: The study conclude that Agile HR emerge from interactions between the field IT and the field HR. Within the field interaction two arenas being identified with different dependence to the interacting field IT. This generates different translations of Agile HR. The differences are being explained by institutional and contingency factors within the environment that create power asymmetries. The dependence emerge from an integration mechanism or from a chain reaction of already existing dependence.