Top Banner
16

Greenfields considered harmful

Jul 11, 2015

Download

Technology

Mike Wessling
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Greenfields considered harmful
Page 2: Greenfields considered harmful

Greenfields considered Harmful

Or at least not very Agile

by Mike Wessling

[email protected]

Page 3: Greenfields considered harmful

___________________

< I feel drained... >

-------------------

\ ^__^

\ (oo)\_______ ________

(__)\ )\/\ |Super |

||----W | |Milker|

|| UDDDDDDDDD|______|

Page 4: Greenfields considered harmful

Long term views required

Greenfields cost time and investments

+

Greenfield opportunites are big and rate events

=

Must cover a large chunk of future

->

But the Future is harder and harder to predict

Page 5: Greenfields considered harmful

__________

< Et Voila >

----------

|-------------------------------|

/| /|

/ | / |

/ |----------------------------/--|

/ / / /

/ / / /

/ / / /

/ / ^__^ / /

/ / (oo)\_______ / /

/ / (__)\ )\/\ / /

/ / ||----w | / /

/ / || || / /

/ / / /

|----------||--------||---------| /

| / ||--/--\--|| | /

|/ ||-/----\-|| |/

|----------||--------||---------|

Page 6: Greenfields considered harmful

Illusion of Done

Goal is to delivery the complete thing

Versus

continuous improvable thing

Page 7: Greenfields considered harmful
Page 8: Greenfields considered harmful

Big integrated solutions->

Less focus on modular & replaceable designs->

Unknown dependencies->

Stuck with the solution for a long time

Consider : Multiple generations

Danger big monoliths

Page 9: Greenfields considered harmful

____________________

< I don't like grass >

--------------------

\ /\ ___ /\

\ // \/ \/ \\

(( O O ))

\\ / \ //

\/ | | \/

| | | |

| | | |

| o |

| | | |

|m| |m|

Page 10: Greenfields considered harmful

Long Feedback Loops

Starting from scratch + big goals->

Long time to deliver->

Separates Dev from Ops/Users->

Long time before feedback (from users, reality, operations)

->Lots of invested time and money

->Hard to change course

Page 11: Greenfields considered harmful

_____________

< Happy now?? >

-------------

\ (__)

\ /oo|

\ (_"_)*+++++++++*

//I#\\\\\\\\I\

I[I|I|||||I I `

I`I'///'' I I

I I I I

~ ~ ~ ~

Scowleton

Page 12: Greenfields considered harmful

Creates Legacy

What about the last generation greenfield?

&

What about the cows in the old fields..

->

Deny new features?

&&/||

Wait until they die/leave?

Page 13: Greenfields considered harmful

_______________

< Rest in Peace >

---------------

\ , ,

\ /( )`

\ \ \___ / |

/- _ `-/ '

(/\/ \ \ /\

/ / | ` \

O O ) / |

`-^--'`< '

(_.) _ ) /

`.___/` /

`-----' /

<----. __ / __ \

<----|====O)))==) \) /====

<----' `--' `.__,' \

| |

\ /

______( (_ / \______

,' ,-----' | \

`--{__________) \/

Page 14: Greenfields considered harmful

From Cradle to what??

Think about Retirement when designing

->

Even consider a test retirement

->

Easier to replace/upgrade parts when needed.

Page 15: Greenfields considered harmful

In summary – Design for Change

• Now is old and the future is fluid.

• Changeability is the main feature

• Usage and Fast Feedback is essential

• Run 1 system with multiple generations

• Consider obsolescence from start

(Note Greenfields are not forbidden.. Just hard to do right)

Page 16: Greenfields considered harmful

Thanks&

Open Fire!!