Conway's law

back to index

description: adage stating that organizations design systems that mirror their own communication structure

16 results

Kill It With Fire: Manage Aging Computer Systems

by Marianne Bellotti  · 17 Mar 2021  · 232pp  · 71,237 words

: Affinity Mapping Team Structure, Organization Structure, and Incentives Individual Incentives Minor Adjustments as Uncertainty Organization Size and Communication Manager Incentives Designing a Team: Applications of Conway’s Law Reorgs Are Traumatic Finding the Right Leadership Exercise: The Smallest Testable Unit Structuring the Team to Account for Past Failure Exercise: In-Group/Out-Group

Site Reliability Engineering: How Google Runs Production Systems

by Betsy Beyer, Chris Jones, Jennifer Petoff and Niall Richard Murphy  · 15 Apr 2016  · 719pp  · 181,090 words

to a small group, preferably within one site. Divide these components among the project subteams, and establish clear deliverables and deadlines. (Try not to let Conway’s law distort the natural shape of the software too deeply.)4 A goal for a project team works best when it’s oriented toward providing some

Team Topologies: Organizing Business and Technology Teams for Fast Flow

by Matthew Skelton and Manuel Pais  · 16 Sep 2019

Reverse Conway Maneuver Software Architectures that Encourage Team-Scoped Flow Organization Design Requires Technical Expertise Restrict Unnecessary Communication Beware: Naive Uses of Conway’s Law Summary: Conway’s Law Is Critical for Efficient Team Design in Tech Chapter 3: Team-First Thinking Use Small, Long-Lived Teams as the Standard Good Boundaries Minimize

Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith

by Sam Newman  · 14 Nov 2019  · 355pp  · 81,788 words

Continuous Delivery (Humble and Farley), Deployment coupling contracts, Breaking Changesconsumer-driven, Use consumer-driven contracts one microservice exposing two contracts, Give consumers time to migrate Conway's law, Modeled Around a Business Domain copying code from the monolith, Cut, Copy, or Reimplement? core competency, teams structured around, Shifting Structures correlation IDs (CIDs), Choreographed

Beautiful Architecture: Leading Thinkers Reveal the Hidden Beauty in Software Design

by Diomidis Spinellis and Georgios Gousios  · 30 Dec 2008  · 680pp  · 157,865 words

the organization. Conway noted that the structure of a system reflects the structure of the organization that built it (1968). The architect may realize that Conway’s Law can be used in reverse. In other words, a good architecture may influence an organization to change so as to be more efficient in building

Building Microservices

by Sam Newman  · 25 Dec 2014  · 540pp  · 103,101 words

Integration checklist for, Are You Really Doing It? mapping to microservices, Mapping Continuous Integration to Microservices Conway's lawevidence of, Evidence in reverse, Conway’s Law in Reverse statement of, Conway’s Law and System Design summary of, Summary coordination process, Distributed Transactions core team, Role of the Custodians CoreOS, Docker correlation IDs, Correlation IDs CP

operating system artifacts, Operating System Artifacts operating systems security, Operating System orchestration architecture, Orchestration Versus Choreography organizational alignment, Organizational Alignment organizational structureConway's law and, Conway’s Law and System Design effect on systems design, Evidence loose vs. tightly coupled, Loose and Tightly Coupled Organizations orphaned services, The Orphaned Service? OSGI (Open Source

pathways, Adapting to Communication Pathways bounded contexts, Bounded Contexts and Team Structures case study, Case Study: RealEstate.com.au Conway's law of, Conway’s Law and System Design delivery bottlenecks, Delivery Bottlenecks effect on organizational structure, Conway’s Law in Reverse feature teams, Feature Teams internal open source model, Internal Open Source organizational structure and, Evidence orphaned services

Succeeding With AI: How to Make AI Work for Your Business

by Veljko Krunic  · 29 Mar 2020

organization to gain access to data. In the larger organization, even within your department and project, you might see some form of Conway’s Law [88,89] acting on you. Conway’s Law states that any organization that designs systems produces a design whose structure is a copy of the organization’s communication structure. If you

Seeking SRE: Conversations About Running Production Systems at Scale

by David N. Blank-Edelman  · 16 Sep 2018

and staging contract termination, Decommissioning control plane, Configuration Management (Control Plane Versus Data Plane) convolutional neural networks, How and When Should We Apply Neural Networks? Conway's law, Getting Buy-In, The Computer and Human Systems Cannot Be Separated Conway, Mel, The Computer and Human Systems Cannot Be Separated Cook, Richard, SRE Cognitive

The Nature of Software Development: Keep It Simple, Make It Valuable, Build It Piece by Piece

by Ron Jeffries  · 14 Aug 2015  · 444pp  · 118,393 words

integration. It’s possible that could happen, but it doesn’t come automatically; it depends on Conway’s law. The more common result is that both sides of the integration end up aiming at a moving target. Conway's Law In a Datamation article in 1968, Melvin Conway described a sociological phenomenon: “Organizations which design systems

The Seventh Sense: Power, Fortune, and Survival in the Age of Networks

by Joshua Cooper Ramo  · 16 May 2016  · 326pp  · 103,170 words

heart monitor. A power grid. But now they overlap and inform one another. Engineers know the idea that network design shapes the real world as Conway’s Law. Melvin Conway was a scientist in the 1960s who noticed that the design of a telephone network had an impact on the businesses, communities, and

The Big Nine: How the Tech Titans and Their Thinking Machines Could Warp Humanity

by Amy Webb  · 5 Mar 2019  · 340pp  · 97,723 words

The Mythical Man-Month

by Brooks, Jr. Frederick P.  · 1 Jan 1975  · 259pp  · 67,456 words

The Stack: On Software and Sovereignty

by Benjamin H. Bratton  · 19 Feb 2016  · 903pp  · 235,753 words

How PowerPoint Makes You Stupid

by Franck Frommer  · 6 Oct 2010  · 255pp  · 68,829 words

The Manager’s Path

by Camille Fournier  · 7 Mar 2017

The Architecture of Open Source Applications

by Amy Brown and Greg Wilson  · 24 May 2011  · 834pp  · 180,700 words