Welcome.

Introduction to DevOps for Non-Engineers

Chris Knotts Techtown Training and Enterprise Learning (ASPE, Inc.)

Curriculum Director, Product Manager, Learning Broker, etc.

We will discuss…

• DevOps: What? Who? • Why it’s important • A few key figures of the movement • Nuts and bolts • DevOps Engineering: important tools • Key Takeaways

Attribute Key Elements

High-trust, high- performance culture IT capabilities = strategic assets, not cost centers Highly automated processes; mature deployment pipeline Continuous delivery of software and IT value Commitment to continuous learning & improvement

Unified mission; aligned incentives across departments and teams; little fear/failure/blame, high quality of work life Projects, features and work flow through fast cycles times, systems are “anti-fragile,” IT processes & capabilities are aligned with overarching organizational needs Technical phases of projects supported by common tools and automation processes, collaboration replaces handoffs, codebase/IT infrastructure is agile and functional by default Features, projects and IT work follow a regular, iterative flow. Cycle time is short, workflow favors small frequent changes Disciplined feedback loops quickly travel back upstream for inclusion. Tools for monitoring, measurement and alerting implemented & effective. Shared knowledge repositories.

DevOps IS…

What is DevOps?

Dev

Ops

A simplified look at Consolidata’s enterprise

s

S e c u r I t y, G o v e r n a n c e S e c u r I t y, G o v e r n a n c e

Business Customer

Application

Development teams IT Operations, Production

Environments, Support

Change Management

Opposing missions

• Development teams rewarded for creating value when software is deployed

• Operations and infrastructure admin

teams penalized for downtime

Leaders are seeing IT costs differently

Enterprise IT costs

Leaders are seeing IT costs differently

Source: IBM

CHEAPER

SAME

How does DevOps fix all this?

PEOPLE: • Better collaboration between functional silos • Culture of continuous improvement • Lessons from other industries TECHNOLOGY: • Virtualizing IT stuff saves a lot of money • New tools are making new things possible • Just as in manufacturing, automation transforms

Application Delivery & Cost of Defects

50% of defects introduced here

John Allspaw & Paul Hammond

“10+ Deploys Per Day”

Early Key Points from “10+ Deploys…”

John Allspaw

Gene Kim

Gene Kim, Kevin Behr, George Spafford

Think overall value chain

From the last slide….

• The Goal (Eliyahu Goldratt) • W. Edwards Deming • “Toyota Production System” • Kanbans and Kanban boards • Lean principles; Agile principles

Business analysis

App Dev

Testing & QA

Release

IT Ops

Idea or need

Delivery

Functional flow

Business analysis

App Dev

Testing & QA

Release

IT Ops

Idea or need

Delivery

Feedback?

Functional flow

Risk/security

Business analysis

App Dev

Testing & QA

Release

IT Ops

Idea or need

Delivery

Feedback?

PMO

Business unit

constructs

Functional flow

Project management

Deployment, Continuous Integration

IaaS

Configuration Management & Automation

Versioning, Social Coding, Push/Pull

Containerization

Kanban

Key Takeaways

• Visualize the work (for real…not mind’s eye) • Find & reduce bottlenecks • Communicate! Capitalize on feedback loops • Embrace failure & eliminate blame • Leverage tools whenever possible • Automate, automate, automate • Culture must focus on overall goals of the

organization • Rigorous version control & traceability

Thank you for joining us! Today’s activity awards 1 PDU

• Go to aspe-sdlc.com/pdu/ for instructions on submitting your PDU.

• You can submit your PDU by mail or electronically. • The Activity code for today’s presentation is WS093014 and

ASPE’s REP number is 2161.

• These web seminars are Category A for one PDU