What does devops culture mean for engineers
•3 likes•1,524 views
Report
Share
Download to read offline
These are the slides from my paper at VoxxedDays Singapore 2018 on DevOps culture. The video is at: https://www.youtube.com/watch?v=oHhnq-3Q66U
Recommended
More Related Content
Similar to What does devops culture mean for engineers
Similar to What does devops culture mean for engineers(20)
Recently uploaded
Recently uploaded(20)
What does devops culture mean for engineers
- 1. The Way We Work What does DevOps Culture mean for engineers? @dwmkerr Dave Kerr McKinsey & Company
- 3. I am a technology consultant. @dwmkerr
- 6. What am I going to talk about? @dwmkerr
- 7. DevOps & Culture …and why does this matter to me? @dwmkerr
- 8. What’s the problem that DevOps is trying to solve? @dwmkerr
- 9. Situation We’ve got better at building and we make more changes @dwmkerr
- 10. “Bridge Builder”, 2000, Alex Austin @dwmkerr
- 11. Classical Architecture & Engineering Static requirements Well known strategies Plan well – change is expensive Detailed Roadmap Effective management & planning @dwmkerr
- 12. “Sim City 2000”, Maxis @dwmkerr
- 13. Dynamic requirements Test and learn Be flexible – change is inevitable Progressive Refinement Effective engineering & change control Evolutionary Architecture & Engineering @dwmkerr
- 14. Dynamic requirements Test and learn Be flexible – change is inevitable Progressive Refinement Effective engineering & change control Classical Architecture & Engineering Evolutionary Architecture & Engineering Static requirements Well known strategies Plan well – change is expensive Detailed Roadmap Effective management & planning @dwmkerr
- 16. To deal with complexity, we need make changes. (and we’ve got good at doing that!) @dwmkerr
- 18. Build Faster Set Higher Expectations Set Higher Demands @dwmkerr
- 19. Build Faster Set Higher Expectations Set Higher Demands @dwmkerr
- 20. Situation We’ve got better at building and we make more changes @dwmkerr
- 21. Situation Complication In many organisations, change causes conflict @dwmkerr
- 22. Development Responsible for building new products and services Assigned to build things @dwmkerr
- 23. Operations Responsible for maintaining existing products and services Assigned to maintain stability @dwmkerr
- 24. Development Responsible for building new products and services Assigned to build things Operations Responsible for maintaining existing products and services Assigned to maintain stability @dwmkerr
- 25. Change is the casus belli for a secret war in many organisations @dwmkerr
- 35. Situation Complication In many organisations, change causes conflict @dwmkerr
- 36. Situation Complication Resolution DevOps - a shared responsibility to manage change @dwmkerr
- 37. Development Operations Responsible for building new products and services Assigned to build things Responsible for maintaining existing products and services Assigned to maintain stability @dwmkerr
- 38. DevOps Responsible for building and maintaining new products and services Assigned to build and maintain robust and resilient things @dwmkerr
- 39. So why should we care? @dwmkerr
- 40. Situation Complication In many organisations, change causes conflict @dwmkerr
- 42. …is boring. Show me the code! Conflict… Politics… Bureaucracy… Intransigence… @dwmkerr
- 43. DevOps Culture for Engineers …because engineers can make these changes happen! @dwmkerr
- 44. Learn about DevOps So that you can be an agent for change… @dwmkerr
- 45. @dwmkerr
- 46. Share your knowledge And be ready to learn… @dwmkerr
- 47. Programming Scripting APM Log Management Containers Container Orchestration Dependency Management Versioning Database Querying Database Admin Rack & Stack Physical Infrastructure Data Centre Management Infrastructure-As-Code Immutable Infrastructure SSL Secret Management TCP/IP HTTP DNS Networking VPN Automated Testing Static Analysis Functional Patterns Platforms Languages Mobile Browser Fat Clients Documentation CI/CD @dwmkerr Automation Artifact Management 12-factorCode Quality TDD Virtualisation Linux Sys Admin Backup & Restore
- 48. Programming Scripting APM Log Management Containers Container Orchestration Dependency Management Versioning Database Querying Database Admin Rack & Stack Physical Infrastructure Data Centre Management Infrastructure-As-Code Immutable Infrastructure SSL Secret Management TCP/IP HTTP DNS Networking VPN Automated Testing Static Analysis Functional Patterns Platforms Languages Mobile Browser Fat Clients Documentation CI/CD @dwmkerr Automation Artifact Management 12-factorCode Quality TDD Virtualisation Linux Sys Admin Backup & Restore
- 49. Empathise Because people have different challenges, and devops is a cultural transformation… @dwmkerr
- 50. Fight for institutional learning Healthy organistions invest heavily in learning @dwmkerr
- 51. Online Courses Certification Brown Bags Meetups Conferences Tech Blogging Hackathons Competitions Spikes & POCs Self-Study Hobby Projects Open Source @dwmkerr
- 52. Fight for institutional learning Because everyone has a lot to learn, and in tech if you are not learning then you are moving backwards @dwmkerr
- 53. Fight Toil You should be the first to automate @dwmkerr
- 54. @dwmkerr Copyright Randall Munroe, XKCD #1205 “Is it worth the time?” https://xkcd.com/1205/
- 55. Create observable systems Always think about monitoring, logging, analytics – and consider the ‘human process’ @dwmkerr
- 56. Elevate this discussion Make this topic important @dwmkerr
- 57. Thanks! @dwmkerr dwmkerr.com github.com/dwmkerr linkedin.com/in/dwmkerr
Editor's Notes
- 5m mark: Serving clients across the world, deploying in airports, writing code.
- To me, this is important. This is about allowing us to do what we love the most – build things, tinker, experiment, learn It’s about reducing conflict, making the places we work more exciting and enjoyable places to work out. Cannot escape the nerves that I've missed something out because there is no code, and I am not the only one!!
- - Before we talk about what DevOps is, why we should care, and if we do, what we do about it, it is important to understand where it has come from.
- The way we build has changed dramatically.
- Traditional, building software was like classical architecture Very expensive materials, very expensive construction Known use case, build perfectly, rarely change. Build upon a rickety structure, software made of a foundation which was never designed to be adapted
- A lot more change is happening
- Nowadays, requirements of users are much more flexible Technology is cheaper & faster, change is much more common Now more like city planning: evolutionary architecture Hosting, Zoning, Infrastructure, Traffic, Capacity In the world of software this might be about designing small, modular components which we can swap in and out, or plugin like systems, or APIs which we can have multiple versions of In architecture, this might be containers, service orientation etc etc
- A lot more change is happening
- A lot more change is happening
- Complicated systems Deterministic and predictable, laws are applicable again and again, learn to get *very* good at designing a bridge Role defining – setting job and task descriptions Decision making – find the ‘best’ choice Tight structuring – use chain of command and prioritise or limit simple actions Knowing – decide and tell others what to do Staying the course – align and maintain focus Complex adaptive systems Many interacting parts, which might be deterministic but chaotic, unexpected results, difficult to predict. Relationship building – working with patterns of interaction Sense making – collective interpretation Loose coupling – support communities of practice and add more degrees of freedom Learning – act/learn/plan at the same time Notice emergent directions – building on what works
- - Before we talk about what DevOps is, why we should care, and if we do, what we do about it, it is important to understand where it has come from.
- A lot more change is happening We enter a feedback loop We do whatever we can to build faster, better tech, better process, whatever
- A lot more change is happening We enter a feedback loop We do whatever we can to build faster, better tech, better process, whatever
- A lot more change is happening We enter a feedback loop We do whatever we can to build faster, better tech, better process, whatever
- A lot more change is happening
- A lot more change is happening
- A lot more change is happening
- Business attack anyone with a computer
- Business attack anyone with a computer
- Business attack anyone with a computer
- Business attack anyone with a computer
- Business attack anyone with a computer
- Business attack anyone with a computer
- Business attack anyone with a computer
- Business attack anyone with a computer
- Business attack anyone with a computer
- A lot more change is happening
- A lot more change is happening
- This bullshit slows you down. It’s not fun. And in an organization where you are not learning, you are moving backwards. You can tell how happy I am by how much of my day I am in tmux. Healthy work environment.
- Familiarise yourself with this. Read the books. Learn about lean. Come to conferences. Talk to people. Blog about it. There’s a lot of stuff in devops, getting it to work is not easy, learn about how other people have done it, and learn the skills to do it yourself.
- A lot more change is happening
- A lot more change is happening
- - When someone objects to what you are doing, try to understand why This change takes a while to happen, as you go through it, peoples roles will change, peoples goals will change This is a cultural change
- - Story: talking to a colleague who was paying to do his own exam
- Think about the ‘human case’, when things fall back to human beings
- A lot more change is happening