Upgrade to Pro — share decks privately, control downloads, hide ads and more …

DevOps @ KnowIT

DevOps @ KnowIT

Talk on DevOps at a breakfast seminar hosted by KnowIT.

Mårten Gustafson

November 12, 2013
Tweet

More Decks by Mårten Gustafson

Other Decks in Technology

Transcript

  1. * Today, this: Omni * 13 devs (backend: 7+3 &

    frontend: 2+2) * I head up the backend & infrastructure team
  2. Awareness * Become aware of what happens outside “our bubble”

    * Become aware of why “things” are happening
  3. Understanding * Understanding why things are the eay they are

    * Understanding that what appears bad to me, might appear good to someone else
  4. Co-planning * If we understand and are aware it’ll be

    easier to plan together * If we plan together we’ll become aware and understand each other
  5. co-lo get a sysops * in your team * (per

    team?) * contract or hire * full or part-time
  6. managed hosting customer responsible technician * whom you assimilate! *

    get person on chat, mailing lists, etc * invite to lunch, AW, whatever
  7. PaaS sysop 2.0? * PaaS, e.g. Heroku, will force a

    bigger responsibility on DEV * and/or a completely different kind of OPS * I’m not sure here, yet
  8. Higher pace. * Do X in half the time? *

    Do X with half the people involved? * More time and or people to do Y and Z!
  9. Higher engagement. * if more of the involved have higher

    awareness we’ll get a higher engagement and we’ll increase quality and deliver faster
  10. Invite. * Invite all “the others” to planning, stand-ups, coffee,

    AW, etc * As with all transformations it won’t happen in an instant and it’ll be shaped over time
  11. Guerrilla cooperation. * (my personal favorite) * Tend to work

    really well * Easier to ask for forgiveness than approval
  12. 1. Get to know each other 2. Involve each other

    3. Start doing things together
  13. 1. Get to know each other 2. Involve each other

    3. Start doing things together 4. Think strategic together
  14. 1. Get to know each other 2. Involve each other

    3. Start doing things together 4. Think strategic together 5. Stop viewing others as “others”
  15. 1. Get to know each other 2. Involve each other

    3. Start doing things together 4. Think strategic together 5. Stop viewing others as “others” 6. Do a project together
  16. Culture. * DevOps is culture * DevOps is not an

    automated infrastructure (automation is a product, project, whatevs) * DevOps is not a title * Culture happens when individuals work together