Greenfields considered Harmful
Or at least not very Agile
by Mike Wessling
___________________
< I feel drained... >
-------------------
\ ^__^
\ (oo)\_______ ________
(__)\ )\/\ |Super |
||----W | |Milker|
|| UDDDDDDDDD|______|
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
__________
< Et Voila >
----------
|-------------------------------|
/| /|
/ | / |
/ |----------------------------/--|
/ / / /
/ / / /
/ / / /
/ / ^__^ / /
/ / (oo)\_______ / /
/ / (__)\ )\/\ / /
/ / ||----w | / /
/ / || || / /
/ / / /
|----------||--------||---------| /
| / ||--/--\--|| | /
|/ ||-/----\-|| |/
|----------||--------||---------|
Illusion of Done
Goal is to delivery the complete thing
Versus
continuous improvable thing
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
____________________
< I don't like grass >
--------------------
\ /\ ___ /\
\ // \/ \/ \\
(( O O ))
\\ / \ //
\/ | | \/
| | | |
| | | |
| o |
| | | |
|m| |m|
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
_____________
< Happy now?? >
-------------
\ (__)
\ /oo|
\ (_"_)*+++++++++*
//I#\\\\\\\\I\
I[I|I|||||I I `
I`I'///'' I I
I I I I
~ ~ ~ ~
Scowleton
Creates Legacy
What about the last generation greenfield?
&
What about the cows in the old fields..
->
Deny new features?
&&/||
Wait until they die/leave?
_______________
< Rest in Peace >
---------------
\ , ,
\ /( )`
\ \ \___ / |
/- _ `-/ '
(/\/ \ \ /\
/ / | ` \
O O ) / |
`-^--'`< '
(_.) _ ) /
`.___/` /
`-----' /
<----. __ / __ \
<----|====O)))==) \) /====
<----' `--' `.__,' \
| |
\ /
______( (_ / \______
,' ,-----' | \
`--{__________) \/
From Cradle to what??
Think about Retirement when designing
->
Even consider a test retirement
->
Easier to replace/upgrade parts when needed.
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)
Thanks&
Open Fire!!