|WikiProject Systems||(Rated Start-class, Low-importance)|
|WikiProject Computing / Software / CompSci||(Rated Start-class, Low-importance)|
- 1 Jargon File?
- 2 Quote No Longer in Cited Harvard Paper
- 3 should "mirroring hypothesis" link here
- 4 untitled
- 5 counter example
- 6 page layout
- 7 Real-life "example"
- 8 OSS
- 9 Another "Conway's Law"
- 10 Reasoning for the Law
- 11 Corollary of Conway's Law
- 12 "Hitler Rule" is Sexton, Not Conway.
- 13 Examples
- 14 Colloquial Interpretation Removal
What's the significance of Jargon File and its maintainer's identity in the topic? Isn't it just trivia? What kind of authentic source is it?
-- Agreed! Also the restatement in the Jargon File is hardly relevant considering that the original source by Conway contains "... five people were assigned to the COBOL job and three to the ALGOL job. The resulting COBOL compiler ran in five phases, the ALG0L compiler ran in three." I suggest that we remove it.
Quote No Longer in Cited Harvard Paper
In the "Supporting Evidence" section, the quote from Harvard Business School's study is cited as coming from reference #6, a PDF of a paper they published about the topic. However, in 2011 the paper was updated and the quote on this page is no longer in the text. There is a new quote with a similar meaning:
In all of the pairs we examine, the product developed by the loosely-coupled organization is significantly more modular than the product from the tightly-coupled organization.
Should we update the quote or link to a 2008 version of the paper as the reference?
I first heard this law referred to as the mirroring hypothesis", and several of the papers references use this name as well. — Preceding unsigned comment added by 126.96.36.199 (talk) 09:36, 10 October 2014 (UTC)
I changed the example from a lame example (C strings vs C++ string class) to a more illustrative one. More examples are certainly welcome.
This page could also use some counter examples: The project Im working on now certainly doesnt fit: We have 3 people working on a system that naturally just has 2 components: 1 person is working on 1 component, and 2 people share the other component.
Counter examples may be found in: Hvatum, Lise, Alan Kelly, "What do I think about Conway's Law now", Conclusions of a EuroPLoP Focus Group, EuroPloP 2005, 2005 URL: http://allankelly.net/patterns/ConwaysLawFocusGroup.pdf —Preceding unsigned comment added by 188.8.131.52 (talk) 12:55, 29 September 2008 (UTC)
I agree also, the Mars Climate Orbiter problem is related to System Integration, System Testing and reusing a System or System component in a way that the component was not orginally intended for hence they didn't test some elements. There is a comprehensive report on a Nasa Website. It has nothing to do with Conway's Law. Personally, I am not really that fussed with Conway's Law anyway. — Preceding unsigned comment added by 184.108.40.206 (talk) 06:01, 20 September 2011 (UTC)
Another "Conway's Law"
I've removed the following text as it seems rather flippant, has no references, and it isn't clear what it has to do with this article. It also vaguely sounds like vandalism (a citation would clarify that issue!) The text was:
Conway's Law is sometimes reported as a different adage:
- In every organization there is one person who knows exactly what is going on at all times. This person must be fired.
- Regardless of the organization or industry, this person's name is most commonly "John".
Reasoning for the Law
A possible reason for the law is because many organizations will create "interfaces" or "protocols" in advance, so that the result of group A will interface (communicate in a pre-formalized manner) with the result of group B.
Corollary of Conway's Law
The section “Corollary of Conway's Law” currently contains the following:
The context in which Conway's Law is seen as humorous, is when social structures of rigid organizations are reflected in designs, the results are often sub-standard. The extension to this circumstance is that interpersonal relationship problems may also manifest in the design.
has anyone found or heard of a corollary in website user experience design, as a specific instance of software design? in that context i have often used the expression 'corporate underpants' to (humorously) indicate that internal structure of an organisation is plainly visible in the navigation system or information architecture of its corporate or branded website. I have some sympathy for the removed comment above as it can indeed come down to individuals (empire-builders) within an organisation dictating the design and architecture of a website based upon their own feelings of self-importance. 220.127.116.11 (talk) 09:53, 4 February 2015 (UTC)
A corollary to Conway's law can be deduced to be: When an organization attempts to change its social structure, the architecture of their application architecture will work against them. There is no reference to this as I made it up - but I am generally considered a thought leader in software development. — Preceding unsigned comment added by Alshall (talk • contribs) 00:50, 2 June 2016 (UTC)
"Hitler Rule" is Sexton, Not Conway.
There is a different "Conway's Law," incorrectly attributed to Mike Conway of the Electronic Freedom Foundation. It is Sexton's Law, originated by Mike, I think it is, Sexton, of Southern Ontario, Canada, a pioneer web developer of the 1980's.
In its various forms, it generally says something like "Every stupid argument winds up with somebody dragging in Hitler -- and the person who does so loses."
Somebody-Or-Other's Law states that all eponymous laws are named after the wrong person.
Colloquial Interpretation Removal
Re: Edit history per: 'Removed "colloquial terms" - it's badly written and not necessary'
Why is not necessary? The introduction is too wordy and indirect to capture in the essence of the idea. The colloquial reinterpretation was intended to make it easier reading for average humans instead of just business or English majors. If the colloquial statement is "poorly written", then please re-write it better rather than outright delete. The baby was tossed out with the bathwater. — Preceding unsigned comment added by 18.104.22.168 (talk • contribs)
Here's the statement in question:
In colloquial terms, it's generally saying software ends up "shaped like" the organizational structure it's designed in or for.
How about this re-wording:
In colloquial terms, it's generally saying software ends up "shaped like" the organizational structure it's designed in or designed for.
We could attempt to clarify what "shaped like" means, but I don't know how to do such without destroying the colloquial nature of it, which is the goal of the phrase in the first place. Being technically precise, and communicating sufficiently to a non-technical audience are sometimes conflicting goals. Suggestions welcomed. As it stands, I find "shaped like" good enough for now and shall still lobby to have it put back despite a better alternative not yet being found.
I will put it back on November 2019 unless somebody objects.