Talk:Brooks' Law

From Citizendium
Revision as of 23:00, 27 July 2008 by imported>Howard C. Berkowitz (First comments while creating talk page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
This article is a stub and thus not approved.
Main Article
Discussion
Related Articles  [?]
Bibliography  [?]
External Links  [?]
Citable Version  [?]
 
To learn how to update the categories for this article, see here. To update categories, edit the metadata template.
 Definition "Adding manpower to a late software project makes it later"- Fred Brooks [d] [e]
Checklist and Archives
 Workgroup category Computers [Categories OK]
 Talk Archive none  English language variant American English

Initial structural and editorial comments

The article should begin with more context. Are you sure the reader will understand the concept of software engineering? If not, a link is appropriate, which I inserted.

I removed your initial explanation that Brooks' Law is in simple words, as it seems more straightforward just to state the Law. Don't worry about the technique I used to emphasize the quotation, but you do need to cite direct quotations such as Brooks' book.

A CZ article is not an essay, so doesn't have a conclusion. I find a good rule comes from journalism, a rule called "inverted pyramid". The most important information: who, what, where, when, why — comes at the top, and the level of detail gets finer and finer as you move downward to the point of the inverted pyramid.

If you use specific examples, such as the one from Apple, cite it.

May I point out that this is Citizendium, where Wikipedia is sometimes gently called The Other Place, and, certainly, citing it as an authority, without even citing the article that contains the assertion, may be less than ideal? Howard C. Berkowitz 23:00, 27 July 2008 (CDT)