Overview
- Status
-
Delivered 2015-10-29 @ Velocity EU 2015, Amsterdam, Netherlands
- Last Updated
-
2015-11-09 10:55:38 EST
- Slides
- Prepared Talk
-
NA
- Video
-
Pending
- Transcript
-
NA
Abstract
Conway’s Three Other Laws
Optimizing Teams in a Distributed World
Most of us know about Conway’s adage “Any organization will produce a design which is a copy of the organization’s communication structure.” But Conway coined four laws in his 1968 paper “How Committees Invent.” What are the other ones? Why are we not talking about them? And what do they tell us about optimizing teams in a distributed world?
The recent rise of the microservices meme, the continued push to improve agility and autonomy of software teams, and the increased likelihood that teams are spread across the globe, are all related, even if they are at times in opposition to each other.
This talk looks at the work of Mel Conway, Fred Brooks, Robin Dunbar, and others; synthesizing advice and guidance on how we can learn from the last 50 years of research and experience in building and managing teams. We see how distance affects communication, and how we can create teams that produce the code we expect at the speed, level of complexity, coupling, and reliability necessary to succeed in today’s distributed world.
References
Here is a list of the references I mentioned in the talk along w/ some additional recommended reading.
Referenced in the Talk
-
The Influence of Organizational Structure On Software Quality: An Empirical Case Study, Nagappan, et al (2009)
-
Demystifying Conway’s Law, Newman (2014)
-
Engineering project organization: defining a line of inquiry and a path forward, Chinowsky (2011)
-
How Do Committees Invent?, Conway (1967)
-
The Mythical Man Month, Brooks (1975)
-
Social Network Size in Humans, Hill & Dunbar (2002)
-
The Social Brain Hypothesis, Dunbar (1998)
-
Scaling Spotify, Kniberg & Ivarrson (2012)
-
The ETTO Principle, Hollnagel (2009)
-
Safety-I and Safet-II, Hollnagel (2014)
-
Continuous Delivery, Carvalho (2014)
-
Continuous Delivery – The Dirty Details, Mike Britain (2015)
-
The New Hacker’s Dictionary, Raymond (1991)
-
Coordination in Large-Scale Software Teams, Begel, et al (2007)
-
Tactics for Global Software Development”, Herbsleb (2008)
-
Continuous Delivery, Humble & Farley (2010)
-
Microservices, Fowler & Lewis (2014)
-
The ‘Two Pizza Rule’ Is Jeff Bezos' Secret To Productive Meetings, Giang (2013)
Other Recommended Reading
-
Normal Accidents, Perrow (1984)
-
Parkinson’s Law And Other Studies in Administration, Parkinson (1957)
-
SystemANTICs, Gall (1986)
-
The Peter Principle, Peter (1969)
Speaker: Mike Amundsen
Director of API Architecture, API Academy, CA Technologies
An internationally known author and lecturer, Mike Amundsen travels throughout the world consulting and speaking on a wide range of topics including distributed network architecture, Web application development, and other subjects.
In his role of Director of Architecture for the API Academy, Amundsen heads up the API Architecture and Design Practice in North America. He is responsible for working with companies to provide insight on how best to capitalize on the myriad opportunities APIs present to both consumers and the enterprise.
Amundsen has authored numerous books and papers on programming over the last 15 years. His last book was a collaboration with Leonard Richardson titled "RESTful Web APIs" published in 2013. His 2011 book, “Building Hypermedia APIs with HTML5 and Node”, is an oft-cited reference on building adaptable Web applications. He is currently working to complete a new book - "Learning Client Hypermedia" due out from O’Reilly in late 2015.
-
Twitter: @mamund
-
Github: http://github.com/mamund
-
LinkedIn: http://linkedin.com/in/mamund