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, Cyril Parkinson, 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.
An internationally known author and speaker, Mike Amundsen travels the world consulting and talking about network architecture, web development, and the intersection of technology and society. He works with companies large and small to help them capitalize on the opportunities APIs and microservices present for both consumers and the enterprise. Mike has authored numerous books and papers. He contributed to the O’Reilly Media book Continuous API Management (2018). His RESTful Web Clients was published by O’Reilly in February 2017, and he coauthored Microservice Architecture (June 2016). His 2013 collaboration with Leonard Richardson RESTful Web APIs and his 2011 book, Building Hypermedia APIs with HTML5 and Node, are common references for building adaptable web applications. His latest book Design and Build Great APIs for Pragmatic Publishing is scheduled for release in early 2019.
©2015, O’Reilly UK Ltd • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org