Agile Software Development Meets Corporate Deployment Procedures: Stretching the Agile Envelope

Gotel, Olly; Leip, David

doi:10.1007/978-3-540-73101-6_4

Cited by 4 publications

(12 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Using specific Agile and Lean software development methods appears frequently in the primary studies as well (e.g. using Scrum [7], continuous Scrum [1], pair programming [10], eXtreme Programming [35], or Rugby which is an agile process model including workflows for the continuous delivery of software [47]).…”

Section: Agile and Lean Software Developmentmentioning

confidence: 99%

“…It enables transparency and understanding of the whole picture of product development activities and overcomes corporate constraints that often cause delays in product deliveries, e.g. hand-over delays and communication gaps [35,7,50,67,40,31,32]. A flat R&D organisational structure is common when applying ASD [35,59].…”

Section: Integrated Corporate Functionsmentioning

confidence: 99%

“…hand-over delays and communication gaps [35,7,50,67,40,31,32]. A flat R&D organisational structure is common when applying ASD [35,59]. However, CD demands a greater alignment of the R&D organisation with other corporate functions [62].…”

Section: Integrated Corporate Functionsmentioning

confidence: 99%

“…However, cross-domain competence may be more challenging in the embedded domain, where extensive knowledge of hardware-related aspects is needed. Additionally, several studies have proposed the use of common practices and platforms for software development and maintenance/operation/release as mechanisms to integrate corporate functions with the R&D organisation [16,32,35]. Using shared models such as roadmaps and a feature dependency matrix has also been identified as a mechanism that facilitates effective coordination and interrelationships between solution designers and release managers of complex services [50].…”

Section: Integrated Corporate Functionsmentioning

confidence: 99%

“…Organisational transparency, which is mentioned above as one of the main targets of integrated corporate functions, is a predecessor for building CD into an organisation. Organisational transparency intends to show the bigger picture of scattered development activities in different parts of the organisation, building a common understanding among stakeholders about the development progress and goals [46,47,35,7,50,67,40,31,32]. In CD, transparency has an important role in creating the ability to foresee, trace and understand important aspects of product development in real time [47,59].…”

Section: Transparencymentioning

confidence: 99%

See 4 more Smart Citations

Continuous deployment of software intensive products and services: A systematic mapping study

Rodríguez

Haghighatkhah

Lwakatare

et al. 2017

Journal of Systems and Software

198

153

View full text Add to dashboard Cite

BACKGROUND-The software intensive industry is moving towards the adoption of a value-driven and adaptive real-time business paradigm. The traditional view of software as an item that evolves through releases every few months is being replaced by the continuous evolution of software functionality. OBJECTIVE-This study aims to classify and analyse the literature related to continuous deployment in the software domain in order to scope the phenomenon, provide an overview of the state-of-the-art, investigate the scientific evidence in the reported results and identify areas suitable for further research. METHOD-We conducted a systematic mapping study and classified the continuous deployment literature. The benefits and challenges related to continuous deployment were also analysed. RESULTS-The systematic mapping study includes 50 primary studies published between 2001 and 2014. An in-depth analysis of the primary studies revealed ten recurrent themes that characterize continuous deployment and provide researchers with directions for future work. In addition, a set of benefits and challenges of which practitioners may take advantage were identified. CONCLUSION-Overall, although the topic area is very promising, it is still in its infancy, thus offering a plethora of new opportunities for both researchers and software intensive companies.

show abstract

Section: Agile and Lean Software Developmentmentioning

confidence: 99%

Section: Integrated Corporate Functionsmentioning

confidence: 99%

Section: Integrated Corporate Functionsmentioning

confidence: 99%

Section: Integrated Corporate Functionsmentioning

confidence: 99%

Section: Transparencymentioning

confidence: 99%

See 3 more Smart Citations

Continuous deployment of software intensive products and services: A systematic mapping study

Rodríguez

Haghighatkhah

Lwakatare

et al. 2017

Journal of Systems and Software

198

153

View full text Add to dashboard Cite

show abstract

DevOps in practice: A multiple case study of five companies

Lwakatare

Kilamo

Karvonen

et al. 2019

Information and Software Technology

132

View full text Add to dashboard Cite

Context: DevOps is considered important in the ability to frequently and reliably update a system in operational state. DevOps presumes cross-functional collaboration and automation between software development and operations. DevOps adoption and implementation in companies is non-trivial due to required changes in technical, organisational and cultural aspects. Objectives: This exploratory study presents detailed descriptions of how DevOps is implemented in practice. The context of our empirical investigation is web application and service development in small and medium sized companies. Method: A multiple-case study was conducted in five different development contexts with successful DevOps implementations since its benefits, such as quick releases and minimum deployment errors, were achieved. Data was mainly collected through interviews with 26 practitioners and observations made at the companies. Data was analysed by first coding each case individually using a set of predefined themes and thereafter perform a cross-case synthesis. Results: Our analysis yielded some of the following results: (i) software development team attaining ownership and responsibility to deploy software changes in production is crucial in DevOps. (ii) toolchain usage and support in deployment pipeline activities accelerates the delivery of software changes, bug fixes and handling of production incidents. (ii) the delivery speed to production is affected by context factors, such as manual approvals by the product owner (iii) steep learning curve for new skills is experienced by both software developers and operations staff, who also have to cope with working under pressure. Conclusion:Our findings contributes to the overall understanding of DevOps concept, practices and its perceived impacts, particularly in small and medium sized companies. We discuss two practical implications of the results.

show abstract