Case study: looking at the agile manifestos from an Organization Development and polar...
summary
Reading the Agile and Software Craftsmanship manifestos through Polarity Management shows the original four contrasts expand into eight values and 132 paired permutations, and proposes concrete practices: use polarity maps (Barry Johnson method), craft a GPS greater-purpose statement, list downside signs and set early warning signals to monitor, then run small actions to nudge balance. The session uses hand-drawn, interactive mapping and reports applying the maps prevents pendulum swings and recurring overuse patterns.
AI-written summary · about
chapters (11)
- 0:00Welcome and introduction
- 1:33Why explore agility differently
- 4:45Diagnostic vs dialogic systems
- 7:39Organization in the mind concept
- 9:01Understanding polarities
- 16:45Agile manifesto as polarity
- 25:48Managing polarity dynamics
- 36:12Agile transformation complexity
- 38:02Mediocrity and organizational health
- 40:15Tensions as necessary forces
- 41:37Q&A and closing remarks
related talks
30mLeadership Lessons from the Agile Manifesto
01h 01mLeadership Lessons from the Agile Manifesto
48mUnwrapping the agile present
49mAgile Manifesto is outdated! We urgently need a Product Manifesto!
43mAutonomy, is that what we really want?
40mUsing perspectives for a holistic Agile transformation
37mNavigating Politics in Agile or Lean Initiatives
34mLeadership Lessons from the Agile Manifesto