Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Towards Continuous Deployment in the Embedded Software Domain and B2B Context

10 views

Published on

Keynote in JIT-RE workshop by Jari Partanen, Bittium.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Towards Continuous Deployment in the Embedded Software Domain and B2B Context

  1. 1. 25/04/2018 Bittium 2017 / Handout from presentation of JIT-RE 2017 1 “TowardsContinuousDeploymentinthe EmbeddedSoftwareDomainandB2B Context” JIT-RE Keynote Handout Case Bittium Jari Partanen 5.9.2017 Content of the presentation ContentofthePresentation 1. Introduction to Bittium and Development path of Way of Working 2. Towards Continuous Deployment 3. Experiments and aspects from the Path towards Continuous Deployment/DevOps 4. Results of experiments 6. Questions © Bittium 2017 I Handout from presentation of JIT-RE2017 2 5. Future Challenges
  2. 2. 25/04/2018 Bittium 2017 / Handout from presentation of JIT-RE 2017 2 Bittium| Development of Way of Working with Lean and Agilemethods • During the journey >100 Certified SCRUM masters trained • Continuous improvement of large-scale agile approaches • Main methods used SCRUM, Kanban and adaptations of Scaled-agile (SAFE, LeSS) models • Embedded DevOps approach incl. SW and HW WayofWorkingatBittium © Bittium 2017 I Handout from presentation of JIT-RE2017 3 Agile methods piloting “Spark” Start of Lean WoW – Lean and AgileAgile Initiatives Agile WOW Corporate – Wide Lean “Scaled Agile” SCRUM, Kanban Continuous integration Beyond budgeting Continuous strategy Transparent Goal Setting E2E Transparency Lean Organizing and “DevOps” Experimental WOW Continuous Deployment 2007 2010 2015 Employee Culture Company Culture Way of Working ContentofthePresentation 1. Introduction to Bittium and Development and our Way of Working 2. Towards Continuous Deployment 3. Experiments and aspects from the Path towards Continuous Deployment/DevOps 4. Results of experiments 6. Questions © Bittium 2017 I Handout from presentation of JIT-RE2017 4 5. Future Challenges
  3. 3. 25/04/2018 Bittium 2017 / Handout from presentation of JIT-RE 2017 3 RoutetoContinuousDeployment © Bittium 2017 I Handout from presentation of JIT-RE2017 Integration level in the Company Cycletime IID Iterative and Incremental Development 1960-> Agile Continuous Deployment In company level. Software developed to a high standard and easily packaged and deployed to test environments, resulting in the ability to rapidly, reliably and repeatedly push out enhancements and bug fixes to customers at low risk and with minimal manual overhead 2011-> Fast Vast Individuals and interactions over processes and tools. Working software over comprehensive documentation. Customer collaboration over contract negotiation. Responding to change over following a plan. 2001-> CI CD Continuous Integration In RD, merging all developer workspaces with a shared mainline several times a day. It was first named and proposed as part of extreme programming (XP). 1999-> What is ContinuousDeployment? 5 Source; DIMECC/Need for Speed Program http://www.n4s.fi/en/ Case BittiumI Keyapproaches for Lean and Agile WoW KeyApproachesofLeanandAgileatBittium © Bittium 2017 I Handout from presentation of JIT-RE2017 6
  4. 4. 25/04/2018 Bittium 2017 / Handout from presentation of JIT-RE 2017 4 Case BittiumI Flow Model usedat Bittiumvs.SAFE and LeSS BasicModels(notexactlybythebookofSAFEorLeSS) © Bittium 2017 I Handout from presentation of JIT-RE2017 7 Source: https://less.works/Source: http://www.scaledagileframework.com/ ContentofthePresentation 1. Introduction to Bittium and Development and our Way of Working 2. Towards Continuous Deployment 3. Experiments and aspects from the Path towards Continuous Deployment/DevOps 4. Results of experiments 6. Questions © Bittium 2017 I Handout from presentation of JIT-RE2017 8 5. Future Challenges
  5. 5. 25/04/2018 Bittium 2017 / Handout from presentation of JIT-RE 2017 5 Case BittiumI Example of practical development targets © Bittium 2017 I Handout from presentation of JIT-RE20179 © Bittium 2017 I Handout from presentation of JIT-RE2017 Developer CII What kind of stuff developersand team leads want to see…? 10
  6. 6. 25/04/2018 Bittium 2017 / Handout from presentation of JIT-RE 2017 6 DevOpsbased SW development WhytouseDevOps?Whatdoesitmean? © Bittium 2017 I Handout from presentation of JIT-RE2017 11 DevOps is an established way of working to bring together the culture, processes and tools across the entire software delivery lifecycle. RAPID DELIVERY HIGH QUALITY REUSABLE Bittium DevOpsI Development Flow SWdevelopmentflow © Bittium 2017 I Handout from presentation of JIT-RE2017 12 Typical SW development flow when developing and testing a new feature. Bittium solution provides real time visibility to SW development progress (coding, building, deployment and testing).
  7. 7. 25/04/2018 Bittium 2017 / Handout from presentation of JIT-RE 2017 7 Bittium DevOpsI System DevOpssystem © Bittium 2017 I Handout from presentation of JIT-RE2017 13 Feedback loop (minutes) Benefits: Deploy 30x more frequently with 200x shorter lead times; have 60x fewer failures and recover 168x faster. Feedback loop (hour) Feedback loop (hour) Amount of errors found in production phase decreases Real time visualization of SW development system with color signals in user interface. Information available for whole SW development team. Latencies for SW development feedback loop are shown in the process pictures. Real time monitoring of development SW dev Flow: Code Deploy Test Release Local SW development Feedback loop seconds Build Test Release Integration engine Production Feedback loop (minutes) Requirement management Cloud Environments Infra Bittium DevOpsI Follow-Up Projectmetrics © Bittium 2017 I Handout from presentation of JIT-RE2017 14
  8. 8. 25/04/2018 Bittium 2017 / Handout from presentation of JIT-RE 2017 8 DevOpsbased SW development SWDevelopmentSuccessStory © Bittium 2017 I Handout from presentation of JIT-RE2017 1515 Customer need Customer wanted to get more efficient software development practices Bittium solution DevOps approach was utilized • SW development environment was virtualized • Build and test automation level was increased • Constant code deployment and very fast feedback of commits was enabled with zero waiting time and automated testing • Kibana based metrics dashboards done Customer benefits • Daily build pass through time improved 80% • Commit pass through time was decreased from one hour to 15 minutes • Time of new server installation improved from 2 days to 30 minutes • Test execution time was decreased from 15 minutes to 5 minutes on target HW • Customer got true DevOps environment Real-time Viewto the aLarge-Scale Development Project StatusFollow-Up,Real-timeView (ContinuouslySwitchingviews) © Bittium 2017 I Handout from presentation of JIT-RE2017 16 • Status of on-going activities/Team / Swithing views • Burndown/Burnup • Latest Estimate for the Release Critical Topics (Overall) SW Commit (Commit, Builds, Rapid Feedback) Critical Performance KPIs Health Barometer
  9. 9. 25/04/2018 Bittium 2017 / Handout from presentation of JIT-RE 2017 9 Needfor Digitalization isArising © Bittium 2017 I Handout from presentation of JIT-RE2017 17 ContentofthePresentation 1. Introduction to Bittium and Development path of Way of Working 2. Towards Continuous Deployment 3. Experiments and aspects from the Path towards Continuous Deployment/DevOps 4. Results of experiments 6. Summary & Questions © Bittium 2017 I Handout from presentation of JIT-RE2017 18 5. Future Challenges
  10. 10. 25/04/2018 Bittium 2017 / Handout from presentation of JIT-RE 2017 10 Case Bittium I Impacts to some KeyKPI´s © Bittium 2017 I Handout from presentation of JIT-RE2017 19 ContentofthePresentation 1. Introduction to Bittium and Development path of Way of Working 2. Towards Continuous Deployment 3. Experiments and aspects from the Path towards Continuous Deployment/DevOps 4. Results of experiments 6. Questions © Bittium 2017 I Handout from presentation of JIT-RE2017 20 5. Future Challenges
  11. 11. 25/04/2018 Bittium 2017 / Handout from presentation of JIT-RE 2017 11 Bittium perspective to Q-Rapids (Quality-Aware Rapid Software Development) ) Similar Tool Flows and Practises not applied the same manner => INCONSISTENCY OF THE DATA DATA VISUALISATION AND BIG DATA PRACTISES EMERGING! Requirement´s tracing needs continuously higher, increasingly Nonfunctional requirements => TRACEABILITY Inconsistency of the data flows over the systems AI Applications potentials Security restrictions for the data itself and access to the data ON-DEMAND ANALYSIS (Developers/DevOps, Stakeholders (Product Owners, PM, Scrum Teams, CITA) Challenge to reduce the Waste ⇒VALUE STREAM VISUALISATION SW CRAFTMANSHIP VISIBILITY / TRANSPARENCY DevOps Practises NON-FUNCTIONAL REQs © Bittium 2017 I Handout from presentation of JIT- RE2017 21 ContentofthePresentation 1. Introduction to Bittium and Development path of Way of Working 2. Towards Continuous Deployment 3. Experiments and aspects from the Path towards Continuous Deployment/DevOps 4. Results of experiments 6. Summary & Questions © Bittium 2017 I Handout from presentation of JIT-RE2017 22 5. Future Challenges
  12. 12. 25/04/2018 Bittium 2017 / Handout from presentation of JIT-RE 2017 12 Summary Summaryofthekeynotepresentation • Development of Lean and Agile WoW takes time • 1st agile initiatives over 10 years ago • How to scale agile in a transparent manner? • Evolution towards Continuous Deployment in embedded SW and B2B context is much more complex than “web deployment” • How to get developers involved? • How to build functional DevOps teams? • In the future transparent development approaches with fast, nearly real-time feedback systems are necessary to be able to see the fulfilment and status of complex requirements (functional/non-functional) • Ability to deliver when necessary! © Bittium 2017 I Handout from presentation of JIT-RE2017 23 Questions? 24

×