- a straight line between ops and dev. #devops
- knowing ops best practices and applying them to the operational requirements of stable dev teams #evangelist
- making the ops team aware of the operational situation facing each team
- document and share
Initially:
- evaluate current operational status
- make plans to bring infrastructure into line with our best practices
- document all of it
- understand future requirements
- assist in the setup of each teams Specialist on Duty Pagerduty escalation
- convert any checks or set up new ones to point at that contact
- assist with New Relic implementation, preferred PD alert method
- attend at least 1 standup weekly
- liaison with the TPM for project kickoffs
- communicate with ops manager for priorities and due dates
- self assessment of effectiveness on your team
- where possible, cross reference sprint items
- make your own tasks for the sprint, or open time slots
- requests still belong to on call and wrangler, who should have no problem doing things #docs #demos
- teams picked on previous experience and preference
- switching teams is always an option
- understand the workload and time estimation
Primary
Platform - Jonas, Mishra, Gonzalo
Publishing - Matt, Ron
Webops - Patrick, Mishra
Labs - Patrick, Jeff
Secondary
IT - Jeff, Ron
Sec - Ron, Jeff
Ads - Patrick
Mobile - Matt
CoreUX - Jonas
Tertiary
Support - Jeff
Customer Success - Mishra
- follows week on call
- cost savings analysis, tagging and EBS cleanup - 1 day
- post on call / 5 why followup - .5 days
- backup analysis - .5 days
By Jeff Oliver
