Effectively Culturing a Healthy Culture and Workflow - DevOps Days Tel Aviv 2016

Transcript

1. Effectively Culturing a Healthy Culture And Workflow DevOps Days Tel Aviv 2016
2. Jeff Pierce Operations Eng @ Remind https://remind.com jeff@remind101.com https://github.com/jeffpierce @Th3Technomancer https://speakerdeck.com/ technomancer
3. About Jeff • Stints at Apple, Rackspace, and change.org • Project Lead and Developer on Cassabon (https:// github.com/jeffpierce/ cassabon) • Blogs infrequently at almostinteresting.net
5. Culture and Workflow
6. Culture and Workflow • Personal Responsibility
7. Culture and Workflow • Personal Responsibility • Choose an application architecture philosophy and stick to it!
8. Culture and Workflow • Personal Responsibility • Choose an application architecture philosophy and stick to it! • Make important decisions before you’re under fire
9. Culture and Workflow • Personal Responsibility • Choose an application architecture philosophy and stick to it! • Make important decisions before you’re under fire • Use existing tools whenever possible
10. Personal Responsibility
11. Personal Responsibility
12. Personal Responsibility • Developers deploy their own code
13. Personal Responsibility • Developers deploy their own code • Requires a strong CI/CD toolchain to get code checked and deployed fast
14. Personal Responsibility • Developers deploy their own code • Requires a strong CI/CD toolchain to get code checked and deployed fast • Requires a robust infrastructure plan that makes rolling back bad deploys easy — like immutable servers!
15. Personal Responsibility • All Hands Pager!
16. Personal Responsibility • All Hands Pager! • Requires a strong set of runbooks for troubleshooting
17. Personal Responsibility • All Hands Pager! • Requires a strong set of runbooks for troubleshooting • Spreads around the pain of on-call duty
18. Personal Responsibility • All Hands Pager! • Requires a strong set of runbooks for troubleshooting • Spreads around the pain of on-call duty • It helps to have a common architecture philosophy to make troubleshooting individual applications easier…
19. Pick an application architecture philosophy…and stick with it!
20. Pick an application architecture philosophy…and stick with it! • 12 Factor App (https://12factor.net) • Use declarative formats for setup automation, to minimize time and cost for new developers joining the project; • Have a clean contract with the underlying operating system, offering maximum portability between execution environments; • Are suitable for deployment on modern cloud platforms, obviating the need for servers and systems administration; • Minimize divergence between development and production, enabling continuous deployment for maximum agility; • And can scale up without significant changes to tooling, architecture, or development practices
21. Pick an application architecture philosophy…and stick with it! • Makes on-boarding new engineers faster!
22. Pick an application architecture philosophy…and stick with it! • Makes on-boarding new engineers faster! • Makes tooling more portable/reusable
23. Pick an application architecture philosophy…and stick with it! • Makes on-boarding new engineers faster! • Makes tooling more portable/reusable • Makes planning for new applications and microservices a breeze!
24. Make decisions when you aren’t under fire!
25. Make decisions when you aren’t under fire! • Mistakes are made when planning is rushed
26. Make decisions when you aren’t under fire! • Mistakes are made when planning is rushed • Plan your objectives on a yearly, quarterly, and per- sprint basis
27. Make decisions when you aren’t under fire! • Mistakes are made when planning is rushed • Plan your objectives on a yearly, quarterly, and per- sprint basis • Write runbooks to remove the amount of thought required at 03:25 and it all goes to hell
28. Make decisions when you aren’t under fire! • Mistakes are made when planning is rushed • Plan your objectives on a yearly, quarterly, and per- sprint basis • Write runbooks to remove the amount of thought required at 03:25 and it all goes to hell • DevOps/Infrastructure teams: Sit in on feature planning!
29. Make decisions when you aren’t under fire! • Mistakes are made when planning is rushed • Plan your objectives on a yearly, quarterly, and per- sprint basis • Write runbooks to remove the amount of thought required at 03:25 and it all goes to hell • DevOps/Infrastructure teams: Sit in on feature planning! • Be proactive, not reactive.
30. Use existing tools when possible
31. Use existing tools when possible • Using tools your company already uses…
32. Use existing tools when possible • Using tools your company already uses… • Reduces training
33. Use existing tools when possible • Using tools your company already uses… • Reduces training • Requires less engineering
34. Use existing tools when possible • Using tools your company already uses… • Reduces training • Requires less engineering • Saves time and money
35. Be the change you want to see! Or, how do I actually get all this in place?!
36. Be the change you want to see • Find a compelling story
37. Be the change you want to see • Find a compelling story • Identify key stakeholders
38. Be the change you want to see • Find a compelling story • Identify key stakeholders • Engage those key stakeholders
39. Be the change you want to see • Find a compelling story • Identify key stakeholders • Engage those key stakeholders • Make a business case
40. Be the change you want to see • Find a compelling story • Identify key stakeholders • Engage those key stakeholders • Make a business case • Prototype your plan
41. Winners ask questions!