DevOps transformation and the most common mistakes made during this phase.

1. How not to do DevOps

2. Hello!
• Zoltan, 39, geek
• Married, father of two
• With Ustream since 2010
• Dev, Ops, Management

3. Our background
•Online video since 2007
•San Francisco / Budapest
•Freemium / Pro / Enterprise
•IBM acquisition in 2016
•Cloud Video / Watson Media
•Budapest Lab
•10 million lines of code
•Hundreds of servers, dozens of
different services / applications

4. Portfolio – IBM Cloud Video
Streaming Products
Ustream Live and on-demand
video platform
Streaming Manager Advanced
video streaming solution
Streaming Manager for
Enterprise Secure video sharing
for teams and enterprises
Enterprise Content Delivery
Network Scale internal video
delivery with ECDN
Media Products
Video Distribution and
Workflow Simplify ingesting
and compiling metadata
OTT Video Management
Empower creation of video
asset catalogs
Solutions
Watson Video Enrichment
Apps
LiveAd
Production services
Developer APIs

5. The DevOps Transition

6. What is DevOps?
You build it, you run
it
Continuous Integration
Continuous Deployment
Cross-functional teams
Next
Agile
Automate all the things!

7. Cultural Change
Eliminate Silos
Mixing Teams
Trust & Communication
Ownership & Responsibility
Knowledge sharing
Redefine Roles
Everyone on Duty

8. Tooling
CI / CD Pipeline
Automation
Metrics & Dashboards
Monitoring & Alerting
Infrastructure as Code
Microservices
Audit trail

9. The ”DevOps Team” Problem

10. What can go wrong?
We are Devs, we can do monitoring only if some other team builds the tools for us
We are Ops, why would we give you root?
As Auditors, we expect to have Ops to interview about deployment, processes, logs, etc
We had an Ops team, what will they do now?
We are Android / iOS developers, what do we Operate?
We have UX, Product, QA, BI embedded in the team. Can’t we simply have Ops too?

11. Typical Team Setups

12. Typical Team Setups

13. How to solve this?
Share knowledge, build ownership
No dedicated DevOps person, no dedicated DevOps team, but everyone should do DevOps
Having a team build tools is nice (but not required)
You should keep your Ops team (Infrastructure team)
We all row in the same boat

14. Our Team Setup

15. The ”By the Book” Problem

16. Rules, rules, rules
There is a single way to do it right, isn’t there?

17. Avoid Cargo Culting
Repeat: ”We are not Spotify” (Daniel Bryant)
No solution will fit all teams
Focus on the goal, the idea itself
Experiment
Measure outcomes, improve continuously

18. Organizational Challenges

19. Top-down
Change
Good intentions don’t matter if you dictate
No super leader has all information
Refuse / resist / revolt / ignore
Can’t build ownership without autonomy

20. Within a bigger organization
No solution will fit all teams
Size does matter
Internal competition
More teams, more diversity, more ways
Communication issues – distance, time zones
Corporate politics and priorities change
Lead by example

21. Wrapping Up

22. Takeaways
Build trust
Share responsibility
Stay open
Focus on the goal
Involve everyone
Be flexible

23. Books
Continuous Delivery (Jez
Humble, David Farley)
The Phoenix Project (Gene
Kim, Kevin Behr, George
Spafford)
The DevOps Handbook (Gene
Kim, Patrick Debois, John
Willis, Jez Humble)

24. Image credits
Droids - Credit: Flickr/donsolo, CC BY-NC-SA
Mac w Code - https://medium.freecodecamp.org/how-to-go-from-hobbyist-to-professional-developer-
11a8b8a52b5f
Take Away - http://www.indianlodge.co.uk/takeaway.html
Tools - https://www.usertesting.com/blog/2013/11/07/10-tools-every-user-experience-pro-should-know-about/
Ninjas - https://www.lego.com/en-us/ninjago/apps/skybound-1009745d7df641608f79cfb8edf5770d
Lord Business - https://www.freeenterprise.com/open-letter-lego-movie-s-lord-business-i-m-just-misunderstood/
Rules - http://www.mylearning.org/british-values-in-action-protest-and-punishment/images/4-4823/

25. 👏👏👏
Thank you!
Questions?