Page

Bringing Real Benefits to Your Business/ Copyright ©2015 by Readify Limited1

Ab

out

Me

2

Paul Glavich - Principal Consultant

Microsoft MVP ~12 years

ASP.NET Insider

Book author & Public Speaker

Twitter - @glav

paul.glavich@readify.net

Who

are

Read

ify?

3

Agenda

WHAT?• Tooling – Practice - Culture

WHY?• Cost – Speed – Efficiency - Productivity

HOW?• Pro’s - Cons - Challenges

4

What

is D

evO

ps?

5

COLLABORATE MORE

SHARE COMMON

GOALS

-

FOCUS ON

IMPROVEMENT

-

BRINGING PEOPLE

TOGETHER

ELIMINATE WASTE

INCREASE EFFICIENCY

-

STREAMLINE

FEEDBACK

-

DELIVERING VALUE

FASTER

SUPPORT PROCESSES

-

ENABLE

COLLABORATION

-

FACILITATE

EXPERIMENTATION

-

EXECUTING THE

DEVOPS STRATEGY

PEOPLE PROCESS TOOLS

No Really, What is it?

• Development teams and IT operations

• Mindset and practice

• An evolution of agile practices

• Taking Agile development practices and

applying them beyond the development team

• Keyword: Automation6

In Practical Terms

7

DevO

ps

Incl

ud

es

8

• Code profiling

• Load/Performance testing

• Security testing/scanning

• Environment tests

• Automated tests

“DevOps adoption is not mandatory -

but neither is survival“

2014 – State of DevOps report

https://puppet.com/resources/white-paper/2014-state-of-devops-report9

Why?

Witho

ut

DevO

ps

10

Em

bra

cing

DevO

ps

11 Image courtesy of http://www.cheezburger.com/

What it may look like now

12

Image courtesy of https://pages.chef.io/rs/255-VFB-268/images/DevOps-and-the-Cloud-Azure.pdf

Risk of non adoption

• Long Infrastructure Wait Time

• Time-consuming Configurations

• Cost Control Issues

• Production fidelity Issues

• Employee frustration, disengagement

13

Real benefits

• Higher quality output• A bug caught in production costs approx. 100x more than if

found earlier in the dev cycle.

• Deployment frequency

• MTTR – Mean time to recover

• Lead time for changes substantially reduced

• Employee engagement improves

14

Metr

ics

15

“2016 State of DevOps” report

https://puppet.com/resources/white-paper/2016-state-of-devops-report

Important note

• Complete adoption of every facet of DevOps is not

required

• Adopt basic tenets

• Apply what makes sense per project

16

So

ho

w?

17

Press the button DevOps

Making DevOps a “thing”

• People – Process – Tooling

• People and processes are the major hurdle• Culture shift cannot be imposed on a team

• Tooling technical decision will follow

18

Ad

op

ting

DevO

ps

19

• Staged adoption

• Revise / Assess / Continue

• Mindset / Process / Culture / most important

• Avoid rushing to the “end goal”

• “How do you eat an elephant?”

Challenges

• Change is not without it’s challenges

• Culture shift, process change

• Can be taken negatively

• Skillset / ramp up time

20

Pre

ferr

ed

way

of

wo

rkin

g

21

How Readify deliver great DevOps projects

Microsoft Azure

Open platform

Visual Studio / Team Services

Sum

mary

22

One team – shared goals

23