O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.
How to Build High-Performing
IT Teams
Presented by Alanna Brown
Agenda
• Build the case
• Identify the desired state
• Align incentives
• Align your teams
• Implement key technical pract...
Build the Case
People don’t buy what you do,
they buy why you do it.
Simon Sinek
http://bit.ly/sinektedtalk
Reliability
Agility
Opposing Forces
High-performing IT orgs are more agile
30x
More frequent
deployments
200x
Faster lead times
than their peers
Source: Puppe...
High-performing IT orgs are more reliable
60x
Change success
rate
168x
Faster mean time to
recover (MTTR)
Source: Puppet L...
High-performing IT orgs are winning
1.5x
More likely to exceed
profitability, market
share & productivity
goals
50%
Higher...
Learning is not compulsory,
but neither is survival.
Edward W. Deming
http://bit.ly/deming14pts
Identify the
Desired State
Organization
Low trust culture  High trust culture
Siloed teams  Cross-functional teams
Lack of alignment  Aligned arou...
Processes
Lots of manual work  Mostly automated work
Long cycle times  Short cycle times
Poor visibility  Fast feedback...
People
High burnout  High job satisfaction
Stagnant  Able to grow
Checking boxes  Creative innovation
Continuous Delivery Practices
Lean Management Practices
Align Incentives
“Trying to effect process, people, technology and
cultural changes across the entire application
portfolio, in a globally ...
Hiscox: Results
• Reduced cost per release on one application
by 97%
• Reduced time per release by 89%
• Reduced staff req...
Conflicting Incentives
Business Delivering value to customers
Dev teams Delivering new features
Ops teams Ensuring stabili...
Everyone is responsible for quality
and we’re all trying to deliver the
best solution for our customers.
Reena Mathew, Pri...
Salesforce: Results
Aligned Incentives
Delivering
value to
customers
Business
Ops
teams
Quality
teams
Dev
teams
We can’t do DevOps because our
application is
________________________.
Architectural Characteristics
Significant affect on IT performance
• Does not require integrated testing
environment
• Can...
Align Your Teams
Typical Enterprise Org Structure
IT Operations
NOC
Commercial Banking
Business Units
Credit Cards
Mortgages
Investment Ban...
Pattern 1: Smooth Operations
Dev Ops
Recommended Reading: http://blog.matthewskelton.net/2013/10/22/what-team-structure-is...
Pattern 2: Cross-functional team
Characteristics
• Consists of devs, testers, ops, product
owner, etc.
• Focused on delive...
Pattern 3: DevOps Team
Dev Ops
Dev
Ops
Characteristics
• Consists ideally of devs with systems
experience, or sysadmins wi...
Roles & Responsibilities
Roles Responsibilities
“The Business” Understand market trends and identify customer needs
IT Man...
Implement Key
Technical Practices
Version
Control
Configuration
Management
Continuous
Integration
Deployment
Tools
Monitoring
And others…
DevOps Toolchain
Infrastructure as Code
Infrastructure as Code
Version
Control
Peer
Review
Continuous
Delivery
Collaboration Iteration
Fast...
Version Control
Source: Puppet Labs 2014 State of DevOps Report
Peer-Reviewed Change Process
• Code can be contributed by anyone
• Code changes can be reviewed by anyone
• Code can be wo...
Continuous Delivery
• Code is repeatable
• Code is sharable
• Code is promotable
• Code is testable
Measuring Results
Throughput
• Deployment frequency
• Change lead time (from dev’s laptop to production)
• Cycle time
Stab...
Deployment Pain
Tomorrow, ask your team two questions:
• How painful are your deployments?
• What’s causing the pain?
Diversify Your Team
Teams with more women
have higher:
• Financial performance
• Stock market performance
• Hedge fund ret...
Q&A
Resources
• The 2015 State of DevOps Report is here! puppetlabs.com/2015-
devops-report
• The Phoenix Project by Gene Kim
...
How to Build High-Performing IT Teams - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
Próximos SlideShares
Carregando em…5
×

How to Build High-Performing IT Teams - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report

2.724 visualizações

Publicada em

Alanna Brown shares how to build the case for DevOops, align incentives and team members, and implement key technical practices, such as version control, configuration management, continuous integration, and monitoring.

Publicada em: Tecnologia
  • Seja o primeiro a comentar

How to Build High-Performing IT Teams - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report

  1. 1. How to Build High-Performing IT Teams Presented by Alanna Brown
  2. 2. Agenda • Build the case • Identify the desired state • Align incentives • Align your teams • Implement key technical practices
  3. 3. Build the Case
  4. 4. People don’t buy what you do, they buy why you do it. Simon Sinek http://bit.ly/sinektedtalk
  5. 5. Reliability Agility Opposing Forces
  6. 6. High-performing IT orgs are more agile 30x More frequent deployments 200x Faster lead times than their peers Source: Puppet Labs 2015 State of DevOps Report
  7. 7. High-performing IT orgs are more reliable 60x Change success rate 168x Faster mean time to recover (MTTR) Source: Puppet Labs 2015 State of DevOps Report
  8. 8. High-performing IT orgs are winning 1.5x More likely to exceed profitability, market share & productivity goals 50% Higher market capitalization growth over 3 years.* Source: Puppet Labs 2015 State of DevOps Report
  9. 9. Learning is not compulsory, but neither is survival. Edward W. Deming http://bit.ly/deming14pts
  10. 10. Identify the Desired State
  11. 11. Organization Low trust culture  High trust culture Siloed teams  Cross-functional teams Lack of alignment  Aligned around business goals
  12. 12. Processes Lots of manual work  Mostly automated work Long cycle times  Short cycle times Poor visibility  Fast feedback & insight
  13. 13. People High burnout  High job satisfaction Stagnant  Able to grow Checking boxes  Creative innovation
  14. 14. Continuous Delivery Practices
  15. 15. Lean Management Practices
  16. 16. Align Incentives
  17. 17. “Trying to effect process, people, technology and cultural changes across the entire application portfolio, in a globally dispersed team and with a lot of associated technical debt, is an epic challenge.” Jonathan Fletcher Enterprise Architect and Lead for Technology, Platform and DevOps at Hiscox http://bit.ly/devopshiscox
  18. 18. Hiscox: Results • Reduced cost per release on one application by 97% • Reduced time per release by 89% • Reduced staff required to release by 75% • Automated testing reduced multiple man days of effort down to an overnight hands-free process
  19. 19. Conflicting Incentives Business Delivering value to customers Dev teams Delivering new features Ops teams Ensuring stability of systems Quality teams Ensuring quality of software releases
  20. 20. Everyone is responsible for quality and we’re all trying to deliver the best solution for our customers. Reena Mathew, Principle Architect Quality Engineering, Salesforce http://bit.ly/sfdevops
  21. 21. Salesforce: Results
  22. 22. Aligned Incentives Delivering value to customers Business Ops teams Quality teams Dev teams
  23. 23. We can’t do DevOps because our application is ________________________.
  24. 24. Architectural Characteristics Significant affect on IT performance • Does not require integrated testing environment • Can deploy/release app independently of other apps/services it depends on • Custom software with microservices architecture No affect on IT performance • Packaged commercial software / COTS. • Systems of record / systems of engagement • New, not-yet-deployed systems. • Software w/ embedded component that runs on manufactured hardware device / user-installed component that runs on user’s machine
  25. 25. Align Your Teams
  26. 26. Typical Enterprise Org Structure IT Operations NOC Commercial Banking Business Units Credit Cards Mortgages Investment Banking Systems Engineers Network Engineers Storage Admins DBAs InfosecDev teams reside in BU
  27. 27. Pattern 1: Smooth Operations Dev Ops Recommended Reading: http://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to- flourish/
  28. 28. Pattern 2: Cross-functional team Characteristics • Consists of devs, testers, ops, product owner, etc. • Focused on delivering a single application • Self-sufficient • Optimized for throughput
  29. 29. Pattern 3: DevOps Team Dev Ops Dev Ops Characteristics • Consists ideally of devs with systems experience, or sysadmins with programming experience • Focused on automating pain points • Responsible for building a platform that allows devs to self-service • Provides a toolchain to enable devs to build, test and deploy their systems • Coaches other teams
  30. 30. Roles & Responsibilities Roles Responsibilities “The Business” Understand market trends and identify customer needs IT Manager Build trust with counterparts on other teams; create culture of learning and continuous improvement; delegate authority; remove roadblocks Dev Manager Build trust with Ops counterpart; bring Ops into the planning process early Systems Engineer Automate the things that are painful; help devs get feedback QE Provide input into scale and performance; provide feedback on staging environments Devs Plan for deployment as you’re planning new features; get feedback from ops and work with them on deployment process
  31. 31. Implement Key Technical Practices
  32. 32. Version Control Configuration Management Continuous Integration Deployment Tools Monitoring And others… DevOps Toolchain
  33. 33. Infrastructure as Code Infrastructure as Code Version Control Peer Review Continuous Delivery Collaboration Iteration Fast Feedback Visibility
  34. 34. Version Control Source: Puppet Labs 2014 State of DevOps Report
  35. 35. Peer-Reviewed Change Process • Code can be contributed by anyone • Code changes can be reviewed by anyone • Code can be worked on as a team
  36. 36. Continuous Delivery • Code is repeatable • Code is sharable • Code is promotable • Code is testable
  37. 37. Measuring Results Throughput • Deployment frequency • Change lead time (from dev’s laptop to production) • Cycle time Stability / Reliability • Change fail rate • Mean time to recover • Availability / downtime
  38. 38. Deployment Pain Tomorrow, ask your team two questions: • How painful are your deployments? • What’s causing the pain?
  39. 39. Diversify Your Team Teams with more women have higher: • Financial performance • Stock market performance • Hedge fund returns • Collective intelligence
  40. 40. Q&A
  41. 41. Resources • The 2015 State of DevOps Report is here! puppetlabs.com/2015- devops-report • The Phoenix Project by Gene Kim • Continuous Delivery by Jez Humble • PuppetConf 2015: http://2015.puppetconf.com/ • DevOps Enterprise Summit: http://devopsenterprise.io/

×