I build the future - Agile 2014

97
I build the future Andrew Clay Shafer Agile 2014

description

 

Transcript of I build the future - Agile 2014

Page 1: I build the future - Agile 2014

I build the futureAndrew Clay ShaferAgile 2014

Page 2: I build the future - Agile 2014

@littleidea

Page 3: I build the future - Agile 2014

me

Page 4: I build the future - Agile 2014

@littleidea

Page 5: I build the future - Agile 2014

three stone cutters walk into a Pareto Inefficient Nash Equilibrium

Page 6: I build the future - Agile 2014

you have to be serious

Page 7: I build the future - Agile 2014

do you have to be so serious?

Page 8: I build the future - Agile 2014

buckle up

Page 9: I build the future - Agile 2014

meanwhile…

Page 10: I build the future - Agile 2014

software kept eating the world

Page 11: I build the future - Agile 2014

in conclusion

Page 12: I build the future - Agile 2014

you are either building a software business...

or you will be losing to someone who is...

Page 13: I build the future - Agile 2014

obvious

Page 14: I build the future - Agile 2014

you are either building a learning organization...

or you will be losing to someone who is...

Page 15: I build the future - Agile 2014
Page 16: I build the future - Agile 2014

everybody wants to go to heaven

none of them want to die

Page 17: I build the future - Agile 2014

learn the past

Page 18: I build the future - Agile 2014

my past

Page 19: I build the future - Agile 2014

AgileI absolutely hated it

Page 20: I build the future - Agile 2014

I hated the dogma

I hated that it wasn’t working

Page 21: I build the future - Agile 2014

Beware the Expert “the keeper of the Agile”

Page 22: I build the future - Agile 2014

People say ‘Agile’, they really mean ‘Scrum’

Page 23: I build the future - Agile 2014

the most tepid Scrum

Page 24: I build the future - Agile 2014

the most tepid version of the most tepid Agile

Page 25: I build the future - Agile 2014

Agile was broken

Page 26: I build the future - Agile 2014

I didn’t realize what or why

Page 27: I build the future - Agile 2014

and then I got lucky...

Page 28: I build the future - Agile 2014

Salt Lake Agile Roundtable

Page 29: I build the future - Agile 2014

I went there for ammunition.

Page 30: I build the future - Agile 2014

what I got was more interesting I got lucky

Page 31: I build the future - Agile 2014

I was never interested in ‘being’ Agile...

Page 32: I build the future - Agile 2014
Page 33: I build the future - Agile 2014

Context Matters

Page 34: I build the future - Agile 2014

how meta is too meta?

Page 35: I build the future - Agile 2014

obey, digress, separate

Page 36: I build the future - Agile 2014

digression…

Page 37: I build the future - Agile 2014

game theorythe study of mathematical models of conflict and cooperation between intelligent rational

decisions makers

Page 38: I build the future - Agile 2014

rationalchoosing to maximize a utility function

Page 39: I build the future - Agile 2014

information is bounded

Page 40: I build the future - Agile 2014

rationality is local

Page 41: I build the future - Agile 2014

Locally Rational Decision Making: The Distracting Effect of Information on Managerial Performance

This paper describes a phenomenon called “locally rational” decision-making, in which the mere presence of information may have dysfunctional consequences even if decision makers do not process the information incorrectly. !Using the results from an experiment conducted with a strategic market simulation game, we find that the accessibility of information results in a disposition to focus on those components of decision-making most clearly addressed by the information. !If these are not the components most closely tied to success, overall performance may in fact suffer. The decision-making process is thus “locally rational” since it may be optimal with respect to specific components of a larger plan, but globally suboptimal with regard to ultimate outcomes and for the organization as a whole.

http://pubsonline.informs.org/doi/abs/10.1287/mnsc.38.2.212?journalCode=mnsc

Page 42: I build the future - Agile 2014

more of my past

Page 43: I build the future - Agile 2014
Page 44: I build the future - Agile 2014

humble and grateful

Page 45: I build the future - Agile 2014

somebody pinch me

Page 46: I build the future - Agile 2014
Page 47: I build the future - Agile 2014

even more past

Page 48: I build the future - Agile 2014

1945 to 1965: The Origins

1965 to 1985: The Software Crisis

1985 to 1989: No Silver Bullet

1990 to 1999: Prominence of the Internet

2000 to Present: Lightweight Methodologies

I know this is true, because Wikipedia

Page 49: I build the future - Agile 2014

1970s 1980s 1990s 2000s future?

structured programming

Cap Gemini SDM

structured systems analysis and design methodology (ssadm)

Information Requirement Analysis /Soft systems methodology (ssm)

Object-oriented programming (OOP)

Rapid application development (RAD)

Dynamic systems development method (DSDM)

Scrum

Team software process

Extreme programming (XP) capability maturity model (CMM)

Capability Maturity Model Integration (CMMI)

Information Technology Infrastructure Library (ITIL) ITIL 2007

devops

???

kanbanlean software

Page 50: I build the future - Agile 2014

CMMI, so amaze, wow

Page 51: I build the future - Agile 2014

ITIL sounds great

• ITIL Service Strategy: understands organizational objectives and customer needs.

• ITIL Service Design: turns the service strategy into a plan for delivering the business objectives.

• ITIL Service Transition: develops and improves capabilities for introducing new services into supported environments.

• ITIL Service Operation: manages services in supported environments.

• ITIL Continual Service Improvement: achieves services incremental and large-scale improvements.

Page 52: I build the future - Agile 2014

CMMI, make it stopCMMI for Development model: !

Maturity Level 2 - Managed CM - Configuration Management MA - Measurement and Analysis

PMC - Project Monitoring and Control PP - Project Planning

PPQA - Process and Product Quality Assurance REQM - Requirements Management

SAM - Supplier Agreement Management !Maturity Level 3 - Defined

DAR - Decision Analysis and Resolution IPM - Integrated Project Management

OPD - Organizational Process Definition OPF - Organizational Process Focus

OT - Organizational Training PI - Product Integration

RD - Requirements Development RSKM - Risk Management

TS - Technical Solution VAL - Validation

VER - Verification !Maturity Level 4 - Quantitatively Managed

OPP - Organizational Process Performance QPM - Quantitative Project Management !

Maturity Level 5 - Optimizing CAR - Causal Analysis and Resolution

OPM - Organizational Performance Management Maturity levels in CMMI for services[edit]

There are five maturity levels. Maturity level ratings are awarded for levels 2 through 5.

Maturity levels in CMMI for services !Maturity Level 2 - Managed

CM - Configuration Management MA - Measurement and Analysis

PPQA - Process and Product Quality Assurance REQM - Requirements Management

SAM - Supplier Agreement Management SD - Service Delivery

WMC - Work Monitoring and Control WP - Work Planning !

Maturity Level 3 - Defined CAM - Capacity and Availability Management

DAR - Decision Analysis and Resolution IRP - Incident Resolution and Prevention

IWM - Integrated Work Management OPD - Organizational Process Definition

OPF - Organizational Process Focus OT - Organizational Training RSKM - Risk Management SCON - Service Continuity

SSD - Service System Development SST - Service System Transition

STSM - Strategic Service Management !Maturity Level 4 - Quantitatively Managed

OPP - Organizational Process Performance QWM - Quantitative Work Management !

Maturity Level 5 - Optimizing CAR - Causal Analysis and Resolution

OPM - Organizational Performance Management

Maturity levels in CMMI for acquisition !Maturity Level 2 - Managed

AM - Agreement Management ARD - Acquisition Requirements Development

CM - Configuration Management MA - Measurement and Analysis

PMC - Project Monitoring and Control PP - Project Planning

PPQA - Process and Product Quality Assurance REQM - Requirements Management

SSAD - Solicitation and Supplier Agreement Development !Maturity Level 3 - Defined

ATM - Acquisition Technical Management AVAL - Acquisition Validation

AVER - Acquisition Verification DAR - Decision Analysis and Resolution IPM - Integrated Project Management

OPD - Organizational Process Definition OPF - Organizational Process Focus

OT - Organizational Training RSKM - Risk Management !

Maturity Level 4 - Quantitatively Managed OPP - Organizational Process Performance

QPM - Quantitative Project Management !Maturity Level 5 - Optimizing

CAR - Causal Analysis and Resolution OPM - Organizational Performance Management

Page 53: I build the future - Agile 2014

ITIL

Page 54: I build the future - Agile 2014

ask me about scrum

Page 55: I build the future - Agile 2014

all practice, no theory

no practice, all theory

Page 56: I build the future - Agile 2014

Theory Practice

Page 57: I build the future - Agile 2014

Theory Practice

CMMI

ITILScrum

XPCrystal kanban

Page 58: I build the future - Agile 2014

software has been developed

Page 59: I build the future - Agile 2014

for every ‘must have’ practice, there exists a

successful counter example

Page 60: I build the future - Agile 2014
Page 61: I build the future - Agile 2014

success doesn’t result from a list of practices

Page 62: I build the future - Agile 2014

success doesn’t result from secret techniques

Page 63: I build the future - Agile 2014

success results from choice and circumstance

Page 64: I build the future - Agile 2014
Page 65: I build the future - Agile 2014

www.techdarkside.com

Page 66: I build the future - Agile 2014

break the cycle

Page 67: I build the future - Agile 2014

innovations in infrastructure

guiding ideas skills and capabilities

awareness and

sensibilities

theory, methods and

tools

domain of action

attitudes and

beliefs

domain of enduring change

(organizational architecture)

(deep learning cycle)

Page 68: I build the future - Agile 2014

improve the work > do the work

Page 69: I build the future - Agile 2014

do be do be do

Page 70: I build the future - Agile 2014
Page 71: I build the future - Agile 2014

@littleidea’s practical guide to organizational transformation

Page 72: I build the future - Agile 2014

@littleidea’s practical guide to organizational transformation

Page 73: I build the future - Agile 2014

@littleidea’s practical guide to organizational transformation

Page 74: I build the future - Agile 2014

panacea peddlers as far as the eye can see

Page 75: I build the future - Agile 2014

buy MY secret to scale agile

Page 76: I build the future - Agile 2014

we know how to draw the owl

Page 77: I build the future - Agile 2014

why do we stop drawing?

Page 78: I build the future - Agile 2014

nothing may be more difficult than getting a person to understand something, when her salary depends upon not understanding it

Page 79: I build the future - Agile 2014
Page 80: I build the future - Agile 2014

We are uncovering better ways of developing software by doing it and helping others do it...

Page 81: I build the future - Agile 2014

We are uncovering better ways of developing infrastructure by doing it and helping others do it...

Page 82: I build the future - Agile 2014

We are uncovering better ways of developing organizations by doing it and helping others do it...

Page 83: I build the future - Agile 2014

Through this work we have come to value:

• individuals interacting with awesome processes and tools

• working software... period, and documentation is nice too

• delighting customers

• learning from change and changing from learning

Page 84: I build the future - Agile 2014

this is not over

Page 85: I build the future - Agile 2014
Page 86: I build the future - Agile 2014

keep uncovering

Page 87: I build the future - Agile 2014

you won’t succeed by finding devops

Page 88: I build the future - Agile 2014

you won’t succeed by hiring the next buzzword consultant

Page 89: I build the future - Agile 2014

The learning organization is one that has the capacity to integrate people and structures in order to move toward continuous learning and change.

Page 90: I build the future - Agile 2014

success is about being the right people

Page 91: I build the future - Agile 2014

success is about becoming the right people

Page 92: I build the future - Agile 2014

don’t be afraid

Page 93: I build the future - Agile 2014

never stop becoming

Page 94: I build the future - Agile 2014

don’t limit yourself

Page 95: I build the future - Agile 2014

don’t limit us

Page 96: I build the future - Agile 2014

BECOME AWESOME

Page 97: I build the future - Agile 2014

come at me

@littleidea