Download to read offline
Uploaded byBen Gracewood
Scaling Without Rules
Ben Gracewood discusses the importance of scaling organizations with minimal rules while fostering creativity, trust, and empowerment. He introduces the concept of 'connascence' as a metric for understanding complexities in software quality and team dynamics. The document emphasizes applying principles over processes to enhance team interactions and effectiveness.
Scaling Without Rules
- 1. Scaling Without Rules BenGracewood VP of Engineering, vendhq.com @nzben
- 2.
- 3.
- 4. learn A system for debuggingpeople and organisations
- 5.
- 6. trust & empowerment We want Vendto succeed with as few rules as possible.
- 7. creativity You must breakthe rules as a matter of policy – all day, every day, with a degree of rigour and dedication to the cause Phil Beadle http://www.amazon.com/Dancing-about-Architecture-Creativity-Independent/dp/1845907256
- 8. cynefin "Cynefin as of1st June 2014" by Snowded - Own work. Licensed under CC BY-SA 3.0 via Wikimedia Commons https://en.wikipedia.org/wiki/Cynefin
- 9. honesty We need tohave honesty without requiring process.
- 10.
- 12. same but different You can’tscale by copying
- 13.
- 16.
- 17.
- 18.
- 19. connascence A software qualitymetric to allow reasoning about the complexity caused by coupling. A tool to help prioritise what should be refactored first. https://youtu.be/Ip2o4vbAK3s
- 20. Connascence of position float divide ( inta , int b ){ … } x = divide ( 1 , 2 )
- 21. Connascence of name float divide( int numerator, int demonminator ) {…} x = divide( numerator: 1, denominator: 2 )
- 22. Connascence • Name • Type •Meaning • Position • Algorithm • Execution • Timing • Values • Identity Stronger Weaker
- 23. types of connasence Static • Name •Type • Meaning • Position • Algorithm Dynamic • Execution • Timing • Value • Identity
- 24.
- 25.
- 26.
- 27. connascence of teams Static • People • Location •Platform Dynamic • Vision • Scope • Deadline
- 28.
- 29.
- 30.
- 31.
- 32. team connascence + team context Aframework for reasoning about the complexity of teams and interactions
- 33.
- 34. what? • Apply principle,not process • Use context and connascence to debug teams and interactions
- 35. Thanks Ben Gracewood VP ofEngineering, vendhq.com @nzben bit.ly/nzben-agile-australia