Leading Devops practice and principle adoption

This research, undertaken in highly structured software-intensive organizations, outlines challenges associated to agile, lean and DevOps practices and principles adoption. The approach collected data via a series of thirty (30) interviews, with practitioners from the EMEA region (Czech Republic, Estonia, Italy, Georgia, Greece, The Netherlands, Saudi Arabia, South Africa, UAE, UK), working in nine (9) different industry domains and ten (10) different countries. A set of agile, lean and DevOps practices and principles, which organizations choose to include in their DevOps adoption journeys were identified. The most frequently adopted structured service management practices, contributing to DevOps practice adoption success, indicate that those with software development and operation roles in DevOps-oriented organizations benefit from existence of highly structured service management approaches such as ITIL®

Exploring the link between leadership and Devops practice and principle adoption

Our research focuses in software-intensive organizations and highlights the challenges that surface as a result of the transitioning process of highly-structured to DevOps practices and principles adoption. The approach collected data via a series of thirty (30) interviews, with practitioners from the EMEA region (Czech Republic, Estonia, Italy, Georgia, Greece, The Netherlands, Saudi Arabia, South Africa, UAE, UK), working in nine (9) different industry domains and ten (10) different countries. A set of agile, lean and DevOps practices and principles were identified, which organizations select as part of DevOps-oriented adoption. The most frequently adopted ITIL® service management practices, contributing to DevOps practice and principle adoption success, indicate that DevOps-oriented organizations benefit from the existence of change management, release and deployment management, service level management, incident management and service catalog management. We also uncover that the DevOps adoption leadership role is required in a DevOps team setting and that it should, initially, be an individual role

Information system development in a process management environment: the dynamics of improvisation and bricolage during embedded software design

The main objective of this thesis is to make a contribution to knowledge regarding the nature of improvisation and bricolage activities in the practice of embedded software design and how the tensional relationship between process management and improvisation and bricolage can be balanced. There is a lack of understanding embedded systems development in practice, and how the difficulties correspond to prescribed and emergent processes in this context. In order to address this knowledge gap I conducted an in‐depth case study of an embedded system development project in the German automobile context between December 2004 and November 2008. The research adopted an interpretive approach, which involved the collection and analysis of qualitative data. Empirical data that was derived through interviews and observation revealed new insights as to how embedded systems are developed in practice. I adopt the position that emergent processes occur not randomly, but as purposeful agents that navigate through a turbulent environment of ongoing need to improvise with the items at hand. The finding indicates that the success to achieve the aims is bound to the capabilities to be continuously reflexive and induce corrective actions as appropriate. A theoretical conceptualisation disclosed measures that may enhance the capacity to be reflexive. The findings implied that process management frameworks help as scaffolding in order to practice improvisation and bricolage as a coping strategy. Moreover, improving the capabilities to cope with challenges means enhancing reflexive capabilities. The original contribution of this research is founded on rich descriptions and interpretations as to how embedded systems are developed in practice, and the theoretical conceptualisation that can aid to balance the tension between process management and improvisation and bricolage

Proceedings of the 1st international workshop on software process education, training and professionalism (SPETP 2015)

These Proceedings contain the papers accepted for publication and presentation at the first 1st International Workshop on Software Process Education, Training and Professionalism (SPETP 2015) held in conjunction with the 15th International Conference on Software Process Improvement and Capability dEtermination (SPICE 2015), Gothenburg, Sweden, during June 15-17, 2015. During the 14th International Conference on Software Process Improvement and Capability dEtermination (SPICE 2014) held in Vilnius, Lithuania, at a post conference dinner, a group of key individuals from education and industry started to discuss the challenges faced for software process education, training and professionalism, especially with the background of the new modes of learning and teaching in higher education. Further discussions held post conference with key players in the relevant professional and personal certification fields led to a consensus that it is time for the industry to rise to the new challenges and set out in a manifesto a common vision for educators and trainers together with a set of recommendations to address the challenges faced. It was therefore agreed co-located the 1st International Workshop on Software Process Education, Training and Professionalism with the 15th International Conference on Software Process Improvement and Capability dEtermination. This workshop focused on the new challenges for and best practices in software process education, training and professionalism. The foundation for learning of software process should be part of a university or college education however software process is often treated as ‘add one’ module to the core curriculum. In a professional context, whilst there have been a number of initiatives focused on the certification related to the software process professional these have had little success for numerous reasons. Cooperation in education between industry, academia and professional bodies is paramount, together with the recognition of how the education world is changing and how education is resourced, delivered (with online and open learning) and taken up. Over the next 10 years on-line learning is projected to grow fifteen fold, accounting for 30% of all education provision, according to the recent report to the European Commission on New modes of learning and teaching in higher education. It is a great pleasure to see the varied contributions to this 1st International Workshop on Software Process Education, Training and Professionalism and we hope that our joint dedication, passion and innovation will lead to success for the profession through the publication of the manifesto as a key outcome from the workshop. On behalf of the SPETP 2015 conference Organizing Committee, we would like to thank all participants. Firstly all the authors, whose quality work is the essence of the conference, and the members of the Program Committee, who helped us with their expertise and diligence in reviewing all of the submissions. As we all know, organizing a conference requires the effort of many individuals. We wish to thank also all the members of our Organizing Committee, whose work and commitment were invaluable

Information system development in a process management environment : the dynamics of improvisation and bricolage during embedded software design

The main objective of this thesis is to make a contribution to knowledge regarding the nature of improvisation and bricolage activities in the practice of embedded software design and how the tensional relationship between process management and improvisation and bricolage can be balanced. There is a lack of understanding embedded systems development in practice, and how the difficulties correspond to prescribed and emergent processes in this context. In order to address this knowledge gap I conducted an in‐depth case study of an embedded system development project in the German automobile context between December 2004 and November 2008. The research adopted an interpretive approach, which involved the collection and analysis of qualitative data. Empirical data that was derived through interviews and observation revealed new insights as to how embedded systems are developed in practice. I adopt the position that emergent processes occur not randomly, but as purposeful agents that navigate through a turbulent environment of ongoing need to improvise with the items at hand. The finding indicates that the success to achieve the aims is bound to the capabilities to be continuously reflexive and induce corrective actions as appropriate. A theoretical conceptualisation disclosed measures that may enhance the capacity to be reflexive. The findings implied that process management frameworks help as scaffolding in order to practice improvisation and bricolage as a coping strategy. Moreover, improving the capabilities to cope with challenges means enhancing reflexive capabilities. The original contribution of this research is founded on rich descriptions and interpretations as to how embedded systems are developed in practice, and the theoretical conceptualisation that can aid to balance the tension between process management and improvisation and bricolage.EThOS - Electronic Theses Online ServiceWarwick Business School (WBS)University of Warwick (UoW)University of Bath (UoB)American Study and Student Exchange Committee (ASSEC)GBUnited Kingdo

Software development and correction estimation in the automotive domain

Während der letzten Jahrzehnte hat sich Software in alle Lebensbereiche ausgebreitet. Die kontinuierlich steigenden Kundenanforderungen ließen auch die Komplexität steigen, bei gleichbleibender Produktqualität. Analysedaten und diverse Beispiele entstammen der Automobildomäne, die einen sicherheitskritischen Bereich darstellt, in dem Produkte mit speziellen Qualitätsanforderungen entwickelt werden. Qualitätsanforderungen müssen von diversen Prozessen und Standards bedient werden, bei gleichzeitiger Einhaltung enger Endtermine. Die Komplexität der Software und der Safety-Aspekt beeinflussen die Fehlerquote der Produkte stark. Viele Anforderungen werden während der Entwicklung hinzugefügt oder verändert und führen zu permanenten Änderungen in der Software und einer weiteren Steigerung der Komplexität. Änderungen müssen analysiert und getestet werden, um die Qualität des entstehenden Produktes zu gewährleisten. Die Vorhersage von Defekten und Änderungen in der Software sind ein wichtiger Anteil des Software Engineering. Die industrielle Software-Entwicklung muss ihr Ziel innerhalb diverser Grenzen erreichen, ganz wichtig ist das Budget, wobei sich Änderungen an Projektparametern negativ auf das geplante Budget auswirken können. Solche Änderungen werden in zwei Klassen eingeteilt, durch Kunden verursachte neue oder veränderte Anforderungen, und die Korrekturen, die durch Systemverbesserungen oder Fehlerbehebungen entstehen, beide Klassen für das Projekt-Budget relevant. Die Aufwände für die neuen Kundenanforderungen können dem Budget einfach aufgeschlagen werden. Die Korrekturen verursachen ebenfalls große Aufwände, die zu einem negativen Budget führen können, was eine große Herausforderung für das Projektmanagement wie auch die automatisierte Schätzung der Aufwände über die gesamte Projektlaufzeit darstellt.Over the past decades, software has spread to most areas of our lives. The complexity increased due to steadily increasing customer demands and, at the same time, the high quality of the products had to be kept. The data for the analyses and many of the examples are taken out of the automotive software development domain. The automotive domain is a safety-critical area where products are developed with specific quality requirements. These quality requirements have to be met by many processes and by satisfying several standards within stipulated deadlines during the development lifecycle. The complexity of the software and the safety aspect have a strong influence on the product defect ratio. Many requirements will be added and adjusted during the development lifecycle leading to continuous changes in the software and increased complexity. All these changes need to be analyzed and tested to ensure the quality of the product. Predicting software defects and changes is a significant part of software engineering. Industrial software development has to achieve its target within several boundaries. One of the important boundaries for an industrial project is the budget, where changes of any project parameters can easily lead to negative effects in the planned budget. Such changes are classified into two types, the changes pushed by the customer as new requirements or changed requirements, and the correction changes in the project because of improvements of the system and identified bugs with their fixes. This classification is important to control the project budget. The effort for the realization of new customer changes can be estimated and added to the budget. The correction changes also cause huge efforts, which can lead to a negative budget in the project which is a big challenge for the project management, the automated calculation of effort estimations for the complete development life-cycle. This thesis offers a new model to improve the effort estimation from multiple perspectives. This model also integrates follow-up-defects in later process phases. Thus, the defect cost flow is part of the model and enables the management defects and follow-up defects which could spread throughout the development phases. The newly developed model was successfully evaluated in the automotive domain. The overall accuracy of the effort estimations was improved by 80%

Requirements Engineering that Balances Agility of Teams and System-level Information Needs at Scale

Context: Motivated by their success in software development, large-scale systems development companies are increasingly adopting agile methods and their practices. Such companies need to accommodate different development cycles of hardware and software and are usually subject to regulation and safety concerns. Also, for such companies, requirements engineering is an essential activity that involves upfront and detailed analysis which can be at odds with agile development methods. Objective: The overall aim of this thesis is to investigate the challenges and solution candidates of performing effective requirements engineering in an agile environment, based on empirical evidence. Illustrated with studies on safety and system-level information needs, we explore RE challenges and solutions in large-scale agile development, both in general and from the teams’ perspectives. Method: To meet our aim, we performed a secondary study and a series of empirical studies based on case studies. We collected qualitative data using interviews, focus groups and workshops to derive challenges and potential solutions from industry. Findings: Our findings show that there are numerous challenges of conducting requirements engineering in agile development especially where systems development is concerned. The challenges discovered sprout from an integration problem of working with agile methods while relying on established plan-driven processes for the overall system. We highlight the communication challenge of crossing the boundary of agile methods and system-level (or plan-driven) development, which also proves the coexistence of both methods. Conclusions: Our results highlight the painful areas of requirements engineering in agile development and propose solutions that can be explored further. This thesis contributes to future research, by establishing a holistic map of challenges and candidate solutions that can be further developed to make RE more efficient within agile environments

The Digital Transformation of Automotive Businesses: THREE ARTEFACTS TO SUPPORT DIGITAL SERVICE PROVISION AND INNOVATION

Digitalisation and increasing competitive pressure drive original equipment manufacturers (OEMs) to switch their focus towards the provision of digital services and open-up towards increased collaboration and customer integration. This shift implies a significant transformational change from product to product-service providers, where OEMs realign themselves within strategic, business and procedural dimensions. Thus, OEMs must manage digital transformation (DT) processes in order to stay competitive and remain adaptable to changing customer demands. However, OEMs aspiring to become participants or leaders in their domain, struggle to initiate activities as there is a lack of applicable instruments that can guide and support them during this process. Compared to the practical importance of DT, empirical studies are not comprehensive. This study proposes three artefacts, validated within case companies that intend to support automotive OEMs in digital service provisioning. Artefact one, a layered conceptual model for a digital automotive ecosystem, was developed by means of 26 expert interviews. It can serve as a useful instrument for decision makers to strategically plan and outline digital ecosystems. Artefact two is a conceptual reference framework for automotive service systems. The artefact was developed based on an extensive literature review, and the mapping of the business model canvas to the service system domain. The artefact intends to assist OEMs in the efficient conception of digital services under consideration of relevant stakeholders and the necessary infrastructures. Finally, artefact three proposes a methodology by which to transform software readiness assessment processes to fit into the agile software development approach with consideration of the existing operational infrastructure. Overall, the findings contribute to the empirical body of knowledge about the digital transformation of manufacturing industries. The results suggest value creation for digital automotive services occurs in networks among interdependent stakeholders in which customers play an integral role during the services’ life-cycle. The findings further indicate the artefacts as being useful instruments, however, success is dependent on the integration and collaboration of all contributing departments.:Table of Contents Bibliographic Description II Acknowledgment III Table of Contents IV List of Figures VI List of Tables VII List of Abbreviations VIII 1 Introduction 1 1.1 Motivation and Problem Statement 1 1.2 Objective and Research Questions 6 1.3 Research Methodology 7 1.4 Contributions 10 1.5 Outline 12 2 Background 13 2.1 From Interdependent Value Creation to Digital Ecosystems 13 2.1.1 Digitalisation Drives Collaboration 13 2.1.2 Pursuing an Ecosystem Strategy 13 2.1.3 Research Gaps and Strategy Formulation Obstacles 20 2.2 From Products to Product-Service Solutions 22 2.2.1 Digital Service Fulfilment Requires Co-Creational Networks 22 2.2.2 Enhancing Business Models with Digital Services 28 2.2.3 Research Gaps and Service Conception Obstacles 30 2.3 From Linear Development to Continuous Innovation 32 2.3.1 Digital Innovation Demands Digital Transformation 32 2.3.2 Assessing Digital Products 36 2.3.3 Research Gaps and Implementation Obstacles 38 3 Artefact 1: Digital Automotive Ecosystems 41 3.1 Meta Data 41 3.2 Summary 42 3.3 Designing a Layered Conceptual Model of a Digital Ecosystem 45 4 Artefact 2: Conceptual Reference Framework 79 4.1 Meta Data 79 4.2 Summary 80 4.3 On the Move Towards Customer-Centric Automotive Business Models 83 5 Artefact 3: Agile Software Readiness Assessment Procedures 121 5.1 Meta Data 121 5.2 Meta Data 122 5.3 Summary 123 5.4 Adding Agility to Software Readiness Assessment Procedures 126 5.5 Continuous Software Readiness Assessments for Agile Development 147 6 Conclusion and Future Work 158 6.1 Contributions 158 6.1.1 Strategic Dimension: Artefact 1 158 6.1.2 Business Dimension: Artefact 2 159 6.1.3 Process Dimension: Artefact 3 161 6.1.4 Synthesis of Contributions 163 6.2 Implications 167 6.2.1 Scientific Implications 167 6.2.2 Managerial Implications 168 6.2.3 Intelligent Parking Service Example (ParkSpotHelp) 171 6.3 Concluding Remarks 174 6.3.1 Threats to Validity 174 6.3.2 Outlook and Future Research Recommendations 174 Appendix VII Bibliography XX Wissenschaftlicher Werdegang XXXVII Selbständigkeitserklärung XXXVII