You Build It, You Own It! Presented by: Sean Miller and - PDF document

AW21 ¡ DevOps ¡Practices ¡ Wednesday, ¡November ¡6th, ¡2019 ¡3:00 ¡PM ¡ You ¡Build ¡It, ¡You ¡Own ¡It! ¡ Presented ¡by: ¡ Sean ¡Miller ¡ and Suresh Chellapilla Capital ¡One ¡ Brought ¡to ¡you ¡by: ¡ 888 -­‑-­‑-­‑ 268 -­‑-­‑-­‑ 8770 ¡ ·√·√ ¡904 -­‑-­‑-­‑ 278 -­‑-­‑-­‑ 0524 ¡-­‑ ¡info@techwell.com ¡ https://agiledevopseast.techwell.com/ ¡

Sean ¡Miller Sean ¡Miller ¡has ¡been ¡working ¡in ¡the ¡financial ¡services ¡industry ¡for ¡eight ¡years ¡and ¡ has ¡worn ¡many ¡different ¡hats, ¡from ¡technology ¡operations ¡to ¡software ¡development. ¡ From ¡humble ¡beginnings ¡as ¡a ¡desktop ¡support ¡engineer, ¡he ¡quickly ¡transitioned ¡to ¡a ¡ business ¡systems ¡analyst, ¡then ¡software ¡engineer, ¡and ¡finally ¡an ¡agile ¡delivery ¡lead ¡ and ¡agile ¡program ¡lead. ¡This ¡experience ¡sets ¡him ¡up ¡for ¡success ¡on ¡both ¡sides ¡of ¡the ¡ fence, ¡so ¡he ¡understands ¡the ¡pain ¡engineers ¡face ¡as ¡well ¡as ¡the ¡value ¡stakeholders ¡ gain. ¡ Suresh Chellapilla Suresh Chellapilla is a senior manager and agile program lead at Capital One and has over twenty years of software development experience, fourteen of which have been spent in an agile environment.

You Build It, You Own It! Sean Miller & Suresh Chellapilla

Who are we? Sean Miller Suresh Chellapilla Agile Program Lead Agile Program Lead 8 years @ Capital One 9 years @ Capital One

Agenda What is DevOps? ● What’s this YBYO thing? ● How has this impacted our development and delivery? ● The Process ● Impact on Resiliency ● Lessons Learned ● Recap ●

What is “DevOps”?

Out with the old... Throwing code over the wall ● Separate Dev and Ops teams ●

...in with the new and passing the baton. ● Full stack teams ● Developers releasing their own code ● Taking full ownership of features in production

Why is a bank using DevOps? We’re a technology company that does banking Things move fast, we need to stay current (and relevant) ● Better customer experience ● Tighter feedback loops ● Lower risk ●

Are you delivering better soware for customers faster?

Introducing YBYO

Translation... You Build It, You Own It!

But what is it? Capital One’s spin on Werner Vogels “You build it, you run it” Design for production . ● Greater employee autonomy . ● Greater transparency . ● More automation . ● More satisfied customers . ●

Impact on Development & Delivery

How has development changed? Faster response to production issues. ● Less process overhead. ● Infrastructure as Code ● Ownership of platforms ● Reliance on Site Reliability Engineers (SREs) ●

What about delivery? ● More frequent releases, shorter time to market. ● Smaller increments ● More willing to take risks ● Addition of feature toggles ● Smaller roll backs (no need to roll back an entire release)

1,000% Increase in releases for Capital One Bank

What about our people? ● Expanded horizons (more knowledge of Ops and Dev) ● Ownership of applications

Impacts on Agile

Scrum + DevOps ● Scrum is just a framework ● No need to wait until the sprint ends ● Leave room in your sprints for unplanned work

Introducing Kanban + DevOps ● No prescribed release cadences ● Continuous flow of work ● No more sprinting

This lead to “Federation” ● Breaking away from large release trains ● Each product or team owning things from end to end (again, YBYO) ● More creative ways of deploying code, i.e. smaller iterations ● Containerizing and building smaller services (microservices)

Our support structure changed too... ● We rebranded our Scrum Masters as “Agile Delivery Leads” with a focus on coaching and delivery. ● Moving away from the stigma that everything is “Scrum” and empowering teams to do what’s best for them. ● Empowering our engineers to stay focused on coding, and less on administrative overhead. ● ADLs stay focused on removing blockers, and can hold their own in technical discussions.

Lean on Lean Organically, we started to see more value in the concept of “Just in Time” to support our journey... ● Backlogs ● Products And therefore, we started to embrace Lean ● Cycle Time ● Throughput ● Flow

The “Process”

Some processes add value... At the end of the day, we provided our engineers with: ● A streamlined approach ● Consistency ● Common toolset

...and we had to be accountable Demo with leadership to... ● Review failover procedures ● Review monitoring and alerting ● Review architecture ● Review a runbook Upon successful completion - YBYO Certified

...and take our Customer Experience seriously. ● Graceful error messages ● Feature toggles ● Service Level Agreements (SLAs, RTOs, RPOs) ● Customer Experience forums

Lessons Learned

Nothing ever goes as planned... ● Lots of obscurity ● Burn out ● Failure to launch ● Conflicting priorities ● Work life balance suffered

...so how did we fix it? ● Lots of trial and error! ● More thoughtful on call rotations ● Lead by example ● Enhancements to our tools and processes ● Support, support, support

Closing

Summary ● DevOps = You build it, you own it! ● Changes everything! ○ Delivery = Faster ○ More agility ○ New roles, i.e. Agile Delivery Lead ● Certification before launch ● Many lessons learned - adapt and overcome

Questions?