The document discusses the concepts of agile infrastructure and agile practices. It begins by defining what agile means according to its original manifesto and principles. It then explores how agile has manifested in different roles and teams. The document notes that infrastructure is now code and the lines between development and operations are blurring. It provides examples of shared practices that cross boundaries. Finally, it discusses how the future requires automated infrastructure, collaboration between teams, and an ability to enable business needs through tools and culture.
6. Love working for startups
Andrew Clay
Shafer
A Villager...
Programmer
7. Love working for startups
‘Agile’ and stuff
Andrew Clay
Shafer
A Villager...
Programmer
8. Love working for startups
‘Agile’ and stuff
Reductive Labs
Andrew Clay
Shafer
A Villager...
Programmer
9. Love working for startups
‘Agile’ and stuff
Reductive Labs
Andrew Clay
Shafer
A Villager...
People behind Puppet
Programmer
10. Love working for startups
‘Agile’ and stuff
Reductive Labs
Andrew Clay
Shafer
A Villager...
People behind Puppet
Programmer
The rest is complicated...
47. Manifesto for Agile Software Development
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
68. BUT What
Is Agile???
PLANNING ENGINEERING
DEVELOPERS
69. BUT What
Is Agile???
PLANNING ENGINEERING
DEVELOPERS
PRODUCT
OWNERS
70. BUT What
Is Agile???
PLANNING ENGINEERING
DEVELOPERS
PRODUCT
OWNERS
TESTERS
71. BUT What
Is Agile???
PLANNING ENGINEERING
DEVELOPERS EXECUTIVES
PRODUCT
OWNERS
TESTERS
72. BUT What
Is Agile???
PLANNING ENGINEERING
DEVELOPERS EXECUTIVES
PRODUCT SYSTEM ADMINISTRATORS
OWNERS
TESTERS
73. BUT What
Is Agile???
PLANNING ENGINEERING
DEVELOPERS EXECUTIVES
PRODUCT SYSTEM ADMINISTRATORS
OWNERS DATABASE ADMINISTRATORS
TESTERS
74. BUT What
Is Agile???
PLANNING ENGINEERING
DEVELOPERS EXECUTIVES
PRODUCT SYSTEM ADMINISTRATORS
OWNERS DATABASE ADMINISTRATORS
TESTERS
NETWORK ENGINEERS
75. BUT What
Is Agile???
PLANNING ENGINEERING
DEVELOPERS EXECUTIVES
PRODUCT SYSTEM ADMINISTRATORS
OWNERS DATABASE ADMINISTRATORS
TESTERS
NETWORK ENGINEERS
DESIGNERS
76. BUT What
Is Agile???
PLANNING ENGINEERING
DEVELOPERS EXECUTIVES
PRODUCT SYSTEM ADMINISTRATORS
OWNERS DATABASE ADMINISTRATORS
TESTERS
NETWORK ENGINEERS
DESIGNERS
USABILITY EXPERTS
77. BUT What
Is Agile???
PLANNING ENGINEERING
CIRCLE OF HAPPINESS
DEVELOPERS EXECUTIVES
PRODUCT SYSTEM ADMINISTRATORS
OWNERS DATABASE ADMINISTRATORS
TESTERS
NETWORK ENGINEERS
DESIGNERS
USABILITY EXPERTS
78. BUT What
Is Agile???
PLANNING ENGINEERING
CIRCLE OF HAPPINESS
DEVELOPERS EXECUTIVES
PRODUCT SYSTEM ADMINISTRATORS
OWNERS DATABASE ADMINISTRATORS
TESTERS
NETWORK ENGINEERS
DESIGNERS
USABILITY EXPERTS
85. Continuous
Pair Programming
Integration
Planning Poker Refactor
Simple Design
(YAGNI)
Test Driven
Development
86. Continuous
Pair Programming
Integration
Planning Poker Refactor
Simple Design
(YAGNI) Sustainable Pace
Test Driven
Development
87. Continuous
Pair Programming
Integration
Planning Poker Refactor
Simple Design
(YAGNI) Sustainable Pace
Test Driven
Development
Small Releases
88. Continuous
Pair Programming
Integration
Planning Poker Refactor
Simple Design
(YAGNI) Sustainable Pace
Test Driven
Development
Small Releases
Shared Metaphor
89. Continuous
Pair Programming
Integration
Planning Poker Refactor
Simple Design
(YAGNI) Sustainable Pace
Test Driven
Development
Small Releases
Shared Metaphor Coding Standards
90. Continuous
Pair Programming
Integration
Planning Poker Refactor
Simple Design
(YAGNI) Sustainable Pace
Test Driven
Development
Small Releases
Shared Metaphor Coding Standards
Onsite ‘Customer’
91. Continuous
Pair Programming
Integration
Planning Poker Refactor
Simple Design
(YAGNI) Sustainable Pace
Test Driven
Development
Small Releases
Shared Metaphor Coding Standards
Onsite ‘Customer’ Collective Ownership
122. Lack of awareness of other disciplines is bad...
Leads to over engineering...
123. Lack of awareness of other disciplines is bad...
Leads to over engineering... Leads to catastrophic failures...
124. Lack of awareness of other disciplines is bad...
Leads to over engineering... Leads to catastrophic failures...
Tools, knowledge, experience, discipline
125. Lack of awareness of other disciplines is bad...
Leads to over engineering... Leads to catastrophic failures...
Tools, knowledge, experience, discipline
Automated Infrastructure
126. Lack of awareness of other disciplines is bad...
Leads to over engineering... Leads to catastrophic failures...
Tools, knowledge, experience, discipline
Automated Infrastructure
Version Control Everything!
127. Lack of awareness of other disciplines is bad...
Leads to over engineering... Leads to catastrophic failures...
Tools, knowledge, experience, discipline
Automated Infrastructure
Version Control Everything! Collaborate
128. Lack of awareness of other disciplines is bad...
Leads to over engineering... Leads to catastrophic failures...
Tools, knowledge, experience, discipline
Automated Infrastructure
Version Control Everything! Collaborate
Shared Version Control
129. Lack of awareness of other disciplines is bad...
Leads to over engineering... Leads to catastrophic failures...
Tools, knowledge, experience, discipline
Automated Infrastructure
Version Control Everything! Collaborate
Shared Version Control
Don’t do work you don’t have to...
130. Lack of awareness of other disciplines is bad...
Leads to over engineering... Leads to catastrophic failures...
Tools, knowledge, experience, discipline
Automated Infrastructure
Version Control Everything! Collaborate
Shared Version Control
Don’t do work you don’t have to...
Monitor Everything
131. Lack of awareness of other disciplines is bad...
Leads to over engineering... Leads to catastrophic failures...
Tools, knowledge, experience, discipline
Automated Infrastructure
Version Control Everything! Collaborate
Shared Version Control
Don’t do work you don’t have to...
Monitor Everything
Don’t be fingerpointy
132. Lack of awareness of other disciplines is bad...
Leads to over engineering... Leads to catastrophic failures...
Tools, knowledge, experience, discipline
Automated Infrastructure
Version Control Everything! Collaborate
Shared Version Control
Don’t do work you don’t have to...
Monitor Everything
Don’t be fingerpointy
Always Ship Trunk
133. Lack of awareness of other disciplines is bad...
Leads to over engineering... Leads to catastrophic failures...
Tools, knowledge, experience, discipline
Automated Infrastructure
Version Control Everything! Collaborate
Shared Version Control
Don’t do work you don’t have to...
Monitor Everything
Don’t be fingerpointy
Always Ship Trunk
Don’t Stereotype
134. Lack of awareness of other disciplines is bad...
Leads to over engineering... Leads to catastrophic failures...
Tools, knowledge, experience, discipline
Automated Infrastructure
Version Control Everything! Collaborate
Shared Version Control
Don’t do work you don’t have to...
Monitor Everything
Don’t be fingerpointy
Always Ship Trunk
Don’t Stereotype
Shared Metrics
135. Lack of awareness of other disciplines is bad...
Leads to over engineering... Leads to catastrophic failures...
Tools, knowledge, experience, discipline
Automated Infrastructure
Version Control Everything! Collaborate
Shared Version Control
Don’t do work you don’t have to...
Monitor Everything
Don’t be fingerpointy
Always Ship Trunk
Don’t Stereotype
Shared Metrics
The business requires change
136. Lack of awareness of other disciplines is bad...
Leads to over engineering... Leads to catastrophic failures...
Tools, knowledge, experience, discipline
Automated Infrastructure
Version Control Everything! Collaborate
Shared Version Control
Don’t do work you don’t have to...
Monitor Everything
Don’t be fingerpointy
Always Ship Trunk
Don’t Stereotype
Shared Metrics
The business requires change
Lower risk through tools and culture
137. Lack of awareness of other disciplines is bad...
Leads to over engineering... Leads to catastrophic failures...
Tools, knowledge, experience, discipline
Automated Infrastructure
Version Control Everything! Collaborate
Shared Version Control
Don’t do work you don’t have to...
Monitor Everything
Don’t be fingerpointy
Always Ship Trunk
Don’t Stereotype
Shared Metrics
The business requires change
Lower risk through tools and culture
One Step Build and Deploy
138. Lack of awareness of other disciplines is bad...
Leads to over engineering... Leads to catastrophic failures...
Tools, knowledge, experience, discipline
Automated Infrastructure
Version Control Everything! Collaborate
Shared Version Control
Don’t do work you don’t have to...
Monitor Everything
Don’t be fingerpointy
Always Ship Trunk
Don’t Stereotype
Shared Metrics
The business requires change
Lower risk through tools and culture
One Step Build and Deploy
Ops job is to enable the business
144. What are the
Best Practices?
How about ‘better than we
did yesterday’ practices?
Robert Mecklenburg
145. What are the
Best Practices?
How about ‘better than we
did yesterday’ practices?
Or ‘seems like a good idea
right now’ practices?
Robert Mecklenburg
150. We believe Agile software development is being
dumbed down, commodified, and is losing its spirit.
We seek to replace the current name with one
having two virtues: first, that it capture more exactly
the attitudes originally behind Agile; second, that it
be obscure enough that no one will assume they
already know what it means and that—amazingly
enough!—they are already doing it.
arxta.net
152. AR⊗TA
Artisanal Retro-Futurism
crossed with
Team-Scale Anarcho-Syndicalism
153. AR⊗TA
Artisanal Retro-Futurism
crossed with
Team-Scale Anarcho-Syndicalism
care about the cheese
154. AR⊗TA
Artisanal Retro-Futurism
crossed with
Team-Scale Anarcho-Syndicalism
care about the cheese
a genuine fascination with technology
155. AR⊗TA
Artisanal Retro-Futurism
crossed with
Team-Scale Anarcho-Syndicalism
care about the cheese
a genuine fascination with technology
focus on the team
156. AR⊗TA
Artisanal Retro-Futurism
crossed with
Team-Scale Anarcho-Syndicalism
care about the cheese
a genuine fascination with technology
focus on the team
emphasis on direct action
157. AR⊗TA
Artisanal Retro-Futurism
crossed with
Team-Scale Anarcho-Syndicalism
care about the cheese
a genuine fascination with technology
focus on the team
emphasis on direct action
158. AR⊗TA
Artisanal Retro-Futurism
crossed with
Team-Scale Anarcho-Syndicalism
care about the cheese
a genuine fascination with technology
focus on the team
emphasis on direct action