Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
About cultural change w/Devops
Maciej Lasyk
Atmosphere Shuttle #01 – Kraków
2015-03-26
Is there a need for change?
Is there a need for change?
Is there a need for change?
Is there a need for change?
“agile” and “cloud”:
→ focus on delivery
→ close collaboration
→ lightweight environment and c...
Conway's law (1968)
organizations which design systems ... are
constrained to produce designs which are copies
of the comm...
Ruth Malan (2008)
if the architecture of the system and the
architecture of the organization are at odds, the
architecture...
tightly-coupled vs loosely coupled
lack of face2face embraces modularity
cultural change
modification of a society through innovation,
invention, discovery, or contact with other
societies
DevOPS ?== CAMS
(culture, automation, measurement, sharing)
DevOPS !== CAMS
DevOPS === people!
People
culture automation
measurement sharing
So how do you hire new people?
→ demo days?
→ dedicated HR processes?
→ dedicated HR systems?
→ where do you look for peop...
Dead sea effect
→ most talented evaporates
→ the residue
→ maintenance experts & bus factor == 1
http://brucefwebster.com/...
Dead sea effect
→ most talented evaporates
→ the residue
→ maintenance experts & bus factor == 1
there is a solution...
ht...
How do you keep people motivated?
How do you keep people motivated?
The answer is in psychology!
And it lays there since 1954...
Maslow's hierarchy of needs
Maslow's hierarchy of needs: physiological
Let's say that until it's North Korea than it's ok ;)
Maslow's hierarchy of needs: safety
→ family
→ $$$
→ job security
Maslow's hierarchy of needs: <3 and belonging
→ friendship?
→ is your team your family?
→ do you find yourself in your com...
Maslow's hierarchy of needs: Esteem
→ are you respected?
→ do u need the fame and glory?
→ what about your recognition?
Maslow's hierarchy of needs: self - actualization
→ is your job aligned w/ur interests?
→ do u feel fulfilled?
→ do you fi...
Maslow's hierarchy of needs
How do you keep good people in company?
people don't leave companies; they leave leaders
How do you keep good people in company?
people don't leave companies; they leave leaders
or just one of the most popular r...
most popular reasons.. to leave your company
→ Frustration with the inversion of meritocracy (“organization stupidities”)
...
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...
Ok let's DEVOPS
Ok let's DEVOPS
(originally: “Before diving into the legacy code” / devopsreactions)
DevOps Anti-Types & patterns
This is a copy/paste from
http://blog.matthewskelton.net/ w/my comments
included
Great job Ma...
DevOps Anti-Types
http://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to-flourish/
DevOps Anti-Types
http://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to-flourish/
DevOps Anti-Types
http://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to-flourish/
DevOps Patterns
http://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to-flourish/
DevOps Patterns
http://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to-flourish/
DevOps Patterns
http://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to-flourish/
DevOps Patterns
http://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to-flourish/
DevOps Patterns
http://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to-flourish/
Ok let's CAMS
So – what about non – functional reqs?
Do we know who “owns” those?
→ backups
→ monitoring
→ HA
→ scalability
→ security
→...
C for Culture
→ talk. often. and get along
→ take responsibility - from beginning to the end
→ continuous improvement. ser...
A for Automation
→ it has to be simple. Ansible ftw
→ don't reinvent the wheel. don't fabric
→ don't rebuild the world fro...
M for Measurement
M for Measurement
M for Measurement
→ KISS
→ don't be a hoarder!
→ RRD vs InfluxDB
→ visualize all the things
→ teach teams how to query
S for Sharing
Ah what about archaeology tools?
use Mikado!
About cultural change w/Devops
Maciej Lasyk
Atmosphere Shuttle #01 – Kraków
2015-03-26
About cultural change w/Devops
Upcoming SlideShare
Loading in …5
×

About cultural change w/Devops

11,628 views

Published on

Is Devops CAMS only? What about people and communication? How to embrace Devops culture in a stiff environments?

Published in: Leadership & Management
  • Be the first to comment

About cultural change w/Devops

  1. 1. About cultural change w/Devops Maciej Lasyk Atmosphere Shuttle #01 – Kraków 2015-03-26
  2. 2. Is there a need for change?
  3. 3. Is there a need for change?
  4. 4. Is there a need for change?
  5. 5. Is there a need for change? “agile” and “cloud”: → focus on delivery → close collaboration → lightweight environment and components
  6. 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. 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. 8. tightly-coupled vs loosely coupled lack of face2face embraces modularity
  9. 9. cultural change modification of a society through innovation, invention, discovery, or contact with other societies
  10. 10. DevOPS ?== CAMS (culture, automation, measurement, sharing)
  11. 11. DevOPS !== CAMS DevOPS === people!
  12. 12. People culture automation measurement sharing
  13. 13. So how do you hire new people? → demo days? → dedicated HR processes? → dedicated HR systems? → where do you look for people?
  14. 14. 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/
  15. 15. 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/
  16. 16. How do you keep people motivated?
  17. 17. How do you keep people motivated? The answer is in psychology! And it lays there since 1954...
  18. 18. Maslow's hierarchy of needs
  19. 19. Maslow's hierarchy of needs: physiological Let's say that until it's North Korea than it's ok ;)
  20. 20. Maslow's hierarchy of needs: safety → family → $$$ → job security
  21. 21. Maslow's hierarchy of needs: <3 and belonging → friendship? → is your team your family? → do you find yourself in your company?
  22. 22. Maslow's hierarchy of needs: Esteem → are you respected? → do u need the fame and glory? → what about your recognition?
  23. 23. 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?
  24. 24. Maslow's hierarchy of needs
  25. 25. How do you keep good people in company? people don't leave companies; they leave leaders
  26. 26. How do you keep good people in company? people don't leave companies; they leave leaders or just one of the most popular reasons...
  27. 27. 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
  28. 28. 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
  29. 29. Ok let's DEVOPS
  30. 30. Ok let's DEVOPS (originally: “Before diving into the legacy code” / devopsreactions)
  31. 31. DevOps Anti-Types & patterns This is a copy/paste from http://blog.matthewskelton.net/ w/my comments included Great job Matthew! Thanks!
  32. 32. DevOps Anti-Types http://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to-flourish/
  33. 33. DevOps Anti-Types http://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to-flourish/
  34. 34. DevOps Anti-Types http://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to-flourish/
  35. 35. DevOps Patterns http://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to-flourish/
  36. 36. DevOps Patterns http://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to-flourish/
  37. 37. DevOps Patterns http://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to-flourish/
  38. 38. DevOps Patterns http://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to-flourish/
  39. 39. DevOps Patterns http://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to-flourish/
  40. 40. Ok let's CAMS
  41. 41. So – what about non – functional reqs? Do we know who “owns” those? → backups → monitoring → HA → scalability → security → deployment → upgradability → testability
  42. 42. 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
  43. 43. 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
  44. 44. M for Measurement
  45. 45. M for Measurement
  46. 46. M for Measurement → KISS → don't be a hoarder! → RRD vs InfluxDB → visualize all the things → teach teams how to query
  47. 47. S for Sharing
  48. 48. Ah what about archaeology tools?
  49. 49. use Mikado!
  50. 50. About cultural change w/Devops Maciej Lasyk Atmosphere Shuttle #01 – Kraków 2015-03-26

×