Cynefin for XPers - Liz Keogh, Lean and Agile Consultant

Agile fluency

• Complicated (Predictable outcomes)
  
  • TDD/BDD (You have to define your outcome, avoid in complex domain)
    
  • Pairing (you don’t need pairing on obvious stuff, if it’s complex, build multiple prototypes, let each dev build alone)
    
  • Small releases turn something complex into something complicated
    
• Complex (Emergent outcomes)
  
  • Simple design are enabling constraints (move from chaos to complex)
    
  • Spikes & prototypes
    
  • Collective Ownership
    
  • Sit together
    
  • Whole team
    
  • Coding standard are enabling constraints
    
• Chaos (Avoiding Chaos)
  
  • Sustainable pace avoids chaos
    
• Obvious
  
  • Customer Tests
    
  • Planning Game
    
• Refactoring prevents you from entering disorder
  

System Metaphor: a story about something that’s taken from another domain that shares some patterns
A Probe Portfolio should include:

• Oblique: not targeting the problem directly
  
• Naïve: from the perspective of an expert in something else (managing for serendipity, create serendipitous conversations that may result in something truly innovatice)