forked from jedi4ever/devopsdays-webby
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request jedi4ever#868 from bridgetkromhout/master
New proposal for Minneapolis.
- Loading branch information
Showing
1 changed file
with
37 additions
and
0 deletions.
There are no files selected for viewing
37 changes: 37 additions & 0 deletions
37
site/content/events/2014-minneapolis/proposals/Conways Law/index.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
--- | ||
extension: html | ||
filter: | ||
- erb | ||
- markdown | ||
dirty: true | ||
proposal: true | ||
talk: true | ||
selected: false | ||
layout: event | ||
author: Speaker 12 | ||
title: "Conway's Law: The Skeleton Of Devops" | ||
--- | ||
|
||
**Abstract:** | ||
|
||
Devops is about communication. In order to make better software, we seek out diverse viewpoints, use a common vocabulary, and encourage transparency. | ||
|
||
But despite all this focus on communication, we don't have much of a framework to guide our decisions. | ||
|
||
"Should we do continuous integration?" | ||
|
||
"Why not? People seem to like that." | ||
|
||
"What about ChatOps?" | ||
|
||
"Sure, yeah; it works for GitHub." | ||
|
||
Well, there's a half-forgotten rule -- first stated 46 years ago -- that can guide us through these decisions. It's called Conway's Law: | ||
|
||
Organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations. | ||
|
||
I'll show how Conway's Law is derived, how it's been empirically tested, and how it informs so much of what we do in devops. I want my audience to walk away with a new tool for spreading devops, shaping cross-team communication, and moving forward with confidence. | ||
|
||
**Speaker:** | ||
Speaker 12 | ||
|