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

DevOpsPorto Meetup24: UXIDevOps: The Trojan Horse for Implementing a DevOps Culture by Domingos Da Silva

DevOpsPorto
February 19, 2019

DevOpsPorto Meetup24: UXIDevOps: The Trojan Horse for Implementing a DevOps Culture by Domingos Da Silva

Talk delivered by Domingos Da Silva

DevOpsPorto

February 19, 2019
Tweet

More Decks by DevOpsPorto

Other Decks in Technology

Transcript

  1. UXIDevOps
    The Trojan Horse for Implementing
    a DevOps Culture

    View Slide

  2. Lead Infrastructure Engineer @ Farfetch
    Domingos Da Silva
    @domlinkgos
    [email protected]
    Game Designer @ Sunken Ship

    View Slide

  3. WTF is UXIDevOps?
    (Because playing with the word “DevOps” is fun)

    View Slide

  4. Going by the Wiki

    View Slide

  5. View Slide

  6. UX for DevOps
    Or
    DevOps for UX?

    View Slide

  7. View Slide

  8. View Slide

  9. Take-Away

    View Slide

  10. View Slide

  11. View Slide

  12. The Jenkins Case

    View Slide

  13. The Jenkins Case

    View Slide

  14. DogFooding

    View Slide

  15. Do you Believe in Magic?

    View Slide

  16. View Slide

  17. View Slide

  18. version: 1
    platform: porto
    boundary: delivery
    name: portodevops
    description: service to manage the logistics entities like
    couriers services and accounts
    maintainers:
    - name.surname
    project_type: service
    tech_type: dotnet_core
    repository: https://repo.farfetch/porto/portodevops.git
    package: porto_portodevops
    dependencies:
    - platform: porto
    boundary: infra
    name: cassandra2
    specs:
    keyspace: porto_portodevops
    ports:
    loadbalancer_ports:
    - 9250
    service_ports:
    - 9250
    The Blueprint Concept

    View Slide

  19. telemetry:
    active_healthcheck: /monitoring/ping
    deep_healthcheck: /monitoring/pong
    security:
    context: standard
    metadata:
    tier: 0
    business_unit: farfetch
    environment_specific:
    - environment: dev
    datacenter: we1
    domain: porto.devops.com
    scale:
    min_instance_count: 1
    max_instance_count: 1
    min_cpu: 1
    max_cpu: 2
    min_memory: 1
    max_memory: 2
    credentials:
    porto_infra_cassandra2_username: ENC[GrF7DhxRqYTQo=]
    porto_infra_cassandra2_password: ENC[Ws2amfN9isW95=]
    - environment: prd
    datacenter: we1
    domain: porto-delivery-portodevops.farfetch.net
    The Blueprint Concept

    View Slide

  20. View Slide

  21. View Slide

  22. View Slide

  23. View Slide

  24. View Slide

  25. View Slide

  26. View Slide

  27. Visibility is Peace of Mind

    View Slide

  28. View Slide

  29. View Slide

  30. View Slide

  31. Automagically

    View Slide

  32. UXing your DevOps
    “B-B-B”

    View Slide

  33. User Behaviors
    User Research
    Usability
    Iteration
    Iteration
    Iteration
    Iteration

    View Slide

  34. The Big Questions
    ● Who are we building for? Who is the end user of our tool?
    ● What are they trying to achieve? What goal does the user have?
    ● What is the level of knowledge you are building for? What’s the overall
    knowledge of our user base?
    ● How can we improve adoption rather than imposing a working tool?
    ● Are we building with our users in mind or based on how we would like it to
    work for us?

    View Slide

  35. The Cultural Problem
    “Get Stuff Done”

    View Slide

  36. View Slide

  37. View Slide

  38. Driving the Change
    Get Management Buy-In.
    Start UX planning early.
    It's all about collaboration.
    Drive smart prioritization.
    Designers need visibility into the product backlog.
    Make sure UX participates at every stage.
    Stick to basic UX design, but remain agile.
    Incorporate feedback quickly.

    View Slide

  39. Flash Round

    View Slide

  40. Visual Monitoring

    View Slide

  41. Visibility is Peace of Mind

    View Slide

  42. Gamification

    View Slide

  43. View Slide

  44. ChatOps

    View Slide

  45. View Slide

  46. If we are not building something that
    simplifies our users experience with our
    systems, no matter how beautiful it is, we
    are not building a good service.

    View Slide