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.
Running Cross
Functional Service
Teams
Philip Reynolds
Workday
About me
§  Got the internet bug at 14 … discovered Linux
§  Have worn many hats – mainly as a developer & sysadmin
§  ...
Preface
§  I didn’t invent this stuff – AmaGooBook
§  Shared learning
-  Nothing revolutionary. Not going to change your...
What?
§  Mix of developers & operations
§  “You build it, you run it” – Amazon
§  Reporting structure not that importan...
Why?
§  Process
-  Redundancy vs dependency
-  Seek to minimize external dependencies
-  Scale – Organizational scalabili...
Why? (contd.)
§  People
-  Drive deeper understanding of the system – grow true domain experts
-  Autonomy of teams. Allo...
Why? (contd.)
§  Technical
-  Architecture - Move to Service Orientated architecture
-  Promote certain systems to “first...
How? (Ops team perspective)
§  Hire a senior developer (… a good one!)
-  Lean on your colleagues for help in hiring one ...
How? (Ops team perspective #2)
§  Create a pipeline
§  Rigorous code reviews
§  Heavy focus on testing. Invest in your ...
How? (Ops team perspective #3)
§  Train the developer on supporting systems.
-  Litmus test: can they go on-call
§  Deve...
How? (Dev team perspective)
§  Hire a senior ops person
§  Set expectations around code
-  Litmus test: can they triage ...
How? (Dev team perspective #2)
§  Set clear responsibilities
-  Business hours triaging? Config mgmt? Monitoring?
§  Ope...
Hiring
§  Culture extremely important – don’t compromise
§  Soft skills / personality is more important for first CF hir...
Learnings
§  Dynamic of team has changed. Develop a rhythm
§  You will spend more time talking about work instead of doi...
Learnings #2
§  Collective ownership of the domain is key. Collaboration
should have increased (desk time goes up)
§  St...
Learnings #3
§  Developers are now second-line on call.
-  Not everyone is ok with that. Be up-front through hiring proce...
Summary
§  Own your service. All of your service
§  Invest in quality
§  Team first
We’re hiring!
@philreynolds
We’re hiring - www.workday.com/careers/
Upcoming SlideShare
Loading in …5
×

Running cross functional service teams

301 views

Published on

A talk about why & how to run cross functional service teams in engineering organisations. Focussed on operations and developers in one team.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Running cross functional service teams

  1. 1. Running Cross Functional Service Teams Philip Reynolds Workday
  2. 2. About me §  Got the internet bug at 14 … discovered Linux §  Have worn many hats – mainly as a developer & sysadmin §  Joined Workday in 2009 §  Manage 2 teams in Workday
  3. 3. Preface §  I didn’t invent this stuff – AmaGooBook §  Shared learning -  Nothing revolutionary. Not going to change your world. §  My team – they’re awesome
  4. 4. What? §  Mix of developers & operations §  “You build it, you run it” – Amazon §  Reporting structure not that important. Team == “Scrum team”
  5. 5. Why? §  Process -  Redundancy vs dependency -  Seek to minimize external dependencies -  Scale – Organizational scalability. Easy model to replicate.
  6. 6. Why? (contd.) §  People -  Drive deeper understanding of the system – grow true domain experts -  Autonomy of teams. Allow teams the freedom to make decisions. -  Cross training -  Team – strength through unity -  Resourcing
  7. 7. Why? (contd.) §  Technical -  Architecture - Move to Service Orientated architecture -  Promote certain systems to “first class” systems. Having service teams own things like monitoring.
  8. 8. How? (Ops team perspective) §  Hire a senior developer (… a good one!) -  Lean on your colleagues for help in hiring one or look internally for candidates. §  Treat all code as code. -  Python – code -  Application configuration – that’s code -  Switch configuration – that’s code too! §  Build dev infrastructure (build & test infrastructure / tooling)
  9. 9. How? (Ops team perspective #2) §  Create a pipeline §  Rigorous code reviews §  Heavy focus on testing. Invest in your testing. §  Continuous Integration – The Holy Grail
  10. 10. How? (Ops team perspective #3) §  Train the developer on supporting systems. -  Litmus test: can they go on-call §  Developers like building stuff. Make sure you recognise that.
  11. 11. How? (Dev team perspective) §  Hire a senior ops person §  Set expectations around code -  Litmus test: can they triage and fix small bugs? §  Dopamine hit comes from fixing stuff
  12. 12. How? (Dev team perspective #2) §  Set clear responsibilities -  Business hours triaging? Config mgmt? Monitoring? §  Operability is a functional requirement §  Everyone on-call
  13. 13. Hiring §  Culture extremely important – don’t compromise §  Soft skills / personality is more important for first CF hire §  You almost certainly have colleagues who can help hire
  14. 14. Learnings §  Dynamic of team has changed. Develop a rhythm §  You will spend more time talking about work instead of doing work. That’s ok. §  Velocity increased – go slower to get faster. -  Defect rate should go down. -  Less rework
  15. 15. Learnings #2 §  Collective ownership of the domain is key. Collaboration should have increased (desk time goes up) §  Started using traditional scrum - moved to Kanban. -  Critical part for ops teams is limiting WIP and breaking down work -  Critical part for dev teams is facilitating reactive work §  Ops people are often more optimistic in planning(!)
  16. 16. Learnings #3 §  Developers are now second-line on call. -  Not everyone is ok with that. Be up-front through hiring process
  17. 17. Summary §  Own your service. All of your service §  Invest in quality §  Team first
  18. 18. We’re hiring! @philreynolds We’re hiring - www.workday.com/careers/

×