DevOps 101Christopher Livett

2

Introduction| Understanding what Agile is| How software is developed in an Agile environment| Why there was a need for the DevOps movement| How DevOps is achieved| What DevOps means for QualiTest

3

Agile Overview

4

Principles of Agile

| Individuals and interactions over processes and tools| Working software over comprehensive documentation| Customer collaboration over contract negotiation| Responding to change over following a plan

5

Frameworks and Methodologies

| Frameworks| Scrum (1995)| Lean (2003)| Kanban (2007)| Scrumban (2009)| SAFe (2011)

| Methodologies| Pair Programming (1995)| Extreme Programming (1999)| Continuous Integration (1999)| TDD (2002)| BDD (2006)| DevOps (2009)

6

Scrum Framework| Product Owner

| Scrum Master

| Dev Team| Developers| Testers| Business Analysts| Architects

7

Development Principles

| Short release cycles| Feature driven| Pair programming| Test Driven Development| “Just in time” design| Flat management| Simplicity and clarity

8

What is missing?

9

Issues with Traditional Agile Development

| Short release cycles| Focus on speed over quality

| Feature driven| Focus on functionality, no NFRs

| “Just in time” design| No detailed plans for post-development support

| Flat hierarchy| Little enforced standards and governance

| Simplicity and clarity| Minimum level of development

10

Development to Production

Day 1 - 9 Day 10

11

<- No trust ->

| Skills| Software| Development| Automation| Innovation

| Skills| Monitoring| Analysis| Management

| Responsibilities| Coding| Builds| Deployments| Testing

| Responsibilities| Changes| Servers| Deployments| Stability

Developers and Operations

12

Introducing DevOps

13

What is DevOps?

| Bridging the skill gap between developers and operations| Operations being part of the team| Change in mindset from building code to owning code| Improving efficiency and quality by:

| Automating deployments| Automating environment configuration| Automating environment scaling| Innovating solutions| Improving development practices

| Improve relationships and cooperation across technology

14

Evolution of DevOps

15

DevOps in Practice

16

DevOps Tool Belt

| Infrastructure| AWS| OpenStack

| Server monitoring| Nagios| New Relic

| Platform Virtualisation| VMware| Vagrant

| Log analysis| ELK| Logz.io

| Service discovery| Consul.io

| Collaboration| Atlassian

| Test and Build| Jenkins| Bamboo

| Deployment| Capistrano

| Containerisation| LXC| Docker

| Configuration management| Chef| Puppet

| Security| Tripwire| Veracode

17

Benefits of DevOps

| Managed and consistent environments| Improved collaboration between developers and operations| Faster feedback of issues| Less production issues| Increased stability| Greater accountability| Increased throughput from idea to production| Reduced server costs

18

QualiTest and DevOps

19

IncreasedTesting Concerns

| Continuous testing and monitoring across all stages| Environment configuration testing| Performance/Scalability testing| Security testing| Alpha/Beta testing| Feature switch testing| Risk-based testing

20

Continuous Testing

21

What DevOps means for QAs

| Technical skills are vital| Automate everything| Continuous testing at all stages| Greater focus on testing process| Closer integration with developers and operations| Educational role

22

DevOps opportunities

| Risk assessment| Designing DevOps continuous testing processes

| Coverage| Automation| Types and tools

| Integrating development, testing and monitoring tools| Non-functional testing| Knowledge consultancy

23

Summary| DevOps is a natural evolution of the Agile process| DevOps aims to achieve improved efficiency, quality and

stability| Continuous testing and monitoring becomes top priority| Mindset, skillset and experience required can be a

challenge

www.QualiTestGroup.com

Questions?

www.QualiTestGroup.com

Thank you!