About cultural change w/Devops
•Download as ODP, PDF•
1 like•12,339 views
Is Devops CAMS only? What about people and communication? How to embrace Devops culture in a stiff environments?
Report
Share
More Related Content
What's hot
What's hot (20)
Similar to About cultural change w/Devops
Similar to About cultural change w/Devops (20)
More from Maciej Lasyk
More from Maciej Lasyk (20)
Recently uploaded
Recently uploaded (20)
About cultural change w/Devops
- 1. About cultural change w/Devops Maciej Lasyk Atmosphere Shuttle #01 – Kraków 2015-03-26
- 2. Is there a need for change?
- 3. Is there a need for change?
- 4. Is there a need for change?
- 5. Is there a need for change? “agile” and “cloud”: → focus on delivery → close collaboration → lightweight environment and components
- 6. Conway's law (1968) organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations http://en.wikipedia.org/wiki/Conway%27s_law
- 7. Ruth Malan (2008) if the architecture of the system and the architecture of the organization are at odds, the architecture of the organization wins. The organizational divides are going to drive the true seams in the system. http://traceinthesand.com/blog/2008/02/13/conways-law/
- 8. tightly-coupled vs loosely coupled lack of face2face embraces modularity
- 10. cultural change modification of a society through innovation, invention, discovery, or contact with other societies
- 11. DevOPS ?== CAMS (culture, automation, measurement, sharing)
- 12. DevOPS !== CAMS DevOPS === people!
- 14. So how do you hire new people? → demo days? → dedicated HR processes? → dedicated HR systems? → where do you look for people?
- 15. Dead sea effect → most talented evaporates → the residue → maintenance experts & bus factor == 1 http://brucefwebster.com/2008/04/11/the-wetware-crisis-the-dead-sea-effect/
- 16. Dead sea effect → most talented evaporates → the residue → maintenance experts & bus factor == 1 there is a solution... http://brucefwebster.com/2008/04/11/the-wetware-crisis-the-dead-sea-effect/
- 17. How do you keep people motivated?
- 18. How do you keep people motivated? The answer is in psychology! And it lays there since 1954...
- 19. Maslow's hierarchy of needs
- 20. Maslow's hierarchy of needs: physiological Let's say that until it's North Korea than it's ok ;)
- 21. Maslow's hierarchy of needs: safety → family → $$$ → job security
- 22. Maslow's hierarchy of needs: <3 and belonging → friendship? → is your team your family? → do you find yourself in your company?
- 23. Maslow's hierarchy of needs: Esteem → are you respected? → do u need the fame and glory? → what about your recognition?
- 24. Maslow's hierarchy of needs: self - actualization → is your job aligned w/ur interests? → do u feel fulfilled? → do you find time for self – development?
- 25. Maslow's hierarchy of needs
- 26. How do you keep good people in company? people don't leave companies; they leave leaders
- 27. How do you keep good people in company? people don't leave companies; they leave leaders or just one of the most popular reasons...
- 28. most popular reasons.. to leave your company → Frustration with the inversion of meritocracy (“organization stupidities”) → Simple boredom → Perception that current project is futile/destined for failure accompanied by organizational powerlessness to stop it → Lack of a mentor or anyone from whom much learning was possible → Promotions a matter of time rather than merit → No obvious path to advancement → Fear of being pigeon-holed into unmarketable technology → Red-tape organizational bureaucracy mutes positive impact that anyone can have → Lack of creative freedom and creative control (aka “micromanaging”) http://www.daedtech.com/how-to-keep-your-best-programmers
- 29. The real role of 1:1s → this is time for your guys → this is not a status update → make sure you always have time for your guys
- 30. Ok let's DEVOPS
- 31. Ok let's DEVOPS (originally: “Before diving into the legacy code” / devopsreactions)
- 32. DevOps Anti-Types & patterns This is a copy/paste from http://blog.matthewskelton.net/ w/my comments included Great job Matthew! Thanks!
- 41. Ok let's CAMS
- 42. So – what about non – functional reqs? Do we know who “owns” those? → backups → monitoring → HA → scalability → security → deployment → upgradability → testability
- 43. C for Culture → talk. often. and get along → take responsibility - from beginning to the end → continuous improvement. seriously → be brave. don't be silent → it's better to be unpolite l/German than polite l/Englishman
- 44. A for Automation → it has to be simple. Ansible ftw → don't reinvent the wheel. don't fabric → don't rebuild the world from scratch → imperativeness vs declarativeness → automate from very beginning. devs - automate
- 47. M for Measurement → KISS → don't be a hoarder! → RRD vs InfluxDB → visualize all the things → teach teams how to query
- 48. S for Sharing
- 49. Ah what about archaeology tools?
- 50. use Mikado!
- 51. About cultural change w/Devops Maciej Lasyk Atmosphere Shuttle #01 – Kraków 2015-03-26
Editor's Notes
- Tutaj info o historii devopsów – począwszy od 1 – osobowej instytycji
- Tutaj info o historii devopsów – począwszy od 1 – osobowej instytycji
- Tutaj info o historii devopsów – począwszy od 1 – osobowej instytycji
- Tutaj info o historii devopsów – począwszy od 1 – osobowej instytycji