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.
Miveo Car-sharing Technologies
… is a leading supplier of complete solutions for car-sharing
including in-vehicle equipmen...
Development department
❖ 4 developers
❖ 20 deployed cloud artifacts
❖ 6 embedded software versions
❖ 1-2 deployments/week
...
Embrace your fears
Devops in a car-sharing cloud context
Anders Qvist, CTO
Typical sprint
❖ 3-4 weeks
❖ Cloud and embedded loosely coupled
❖ Myriad use case variations
Whence come maintenance?
❖ Third-line support
❖ Critical defects
❖ “Uninstrumented” procedures
❖ Reactive systems maintena...
The anatomy of disruption
❖ Steals time
❖ Disrupts flow
❖ Dilutes focus
prod > dev
❖ Familiarity with production
➢ Proactive monitoring
➢ Access to logs
➢ Low-level tools
❖ Engage with running code
➢ Devel...
Some best practices
❖ Feature cherry-picking
❖ Production data access
❖ Stand-up meeting at 11
… that is devops to us
Upcoming SlideShare
Loading in …5
×

Embrace your fears - devops in a car-sharing cloud context | Anders Qvist | LTG-31

1,106 views

Published on

Presentation held at Lean Tribe Gahtering 31 in Gothenburg nov 4th 2015.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Embrace your fears - devops in a car-sharing cloud context | Anders Qvist | LTG-31

  1. 1. Miveo Car-sharing Technologies … is a leading supplier of complete solutions for car-sharing including in-vehicle equipment, driver and operator interfaces, and a solid cloud-based backbone with booking, fleet management and reporting.
  2. 2. Development department ❖ 4 developers ❖ 20 deployed cloud artifacts ❖ 6 embedded software versions ❖ 1-2 deployments/week ❖ Responsible for production system
  3. 3. Embrace your fears Devops in a car-sharing cloud context Anders Qvist, CTO
  4. 4. Typical sprint ❖ 3-4 weeks ❖ Cloud and embedded loosely coupled ❖ Myriad use case variations
  5. 5. Whence come maintenance? ❖ Third-line support ❖ Critical defects ❖ “Uninstrumented” procedures ❖ Reactive systems maintenance
  6. 6. The anatomy of disruption ❖ Steals time ❖ Disrupts flow ❖ Dilutes focus
  7. 7. prod > dev
  8. 8. ❖ Familiarity with production ➢ Proactive monitoring ➢ Access to logs ➢ Low-level tools ❖ Engage with running code ➢ Develop for production ➢ Closure in usage How do we embrace?
  9. 9. Some best practices ❖ Feature cherry-picking ❖ Production data access ❖ Stand-up meeting at 11
  10. 10. … that is devops to us

×