Release processes form an important, if overlooked, part of the complete software development life cycle. Many organizations implement the roles of release engineering and release management in different ways, with a wide amount of variance within the software industry. Ill-designed processes can lead to a higher number of software faults and costly delays. Failures in release engineering can have negative implications, yet the causes of release process failures are not well understood within in the software engineering research community. This dissertation addresses the questions of what the common release process structure is, what the common failure modes are, and how organizations recover from and prevent these failures. We address these questions through a series of case studies with practicing release engineers at commercial software companies. The live interviews with these individual companies provide insight into the state of the practice in release engineering today across a broad spectrum of organization and software domains. The results of these studies indicate four areas of theory in release engineering which future researchers can probe in more depth. These areas center around process organization, social causes of release process failure, the relationship between software architecture and the release process, and how organizations attempt to improve release processes. For practicing release engineers, these results show that most organizations would benefit from three primary improvements: increased process automation, more modular software design, and improved organizational communication and support of release engineering groups. By implementing these improvements, software development companies and the release engineering processes they support will avoid the most common process failures in this critical phase of the software life cycle. / text

Releasing software is challenging. To decide when to release software, developers may consider a deadline, a set of features or quality attributes. Yet, there are many stories of software that is not released on time. In large-scale software development, release management requires significant communication and coordination. It is particularly challenging in Free and Open Source Software (FOSS) ecosystems, in which hundreds of loosely connected developers and their projects are coordinated for releasing software according to a schedule. In this work, we investigate the release management process in two large-scale FOSS development projects. In particular, our focus is the communication in the whole release management process in each ecosystem across multiple releases. The main research questions addressed in this dissertation are: (1) How do developers in these FOSS ecosystems communicate and coordinate to build and release a common product based on different projects? (2) What are the release management tasks in a FOSS ecosystem? and (3) What are the challenges that release managers face in a FOSS ecosystem? To understand this process and its challenges better, we used a multiple case study methodology, and colleced evidence from a combination of the following sources: documents, archival records, interviews, direct observation, participant observation, and physical artifacts. We conducted the case studies on two FLOSS software ecosystems: GNOME and OpenStack. We analyzed over two and half years of communication in each ecosystem and studied developers’ interactions. GNOME is a collection of libraries, system services, and end-user applications; together, these projects provide a unified desktop —the GNOME desktop. OpenStack is a collection of software tools for building and managing cloud computing platforms for public and private clouds. We catalogued communication channels, categorized coordination activities in one channel, and triangulated our results by interviewing key developers identified through social network analysis. We found factors that impact the release process in a software ecosystem, including a release schedule positively, influence instead of direct control, and diversity. The release schedule drives most of the communication within an ecosystem. To achieve a concerted release, a Release Team helps developers reach technical consensus through influence rather than direct control. The diverse composition of the Release Team might increase its reach and influence in the ecosystem. Our results can help organizations build better large-scale teams and show that software engineering research focused on individual projects might miss important parts of the picture. The contributions of this dissertation are: (1) an empirical study of release management in two FOSS ecosystems (2) a set of lessons learned from the case studies, and (3) a theory of release management in FOSS ecosystems. We summarize our theory that explains our understanding of release management in FOSS ecosystems as three statements: (1) the size and complexity of the integrated product is constrained by the release managers capacity, (2) release management should be capable of reaching the whole ecosystem, and (3) the release managers need social and technical skills. The dissertation discusses this theory in the light of the case studies, other research efforts, and its implications. / Graduate / 0984 / gpoo+proquest@calcifer.org

Software development is increasingly conducted in a recurrent fashion, where the same product or service is continuously being developed for the marketplace. Still, we lack detailed studies about this particular context of software development. Against this backdrop, this dissertation presents an action research study into Software Inc., a large multi-national software provider. The research addressed the challenges the company faced in managing releases and organizing software process improvement (SPI) to help recurrently develop and deliver a specific product, Secure-on-Request, to its customers and the wider marketplace. The initial problem situation was characterized by recent acquisition of additional software, complexity of service delivery, new engineering and product management teams, and low software development process maturity. Asking how release management can be organized and improved in the context of recurrent development of software, we draw on Pettigrew’s contextualist inquiry to focus on the ongoing interaction between the contents, context and process to organize and improve release cycle practices and outcomes. As a result, the dissertation offers two contributions. Practically, it contributes to the resolution of the problem situation at Software Inc. Theoretically, it introduces a new software engineering discipline, release cycle management (RCM), focused on recurrent delivery of software, including SPI as an integral part, and grounded in the specific experiences at Software Inc.

Fierce competition in the market is driving software vendors to rely on Software-as-a-Service (SaaS) strategies and to continuously match new software versions with customers’ needs and competitors’ moves. Although release management as a recurrent activity related to SaaS arguably shapes how a vendor services its customers, the literature is surprisingly limited on how software releases are managed to support SaaS strategies. Against this backdrop, we present a collaborative action-research study with Software Inc., a large multi-national software provider, focused on improving the release cycle management process for a complex security software service. The study is part of a comprehensive intervention into Software Inc. that combines a perspective rooted in software process improvement and engineering practices with one rooted in service delivery and customer interactions. The part that is reported in this dissertation draws on the service-dominant logic framework to analyze how the release cycle management process was organized to improve Software Inc.’s ongoing value co-creation with its customers. As a result, the study contributed to improving release cycle management at Software Inc. and it expands industry knowledge about the challenges and opportunities for software vendors to manage releases and improve the value delivered to and co-created with their customers. This added knowledge is of interest to both practitioners and researchers as SaaS strategies increasingly shape the industry with important implications for how software is released.

Made available in DSpace on 2014-06-12T15:53:51Z (GMT). No. of bitstreams: 2 arquivo1933_1.pdf: 2116074 bytes, checksum: 1144c9fce7906fba6fc1437ad2a4c27b (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2009 / Reuso de software é um aspecto chave para organizações interessadas em obter melhorias de produtividade, qualidade e redução de custos. Linhas de Produto de Software é uma abordagem de reúso de software que provou seus benefícios em diferentes contextos industriais (Weiss et al., 2006). Em termos de evolução, uma linha de produtos é um conjunto em contínua evolução, e por isso, sua evolução precisa ser gerenciada para que se alcance os benefícios dessa abordagem. O fato de um core asset ser compartilhado entre produtos, e todas as mudanças neste core asset poder ter efeito sobre diversos produtos (McGregor, 2003), aliado ao fato que em linhas de produto de software é preciso lidar com evolução no tempo (versões) e também evolução no espaço (variabilidade) (Krueger, 2002), faz com que o gerenciamento da evolução (mudanças) em linhas de produto de software seja mais complexo e mais desafiador do que o desenvolvimento tradicional de sistemas únicos (Pussinen, 2002). Portanto, a evolução dos core assets e também dos produtos precisa ser bem gerenciada para minimizar os problemas causados por ela. Este desafio envolve diferentes soluções, como questões técnicas, gerenciais e processuais. Desta forma, o foco desta dissertação está nos problemas ligados ao processo de gerenciamento evolução em linhas de produto de software. Neste contexto, este trabalho apresenta o RiPLE-EM, que é um processo para gerenciamento da evolução. Este processo é uma forma sistemática de guiar e gerenciar a evolução de cada core asset e cada produto, englobando atividades de gerenciamento de mudanças, builds, e entregas. Esta dissertação também apresenta a validação inicial do RiPLE-EM, seguindo guias bem estabelecidos de experimentação de software (Wohlin et al., 2000), e de acordo com os dados coletados e analisados na experimentação, RiPLE-EM mostra indicações de que seja um processo viável para o gerenciamento da evolução em linhas de produto de software

The purpose of the thesis is to conduct a case study for investigating change and release management at Catella Bank, within the context of IT Service Management (ITSM), by measuring and to provide suggestions for improvements. Incident and operations management is included to enhance the understanding of the historical performance at Catella. The case study is set out to answer the following research questions: 1. “How does a transition in change management structure impact the performance of successfully delivering both changes and releases of IT services at a financial institution?” 2. “What are the causes of delays in the delivering changes and releases?” 3. “How does stakeholder involvement alter the performance of implementing a successful change and release?” 4. “How do Information Technology, and the corresponding departments manage and control necessary changes and releases of software at present?” Research methodology utilized in the thesis includes both qualitative and quantitative research, including interviews, participation in meetings and empirical investigation of internal material at Catella. The result from the research has provided a significant collection of issues, as well as suggested solutions for Catella to take to improve organizational maturity in enhancing the capabilities in performing work related to the four managerial disciplines within ITSM. The research culminated in the creation of the CHARM (CHange And Release Management) model, which consists of integrating change and release management into project management, split between three different components for the three organizational levels. The author has created the following components: Strategy matrix, a governance model, and a process model.

When shortening release cycles and moving towards continuous delivery, a different approach for quality assurance may be needed than in traditional release management. To allow the transition, all stakeholders must retain a sense of confidence in the quality of release candidates. This thesis proposes a definition for confidence consisting of 30 confidence factors to take into account to ensure confidence from all stakeholders. Confidence factors have been found through interviews with 11 stakeholders, analyzed and categorized using grounded theory analysis. The found factors are grouped into two main categories: Process and Verification Results. The thesis additionally contains a literature review of quality measurements and explores how confidence can be expressed in a continuous delivery pipeline. It is found that it is not possible to comprehensively express confidence only with metrics displayable in a pipeline when including only currently well-researched metrics, but with the combination of processes known to be followed in the organization some metrics provide coverage for many of the confidence factors.

The thesis focuses on research of IT process weakness. In theoretical part are described basic terms and also frameworks or best practise of process maturity rating. Selected practice ITIL and COBIT are then used for rating in practical part. For this purpose is choosen one of process which is outsourced by external contractor. Rating is made using free accessible tools, which are offered by selected practice and which offer rating process. Result is established according to consultation with people involved in project and their rating using mentioned tools.

The last couple of years the trend within the software industry has been to releasesmaller software updates more frequent, to overcome challenges and increase flexibility, to alignwith the swiftly changing industry environment. As an effect, we now see companies moving over tocapitalizing on subscriptions and incremental releases instead of charging for upgrades. By utilizingneo-institutional theory and Oliver’s (1991) strategic response theory, an enterprise systemsvendor’s response to the emerging DevOps trend can be determined.

The thesis deals with the evaluation of IT processes maturity. In the theoretical part, management of information technologies and methods of assessment in the organization are described. Four methods are selected and used for the maturity assessment of the Release Management process in Česká pojišťovna a.s. In the practical section, a questionnaire is evaluated and the Release Management process maturity level is set. The main objective of this thesis is to evaluate maturity of Release Management process and suggest possible improvements. The objective was achieved through the completed questionnaires of Česká pojišťovna a.s. employees and subsequent consultations with the process owner. The thesis consists of six parts. The first chapter deals with the management of information technology in an organization. The second chapter is devoted to the evaluation of process maturity and description of the selected methods of maturity evaluation. The third chapter maps processes according to ITIL, Cobit 4.1 Cobit 5 and provide their introduction. The fourth chapter introduce the organization of Česká pojišťovna a.s.. The fifth chapter describes the specific process Migrating applications in the Česká pojišťovna a.s.. The sixth chapter focuses on the actual comparison of individual methods of evaluating and interpretation of the results.