A Leap from Agile to DevOps Jeffrey Fredrick TIM Group 2005 2006 - - PowerPoint PPT Presentation

▶

Nov 13, 2023 275 likes •601 views

A Leap from Agile to DevOps Jeffrey Fredrick TIM Group 2005 2006 2007 2008 2009 Adopt pair programming Add extensive testing including TDD Support with elaborate continuous integration 2005 2006 2010 2011 Managed hosting

SLIDE 1

A Leap from Agile to DevOps

Jeffrey Fredrick TIM Group

SLIDE 2

SLIDE 3

SLIDE 4

2005 2006

SLIDE 5

2005 2006 2007 2008 2009

Adopt pair programming
Add extensive testing including TDD
Support with elaborate continuous integration

SLIDE 6

2005 2006 2007 2008 2009

Managed hosting limiting evolution of

architecture

Bring in consultants, create migration plan
Hire sysadmin team, build collocation sites

2010 2011

SLIDE 7

2005 2006 2007 2008 2009 2010 2011 2012

At migration complete merged sysadmin

project team with Ops and Tools team to create new Infrastructure team

Went live from our new data centers in

January

SLIDE 8

SLIDE 9

John Willis: What Devops Means to Me http://is.gd/B6z7E7

SLIDE 10

John Willis: What Devops Means to Me http://is.gd/B6z7E7

Ops was application support, the semi-

technical buffer between production & users and the developers

Company bottleneck seen as developer time
Enabling architectural change was the

motivating factor

SLIDE 11

Continuous deployment for new components

put in place by development

SLIDE 12

"Metrics": a two week block on the Gantt chart
Application metrics are (almost) all technical
Business metrics come from the same nightly

"ops project" scripts as before the transition

SLIDE 13

"Shared problems are the basis of teamwork"
Root Cause Analysis is our established

mechanism for addressing problems

Success on shared problems have been

creating a virtuous cycle

SLIDE 14

The wake up call

Fault tolerant infrastructure + Fault tolerant architecture = Outage within 15 minutes of going live

SLIDE 15

New component introduced to have

calculation code against a slave database

API code transparently calling new

component; fallback to old code on failure

Two component instances behind a load

balancer

SLIDE 16

SLIDE 17

SLIDE 18

SLIDE 19

SLIDE 20

SLIDE 21

SLIDE 22

SLIDE 23

SLIDE 24

SLIDE 25

Patrick Debois: Devops Areas - Codifying devops practices http://is.gd/IyicB3

SLIDE 26

Patrick Debois: Devops Areas - Codifying devops practices http://is.gd/IyicB3

SLIDE 27

SLIDE 28

SLIDE 29

SLIDE 30

2005 2006 2007 2008 2009 2010 2011 2012

Questions?

jtf@jeffreyfredrick.com

SLIDE 31

2005 2006 2007 2008 2009 2010 2011 2012

A Leap from Agile to DevOps

jtf@jeffreyfredrick.com