You build it, but you ain't gonna run it – DevOps practices for IT providers

The DevOps movement tries to break down silos between Dev and Ops and foster an intensive collaboration between both parties. Many companies have been improving their internal adoption of DevOps practices over the last few years. But if they employ external IT suppliers, often the old silos arise again. The solution is built by the supplier and operated by customer after being handed over.

It’s possible to adopt DevOps practices as an external IT supplier though. I will show you some patterns and practical examples to do so.

Transcript

1. Konstantin Diener | konstantin.diener@cosee.biz | @coseeaner
   DevOps practices for IT providers
   You build it,
   
   
   but you ain't gonna run it
   

   View Slide

2. View Slide

3. • as many Features as possible
   
   
   • quick response
   
   
   • Scrum: Shippable Product
   • stable application
   
   
   • no Incidents or major bugs
   
   
   • no Downtimes
   >> throughput >> stability
   Development Operations
   

   View Slide

4. https://de.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr/
   

   View Slide

5. Spock Scotty
   Little bit weird
   Sits closer to the boss
   Thinks too hard
   Pulls levers & turns knobs
   Easily excited
   Yells a lot in emergencies
   https://de.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr/
   

   View Slide

6. https://de.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr/
   Ops’ job is to enable the business
   (this is dev’s job too)
   

   View Slide

7. You build it,
   you run it.
   “
   Werner Vogels
   

   View Slide

8. Maybe that’s true for
   
   
   product
   organisations, but …
   

   View Slide

9. … when an
   IT supplier
   comes into play it’s o
   ft
   en …
   
   
   

   View Slide

10. You build it,
    
    
    but you ain’t
    gonna run it.
    

    View Slide

11. Konstantin Diener
    CTO and Co-Founder of
    cosee
    

    View Slide

12. Start Scale
    product development
    

    View Slide

13. But, what’s the
    
    
    di
    ff
    erence?
    

    View Slide

14. Customers
    Client
    Supplier
    

    View Slide

15. View Slide

16. Spock Scotty
    Little bit weird
    Sits closer to the boss
    Thinks too hard
    Pulls levers & turns knobs
    Easily excited
    Yells a lot in emergencies
    https://de.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr/
    

    View Slide

17. View Slide

18. What’s the
    
    
    alternative?
    

    View Slide

19. Accelerate
    Nicole Forsgren, Jez Humble,
    Gene Kim
    

    View Slide

20. Pathological
    
    
    (Power-Oriented)
    Bureaucratic
    
    
    (Rule-Oriented)
    Generative
    
    
    (Performance-Oriented)
    Low cooperation Modest cooperation High cooperation
    Messengers “shot” Messengers neglected Messengers trained
    Responsibilities shirked Narrow responsibilities Risks are shared
    Bridging discouraged Bridging tolerated Bridging encouraged
    Failure leads to scapegoating Failure leads to justice Failure leads to inquiry
    Novelty crushed Novelty leads to problems Novelty implemented
    

    View Slide

21. Generative
    organizations focus on
    the mission. How do we
    accomplish our goal?
    Accelerate
    

    View Slide

22. What’s the
    
    
    client’s goal?
    

    View Slide

23. Why
    
    
    do we build products?
    

    View Slide

24. User Story Mapping
    Je
    ff
    Patton
    

    View Slide

25. Je
    ff
    Patton, User Story Mapping, https://jpattonassociates.com/
    

    View Slide

26. Your company can’t get
    what it wants unless your
    customers and and users
    get something they want.
    “
    Je
    ff
    Patton
    

    View Slide

27. Je
    ff
    Patton, User Story Mapping, https://jpattonassociates.com/
    

    View Slide

28. Customers
    Client
    Supplier
    

    View Slide

29. Customers
    Client
    Supplier
    

    View Slide

30. Vision Statement Kurze Beschreibung der Vision/Idee
    Zielgruppe
    Welches Marktsegment/Ziel- oder Nutzer-
    gruppe soll das Produkt ansprechen?
    Dieser Punkt kann auch in Form einer
    Persona beschrieben sein.
    Bedürfnisse/Probleme
    Welche Bedürfnisse der Zielgruppe werden
    befriedigt?
    In welcher Form schafft das Produkt Wert
    für den Benutzer oder empfindet er es als
    wertvoll?
    Welche Emotionen weckt das Produkt?
    Top Features
    Welches sind die drei bis fünf wichtigsten
    Funktionen?
    Gibt es ein Alleinstellungsmerkmal (USP)?
    Geschäftsmodell
    Wie wird mit dem Produkt Geld verdient?
    Wer sind die zahlenden Kunden?
    Was ist der Kunde bereit zu bezahlen und
    wie bezahlt er?
    Konkurrenz
    Gibt es Organisationen am Markt,
    die ein ähnliches Produkt anbieten?
    Differenznutzen
    Was bietet das Produkt mehr, weniger
    oder anders gegenüber vergleichbaren
    Produkten?
    angelehnt an http://www.romanpichler.com/tools/vision-board
    cosee_VisionStatement_Plakat2019_ Druck.indd 1 15.11.18 10:17
    

    View Slide

31. Understand
    
    
    what’s the real
    
    
    customer need …
    

    View Slide

32. … and don’t just
    implement a wish
    list of features.
    

    View Slide

33. Je
    ff
    Patton, User Story Mapping, https://jpattonassociates.com/
    

    View Slide

34. Small
    
    
    Experiments
    
    
    Batch Sizes
    

    View Slide

35. Every Release is a
    
    
    working product.
    

    View Slide

36. Use
    
    
    Continuous
    Integration!
    

    View Slide

37. We do! ✅
    

    View Slide

38. Really? 🤔
    

    View Slide

39. Trunk Based
    Development?
    

    View Slide

40. #NoFeatureBranches
    

    View Slide

41. Continuous Delivery
    Jez Humble,
    David Farley
    

    View Slide

42. Use
    
    
    Continuous
    Delivery!
    

    View Slide

43. Application is
    always in a
    releasable state.
    

    View Slide

44. + +
    Repo Build
    Executable
    Repo Pipeline
    running product
    = =
    

    View Slide

45. Let production be
    
    
    „yet another
    environment“.
    

    View Slide

46. t
    Application
    Infrastructure
    

    View Slide

47. Je
    ff
    Patton, User Story Mapping, https://jpattonassociates.com/
    

    View Slide

48. Run your application in
    production.
    

    View Slide

49. t
    Code
    Infrastructure
    

    View Slide

50. Build
    
    
    metrics & alerting
    in.
    

    View Slide

51. Eat your own
    
    
    dog food.
    

    View Slide

52. Learn your application footprint by
    early performance
    tests.
    

    View Slide

53. We want to ship continuously, but we
    have to
    
    
    wait for the client’s …
    

    View Slide

54. Legal
    designers
    sales team
    Content
    Authors
    IT
    Marketing
    

    View Slide

55. View Slide

56. Use DevOps
    
    
    collaboration models
    
    
    to
    avoid silos.
    

    View Slide

57. Team Topologies
    Matthew Skelton &
    Manuel Pais
    

    View Slide

58. Embedding
    Inspired by devopstopologies.com
    

    View Slide

59. Embedding x as a Service
    Inspired by devopstopologies.com
    

    View Slide

60. Site Reliability
    Engineering
    

    View Slide

61. Embedding x as a Service Collaboration
    Inspired by devopstopologies.com
    

    View Slide

62. Use DevOps collaboration models for
    handover &
    onboarding.
    

    View Slide

63. Embedding x as a Service Collaboration
    Inspired by devopstopologies.com
    

    View Slide

64. Use
    
    
    blameless postmortems
    
    
    to
    share knowledge
    
    
    about the application with the client.
    

    View Slide

65. Use
    basic
    
    
    DevOps practices …
    

    View Slide

66. Make
    work visible
    
    
    … also to the client.
    

    View Slide

67. Shi
    ft
    le
    ft
    . ⬅
    

    View Slide

68. Everybody is
    
    
    responsible.
    

    View Slide

69. Continuous
    Improvement 💪
    

    View Slide

70. Discovery-
    Phase
    Backlog
    Expert-Teams
    Billing
    Models
    Iterative
    Delivery
    Software-
    Releases
    

    View Slide

71. konstantin.diener@cosee.biz | @onkelkodi
    Picture credits:
    
    
    Boat: https://www.shutterstock.com/de/g/solovushka
    
    
    Silos: https://www.shutterstock.com/de/g/davotibarna
    
    
    Gated Bridge: https://www.istockphoto.com/de/portfolio/vesilvio
    Interested?
    Konstantin Diener | cosee GmbH
    cosee.biz
    

    View Slide