QEOPS (Development, Ops, and QE) with Behance

Advice on building a QEOPS culture at your company. Recommendations for Developers, Operation Engineers, Business Development, and Analysts.

Transcript

1. QEOPS AT BEHANCE // MALCOLM JONES OPERATIONS ENGINEER //@BOSSJONES
2. QEOPS (DEVELOPMENT, OPS, AND QE) WITH BEHANCE
3. AKA, HOW WE GET SHIT DONE AT BEHANCE.
4. WHO AM I? AND WHY DOES HE CALL HIMSELF BOSSJONES?
6. UNCUBED GOT ME MY DREAM JOB
7. What is the Behance story Devops & its role in a company culture How QEOPS improves on said culture Specifics on getting shit done Questions?
8. WHAT DOES BEHANCE DO?
10. Attribution & Exposure
11. PROSITE Personal portfolio sites powered by Behance
12. SERIES A May, 2012 Union Square Ventures Top Angels
13. ACQUISITION December, 2012 100% Retention - 2 Years Team growth to ~62
14. CREATIVE TALENT SEARCH Connecting the world’s best creative talent with the best opportunities
15. Discover Candidates
16. Manage Your Search
17. LETS QUICKLY TALK ABOUT DEVOPS
18. SO WHAT IS QEOPS THEN?
19. WE <3 TECHNOLOGY BLEEDING EDGE HIPPIE PROGRAMMERS
20. iOS USES TOP TECHNOLOGY
21. • Distributed Decision Making (be closer to the problem) • Communication (who are you again?) • Process & tools as enablers vs process as an end • Specialization yet understanding the bigger picture • Go Alone when you are proving a concept. Rally the troops when you’re ready to scale. • Visibility empowering the team by giving them insight into how things are performing across all tiers.
 
 Test All The Things static checks, unit tests, integration tests, smoke tests, End to end tests, DPXDT. ORGANIZATIONAL DESIGN :: HOW WE WORK
22. DECISION MAKING Be closer to the problem.
23. COMMUNICATION “You’ve got FaceMail” -Jackie & Zach
24. COMMUNICATION Working with remote teams :: over communicate
25. COMMUNICATION Assume no one knows what is happening (and then be pleasantly surprised)
26. COMMUNICATION Over communicate, be annoying!
27. COMMUNICATION: TRELLO
28. COMMUNICATION: TABLEAU
29. COMMUNICATION: DATA DOG
30. COMMUNICATION: AMAZON REDSHIFT
31. COMMUNICATION: HADOOP
32. COMMUNICATION: SUMOLOGIC
33. COMMUNICATION: SLACK
34. PROCESS When it stops working, stop doing it. (ask: why are we doing it this way?)
35. SPECIALIZATION Growth leads to specialization. Take the time to understand the BIG picture.
36. GOING ALONE VS TOGETHER Knowing when to be self-sufficient, and when to tap into the broader resources.
37. TEST ALL THE THINGS Just do it.
38. One deploy a day is a culture change, one hundred deploys a day are an implementation detail “ ” - - Mathias Meyer, Travis CI @ #conli2014
39. CONTINOUS DEPLOYMENT!
40. YO DAWG I HEAR YOU LIKE DEPLOYING
41. MOONBEAM DEPLOY ALL THE THINGS
46. OUR QE TEAM AUTOMATED THEMSELVES OUT OF WORK AND CAN NOW FOCUS ON BUILDING TOOLS THAT IMPROVE OUR WORKFLOW
47. THANK YOU! MALCOLM JONES // @BOSSJONES