building devops culture from bottom up

Building DevOps culture from bottom up

January 2017


Agenda

1. Why DevOps has become a hot topic now

2. What DevOps product is about

and what makes it different from

a plain CI initiative

3. How to get into DevOps if your management does not give a damn


Engineering relevance

January 2017


Cumbersome tools

January 2017


Cloud is not for rich anymore

January 2017


Engineering maturity has grown

January 2017


Business Relevance

January 2017


Let’s solve it with ‘The methodology’

January 2017


January 2017

Hope

Time


Fuck agile, I wanna do it now!-Sharon Tal


DevOps product


Value-added product. Take Docker vs. predecessors (e.g. LXC, Jails) d product. Take Docker vs. predecessors (e.g. LXC, Jails) ✓ Developer friendly

✓ Name and Logo :)

✓ Documentation

✓ Portability

✓ Configuration alternative to Chef hell

✓ Registry

January 2017


When you are building internal DevOps product consider experience difference

● ELK stack vs. Papertrail

● Jenkins vs. Circleci, Semaphorci

and others

● MySQL vs. RDS

● Gitosis vs. github

January 2017


Enterprise-level cloud CI vs. Vanilla Jenkins

January 2017


January 2017

Complete DevOps product for BigData

January 2017


Building DevOps culture from bottom-up


How to motivate others to go DevOps

✓ Personal leadership skills development

✓ New cross-discipline skills development

✓ Make your own life easier

✓ Make your engineering culture more attractive for top-talents

January 2017


Re-define your DevOps skills

January 2017


Re-define your DevOps skills

✓ Move beyond Slack administration and Datadog dashboarding

✓ Get back to your hands-on programming skills. There are gaps you’ll need to

bridge as enterprise level processes does not fit into plug-n-play tools

✓ AWS, Docker, Jenkins, Kubernetes are not easy at all - be ready to fix bugs and

contribute to the community

January 2017


Re-define your DevOps role

✓ Sale & Marketing

✓ Product Owner

✓ UX Designer

✓ Architect

✓ Software Engineer

✓ Admin

✓ QA

✓ Level 1-2-3 Support engineer

January 2017


Establish beachhead

January 2017


Establish beachhead

✓ Start with development environment

✓ Pitch transition from SVN to Git (looks funny but it takes years to change)

✓ Suggest to sign-up for basic SaaS services e.g.:

Source control - github

Error monitoring - airbreak or alternatives

Logs aggregation – papertrail

Performance monitoring – newrelic

CI - circleci, travis-ci and dozen alternatives

Start with business lunch-priced trials (e.g. $15 vs. $10 Github subscription)

gineering culture more attractive for top-talents

January 2017


Share responsibility

January 2017

OPERATIONS

DEVELOPMENT


Share responsibility and help others

✓ Start involving other teams/mates. (e.g. provide access to Jenkins

console for QA folks)

✓ Setup communication channels at Slack for deployments, errors,

other alerts

✓ Seduce admins to start using development tools and practices

including version control (where do you store Zabbix configs or

secret bash-scripts?)

✓ Create sandbox environment for Data Science team

January 2017

Title of the Presentation

If I’m awake you are awake

strategy

If I’m awake you are awake

strategy

If I’m awake you are awake strategy


Make DevOps tangible to win allies

1. Introduce metrics: uptime %, production incidents per month, releases per month.2. Connect metrics with money - the best arguments for business are:● Cost of change ● Cost of delay● Cost of failure● Cost of innovation1. Visualise metrics on dashboards.


Summary

1. Complete DevOps products evoke more credibility, bring more value and easier to implement

2. Appeal to personal motivation of peers when you advocate for DevOps

3. Move slowly with suggested steps that require close to zero approval

4. Visualize the value of your work for others

www.squadex.com

125 University Avenue,

Suite 290, Palo Alto,

California, 94301

Let your company and DevOps live happily ever after

building devops culture from bottom up

Technology