PARADIGM SHIFT FROM LARGE RELEASES TO CONTINUOUS DEPLOYMENT OF SOFTWARE. DESIGNING A REFERENCE MODEL FOR CONTINUOUS DEPLOYMENT.

Transcription

1 PARADIGM SHIFT FROM LARGE RELEASES TO CONTINUOUS DEPLOYMENT OF SOFTWARE. DESIGNING A REFERENCE MODEL FOR CONTINUOUS DEPLOYMENT. PhD Student Teemu Karvonen Supervisors: Markku Oivo and Pasi Kuvaja XP2015 Doctoral Symposium,

2 Research overview Presenta)on contents Research context & background Need for Speed program Research goals: Understanding suppliers capabili)es for con)nuous deployment and how to improve them. Designing a reference model for con)nuous deployment. Implementa)on plan and research methods Brief summary of what has happened so far what are the plans forward Publica)ons (2 published, 2 ongoing/planned) Next steps and recommenda)ons?

3 Research context & Background

4 Con9nuous delivery is a set of prac9ces and principles to release sohware faster and more frequently Introduc9on of Con9nuous Delivery in Mul9- Customer Project Courses, Stephan Krusche and Lukas Alperowitz (ICSE 2014) Officially, we describe con9nuous delivery as the ability to release sohware whenever we want. This could be weekly or daily deployments to produc9on; it could mean every check- in goes straight to produc9on. The frequency is not our deciding factor. It is the ability to deploy at will. Con9nuous Delivery? Easy! Just Change Everything (well, maybe it is not that easy), Steve Neely and Steve Stolt (2013 Agile Conference) The concept of con9nuous deployment, i.e. the ability to deliver sohware func9onality frequently to customers and subsequently, the ability to con9nuously learn from real- 9me customer usage of sohware. Climbing the Stairway to Heaven, Helena Holmström Olsson, Hiva Alahyari and Jan Bosch (2012 SEAA Conference)

5 the prac9ces that Internet companies use are known as con9nuous deployment. This reflects the habit of deploying new code as a series of small changes as soon as it s ready. Development and Deployment at Facebook, Dror G. Feitelson, Eitan Frachtenberg and Kent L. Beck (IEEE Internet Compu9ng 2013) Con9nuous deployment is the idea that you push out changes to the code all the 9me instead of doing large builds and having planned releases of large chunks of func9onality. This allows for con9nuous customer feedback, the ability to learn from customer usage data, i.e. real- 9me customer behavior, and to eliminate any work that doesn t produce value for the customer Towards R&D As Innova9on Experiment Systems: A Framework For Moving Beyond Agile SoHware Development, Helena Holmström Olsson, Jan Bosch and Hiva Alahyari (2013)

6 con9nuous delivery [1] that is, to con9nuously deploy the environment in a test environment that is reasonably similar to the actual produc9on environment as part of development and tes9ng efforts and to promote it to produc9on when appropriate. Weaver: Language and run9me for sohware defined environments, M. H. Kalantar et al. (2014 IBM Journal of Research and Development) SaaS products provide an opportunity to provide consumers with con9nuous deployment of new features, as opposed to scheduled version upgrades as is the norm for products installed on- premise. con9nuous deployment of new versions of a sohware product in produc9on Con9nuous SCRUM: Agile Management of SAAS Products, Puneet Agarwal, (ISEC 11, 2011)

7 Within con9nuous integra9on, a number of further modes of con9nuous ac9vi9es can be iden9fied, namely con9nuous deployment and con9nuous delivery. These concepts are related in that con9nuous deployment is a prerequisite for con9nuous delivery, but the reverse is not necessarily the case. That is, con9nuous delivery refers to releasing valid sohware builds to users automa9cally, whereas con9nuous deployment refers to the prac9ce of deploying the sohware to some environment, but not automa9cally delivering to customers. Brian Fitzgerald and Klaas- Jan Stol (RCoSE ) Con9nuous SoHware Engineering and Beyond: Trends and Challenges References: [28] J. Humble. Con)nuous delivery vs con)nuous deployment, h[p://con)nuousdelivery.com/2010/08/con)nuous- delivery- vs- con)nuous- deployment/. [35] F. Lacoste. Killing the gatekeeper. In Agile Conf., 2009.

8 What is con)nuous deployment? Stairway to Heaven (evolu)onary step) Towards R&D As Innovation Experiment Systems: A Framework For Moving Beyond Agile Software Development Helena Holmström Olsson, Jan Bosch and Hiva Alahyari (2013)

9 Need for Speed (N4S) Real- Time value delivery Large na)onal research program aimed at enhancing Finnish ICT companies capability to deliver value in real- )me. Delivering value in real- )me Deep customer insight Mercury Business

10 N4S-PROGRAM Need for Speed The N4S consortium includes the ideal mix of partners, providing both research expertise and practical business experience % Industry partners 16 SME s and 13 large companies. 16 Large SME's Research 30% Research organizations 11 research institutes and universities Paradigm change Delivering Value in Real- <me Deep Customer Insight Mercury Business Work Packages Read about the N4S Work Packages at N4S

11

12

13 My research goals

14 The first goal of this study is to understand suppliers capabili)es for con)nuous deployment. What are the socware suppliers capabili<es for con<nuous deployment? The second goal of this study inves)gate and develop approaches how to improve those capabili)es How can socware suppliers capabili<es for con<nuous deployment be improved?

15 Research implementa<on overview

16 What are the socware suppliers capabili<es for con<nuous deployment? How can socware suppliers capabili<es for con<nuous deployment be improved? 1. Study how things are. Primary research method is to conduct case studies in Need for Speed partner companies: Elektrobit, Nokia, Ericsson, Tieto, Valmet 2. Understand current state of the research in context of con)nuous deployment (exis)ng body of knowledge). Primary research method: Literature reviews 3. Gather findings to Con)nuous Deployment Reference Model (reference model design & evalua<on) Con<nuous deployment reference model (ar<fact) Sec)on I: Capabili)es for con)nuous deployment Sec)on II: Approaches for improving capabili)es for con)nuous deployment

17 Research ac<vi<es so far & way forward

18 Ar<cle #1: Lean assessment tool adapta<on (from aerospace industry) to socware development domain DONE Karvonen T., Rodriquez P., Kuvaja P., Mikkonen K., Oivo M. : Adap9ng the Lean Enterprise Self- Assessment Tool for the SoHware Development Domain (2012 SEAA) RQ: How to adapt lean enterprise self- assessment tool for SW development domain? Research highlights: 1. Review of lean concepts and transla)on to so@ware development language and so@ware lifecycle processes 2. Mapping of LESAT lean prac)ces (sec)ons, statements, indicators) to 1. ISO/IEC standard (SW lifecycle processes) 2. Lean so@ware development (Poppendieck) and classic lean principles (Womack and Jones) 3. Comparison of the tool to Ericsson s (Finland) lean survey (tool evalua)on) 4. LESAT for so@ware evalua)on by using Focus Group (NOT REPORTED) Theories and research background: Womack, Jones: Classic Lean Thinking, Machine that Changed the World M. & T. Poppendieck: Lean so@ware development: From Concept to Cash Lean Advancement Ini)a)ve (MIT): Lean Enterprise Self- Assessment Tool i.e. Lean capability assessment framework: 1. Lean transforma)on and Leadership Processes, Lifecycle processes and Infrastructure processes LESAT for So@ware download: h[ps://goo.gl/9odqv

19 Ar<cle #2: Mul<ple case- study: Challenges and benefits of moving towards con<nuous deployment DONE RQ1: What are the important prac)ces, barriers and benefits of moving towards Innova)on Experiment Systems in development? Research highlights: Replica)on of case studies conducted in Sweden 2012: Current ways of working? Current ways interac)ng with customer? Barriers and benefits of moving towards experimenta)ons? Extension of Stairway to Heaven model: Prac)ces that characterize each step of the Stairway to Heaven model (4 categories of prac)ces: Business, Architecture, Process, Organiza)on. 4 levels of adop)on: Not adopted, Team, Product, Ins)tu)onalized) Karvonen T., Lwakatare L. Sauvola T., Holmström Olsson H., Bosch J., Kuvaja P., Oivo M.: Himng the Target: Prac9ces for Moving toward Innova9on Experiment Systems (2015 ICSOB) Theories and research background: Stairway to Heaven model (Helena Holmström Olsson, Jan Bosch): Evolu)onary steps of so@ware development companies: Step A: Tradi)onal Development Step B: Agile R&D Step C: Con)nuous Integra)on Step D: Con)nuous Deployment Step E: R&D as Innova)on Experiement Systems

20 Ar<cle #4: Literature review (and op<onal case studies in Need for Speed program) on approaches for how to improve socware supplier s capabili<es for con<nuous deployment ONGOING Karvonen T., NN, NN, NN Approaches for improving so@ware supplier s capabili)es for con)nuous deployment - Systema)c Review (plan to be submi[ed fall 2015) RQ: What approaches so@ware development companies apply for improving capabili)es for con)nuous deployment? Research highlights: Theories and research background: Approaches for retrospec)ves Con)nuous improvement methods (Kaizen etc.) Tradi)onal so@ware process improvement methods Capability Assessment etc. Summary of what is currently known about improving so@ware supplier s capabili)es for con)nuous deployment? Con)nuous Deployment Reference model Part!!

21 Paper 4: Con<nuous deployment reference model design and evalua<on (based on case studies in Need for Speed program) ONGOING RQ: How to design and evaluate reference model for con)nuous deployment Karvonen T., NN, NN: Designing a Reference Model for Con9nuous Deployment Theories and research background:?? Expected research highlights: Summary of what is currently known about improving so@ware supplier s capabili)es for con)nuous deployment? Con)nuous Deployment Reference model Part! How to design reference model for CD? Current plan: 1. Collect empirical data and requirements for the CD reference model 2. Qualita)ve analysis - > Define capabili)es, prac)ces, indicators for CD 3. Evaluate reference model in so@ware development companies 4. Improve reference model 5. Go back to step 1 and repeat

22 Way forward How to manage con)nuous deployment in very different domains inside of development? Embedded systems development? (my cases are probably mostly from this domain) Cloud (SaaS, Paas, IaaS) development? Capability improvement approaches. What are they? Can tradi)onal capability improvement methods (CMMI, SPICE, ISO/IEC etc.) be applied for improving con)nuous deployment prac)ces / agile. (Yes/No/Maybe?)

23 Thank You! PARADIGM SHIFT FROM LARGE RELEASES TO CONTINUOUS DEPLOYMENT OF SOFTWARE. DESIGNING A REFERENCE MODEL FOR CONTINUOUS DEPLOYMENT. PhD Student Teemu Karvonen (teemu.3.karvonen@oulu.fi) Supervisors: Markku Oivo and Pasi Kuvaja XP2015 Doctoral Symposium,

24 EXTRA SLIDES

25 C D CONTINUOUS DEPLOYMENT R&D AS INNOVATION EXPERIMENT SYSTEM + A TRADITIONAL DEVELOPMENT + BUSINESS: Customer valida)on at the end of the project ARCHITECTURE: Early- on requirement freeze PROCESS: Milestone- driven development ORGANISATION: Large development teams divided into discipline (testers, architects etc.) B AGILE R&D ORGANISATION + BUSINESS: Product owner to represent the customer ARCHITECTURE: Lead architect to protect architecture from erosion PROCESS: Sprints & Daily standups ORGANISATION: Feature teams (cross- func)onal) CONTINUOUS INTEGRATION + BUSINESS: Reduce cost of bad quality ARCHITECTURE: Modularisa)on to improve ability to do unit & subsystem tes)ng PROCESS: Test- driven development & Automated test scripts & Automated builds ORGANISATION: V&V func)on integrated in agile team (Con)nuous integra)on roles & infrastructure) + BUSINESS: Business model transforma)on ARCHITECTURE: Componen)sa)on for par)al release & rollback mechanisms PROCESS: Con)nuous release process ORGANISATION: UX/system design integrated in team E BUSINESS: A/B tes)ng ARCHITECTURE: Architecture suppor)ng run- )me varia)on of func)onality PROCESS: Customers real usage data collec)on prac)ces ORGANISATION: Product management & Business development integrated in team EXTENSION

26 Docker, Ansible devops prac)ces Agile acceptance tes)ng automated deployment pipeline Agile lead customer Agile business model X Agile product Management Business reason con)nuous planning Lean SW development prac)ces con<nuous deployment Customer data driven product development Agile R&D con)nuous Integra)on automated customer feedback data channels con)nuos customer experiments Extreme Programming prac)ces Jenkins, Git automated integra)on and verifica)on prac)ces enables

27 What capabili<es socware supplier should have for con<nuous deployment? Agile R&D capabili<es Agile & Lean prac)ces Con)nuous integra)on prac)ces Automated product verifica)on and valida)on Automated deployment pipeline Agile product management capabili<es Con)nuous planning prac)ces Business model for con)nuous deployment Agile customer capabili<es CD processes? Trust? Agile R&D capabili)es Business reasons: Compe))on Efficiency Requirements churn New product innova)on Agile Product Management capabili)es Business reason needs Agile customer capabili)es