6. 6
Strengths:
- Closest to business needs
- Deliver new capabili:es
- Protect user experience
- Experienced automators
Weaknesses:
- Lose focus on scalability, stability,
and supportability at :mes
- Typically under pressure to deliver
quickly
- Security not always top of mind
- Not always experienced op:mizers
Tradi(onal Development Group
Development
7. 7
Strengths:
- Experienced op:mizers
- Cost conscience
- Focus on stability and availability
- Tend to consider cross-func:onal impacts
- Experienced data and performance
analysts
- Champion documenta:on
Weaknesses:
- Typically manual process intensive
- Under pressure to minimize change
- Catching up on automa:on
- OXen viewed as a bo.leneck to agility
Tradi(onal Opera(ons Group
Opera:ons
8. 8
Strengths:
- Focus on quality (obviously)
- Experienced in crea:ng test cases
- Consider all users / personas
- Collaborators by necessity
Weaknesses:
- OXen require heavy guidance from
development team
- OXen heavily func:onal focused (at the
expense of load, performance, and
security tes:ng)
- Usually the most to suffer in a :meline
crunch
Tradi(onal QA Group
Quality Assurance
14. 14
• Mindset/Culture Change
• Org Changes
• Skillset Changes
• Focus on Decreasing Time
to Value
What does DevOps Involve?
People Process Technology
• Dev / Ops / QA / SEC
Process Changes
• Automa:on of Process
(requires understanding/
documenta:on)
• Accountability Changes
• New/Updated Roles
• Configura:on Management
• Con:nuous Delivery
• Automa:on U:li:es /
Scrip:ng
• Automated Tes:ng
• Security Automa:on
15. 15
• Infrastructure CreaCon
• Automa:cally create infrastructure components and server instances.
• ConfiguraCon Management
• Configure server instances to hardened/defined specs with necessary components installed.
• ConCnuous IntegraCon / ConCnuous Delivery
• Automate the delivery of applica:on releases from Dev to Produc:on.
• Source Control
• Centralized code management for Apps and Infrastructure.
• ContainerizaCon
• Host applica:ons / components within logical containers within a virtual/physical host
• TesCng AutomaCon
• Automate func:onal, integra:on, regression, and security tes:ng
DevOps Technology Areas
20. 20
DevOps Mindset Impacts all IT
• Development
• Gain a stake in what it takes to run and support the applica:on at scale.
• Embed security / QA tes:ng into the SDLC.
• Assists Ops, QA, and Security with automa:on of their processes.
• Begin to build performance and stability metrics into delivery pipeline.
• You build it – you support it mentality (shared accountability).
• Opera:ons
• Begin to automate repeatable and standardized processes.
• Start to manage infrastructure as code.
• Become involved in applica:on quality process.
• Be.er ingrain security hardening into infrastructure.
• Gain understanding of what code/applica:on is doing on their boxes.
21. 21
DevOps Mindset Impacts all IT
• QA
• Automate tes:ng so it can be performed at scale.
• Collaborate with development group on business context and needs.
• Include security checks into tes:ng loops.
• Begin to become scalable.
• Security
• Ensure immediate compliance by collabora:ng on infrastructure automa:on and CICD.
• Reduce organiza:onal risk by integra:ng into the SDLC.
• Share experience and knowledge of common a.ack vectors with Dev & Ops.
• Increase confidence that the environment is “known”.
• Become enablers instead of blockers.
23. 23
1. Culture – Above all DevOps is a Mindset.
• Educa:on
• Org Changes
• Champions
• Skill Addi:ons
• Consul:ng
2. Process Changes – Start Small
• Iden:fy a key service with the highest value proposi:on and limited risk
• Remember the manufacturing factory analogy. Iden:fy a bo.leneck or pain
point.
• Lean mindset with realis:c goals and con:nuous improvement loops.
I’m Ready for DevOps – Where to Start?
24. 24
• Tools – Culture and process changes will lead you to tools.
• Infrastructure CreaCon
• Terramark, AWS CloudForma:on, Cloud Service Broker, VMWare
• ConfiguraCon Management
• Chef, Puppet, Ansible, Salt
• ConCnuous IntegraCon / ConCnuous Delivery
• Jenkins, TeamCity, Bamboo, Maven
• Source Control
• Git, GitHub, BitBucket
• ContainerizaCon
• Docker
• TesCng AutomaCon
• Selenium, Appium, QMetry
I’m Ready for DevOps – Tools
25. 25
• Strong OS, Scrip:ng, and Infrastructure Skills with Development Competence
• Strong desire to automate (obviously)
• Tinkerer
• Con:nually seeking to understand the "Why" behind the "What”
• Intrinsically Mo:vated – Want to build great things
• Typically out in front of their organiza:on
(Hint: pick up great talent frustrated with slow cultural movement of current employer)
• Con:nually trying to automate themselves out of the process.
• HATES repe::ve tasks (Healthy level of laziness)
• Enjoys change and new tools
Prac(cal – Traits of a Great DevOps Engineer
26. 26
• Reduce Time to Value
• Turn IT from a controlling bo.leneck to a business enabler
• Build resiliency & scalability into your infrastructure
• Enable new capabili:es
• Leverage things like on-demand and server-less compu:ng to save
infrastructure costs
• Embed security and QA tes:ng into the delivery lifecycle.
• Increased Quality
• Reduced Risk
• Help drive meaningful business growth
Recap – Why DevOps?
