Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Death to the DevOps team - Agile Yorkshire 2014


Published on

Talk given on 14th October at Agile Yorkshire

An increasing number of organisations - including many that follow Agile practices - have
begun to adopt DevOps as a set of guidelines to help improve the speed and quality of
software delivery. However, many of these organisations have created a new 'DevOps
team' in order to tackle unfamiliar challenges such as infrastructure automation and
automated deployments.
Although a dedicated team for infrastructure-as-code can be a useful intermediate step
towards greater Dev and Ops collaboration, a long-running 'DevOps team' risks becoming
another silo, separating Dev and Ops on a potentially permanent basis.
I will share my experiences of working with a variety of large organisations in many
different sectors, helping them to adopt a DevOps approach whilst avoiding another team
We will see examples of activities, approaches, and ideas that have helped organisations
to avoid a DevOps team silo, including:
- DevOps Topologies: "Venn diagrams for great benefit DevOps strategy"
- techniques for choosing tools (without fixating on features)
- new flow exercises based on the Ball Point game
- recruitment brainstorming
- Empathy Snap, a new retrospective exercise well suited to DevOps
This session will provide 'food for thought' when adopting and evolving DevOps within your
own organisation.

Published in: Technology

Death to the DevOps team - Agile Yorkshire 2014

  1. 1. Death to the DevOps team! How to avoid another silo Matthew Skelton, Skelton Thatcher Consulting Agile Yorkshire, Tuesday 14thOctober 2014, Leeds, UK #agileyorkshire
  2. 2. DevOps ‘DevOps’
  3. 3. Team topologies Flow exercises Choosing tools Recruitment Empathy Snap
  4. 4. Matthew Skelton •Building & operating commercial software systems since 1998 •Cybernetics + Neuroscience + Music •control engineering •psychology •‘network’ and group interactions @matthewpskelton
  5. 5. Skelton Thatcher Introduction and Services Overview
  6. 6. ‘Cloud’ changes the way we mustdesign, deliver, and operateour software systems
  7. 7. Changes for ‘cloud’
  8. 8. DevOps ‘DevOps’
  9. 9. Not DevOps: “Automation” “Build & Release” “Infrastructure Development” “System Administration”
  10. 10. DevOps “Highly effective, daily collaboration between software developers and IT operations people to produce relevant, working systems” * *also QA/Testing, IT Service Desk, Programme Management, Commercial, Marketing, etc.
  11. 11. Sectors •Tourism •Betting •Travel booking •Legal software •Healthcare •Financial data & reporting •Government agencies •Foreign Exchange
  12. 12. Organisations 1.Financial data 2.Legal software 3.Travel booking
  13. 13. Team topologies Flow exercises Choosing tools Recruitment Empathy Snap
  14. 14. Team Topologies
  15. 15.
  16. 16. HT: @EricMinick, IBM
  17. 17. Organisations 1.Financial data 2.Legal software 3.Travel booking
  18. 18. 1. Financial data Goal: shorter Lead Time No ‘DevOps’ team  Challenge: define the purpose of the new team(s) (‘naming things is hard’)
  19. 19. 1. Financial data ?
  20. 20. 1. Financial data Are the main challenges technical? (Clue: probably not)
  21. 21. 1. Financial data Evolve the team(s) over 2 years Clarity of purpose Spread culture
  22. 22. 2. Legal software Genuine ‘no Ops’ Challenge: avoid a ‘tooling takeover’
  23. 23. 2. Legal software ? ?
  24. 24. 2. Legal software Grow an Operations capability Use and train the Support team ‘SRE’ or ‘Web Operations’
  25. 25. 3. Travel booking Service Desk silo Challenge: slow or limited feedback from Production
  26. 26. 3. Travel booking ? ?
  27. 27. 3. Travel booking Collaboration with shared tools Visualise and broadcast Retain Ops discipline
  28. 28. Team topology determines recruitment needs
  29. 29. Team Topologies SkeltonThatcher/DevOpsTopologies
  30. 30.
  31. 31. There is no ‘right’ team topology, but several ‘bad’ topologies for any one organisation
  32. 32. Team topologies Flow exercises Choosing tools Recruitment Empathy Snap
  33. 33. Flow Exercises
  34. 34. Experience DevOps A hands-on workshop for DevOps culture
  35. 35. @jamesbetteley @johnC_bristol
  36. 36. 2 Dev teams, 1 Ops team  Ops team did ‘stop the line’ 
  37. 37. 2x throughput!  Service Teams 
  38. 38. Modelling teams & constraints Single team Two Dev teams, one Ops team Two service teams (Dev + Ops) Provisioning delays Backlog item prioritisation
  39. 39. “… organising the North of England’s largest ball flow game”
  40. 40. Explore topology effectiveness with different constraints Drive team topology with metrics from flow exercises!
  41. 41. Team topologies Flow exercises Choosing tools Recruitment Empathy Snap
  42. 42. Choosing Tools
  43. 43.
  44. 44. “How does [the use of] this tool help people to collaborate*?” * Work together, at the same keyboard/screen
  45. 45. ‘How to choose tools for DevOps and Continuous Delivery’ ‘DZoneguide to Continuous Delivery 2014’
  46. 46. How to choose tools for DevOps Value collaboration aspects Avoid a learning mountain: evolve tooling Avoid Production-only tools Consider Conway’s Law (this list is incomplete!)
  47. 47. Team topologies Flow exercises Choosing tools Recruitment Empathy Snap
  48. 48. Recruitment
  49. 49. Don’t hire ‘DevOps’
  50. 50. Recruitment suggestions Site Reliability Engineers (SRE) Web Operations (‘WebOps’?) SysAdmin+ Git + TDD (?)
  51. 51. Recruitment suggestions Diplomacy Facilitating Evangelising Mentor Deep specialism in SAN fabrics
  52. 52. Yes, we still need operations Metrics Layer 2 / 3 subtleties Rapid diagnosis Fault heuristics Incident response experience ‘Battle-scars’
  53. 53. Recruiting for DevOps Don’t hire ‘DevOps’ Don’t advertise for ‘DevOps Engineer’ Use SRE / WebOps/ TDD Don’t forget Operations skills!
  54. 54. Team topologies Flow exercises Choosing tools Recruitment Empathy Snap
  55. 55. Empathy Snap
  56. 56. Empathy Snap
  57. 57. Recapitulation
  58. 58. How to avoid another silo
  59. 59. Team topologies There is no ‘right’ topology Many ‘wrong’ topologies for one organisation Consider skills, core business, SLAs, … Evolve the topology over time (2 years) Communicate the purpose
  60. 60. Flow exercises Adapt to include IT Ops people Learning through physical interaction Model and measure flow Flow exercises help choose a team topology
  61. 61. Other things Consider the collaboration value in all tools Shared tools for shared responsibilities Don’t hire ‘DevOps’ Encourage empathy
  62. 62. We did not really mention: Funding: CapExvs OpEx Bonuses & financial rewards / penalties Building a culture Conway’s Law …
  63. 63. Death to the ‘DevOps’ teamLong live the DevOps team
  64. 64. Effective DevOps for Leadershalf-day seminarLeeds: 27thJanuary 2015 Promo code ‘AGILEYORKS’ –10% discount
  65. 65. Further reading Build Quality In Forewords by Dave Farley and Patrick Debois Discount for #AgileYorkshire! AgileYorkshire Valid until 14th November 2014
  66. 66. Further reading @annashipman–DevOps @ GDS (Build Quality In) antipattern-is-an-antipattern/ organization-2/ Allan Kelly on Conway’s Law:
  67. 67. Thank you! @SkeltonThatcher +44 (0)20 8242 4103