Agile Infra @AgileRoots 2009

133
AGILE INFRASTRUCTURE

description

The prelude to the talks at Velocity and Agile 2009. A few of the same slides and sentiment, but presented in a different way. More mentions of Puppet specifically for one.

Transcript of Agile Infra @AgileRoots 2009

Page 1: Agile Infra @AgileRoots 2009

AGILE INFRASTRUCTURE

Page 2: Agile Infra @AgileRoots 2009

ANDREW CLAY SHAFER

Page 3: Agile Infra @AgileRoots 2009

ANDREW CLAY SHAFER

Developer Once Upon A Time

Page 4: Agile Infra @AgileRoots 2009

ANDREW CLAY SHAFER

Developer Once Upon A Time

Agile Team member

Page 5: Agile Infra @AgileRoots 2009

ANDREW CLAY SHAFER

Developer Once Upon A Time

Agile Team member

Tolerated at Salt Lake Agile Roundtable

Page 6: Agile Infra @AgileRoots 2009

ANDREW CLAY SHAFER

Developer Once Upon A Time

Agile Team member

Tolerated at Salt Lake Agile Roundtable

Mostly Worked For Start Ups

Page 7: Agile Infra @AgileRoots 2009

ANDREW CLAY SHAFER

Developer Once Upon A Time

Founding Partner Reductive Labs Inc.

Agile Team member

Tolerated at Salt Lake Agile Roundtable

Mostly Worked For Start Ups

Page 8: Agile Infra @AgileRoots 2009

ANDREW CLAY SHAFER

Developer Once Upon A Time

Founding Partner Reductive Labs Inc.

Agile Team member

All Around Trouble Maker

Tolerated at Salt Lake Agile Roundtable

Mostly Worked For Start Ups

Page 9: Agile Infra @AgileRoots 2009

ANDREW CLAY SHAFER

Developer Once Upon A Time

Founding Partner Reductive Labs Inc.

Agile Team member

All Around Trouble Maker

Tolerated at Salt Lake Agile Roundtable

Mostly Worked For Start Ups

The Rest is Complicated...

Page 10: Agile Infra @AgileRoots 2009

O H Y E A H , T H E R E I S A LWAY S A D U C K . . .

Page 11: Agile Infra @AgileRoots 2009

WHAT IS AGILE?

Page 12: Agile Infra @AgileRoots 2009

M A N I F E S T O , 4 VA L U E S , 1 2 P R I N C I P L E S . . .

Page 13: Agile Infra @AgileRoots 2009

M A N I F E S T O , 4 VA L U E S , 1 2 P R I N C I P L E S . . .

Page 14: Agile Infra @AgileRoots 2009

M A N I F E S T O , 4 VA L U E S , 1 2 P R I N C I P L E S . . .

Page 15: Agile Infra @AgileRoots 2009

M A N I F E S T O , 4 VA L U E S , 1 2 P R I N C I P L E S . . .

Page 16: Agile Infra @AgileRoots 2009

M A N I F E S T O , 4 VA L U E S , 1 2 P R I N C I P L E S . . .

Page 17: Agile Infra @AgileRoots 2009

M A N I F E S T O , 4 VA L U E S , 1 2 P R I N C I P L E S . . .

Page 18: Agile Infra @AgileRoots 2009

M A N I F E S T O , 4 VA L U E S , 1 2 P R I N C I P L E S . . .

Page 19: Agile Infra @AgileRoots 2009

M A N I F E S T O , 4 VA L U E S , 1 2 P R I N C I P L E S . . .

Page 20: Agile Infra @AgileRoots 2009

M A N I F E S T O , 4 VA L U E S , 1 2 P R I N C I P L E S . . .

Page 21: Agile Infra @AgileRoots 2009

M A N I F E S T O , 4 VA L U E S , 1 2 P R I N C I P L E S . . .

Page 22: Agile Infra @AgileRoots 2009

BUT WHAT IS

AGILE???

Page 23: Agile Infra @AgileRoots 2009

BUT WHAT IS

AGILE???PLANNING

Page 24: Agile Infra @AgileRoots 2009

BUT WHAT IS

AGILE???PLANNING ENGINEERING

Page 25: Agile Infra @AgileRoots 2009

BUT WHAT IS

AGILE???PLANNING ENGINEERING

DEVELOPERS

Page 26: Agile Infra @AgileRoots 2009

BUT WHAT IS

AGILE???PLANNING ENGINEERING

DEVELOPERSPRODUCTOWNERS

Page 27: Agile Infra @AgileRoots 2009

BUT WHAT IS

AGILE???PLANNING ENGINEERING

DEVELOPERSPRODUCTOWNERS

TESTERS

Page 28: Agile Infra @AgileRoots 2009

BUT WHAT IS

AGILE???PLANNING ENGINEERING

DEVELOPERSPRODUCTOWNERS

EXECUTIVES

TESTERS

Page 29: Agile Infra @AgileRoots 2009

BUT WHAT IS

AGILE???PLANNING ENGINEERING

DEVELOPERSPRODUCTOWNERS

SYSTEM ADMINISTRATORSEXECUTIVES

TESTERS

Page 30: Agile Infra @AgileRoots 2009

BUT WHAT IS

AGILE???PLANNING ENGINEERING

DEVELOPERSPRODUCTOWNERS

SYSTEM ADMINISTRATORSDATABASE ADMINISTRATORS

EXECUTIVES

TESTERS

Page 31: Agile Infra @AgileRoots 2009

BUT WHAT IS

AGILE???PLANNING ENGINEERING

DEVELOPERSPRODUCTOWNERS

SYSTEM ADMINISTRATORSDATABASE ADMINISTRATORS

NETWORK ENGINEERS

EXECUTIVES

TESTERS

Page 32: Agile Infra @AgileRoots 2009

BUT WHAT IS

AGILE???PLANNING ENGINEERING

DEVELOPERSPRODUCTOWNERS

SYSTEM ADMINISTRATORSDATABASE ADMINISTRATORS

NETWORK ENGINEERS

EXECUTIVES

TESTERSDESIGNERS

Page 33: Agile Infra @AgileRoots 2009

BUT WHAT IS

AGILE???PLANNING ENGINEERING

DEVELOPERSPRODUCTOWNERS

SYSTEM ADMINISTRATORSDATABASE ADMINISTRATORS

NETWORK ENGINEERS

EXECUTIVES

TESTERSDESIGNERS

USABILITY EXPERTS

Page 34: Agile Infra @AgileRoots 2009

BUT WHAT IS

AGILE???PLANNING ENGINEERING

DEVELOPERSPRODUCTOWNERS

CIRCLE OF HAPPINESS

SYSTEM ADMINISTRATORSDATABASE ADMINISTRATORS

NETWORK ENGINEERS

EXECUTIVES

TESTERSDESIGNERS

USABILITY EXPERTS

Page 35: Agile Infra @AgileRoots 2009

BUT WHAT IS

AGILE???PLANNING ENGINEERING

DEVELOPERSPRODUCTOWNERS

CIRCLE OF HAPPINESS

SYSTEM ADMINISTRATORSDATABASE ADMINISTRATORS

NETWORK ENGINEERS

EXECUTIVES

TESTERSDESIGNERS

USABILITY EXPERTS

Page 36: Agile Infra @AgileRoots 2009

BUT WHAT IS

AGILE???PLANNING ENGINEERING

DEVELOPERSPRODUCTOWNERS

CIRCLE OF HAPPINESS

SYSTEM ADMINISTRATORSDATABASE ADMINISTRATORS

NETWORK ENGINEERS

EXECUTIVES

TESTERSDESIGNERS

USABILITY EXPERTS

Page 37: Agile Infra @AgileRoots 2009

BUT THE WAY SOFTWARE GETS DELIVERED HAS

CHANGED A LOT...

Page 38: Agile Infra @AgileRoots 2009

BUT THE WAY SOFTWARE GETS DELIVERED HAS

CHANGED A LOT...

...AND THINGS ARE CHANGING FAST RIGHT NOW .

Page 39: Agile Infra @AgileRoots 2009

WHO IS WORKING ON A

WEB APP?

Page 40: Agile Infra @AgileRoots 2009

END OF SHRINK WRAP

Page 41: Agile Infra @AgileRoots 2009

END OF SHRINK WRAP

Page 42: Agile Infra @AgileRoots 2009

Clouds Are Rising

END OF SHRINK WRAP

Page 43: Agile Infra @AgileRoots 2009

WHO IS WORKING ON A

WEB APP?

Page 44: Agile Infra @AgileRoots 2009

WHO IS WORKING ON A

WEB APP?WHERE DOES THAT WEB APP RUN?

Page 45: Agile Infra @AgileRoots 2009

WHO IS WORKING ON A

WEB APP?WHERE DOES THAT WEB APP RUN?

WHO TAKES CARE OF THOSE SERVERS?

Page 46: Agile Infra @AgileRoots 2009

WHO IS WORKING ON A

WEB APP?WHERE DOES THAT WEB APP RUN?

WHO TAKES CARE OF THOSE SERVERS?HOW DO YOU INTERACT WITH THEM?

Page 47: Agile Infra @AgileRoots 2009

WHO IS WORKING ON A

WEB APP?WHERE DOES THAT WEB APP RUN?

WHO TAKES CARE OF THOSE SERVERS?HOW DO YOU INTERACT WITH THEM?

‘THEM’ IS PEOPLE OR SERVERS?

Page 48: Agile Infra @AgileRoots 2009

ENGINEERINGVersion Control

Build From Source

Page 49: Agile Infra @AgileRoots 2009

WHO USES VERSION CONTROL FOR SYSTEM

CONFIGURATIONS?

Page 50: Agile Infra @AgileRoots 2009

WHO USES VERSION CONTROL FOR SYSTEM

CONFIGURATIONS?

WHO CAN AUTOMATICALLY

REBUILD SYSTEMS?

Page 51: Agile Infra @AgileRoots 2009

Infrastructure is Code!!!

Page 52: Agile Infra @AgileRoots 2009

Infrastructure is Code!!!SEMANTICS

Page 53: Agile Infra @AgileRoots 2009

Infrastructure is Code!!!SEMANTICS

REPRODUCIBLE

Page 54: Agile Infra @AgileRoots 2009

Infrastructure is Code!!!SEMANTICS

REPRODUCIBLEMAINTAINABLE

Page 55: Agile Infra @AgileRoots 2009

Infrastructure is Code!!!SEMANTICS

REPRODUCIBLEMAINTAINABLE

EXTENSIBLE

Page 56: Agile Infra @AgileRoots 2009

Infrastructure is Code!!!SEMANTICS

REPRODUCIBLEMAINTAINABLE

EXTENSIBLESHAREABLE

Page 57: Agile Infra @AgileRoots 2009

WHO IS USING PUPPET?

Page 58: Agile Infra @AgileRoots 2009

Infrastructure is Code!!!SEMANTICS

REPRODUCIBLEMAINTAINABLE

EXTENSIBLESHAREABLE

Open Source Software!

Page 59: Agile Infra @AgileRoots 2009

HELP ME TO SEE IT...

Page 60: Agile Infra @AgileRoots 2009

HELP ME TO SEE IT...

USING TRADITIONAL TECHNIQUES CONFIGURATIONS TEND TO DRIFT

Page 61: Agile Infra @AgileRoots 2009

BUT WHY?

Page 62: Agile Infra @AgileRoots 2009

BUT WHY?BACKLOG OF REQUESTS

Page 63: Agile Infra @AgileRoots 2009

BUT WHY?BACKLOG OF REQUESTS

CONFIGURATION OF CRITICAL SERVICES ARE OFTEN NOT DOCUMENTED AND MUST BE RECREATED

Page 64: Agile Infra @AgileRoots 2009

BUT WHY?

INCONSISTENCIES CAUSE CONFUSION AND MISTAKES

BACKLOG OF REQUESTS

CONFIGURATION OF CRITICAL SERVICES ARE OFTEN NOT DOCUMENTED AND MUST BE RECREATED

Page 65: Agile Infra @AgileRoots 2009

BUT WHY?

MORE AND MORE SYSTEMS TO MANAGE

INCONSISTENCIES CAUSE CONFUSION AND MISTAKES

BACKLOG OF REQUESTS

CONFIGURATION OF CRITICAL SERVICES ARE OFTEN NOT DOCUMENTED AND MUST BE RECREATED

Page 66: Agile Infra @AgileRoots 2009

BUT WHY?

MORE AND MORE SYSTEMS TO MANAGE

INCONSISTENCIES CAUSE CONFUSION AND MISTAKES

BACKLOG OF REQUESTS

CONFIGURATION OF CRITICAL SERVICES ARE OFTEN NOT DOCUMENTED AND MUST BE RECREATED

WORK ON THE BIGGEST FIRE

Page 67: Agile Infra @AgileRoots 2009
Page 68: Agile Infra @AgileRoots 2009

Dear Diary,

Page 69: Agile Infra @AgileRoots 2009

Dear Diary, Today I was on fire for 12 hours...

Page 70: Agile Infra @AgileRoots 2009

Dear Diary, Today I was on fire for 12 hours...It wasn’t as pleasant as it sounds.

Page 71: Agile Infra @AgileRoots 2009

Dear Diary, Today I was on fire for 12 hours...It wasn’t as pleasant as it sounds.--Eben Brinson Smith III

Page 72: Agile Infra @AgileRoots 2009

Dear Diary, Today I was on fire for 12 hours...It wasn’t as pleasant as it sounds.--Eben Brinson Smith III

Page 73: Agile Infra @AgileRoots 2009

WHAT DOES THAT REALLY MEAN?

Page 74: Agile Infra @AgileRoots 2009

WHAT DOES THAT REALLY MEAN?DEPLOYMENTS AND UPGRADES

ARE EXPENSIVE, TEDIOUS AND ERROR PRONE

Page 75: Agile Infra @AgileRoots 2009

WHAT DOES THAT REALLY MEAN?DEPLOYMENTS AND UPGRADES

ARE EXPENSIVE, TEDIOUS AND ERROR PRONE

THE CHANCE THAT DEV, TEST AND PROD ARE CONFIGURED THE SAME APPROACHES ZERO

Page 76: Agile Infra @AgileRoots 2009

WHAT DOES THAT REALLY MEAN?DEPLOYMENTS AND UPGRADES

ARE EXPENSIVE, TEDIOUS AND ERROR PRONE

THE CHANCE THAT DEV, TEST AND PROD ARE CONFIGURED THE SAME APPROACHES ZERO

HARDWARE FAILURE CAN BE CATASTROPHIC

Page 77: Agile Infra @AgileRoots 2009

WHAT DOES THAT REALLY MEAN?DEPLOYMENTS AND UPGRADES

ARE EXPENSIVE, TEDIOUS AND ERROR PRONE

THE CHANCE THAT DEV, TEST AND PROD ARE CONFIGURED THE SAME APPROACHES ZERO

HARDWARE FAILURE CAN BE CATASTROPHIC

HEAVY WEIGHT CHANGE CONTROL PROCESSES SEEM LIKE A GOOD IDEA

Page 78: Agile Infra @AgileRoots 2009

WHAT DOES THAT REALLY MEAN?

MORE AND MORE SYSTEMS TO MANAGE

DEPLOYMENTS AND UPGRADES ARE EXPENSIVE, TEDIOUS AND ERROR PRONE

THE CHANCE THAT DEV, TEST AND PROD ARE CONFIGURED THE SAME APPROACHES ZERO

HARDWARE FAILURE CAN BE CATASTROPHIC

HEAVY WEIGHT CHANGE CONTROL PROCESSES SEEM LIKE A GOOD IDEA

Page 79: Agile Infra @AgileRoots 2009

VIRTUALMACHINES

Page 80: Agile Infra @AgileRoots 2009

VIRTUALMACHINES

A NEW ‘MACHINE’ API

Page 81: Agile Infra @AgileRoots 2009

VIRTUALMACHINES

A NEW ‘MACHINE’ API

MORE MACHINES TO CONFIGURE

Page 82: Agile Infra @AgileRoots 2009

VIRTUALMACHINES

A NEW ‘MACHINE’ API

MORE MACHINES TO CONFIGURE

DO NOT MAKE GOLDEN IMAGES

Page 83: Agile Infra @AgileRoots 2009

VIRTUALMACHINES

A NEW ‘MACHINE’ API

MORE MACHINES TO CONFIGURE

DO NOT MAKE GOLDEN IMAGES

REALLY FOIL BALLS

Page 84: Agile Infra @AgileRoots 2009

VIRTUALMACHINES

A NEW ‘MACHINE’ API

MORE MACHINES TO CONFIGURE

DO NOT MAKE GOLDEN IMAGES

WTF?REALLY FOIL BALLS

Page 85: Agile Infra @AgileRoots 2009

VIRTUALMACHINES

A NEW ‘MACHINE’ API

MORE MACHINES TO CONFIGURE

DO NOT MAKE GOLDEN IMAGES

WTF?REALLY FOIL BALLS

...OR SHOULD I SAY WTD?

Page 86: Agile Infra @AgileRoots 2009

INFRASTRUCTUREIS CODE!

Page 87: Agile Infra @AgileRoots 2009

INFRASTRUCTUREIS CODE!

AUTOMATE EVERYTHING

Page 88: Agile Infra @AgileRoots 2009

INFRASTRUCTUREIS CODE!

AUTOMATE EVERYTHING

GET MORE DONE SPEND LESS TIME DOING IT

Page 89: Agile Infra @AgileRoots 2009

INFRASTRUCTUREIS CODE!

AUTOMATE EVERYTHING

GET MORE DONE SPEND LESS TIME DOING IT

PEOPLE SPEND TIME MAKING DECISIONSNOT DOING TEDIOUS WORK OVER AND OVER

Page 90: Agile Infra @AgileRoots 2009

INFRASTRUCTUREIS CODE!

AUTOMATE EVERYTHING

GET MORE DONE SPEND LESS TIME DOING IT

PEOPLE SPEND TIME MAKING DECISIONSNOT DOING TEDIOUS WORK OVER AND OVER

NO LONGER MANAGING SERVERS, MANAGE SERVICES

Page 91: Agile Infra @AgileRoots 2009

INFRASTRUCTUREIS CODE!

AUTOMATE EVERYTHING

GET MORE DONE SPEND LESS TIME DOING IT

PEOPLE SPEND TIME MAKING DECISIONSNOT DOING TEDIOUS WORK OVER AND OVER

TAKE ADVANTAGE OF THE PROCESSES AND TOOLSWE HAVE FOR SOFTWARE DEVELOPMENT

NO LONGER MANAGING SERVERS, MANAGE SERVICES

Page 92: Agile Infra @AgileRoots 2009

MORE AND MORESERVERS TO MANAGE

Page 93: Agile Infra @AgileRoots 2009

MORE AND MORESERVERS TO MANAGE

BRING IT ON!!!

Page 94: Agile Infra @AgileRoots 2009

PLANNINGCommunication

CollaborationEstimation

Prioritization

Page 95: Agile Infra @AgileRoots 2009

NON-FUNCTIONALREQUIREMENTS

Page 96: Agile Infra @AgileRoots 2009

NON-FUNCTIONALREQUIREMENTS

REQUIREMENTS THAT WILL RENDER THE APPLICATION NON-FUNCTIONAL IF NOT FULFILLED

Page 97: Agile Infra @AgileRoots 2009

NON-FUNCTIONALREQUIREMENTS

REQUIREMENTS THAT WILL RENDER THE APPLICATION NON-FUNCTIONAL IF NOT FULFILLED

WTD?

Page 98: Agile Infra @AgileRoots 2009

NON-FUNCTIONALREQUIREMENTS

REQUIREMENTS THAT WILL RENDER THE APPLICATION NON-FUNCTIONAL IF NOT FULFILLED

WTD?

STOP THINKING LIKE THAT

Page 99: Agile Infra @AgileRoots 2009

REQUIREMENTS ARE REQUIREMENTS

Page 100: Agile Infra @AgileRoots 2009

REQUIREMENTS ARE REQUIREMENTS

A WEB APP IS THE INFRASTRUCTURE

Page 101: Agile Infra @AgileRoots 2009

REQUIREMENTS ARE REQUIREMENTS

A WEB APP IS THE INFRASTRUCTURE

WITHOUT INFRASTRUCTURE THERE IS NO APP

Page 102: Agile Infra @AgileRoots 2009

REQUIREMENTS ARE REQUIREMENTS

A WEB APP IS THE INFRASTRUCTURE

WITHOUT INFRASTRUCTURE THERE IS NO APP

A CHANGE IN USAGE PATTERNS CAN CRUSH THE INFRASTRUCTURE

Page 103: Agile Infra @AgileRoots 2009

REQUIREMENTS ARE REQUIREMENTS

A WEB APP IS THE INFRASTRUCTURE

WITHOUT INFRASTRUCTURE THERE IS NO APP

A CHANGE IN USAGE PATTERNS CAN CRUSH THE INFRASTRUCTURE

REQUIRES COLLABORATION BETWEEN DEV AND OPS

Page 104: Agile Infra @AgileRoots 2009

DEVELOPERS OPERATIONS

Page 105: Agile Infra @AgileRoots 2009

DEVELOPERS OPERATIONS

Page 106: Agile Infra @AgileRoots 2009

DEVELOPERS OPERATIONS

Page 107: Agile Infra @AgileRoots 2009

DEVELOPERS OPERATIONS

Page 108: Agile Infra @AgileRoots 2009

DEVELOPERS OPERATIONS

Page 109: Agile Infra @AgileRoots 2009

DEVELOPERS OPERATIONS

Page 110: Agile Infra @AgileRoots 2009

DEVELOPERS OPERATIONS

Page 111: Agile Infra @AgileRoots 2009

DEVELOPERS OPERATIONS

BOUNDARY OBJECTS

Page 112: Agile Infra @AgileRoots 2009

DEVELOPERS OPERATIONS

BOUNDARY OBJECTS

COMMUNITY OF INTEREST

Page 113: Agile Infra @AgileRoots 2009

DEVELOPERS OPERATIONS

BOUNDARY OBJECTS

COMMUNITY OF INTEREST

Page 114: Agile Infra @AgileRoots 2009

DEVELOPERS OPERATIONS

BOUNDARY OBJECTS

COMMUNITY OF INTERESTWWW .VISIBLEWORKINGS.COM/ANALOGYFEST/MARICK-BOUNDARY-OBJECTS.PDF

Page 115: Agile Infra @AgileRoots 2009

INFRASTRUCTUREIS CODE!

Page 116: Agile Infra @AgileRoots 2009

INFRASTRUCTUREIS CODE!

PLAN FOR INFRASTRUCTURE REQUIREMENTS

Page 117: Agile Infra @AgileRoots 2009

INFRASTRUCTUREIS CODE!

PLAN FOR INFRASTRUCTURE REQUIREMENTS

...BUT BE WILLING AND ABLE TO CHANGE THEM

Page 118: Agile Infra @AgileRoots 2009

INFRASTRUCTUREIS CODE!

OPERATIONS’ CUSTOMER IS THE APP

PLAN FOR INFRASTRUCTURE REQUIREMENTS

...BUT BE WILLING AND ABLE TO CHANGE THEM

Page 119: Agile Infra @AgileRoots 2009

INFRASTRUCTUREIS CODE!

OPERATIONS’ CUSTOMER IS THE APP

PLAN FOR INFRASTRUCTURE REQUIREMENTS

...BUT BE WILLING AND ABLE TO CHANGE THEM

IF THE INFRASTRUCTURE ISN’T WORKING NOTHING IS

Page 120: Agile Infra @AgileRoots 2009

INFRASTRUCTUREIS CODE!

OPERATIONS’ CUSTOMER IS THE APP

CREATE A CULTURE OF COLLABORATION

PLAN FOR INFRASTRUCTURE REQUIREMENTS

...BUT BE WILLING AND ABLE TO CHANGE THEM

IF THE INFRASTRUCTURE ISN’T WORKING NOTHING IS

Page 121: Agile Infra @AgileRoots 2009

INFRASTRUCTUREIS CODE!

OPERATIONS’ CUSTOMER IS THE APP

CREATE A CULTURE OF COLLABORATION

PLAN FOR INFRASTRUCTURE REQUIREMENTS

TAKE ADVANTAGE OF THE PROCESSES AND TOOLSWE HAVE FOR SOFTWARE DEVELOPMENT

...BUT BE WILLING AND ABLE TO CHANGE THEM

IF THE INFRASTRUCTURE ISN’T WORKING NOTHING IS

Page 122: Agile Infra @AgileRoots 2009

INFRASTRUCTUREIS CODE!

OPERATIONS’ CUSTOMER IS THE APP

CREATE A CULTURE OF COLLABORATION

PLAN FOR INFRASTRUCTURE REQUIREMENTS

TAKE ADVANTAGE OF THE PROCESSES AND TOOLSWE HAVE FOR SOFTWARE DEVELOPMENT

...BUT BE WILLING AND ABLE TO CHANGE THEM

IF THE INFRASTRUCTURE ISN’T WORKING NOTHING IS

Page 123: Agile Infra @AgileRoots 2009

INFRASTRUCTUREIS CODE!

OPERATIONS’ CUSTOMER IS THE APP

CREATE A CULTURE OF COLLABORATION

PLAN FOR INFRASTRUCTURE REQUIREMENTS

TAKE ADVANTAGE OF THE PROCESSES AND TOOLSWE HAVE FOR SOFTWARE DEVELOPMENT

...BUT BE WILLING AND ABLE TO CHANGE THEM

IF THE INFRASTRUCTURE ISN’T WORKING NOTHING IS

Page 124: Agile Infra @AgileRoots 2009

THE MOST IMPORTANT STATEMENT FROM THE

MANIFESTO...

Page 125: Agile Infra @AgileRoots 2009

THE MOST IMPORTANT STATEMENT FROM THE

MANIFESTO......MIGHT NOT BE THE VALUES...

Page 126: Agile Infra @AgileRoots 2009

THE MOST IMPORTANT STATEMENT FROM THE

MANIFESTO...

...OR THE PRINCIPLES...

...MIGHT NOT BE THE VALUES...

Page 127: Agile Infra @AgileRoots 2009
Page 128: Agile Infra @AgileRoots 2009

‘We are uncovering better ways of developing software by doing it and

helping others do it.’

Page 129: Agile Infra @AgileRoots 2009

‘We are uncovering better ways of developing software by doing it and

helping others do it.’

Page 130: Agile Infra @AgileRoots 2009

K E E P U N C O V E R I N G

Page 131: Agile Infra @AgileRoots 2009

K E E P U N C O V E R I N G

Page 132: Agile Infra @AgileRoots 2009

[email protected]/littleidea

Page 133: Agile Infra @AgileRoots 2009

[email protected]/littleidea