How GitHub Does Devops

Companies want to know how to transform. They want to change. They want to not be left behind and they want to work in a faster way. People at companies everywhere are racing and are trying to figure out how to drive change and cultural transformation at their companies. In this talk, Brent will help you make the first couple of steps to get you started on this journey.

Transcript

2. Reference: https://searchengineland.com/bidding-competition-really-worth-258398
3. Reference: http://www.dailystar.co.uk/tech/news/591737/Nokia-3310-launch-phone-relaunched-month-battery-new-design-MWC-2017
4. How GitHub Does DevOps Brent Beer @brntbeer Solutions Engineer
5. What is DevOps?
7. HTTP://WWW.EWEEK.COM/ENTERPRISE-APPS/SLIDESHOWS/DEVOPS-5-SIGNS-ENTERPRISES-NEED-TO-UNITE-THE-DEV-AND-OPS-CAMPS.HTML
8. REFERENCE: HTTPS://AWS.AMAZON.COM/DEVOPS/WHAT-IS-DEVOPS/ “DevOps is the combination of cultural philosophies, practices, and tools that increases an organization’s ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes. This speed enables organizations to better serve their customers and compete more effectively in the market.”
10. Organize
11. Tools
12. Tools Reference: https://hbr.org/2015/01/why-a-messy-workspace-undermines-your-persistence
13. Tools Reference: https://en.wikipedia.org/wiki/The_Paradox_of_Choice
14. Tools Reference: https://www.gardenbuildingsdirect.co.uk/blog/garden-shed-garage-organising-ideas/
15. People
16. People
17. People Reference: https://www.youtube.com/watch?v=KndSVsY5HWM
18. People Reference: https://www.youtube.com/watch?v=KndSVsY5HWM
19. People
20. Step 1 • Grab some tools your developers are using today. Lay them out on the table and remove some if need be, but keep some even if they completely overlap (CI tools may be an easy one to think about). • Additionally, group some people together, but let them stay fluid. People may move to new tools or new tools will move to people.
21. Communicate
22. Reference: https://devops.com/devops-culture-mind-matter/ “Even if an org is full-on DevOps, there is still the requirement of cross-team communications to make sure everyone understands what is going on. […] Increase communication, not chatter.” - Don Macvittie, DevOps.com
23. Reference: http://itribesolutions.com/email_appending.php
24. Reference: https://slackhq.com/email-meet-slack-slack-email-1d5b36a68e79
25. Reference: http://www.blackberryos.com/content/verizon-z10-owners-heres-why-you-cant-download-whatsapp-blackberry-world-yet-5651/
26. Reference: https://www.createful.com/2017/beware-slack-trap/
27. Reference: https://www.forbes.com/sites/theodorecasey/2017/09/08/new-slack-clone-highlights-a-generational-divide-in-chat/#6aad4cfe7600 “Slack is easy for me because I grew up with AOL Instant Messenger and chat rooms. I can make sense of it. It must be even easier for kids who grew up with texting.” - Theo Miller, Forbes Contributor
28. Asynchronous best practices • Only use private messages when you absolutely have to, e.g. for privacy, legal, HR, or other reasons that make a discussion sensitive. • NEVER EVER do this: “@ username can i ask you a question?” Just ask the question. • When you respond to someone’s question in chat, unless it’s 30 seconds after they asked, @ them by username • Expect chat to be asynchronous, people will respond to you when they are able. • Don’t stare at your chat client all day, it’s easy to fool yourself into thinking replying to chats is the same as being productive. Reference: https://medium.com/@danielhengeveld/best-slacktices-e0cdfc050dd2
34. Step 2 • Choose to communicate more asynchronously. Be more open and let your coworkers bond and share ideas as often as possible. If they struggle with the new forms of communication, be patient and have empathy. Help them out.
35. Develop
36. Workflow Prerequisites • You’re using Git • You know your tools you planned on step 1 are involved • You want to do code review (automated and/or peer) • You want to deploy and iterate as fast as possible
41. Tools Reference: https://www.gardenbuildingsdirect.co.uk/blog/garden-shed-garage-organising-ideas/
42. Step 3 • If you pick a platform for combining all your tools, people, and working with good communication that doesn’t allow you to stay flexible and make these changes, you will never reach your full potential.
43. Next steps We just talked about a lot of things.
44. Take a deep breath
45. Recap • Step 1: Bundle your tools together to give your people choice. People also need to know how to move teams or move tools to their team • Step 2: Choose a communications platform that is open and promotes good asynchronous communication. This tool should also integrate well with some other tools from step 1. • Step 3: Pick a platform that allows you to implement steps 1 and 2 flawlessly, and allows you to grow as well. • (Bonus) Step 4: When the moment is right, revisit steps 1-3. Iterate and improve
48. Reference: https://octoverse.github.com/