DevOps at its CoreAnn Marie Fred

IBM May 1, 2015

About Me

Duke BS CS 1999

pervasive & mobile

web applications

algorithms

UNC MS CS 2005

distributed systems

software engineering

About Me

IBM since 1998

pervasive & mobile

web applications

systems management

cloud computing

DevOps since 2011: 5 different teams

DevOps: Goals

Happy Developers

Happy IT Operators

Happy Business Stakeholders

Happy Consumers

Happy DevsWork-Life Balance

Fun

Passion

Uptime

Quality

Velocity

Business Value

Sharing Knowledge & Experience

Broad & Deep Skills

Clear Communications

Continuous Process Improvement

Happy OpsWork-Life Balance

Fun

Passion

Uptime

Quality

(maybe not Velocity)

Business Value

Sharing Knowledge & Experience

Broad & Deep Skills

Clear Communications

Continuous Process Improvement

Happy BusinessWork-Life Balance

Fun

Passion

Uptime

Quality

Agility (+)

Velocity

Business Value

Sharing Knowledge & Experience

Broad & Deep Skills

Clear Communications

Continuous Process Improvement

Happy ConsumersFun

Passion

Uptime

Quality

Agility

Velocity

Business Value

Clear Communications

DevOps: Core ValuesWork-Life Balance

Fun

Passion

Clear Communications

Sharing Knowledge & Experience

Broad & Deep Skills

DevOps: Core ValuesUptime

Quality

Agility

Velocity

Business Value

Continuous Process Improvement

Warm Fuzzies: Work-Life Balance, Fun, and Passion

Attract & Retain Talent

Hire for the Warm Fuzzies.

Assess Management on the Warm Fuzzies.

Consciously make these happen.

The other DevOps Core Values help immensely.

Clear Communications: Required

Talking

Chat Services

Wikis and Blogs

Forums

Bug Reporting & Tracking

Agile Planning & Tracking

Clear Communications: Extras

Co-location

Social Media

Conferences

User Groups and Meetups

Email and Newsletters

Specific Agile Methodologies (Scrum, Kanban, etc.)

Sharing Knowledge & Experience, Broad & Deep

Skills: RequiredSee: Clear Communications

Document as you build: how and why

Informal Training

Internet Resources

Code Reviews

Sharing Knowledge & Experience, Broad & Deep

Skills: ExtrasWork on things you don’t know how to do.

Pair Programming

Cross Pollination

Open Source Model

Formal Training

Books

Uptime: Required

See: Quality

Monitoring

Graceful Fail-over

Sharing the Pager

Post-Mortems

Continuous Delivery

Continuous Delivery

Automated Deployment into Production

Deployment Automation

Infrastructure as Code

Frequent Deployments (ideally, several per day)

Small, Incremental Changes

Zero Downtime

Continuous Delivery

Automated Tests in Production or At Least Staging

Including NFRs: performance, dropoff, etc.

Staged Rollouts

Dark Launches

Rolling Deployments

A/B Testing

etc.

Uptime: Extras

See: Sharing Knowledge & Experiece, Broad & Deep Skills

Graceful degradation

Dedicated Support Team

Quality: Required

See: Uptime

Bug Tracking

Source Control

Code Reviews

Security Testing

Continuous Integration

Continuous Testing

Continuous Integration

On Every Check In of Source Code:

Build Automatically

Test the Source Code Automatically

Static Code Analysis

Linters for Code Style

API Tests

Anything that doesn’t require a running system

Package Build Artifacts for Deployment

Store Build Artifacts in a Library

Continuous TestingRetrieve Build Artifacts from Library

Deploy Automatically in the Lab

As close to production as possible

Automatically Test Running Systems

Report Test Results Quickly

Voting and Non-Voting Tests

Failed tests make the build fail

If the build fails, fix it before moving on

Quality: Extras

See: Sharing Knowledge & Experience, Broad & Deep Skills

Continuous Delivery

Agility

See: Clear Communication

Agile Planning and Tracking

Frequent Releases

Continuous Delivery Helps

Short Feedback Loops

Autonomous, Empowered Teams

Quality and Agility

"Agile has not only improved our ability to plan effectively but it also has allowed us to spend more time working on user stories by improving the quality of the code we deliver." - Richard Gebhardt, Technical Team Lead for Service Engage.

Velocity

Slow at first, while building the frameworks for quality and uptime.

Faster in the long run.

Low Bug Count

Low Technical Debt

Frequent Releases

Agility and Velocity

"By having daily scrum meetings, everyone knows who is working on what, resources quickly get directed to problem areas and impediments are addressed quickly and efficiently." - Chuck Brant, Service Engage Release Manager.

Business ValueSee: Uptime, Quality, Agility, Velocity

The Right Stakeholders

Feedback Directly from Consumers

User Centered Design

Evaluate teams on business value.

Monitor business value.

Agility and Business Value

"As a product line manager, working on one-week sprints gives me the flexibility to change priorities as things change. I can still get the big-ticket items delivered - but I can do so without getting locked into an unyielding plan and can react rapidly to shifting business priorities." - Pete Marshall, Product Manager, IBM Service Engage/Cloud Foundation Services.

Continuous Process Improvement

See: Sharing Knowledge & Experience

Blameless Post Mortems

Sprint Retrospectives

ResourcesMe: amfred@us.ibm.com, Twitter @DukeAMO

Triangle DevOps Meetup group

DevOps Days conferences

Code as Craft, Etsy’s Engineering Blog

Blogs from Netflix, Facebook, IBM

Books from O’Reilly Media