This presentation will explain the idea, pros and cons of the Evolution Game. It will also compare it against the usual strategies. Lastly, it will show all tactics that need to be applied in order to involve stakeholders and evaluate the actual architecture sanity, particularly how to measure "evolvability".
7. *Based on the Shadow Organization concept by Ralph Stacy, 1997
8. • Business value not delivered
• Better ways of providing it
Unfulfilled Business Needs
• Wrong Domain/Metaphor
• Built in Solution Space
• Defective Communication Channel
Forced Domain Anti-pattern
• Non participating stakeholders
• Operational TI, non-tactic, non-strategic
Invisibilized Talent
9. • Additional cost in control and support
• May be competing solutions
Unofficial Architecture
• Need of TI learning
• Unnatural solutions
• Non-expert’s work
Dysfunctional Domain
• Analyze and Measure
• I.E Capturing stakeholders needs and natural process.
Taking advantage?
10.
11.
12. • Speed, Precision,Trust
• Modeling,Validation, Coherence
Development
• Impedance mismatch, no Ownership
• Workarounds, Conflict, Barrier, even Sarbanes-Oxley!
Adoption
• Unnatural Patches, No Flexibility
• Lack of Governance!
Evolution
17. • Keep track of information,process
• Keep an eye on symptoms
• Document and learn from shadows
Knowing
• Domain Nurturing
• Contextual Interviews for domain design and
Variations
• Absorb, combine shadows.Under control, official.
• Make stakeholdrs part of it
Acting
18. • Put in place an Evaluation
The cycle
• Domain Nurturing
• Contextual Interviews for domain design and
Variations
• Absorb, combine shadows. Under control, official.
• Make stakeholdrs part of it
Acting