Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Speed to innovation in retail with DevOps

87 Aufrufe

Veröffentlicht am

How many of the top 100 retailers still struggling to promote innovation or even minor change into production? Development teams take weeks to write code, and when it’s finally handed off to operations for deployment, there might still be several roll-backs before you get it stabilized.
What does it take to move your it into DevOps – change mindsets of development and operations teams, enable true collaboration, automate your development pipelines, configuration management and continuous integration, automated testing, one-click deployment, performance monitoring etc.
Fujitsu has DevOps in the DNA of the new generation products for Retail (Market Place), and we’re happy to share our practices with our customers, but what’s more important – understand, how can we help them with their IT transformation.

Seaker:
Galina Musina
Dmitry Kashtanov

Veröffentlicht in: Technologie
  • Als Erste(r) kommentieren

Speed to innovation in retail with DevOps

  1. 1. Human Centric Innovation Co-creation for Success © 2018 FUJITSU Fujitsu Forum 2018 #fujitsuforum
  2. 2. © 2018 FUJITSU Speed to innovation in retail with DevOps Galina Musina Head of Retail Vertical/Head of Service Delivery, Russia GDC, GSDU, Fujitsu Dmitry Kashtanov Head of Digital R&D and Business Innovation, Russia GDC, GSDU, Fujitsu
  3. 3. 2 © 2018 FUJITSU DevOps or how to increase speed to innovation in Retail DevOps
  4. 4. 3 © 2018 FUJITSU Speed to innovation in retail with DevOps  Question: What is DevOps?
  5. 5. 4 © 2018 FUJITSU Speed to innovation in retail with DevOps  Question: What is DevOps?  Answer: is a software development methodology that combines software development (Dev) with information technology operations (Ops). The goal of DevOps is to shorten the systems development life cycle while also delivering features, fixes, and updates frequently in close alignment with business objectives* * https://en.Wikipedia.org/wiki
  6. 6. 5 © 2018 FUJITSU Speed to innovation in retail with DevOps  Question: How does it change software evolution reality?
  7. 7. 6 © 2018 FUJITSU Speed to innovation in retail with DevOps  Question: How does it change software evolution reality?  Answer: Design DevOps Design Code Test Code Test Code Test Code Test Deploy Agile Design Code Test Deploy Traditional (Waterfall) Software evolution
  8. 8. 7 © 2018 FUJITSU Speed to innovation in retail with DevOps  Question: What does it mean to move to DevOps?
  9. 9. 8 © 2018 FUJITSU Speed to innovation in retail with DevOps  Question: What does it mean to move to DevOps?  Answer: change mindsets of development and operations teams, enable true collaboration, introduce performance monitoring, introduce continuous integration, automate testing, automate deployment (one-click), automate your development pipelines, introduce continuous insight into the data flows using DataOps
  10. 10. 9 © 2018 FUJITSU Speed to innovation in retail with DevOps  Question: What do you expect when going for DevOps?
  11. 11. 10 © 2018 FUJITSU Speed to innovation in retail with DevOps  Question: What do you expect when going for DevOps?  Answer: Increased Agility To enable near instant change deployment Increased Quality To increase end user satisfaction Improves Innovation To increase innovation cycles Reduced Outages Up to 80% outages are change related
  12. 12. 11 © 2018 FUJITSU Speed to innovation in retail with DevOps  Question: What can be the reality?
  13. 13. 12 © 2018 FUJITSU Speed to innovation in retail with DevOps  Question: What can be the reality?  Answer: High investments in new tooling OPEX/CAPEX increase with no sensible ROI Devs vs Ops Dev and operation teams resisting to change Legacy Software Monolithic Retail solutions are not flexible and it's too expensive to put those in DevOps pipeline Inflexible sourcing Flexible approach may not fit outsourcers and providers contract terms
  14. 14. 13 © 2018 FUJITSU Speed to innovation in retail with DevOps  Question: How to ensure successful move to DevOps?
  15. 15. 14 © 2018 FUJITSU Speed to innovation in retail with DevOps  Question: How to ensure successful move to DevOps?  Answer: Make DevOps a part of the Business and IT Strategy Ensure DevOps is aligned with Business Strategy. Set a business goal for DevOps implementation. Learn and apply tools There are a lot of tools available: VCS, CI, CD, AutoTest, Infra as Code, Private Cloud etc. Prefer declarative approach (configuration, target state) over imperative (code). Change mindsets and culture Break down silos, enable collaboration, remove blame games, bring in DevOps champion, adjust KPI and incentives
  16. 16. 15 © 2018 FUJITSU Speed to innovation in retail with DevOps  Question: How DevOps is integrated with retail business?
  17. 17. 16 © 2018 FUJITSU Speed to innovation in retail with DevOps  Question: How DevOps is integrated with retail business?  Answer: With Agile With Agile and DevOps With Agile and DevOps integrated with retail operations Software Infrastructure Flexible Inflexible Software Infrastructure Business Users Flexible Flexible Engaged Software Infrastructure Business Users Flexible Flexible Left Out
  18. 18. 17 © 2018 FUJITSU Connected Retail. FUJITSU Retail Solution Market Place with DevOps in DNA
  19. 19. 18 © 2018 FUJITSU DevOps in Fujitsu Retail App Roadmaps Business Requirements Development Deployment Continuous ImprovementOperate, Monitor, Measure Feedback DevOps Culture Sprints Continuous Testing Continuous Integration Continuous Deployment Continuous Monitoring Continuous Improvements ContinuousPlanning Test Automation Feedback & MonitoringArchitecture & development Deployment Pipeline  Agile development practices ✓  Peer reviews ✓  Loosely coupled architectures  Continuous refactoring  Development analytics  MS Visual Studio ✓  MS Team Foundation Server ✓ -> MS Azure DevOps  Automated unit tests ✓  Automated UI tests ✓  Automated integration test, POS/MPE  Automated security & performance tests  MS Unit Test Framework ✓  MS CodedUI ✓  Automated builds ✓  Automated code analysis ✓  Automated deployment ✓  Automated test environments provisioning  Automated test system installations  MS Visual Studio ✓  VMWare, MS Hyper-V ✓  MS PowerShell ✓  InstallShield ✓  MarketPlace Enterprise Deployment ✓  MS SCCM, Miradore ✓  MS Azure DevOps Services  System monitoring ✓  Problem Management ✓  Project & Service Post Mortems ✓  MarketPlace Enterprise Monitoring ✓  ServiceNow ✓
  20. 20. 19 © 2018 FUJITSU Deployment Pipeline - FJMP Automated FJMP installation in Azure POS, StoreNode, MPE Automated environment provisioning in Azure MPE, StoreNode, POSes Automated FJMP builds POS & MPE, including automated unit/component tests Automated POS-MPE integration test UI automation tests POS, MPE Pipeline orchestration (”Pressing a button”) Manual testing
  21. 21. 20 © 2018 FUJITSU Only when all automated tests have passed To be continuously run by developers; very frequently; must be fast Test Automation Pyramid To be run often as part of the deployment pipeline; may be slower Automated Unit Tests Automated Component Tests Automated Integration Tests Automated API Tests Automated UI Tests Manual Testing
  22. 22. 21 © 2018 FUJITSU Why DevOps? What are we striving for? Ability to deliver new functionality quickly to the customer Ability to deliver new releases often and reliably Short time-to-market from the customer’s spec to working system in production. As a result, business benefit (competitive edge) Enhanced development process in order to improve system quality Standard quality control by use of automation Flexibility of environments Reducing hardware cost Enabling quick, automated setup of environments for several roles System stability Low failure rate Fast recovery from failures Continuous development Continuous improvement of the delivery process Short lead times and frequent releases Top quality systems Transparency and fast feedback Transparency to the customer during development Fast feedback to all team members e.g. by use of automation Routine and repetitive tasks will be automated. Focusing human work on higher-level design tasks Focus on value adding work
  23. 23. 22 © 2018 FUJITSU DevOps in Retail Services - Benefits Business Requirements Development Deployment Continuous Improvement Operate, Monitor, Measure  Requirements in one place  Speed of development  Flexibility to changes  Standard quality control by use of automation  Flexibility of environments by virtualization (”everything is code”)  Lower hardware costs  Transparency to the customer during development  Fast feedback to all team members by use of automation  Frequent and reliable releases  A new release can be published by ”pressing a button”  Speed of rollout, short lead time  Centralized, detailed control of all releases in production  Deployment with fewer personnel  Low failure rate, preventing failures by use of predictive diagnostics  Fast recovery from failure  Constantly optimized delivery engine  Continuous skills development  Short time-to-market of new functionality, contributing to early business benefits  Focus on value adding work, based e.g. on extensive use of automation  Improved system quality  Lower cost, e.g. hardware
  24. 24. 23 © 2018 FUJITSU Realtime monitoring of SW evolution with DevOps Builds DashboardQA Dashboard Just couple of samples on how this looks in practice…
  25. 25. 24 © 2018 FUJITSU Q&A In case we haven’t answered your questions at FF2018, you can contact any time  Galina Musina  Head of Retail Vertical/Head of Service Delivery, Russia GDC, GSDU, Fujitsu  Mobile: +7 (919) 6219884  E-mail: Galina.Musina.GDC@ts.fujitsu.com  Dmitry Kashtanov  Head of Digital R&D and Business Innovation, Russia GDC, GSDU, Fujitsu  Mobile: +7 (917) 9060910  E-mail: Dmitry.Kashtanov.GDC@ts.fujitsu.com
  26. 26. Fujitsu Sans Light – abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789 ¬!”£$%^&*()_+-=[]{};’#:@~,./<>?| ©¨~¡¢¤¥¦§¨ª«»¬- ®¯°±²³µ¶·¸¹º¼½¾¿ÀÁÂÃÄÅÇÈÆÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûü ýþÿĐıŒœŠšŸŽžƒʼˆˇˉ˙˚˛˜˝·-‒–—―‘’‚“”„†‡•…‰‹›‾⁄⁰⁴⁵⁶⁷⁸⁹₀₁₂₃₄₅₆₇₈₉€™Ω→∂∆∏∑−√∞∫≈≠≤≥⋅■◊fifl Fujitsu Sans – abcdefghijklmnopqrstuvwxyz 0123456789 ¬!”£$%^&*()_+-=[]{};’#:@~,./<>?| ©¨~¡¢¤¥¦§¨ª«»¬- ®¯°±²³µ¶·¸¹º¼½¾¿ÀÁÂÃÄÅÇÈÆÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúû üýþÿĐıŒœŠšŸŽžƒʼˆˇˉ˙˚˛˜˝·-‒–—―‘’‚“”„†‡•…‰‹›‾⁄⁰⁴⁵⁶⁷⁸⁹₀₁₂₃₄₅₆₇₈₉€™Ω→∂∆∏∑−√∞∫≈≠≤≥⋅■◊fifl Fujitsu Sans Medium – abcdefghijklmnopqrstuvwxyz 0123456789 ¬!”£$%^&*()_+- =[]{};’#:@~,./<>?| ©¨~¡¢¤¥¦§¨ª«»¬- ®¯°±²³µ¶·¸¹º¼½¾¿ÀÁÂÃÄÅÇÈÆÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùú ûüýþÿĐıŒœŠšŸŽžƒʼˆˇˉ˙˚˛˜˝·-‒–— ―‘’‚“”„†‡•…‰‹›‾⁄⁰⁴⁵⁶⁷⁸⁹₀₁₂₃₄₅₆₇₈₉€™Ω→∂∆∏∑−√∞∫≈≠≤≥⋅■◊fifl

×