Return to search

Design requirements to improve adoption of continuous development services

The adoption of Continuous Development presents many challenges to users and
organizations. The complexity of Continuous Development adoption is partially
attributable to the diversity of the challenges faced, including technical challenges,
cultural challenges, compliance regulations, and lack of understanding. In this thesis,
I worked with industry partner IBM to improve their Continuous Delivery Pipeline
offering to overcome adoption challenges faced by their users. Following Hevner’s
Three Cycle Design Science Methodology, my research had two distinct stages:
Characterizing Continuous Development Adoption Challenges and Creating
Design Requirements to Aid Organizations Offering Continuous Development
Services. Both stages necessitated involvement from both academic literature and
industry collaboration with IBM. Industry collaboration included interviews, surveys,
developer forum analysis, and collaboration with IBM’s “Continuous Delivery” teams.
The design requirements I developed in this thesis addressed cultural, technical,
compliance, and knowledge gap adoption challenges that were identified during the
problem characterization stage. When tested within the Continuous Development
community, feedback indicated that my design requirements would add value to users’
development process, enabling their Continuous Development adoption. This thesis
provides a foundation of empirical research for future study and a set of guidelines
for industry practitioners. / Graduate

Identiferoai:union.ndltd.org:uvic.ca/oai:dspace.library.uvic.ca:1828/11761
Date21 May 2020
CreatorsRae, Trevor
ContributorsDamian, Daniela
Source SetsUniversity of Victoria
LanguageEnglish, English
Detected LanguageEnglish
TypeThesis
Formatapplication/pdf
RightsAvailable to the World Wide Web

Page generated in 0.0066 seconds