Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Continuous Delivery on Mobile

Continuous Delivery on Mobile

Given at Delivery World of Things 2016

Alexander Greim

April 25, 2016
Tweet

More Decks by Alexander Greim

Other Decks in Technology

Transcript

  1. 4

  2. How We Built Mobile Apps Before 9 • Single agile

    team with 4 developers + QA • Building every facet of the app • Collaboration with domain teams
  3. Growing Demand Inside the Company 10 • Mobile use cases

    • Additional products • Increased user activity
  4. Scaling Mobile at XING 11 1. Split apps into modules

    2. Build a release train 3. Make all teams mobile-ready
  5. 1. Split Apps into Modules 12 • Loose coupling of

    sections • Shared libraries …
  6. 2. Build a Release Train 13 • Frequent, periodic releases

    • Fixed dates, fixed quality, variable scope • Stabilisation phase
  7. 3. Make All Teams Mobile-Ready 14 • Hiring additional developers

    • Onboarding in central team • Training QA, UX, Product … Fully functional agile team
  8. Development Process in Teams • Focus on rapid value delivery

    • Planning and release contribution • Assuring functional quality 16 Iteration Analyse Develop Test Design Upstream α α
  9. Release Train Process 18 • Driven by the Platform Team

    • Assuring final quality • Highly automated
  10. What’s special about releasing on Mobile • Packaged software •

    High fragmentation • Automated testing still complex 23
  11. Android Device Fragmentation 24 Source: Open Signal Android Fragmentation Report

    - http://opensignal.com/reports/2015/08/android-fragmentation/
  12. What’s Ahead: Optimising Time to Market • Reducing rollout time

    by 40% 26 QA Pre-Release Development Stage LIVE Rollout Time