Code / Build / Test
Source control, the practice of tracking and managing changes to software code, is also known as this name
Version Control
Also a famous British butler, the open source automation server we use to build & deploy software
Jenkins
A dinosaur-themed exercice that simulates network outages in our AWS public cloud; typically conducted 4X/year
TREx
A target range of values for a service level; often measured by its close cousin, the SLI
SLO
Agile ceremony that happens once every 6 weeks where we plan the next product increment of work
PI Planning
The name of the version control system we use here at Capital One
Github
Also a term of art in warfare used to describe enemy aircraft, this is our main in-house CI/CD tool
Bogie
This type of engineering specialization describes the practice of defining SLIs, SLOs, and SLAs
Reliability
A portmanteau that is also an oxymoron, it’s also the name of main observability tool we use
NewRelic
80% is the agreed upon number for measuring an engineering team’s commitment during a 6-week PI
Capacity
Also meaning 'one who is experienced or knowledgeable', this is a popular software project management tool
Maven
The component of Bogie used for infrastructure management
Gears
A metal more precious than gold, 4 ‘9’s describes this level of availability required to achieve this Resiliency Tier
Platinum
I am a business commitment that a service provider makes to a customer; often in the form of a contract with financial penalties if I’m missed
SLA
This agile ceremony which occurs daily, answers the following questions–’What did I work on yesterday, what am I working on today, and do I have any impediments?’
Daily Stand Up, S1, Scrum all acceptable
Commonly referred to as SCA, this type of tool searches for and finds security bugs in our code, hopefully before we run it in production
Static or Source Code Analysis both acceptable
The term used to describe a recovery from a bad deployment, or return to steady state operations
Rollback
15 minutes is all we get to meet this type of reliability metric
Recovery Time
This strange acronym ‘MTBF’ describes the expected (arithmetic mean) time between two failures of a system
Mean Time Between Failures
A Capital One Agile process with a funny name that addresses changes to the PI Plan in the event of the need to move shift work priority
WiWo
80% is the bare minimum (cough) for code coverage for this type of test which measures functionality in isolation without deployment
Unit Test
LaunchDarkly is an example of a tool that allows for this type of flag release
Feature
The 'top of the pyramid', this level of observability maturity introduces proactive low-sev incidents; yikes!
Level 4
The amount of permissible impact of failed events; similar to its financial analog, it's bad for operations if we exhaust it
Event Budget
The agile ceremony where risks are discussed and dispositioned; aka ‘Scrum of Scrum of Scrums’ ;-)
S3