A lot of research has gone into processes to deal with large, rapidly scaling teams working on complex problems. So why do we keep failing? In this session, we will compare idealism to reality from two angles: Agile processes applied in the real world; and famous examples (Spotify, GitHub, Netflix) in the real world. Following this, we'll cover what's worked for Vend while scaling teams, some theories for team constraints, and why you should understand, but ignore most of it.

1. Scaling Without Rules
Ben Gracewood
VP of Engineering, vendhq.com
@nzben

2. :(

3. @nzben

4. learn
A system for
debugging people
and organisations

5. wtf?

6. trust
&
empowerment
We want Vend to
succeed with as few
rules as possible.

7. creativity
You must break the 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 of 1st 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 to have
honesty without
requiring process.

10. research

12. same but
different
You can’t scale by
copying

13. vend

16. highly aligned,
loosely coupled
small teams

17. ideas

18. bounded
context
https://www.flickr.com/photos/quasimondo

19. connascence
A software quality metric 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 (
int a , 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. reasoning

25. bounded
context
https://www.flickr.com/photos/quasimondo

26. connascence
of
teams?
¯_(ツ)_/¯

27. connascence
of
teams
Static
• People
• Location
• Platform
Dynamic
• Vision
• Scope
• Deadline

28. framework
for
reasoning

29. framework
for
reasoning

30. framework
for
reasoning

31. framework
for
reasoning

32. team connascence
+
team context
A framework for
reasoning about the
complexity of teams
and interactions

33. so?

34. what?
• Apply principle, not process
• Use context and
connascence to debug
teams and interactions

35. Thanks
Ben Gracewood
VP of Engineering, vendhq.com
@nzben
bit.ly/nzben-agile-australia