DevOps @ KnowIT

Talk on DevOps at a breakfast seminar hosted by KnowIT.

Transcript

1. Hello!
2. * I’m Mårten * I tend to work at companies with blue logos
3. * Today, this: Omni * 13 devs (backend: 7+3 & frontend: 2+2) * I head up the backend & infrastructure team
4. Infrastructure aware development and vice versa
5. Why?
6. Awareness * Become aware of what happens outside “our bubble” * Become aware of why “things” are happening
7. Understanding * Understanding why things are the eay they are * Understanding that what appears bad to me, might appear good to someone else
8. Precision * Less confustion * Higher pace * Quicker to find the “right direction”
9. Co-planning * If we understand and are aware it’ll be easier to plan together * If we plan together we’ll become aware and understand each other
10. We’re on the same team!
11. “No, we’re not!” * (get a grip)
12. co-lo get a sysops * in your team * (per team?) * contract or hire * full or part-time
13. managed hosting customer responsible technician * whom you assimilate! * get person on chat, mailing lists, etc * invite to lunch, AW, whatever
14. cloud == co-lo get a sysops * I consider cloud based servers as co-lo
15. PaaS sysop 2.0? * PaaS, e.g. Heroku, will force a bigger responsibility on DEV * and/or a completely different kind of OPS * I’m not sure here, yet
16. How?
17. Don’t know. * There’s no exact answer as to “how”
18. Why?
19. Higher pace. * Do X in half the time? * Do X with half the people involved? * More time and or people to do Y and Z!
20. Higher quality. * Avoid the most common mishaps? (without loosing pace!)
21. Higher awareness.
22. Higher engagement. * if more of the involved have higher awareness we’ll get a higher engagement and we’ll increase quality and deliver faster
23. Key. Words.
24. Cooperate. * Make it natural * Make it easy
25. Communicate. * Direct, clear, concise, transparent
26. The rest will “sort itself” out. * Not quite, but almost
27. Hints
28. Find “like-minded”
29. Invite. * Invite all “the others” to planning, stand-ups, coffee, AW, etc * As with all transformations it won’t happen in an instant and it’ll be shaped over time
30. Guerrilla cooperation. * (my personal favorite) * Tend to work really well * Easier to ask for forgiveness than approval
32. 1. Get to know each other
33. 1. Get to know each other 2. Involve each other
34. 1. Get to know each other 2. Involve each other 3. Start doing things together
35. 1. Get to know each other 2. Involve each other 3. Start doing things together 4. Think strategic together
36. 1. Get to know each other 2. Involve each other 3. Start doing things together 4. Think strategic together 5. Stop viewing others as “others”
37. 1. Get to know each other 2. Involve each other 3. Start doing things together 4. Think strategic together 5. Stop viewing others as “others” 6. Do a project together
38. Culture. * DevOps is culture * DevOps is not an automated infrastructure (automation is a product, project, whatevs) * DevOps is not a title * Culture happens when individuals work together
39. “An organizations culture isn’t in ‘the walls’. It’s in the people”