We serve the function of Product Infrastructure and Software Operations, and those executing against its assignments. Our goal is continuous improvement of the tools and processes (balancing autonomy and focusing on feedback loops).
Expectations / Description
Key Results/Outcomes
ENGAGEMENT:
- The people taking on the roles listed within the Engineering / Development domain, agree or strongly agree to the following statements:
- I know how I’m being evaluated on these roles.
- I receive actionable (meaning timely, frequent, specific, and observation-based) constructive feedback on my performance within the roles identified above.
- I receive actionable (meaning timely, frequent, specific, and observation-based) recognition (public or private) on my performance within the roles identified above.
- I believe I have the tools to meet or exceed the outcomes listed within the roles in question.
- I believe I have the processes and environment to meet or exceed the outcomes listed within the roles in question.
- I believe we are continuously improving in how we go about taking on these roles.
- Note: This SHOULD have a direct impact on the NPS score of engineers (where they select 8+ on a 10-point scale to the question; “I’d recommend a friend come to work here”). However, given that full engagement is more inclusive than their primary roles, it doesn’t feel right to have that as a part of the measure of enablement leads.
ACTIVITIES / RESPONSIBILITIES:
- Manage Infrastructure Costs
- Monitor infrastructure costs
- Provide estimates for future costs
- Work to reduce costs where possible
- Coordinate Maintenance
- Make sure all parts of the company are on the same page regarding maintenance
- Manage third-party integrations
- Track utilization of third-parties
- Help with contract renewal discussions
- Enable other engineering team members
- Provide documentation on how to acquire / reconfigure infrastructure
- Track requests for acquisition/creation of infrastructure
Requirements
- Dev Ops Enablement Lead's must have a position with the reach of 3.1 or higher
- Dev Ops Enablement Lead's must be milestone 2+,Systems Management
- Dev Ops Enablement Lead's must be milestone 1+,Infrastructure
Configuration Health
- ✅ Has 2 Abilities
- ✅ Is a part of 3 Positions
- ✅ Has been referenced in 2 pieces of public recognition
- ℹ️ No one has reacted to this Assignment
- ℹ️ No one has an official rating on this Assignment
- ⛔️ Last updated: over 4 years ago
- ℹ️ Never conversed about
Examples / Observations
Observation created almost 5 years agoFeaturing:Stephen G.Engineering CommunicationInitiativeStakeholder / Feedback ManagementDevOps Enablement LeadUnexpected, concise, clear, communicated with both summaries and details, and action-oriented. As it pertains to emails about technical topics, it doesn't get much better than this.
I now feel that much more confident that Stephen isn't just thinking about doing the tasks he is assigned... he is thinking about the overall picture and health of Lessonly as we navigate this journey we are on.
Love it!!
Email #1:
HI everybody,
As you may or may not be aware there was a massive hack on solarwinds which provides infrastructure software to many companies. ( https://www.solarwinds.com/securityadvisory ).
I want to present to this group the (preliminary) findings as I investigated our exposure because industry-wide implications and more customers are going to be asking about this. It is going to be beneficial to have some sort of statement to respond with.
If you would like me to work with somebody on what that statement should be please let me know. And if you have any guidance on verbage before we craft such a statement I would appreciate it.
Executive Summary
We use a small unaffected Solarwinds product in non production environments. A couple of our vendors had similar exposure. Our biggest risk is Twilio which actually used an affected product, but they believe they were not impacted by the breach.
Our Direct Exposure
We do not use their software directly in our data centers.
PaperTrail
We use a product called PaperTrail in non-production environments for logging. No sensitive information should be sent there. This product
Vendors
Vendors known to have some exposure to SolarWinds Products
Twilio (Sendgrid, Twilio, Segment)
The company Twilio owns 3 services that we use. Twilio did use the affected software "in a limited fashion." They have been working with SolarWinds and believe they were ultimately unaffected by the breach
Twilio is our biggest risk, but at this point I believe it to be mitigated.
Harness
Harness used an unaffected SolarWinds product (Pingdom). Ultimately I see no risk here, but they did share this for transparency.
CloudBees (Codeship)
CloudBees owns the codeship product that we use. They, like Harness, used some unaffected SolarWinds products
Librato (scoped to our CodeShip product)
PaperTrail (scoped to our CodeShip product)
PingDom (basic external monitoring used by Ops)
Observation created almost 5 years agoStephen publicly highlighted the work that Brittany and Matt B. did to keep queue size down when reindexing all Lessons: https://lessonly.slack.com/archives/G8Q5B0EVA/p1607543001201000 This shout-out not only encourages those on the receiving end to continue being good stewards of our systems, but gives all developers an example to emulate. I'm sure not every engineer would have considered the impact of enqueuing any number of jobs—perhaps now they will, and might even remember that keeping queue depth to within a few hundred is a good thing, as Stephen pointed out.
Official Dev Ops Enablement Leads
This section is for Lessonly folks only. Sign your team up to find your Gruuv!
Teams needing a DevOps Enablement Lead
This section is for Lessonly folks only. Sign your team up to find your Gruuv!
Positions that reference being a DevOps Enablement Lead
This section is for Lessonly folks only. Sign your team up to find your Gruuv!
Conversations about DevOps Enablement Lead
This section is for Lessonly folks only. Sign your team up to find your Gruuv!