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.
6. Agile Team member
Tolerated at Salt Lake Agile Roundtable
ANDREW CLAY
SHAFER
Developer Once Upon A Time
Mostly Worked For Start Ups
7. Agile Team member
Tolerated at Salt Lake Agile Roundtable
ANDREW CLAY
SHAFER
Developer Once Upon A Time
Mostly Worked For Start Ups
Founding Partner
Reductive Labs Inc.
8. Agile Team member
All Around Trouble Maker
Tolerated at Salt Lake Agile Roundtable
ANDREW CLAY
SHAFER
Developer Once Upon A Time
Mostly Worked For Start Ups
Founding Partner
Reductive Labs Inc.
9. Agile Team member
All Around Trouble Maker
Tolerated at Salt Lake Agile Roundtable
ANDREW CLAY
SHAFER
Developer Once Upon A Time
Mostly Worked For Start Ups
Founding Partner
Reductive Labs Inc.
The Rest is Complicated...
10. O H Y E A H , T H E R E I S A LWAY S A D U C K . . .
25. BUT WHAT
IS
AGILE???
PLANNING ENGINEERING
DEVELOPERS
26. BUT WHAT
IS
AGILE???
PLANNING ENGINEERING
DEVELOPERS
PRODUCT
OWNERS
27. BUT WHAT
IS
AGILE???
PLANNING ENGINEERING
DEVELOPERS
PRODUCT
OWNERS
TESTERS
28. BUT WHAT
IS
AGILE???
PLANNING ENGINEERING
EXECUTIVES
DEVELOPERS
PRODUCT
OWNERS
TESTERS
29. BUT WHAT
IS
AGILE???
PLANNING ENGINEERING
EXECUTIVES
DEVELOPERS
SYSTEM ADMINISTRATORS
PRODUCT
OWNERS
TESTERS
30. BUT WHAT
IS
AGILE???
PLANNING ENGINEERING
EXECUTIVES
DEVELOPERS
SYSTEM ADMINISTRATORS
PRODUCT
OWNERS DATABASE ADMINISTRATORS
TESTERS
31. BUT WHAT
IS
AGILE???
PLANNING ENGINEERING
EXECUTIVES
DEVELOPERS
SYSTEM ADMINISTRATORS
PRODUCT
OWNERS DATABASE ADMINISTRATORS
TESTERS NETWORK ENGINEERS
32. BUT WHAT
IS
AGILE???
PLANNING ENGINEERING
EXECUTIVES
DEVELOPERS
SYSTEM ADMINISTRATORS
PRODUCT
OWNERS DATABASE ADMINISTRATORS
TESTERS NETWORK ENGINEERS
DESIGNERS
33. BUT WHAT
IS
AGILE???
PLANNING ENGINEERING
EXECUTIVES
DEVELOPERS
SYSTEM ADMINISTRATORS
PRODUCT
OWNERS DATABASE ADMINISTRATORS
TESTERS NETWORK ENGINEERS
DESIGNERS
USABILITY EXPERTS
34. BUT WHAT
IS
AGILE???
PLANNING ENGINEERING
CIRCLE OF HAPPINESS
EXECUTIVES
DEVELOPERS
SYSTEM ADMINISTRATORS
PRODUCT
OWNERS DATABASE ADMINISTRATORS
TESTERS NETWORK ENGINEERS
DESIGNERS
USABILITY EXPERTS
35. BUT WHAT
IS
AGILE???
PLANNING ENGINEERING
CIRCLE OF HAPPINESS
EXECUTIVES
DEVELOPERS
SYSTEM ADMINISTRATORS
PRODUCT
OWNERS DATABASE ADMINISTRATORS
TESTERS NETWORK ENGINEERS
DESIGNERS
USABILITY EXPERTS
36. BUT WHAT
IS
AGILE???
PLANNING ENGINEERING
CIRCLE OF HAPPINESS
EXECUTIVES
DEVELOPERS
SYSTEM ADMINISTRATORS
PRODUCT
OWNERS DATABASE ADMINISTRATORS
TESTERS NETWORK ENGINEERS
DESIGNERS
USABILITY EXPERTS
37. BUT THE WAY SOFTWARE
GETS DELIVERED HAS
CHANGED A LOT...
38. BUT THE WAY SOFTWARE
GETS DELIVERED HAS
CHANGED A LOT...
...AND THINGS ARE CHANGING FAST RIGHT NOW .
44. WHO IS WORKING ON A
WEB APP?
WHERE DOES THAT WEB APP RUN?
45. WHO IS WORKING ON A
WEB APP?
WHERE DOES THAT WEB APP RUN?
WHO TAKES CARE OF THOSE SERVERS?
46. 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?
47. 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?
63. BUT WHY?
BACKLOG OF REQUESTS
CONFIGURATION OF CRITICAL SERVICES ARE OFTEN NOT
DOCUMENTED AND MUST BE RECREATED
64. BUT WHY?
BACKLOG OF REQUESTS
CONFIGURATION OF CRITICAL SERVICES ARE OFTEN NOT
DOCUMENTED AND MUST BE RECREATED
INCONSISTENCIES CAUSE CONFUSION AND MISTAKES
65. BUT WHY?
BACKLOG OF REQUESTS
CONFIGURATION OF CRITICAL SERVICES ARE OFTEN NOT
DOCUMENTED AND MUST BE RECREATED
INCONSISTENCIES CAUSE CONFUSION AND MISTAKES
MORE AND MORE SYSTEMS TO MANAGE
66. BUT WHY?
BACKLOG OF REQUESTS
CONFIGURATION OF CRITICAL SERVICES ARE OFTEN NOT
DOCUMENTED AND MUST BE RECREATED
INCONSISTENCIES CAUSE CONFUSION AND MISTAKES
MORE AND MORE SYSTEMS TO MANAGE
WORK ON THE BIGGEST FIRE
74. WHAT DOES THAT
REALLY MEAN?
DEPLOYMENTS AND UPGRADES
ARE EXPENSIVE, TEDIOUS AND ERROR PRONE
75. 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
76. 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
77. 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
78. 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
MORE AND MORE
SYSTEMS TO MANAGE
88. INFRASTRUCTURE
IS CODE!
AUTOMATE EVERYTHING
GET MORE DONE SPEND LESS TIME DOING IT
89. INFRASTRUCTURE
IS CODE!
AUTOMATE EVERYTHING
GET MORE DONE SPEND LESS TIME DOING IT
PEOPLE SPEND TIME MAKING DECISIONS
NOT DOING TEDIOUS WORK OVER AND OVER
90. INFRASTRUCTURE
IS CODE!
AUTOMATE EVERYTHING
GET MORE DONE SPEND LESS TIME DOING IT
PEOPLE SPEND TIME MAKING DECISIONS
NOT DOING TEDIOUS WORK OVER AND OVER
NO LONGER MANAGING SERVERS, MANAGE SERVICES
91. INFRASTRUCTURE
IS CODE!
AUTOMATE EVERYTHING
GET MORE DONE SPEND LESS TIME DOING IT
PEOPLE SPEND TIME MAKING DECISIONS
NOT DOING TEDIOUS WORK OVER AND OVER
NO LONGER MANAGING SERVERS, MANAGE SERVICES
TAKE ADVANTAGE OF THE PROCESSES AND TOOLS
WE HAVE FOR SOFTWARE DEVELOPMENT
101. REQUIREMENTS ARE
REQUIREMENTS
A WEB APP IS THE INFRASTRUCTURE
WITHOUT INFRASTRUCTURE
THERE IS NO APP
102. REQUIREMENTS ARE
REQUIREMENTS
A WEB APP IS THE INFRASTRUCTURE
WITHOUT INFRASTRUCTURE
THERE IS NO APP
A CHANGE IN USAGE PATTERNS
CAN CRUSH THE INFRASTRUCTURE
103. 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
116. INFRASTRUCTURE
IS CODE!
PLAN FOR INFRASTRUCTURE REQUIREMENTS
117. INFRASTRUCTURE
IS CODE!
PLAN FOR INFRASTRUCTURE REQUIREMENTS
...BUT BE WILLING AND ABLE TO CHANGE THEM
118. INFRASTRUCTURE
IS CODE!
PLAN FOR INFRASTRUCTURE REQUIREMENTS
...BUT BE WILLING AND ABLE TO CHANGE THEM
OPERATIONS’ CUSTOMER IS THE APP
119. INFRASTRUCTURE
IS CODE!
PLAN FOR INFRASTRUCTURE REQUIREMENTS
...BUT BE WILLING AND ABLE TO CHANGE THEM
OPERATIONS’ CUSTOMER IS THE APP
IF THE INFRASTRUCTURE ISN’T WORKING NOTHING IS
120. INFRASTRUCTURE
IS CODE!
PLAN FOR INFRASTRUCTURE REQUIREMENTS
...BUT BE WILLING AND ABLE TO CHANGE THEM
OPERATIONS’ CUSTOMER IS THE APP
IF THE INFRASTRUCTURE ISN’T WORKING NOTHING IS
CREATE A CULTURE OF COLLABORATION
121. INFRASTRUCTURE
IS CODE!
PLAN FOR INFRASTRUCTURE REQUIREMENTS
...BUT BE WILLING AND ABLE TO CHANGE THEM
OPERATIONS’ CUSTOMER IS THE APP
IF THE INFRASTRUCTURE ISN’T WORKING NOTHING IS
CREATE A CULTURE OF COLLABORATION
TAKE ADVANTAGE OF THE PROCESSES AND TOOLS
WE HAVE FOR SOFTWARE DEVELOPMENT
122. INFRASTRUCTURE
IS CODE!
PLAN FOR INFRASTRUCTURE REQUIREMENTS
...BUT BE WILLING AND ABLE TO CHANGE THEM
OPERATIONS’ CUSTOMER IS THE APP
IF THE INFRASTRUCTURE ISN’T WORKING NOTHING IS
CREATE A CULTURE OF COLLABORATION
TAKE ADVANTAGE OF THE PROCESSES AND TOOLS
WE HAVE FOR SOFTWARE DEVELOPMENT
123. INFRASTRUCTURE
IS CODE!
PLAN FOR INFRASTRUCTURE REQUIREMENTS
...BUT BE WILLING AND ABLE TO CHANGE THEM
OPERATIONS’ CUSTOMER IS THE APP
IF THE INFRASTRUCTURE ISN’T WORKING NOTHING IS
CREATE A CULTURE OF COLLABORATION
TAKE ADVANTAGE OF THE PROCESSES AND TOOLS
WE HAVE FOR SOFTWARE DEVELOPMENT