The Mythical Man Month - Factbites
 Factbites
 Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: The Mythical Man Month


    Note: these results are not from the primary (high quality) database.


Related Topics
IBM

In the News (Sat 19 Dec 09)

  
 The Mythical Man-Month - Wikipedia, the free encyclopedia
The Mythical Man-Month: Essays on Software Engineering is a classic book on software project management written by Fred Brooks.
Another of his challenges to the idea of expecting results to match labor expended was the assertion that writing an Algol compiler requires six months, regardless of the number of workers involved.
Reflecting on his time at IBM managing the development of OS/360, Brooks recounts the mistakes made and lessons learned.
en.wikipedia.org /wiki/The_Mythical_Man-Month

  
 Kids.net.au - Encyclopedia The Mythical Man-Month -
The Mythical Man-Month is a term coined in a book of the same name by Frederick P. Brooks, describing the unique problem of software development on correction of schedule slippage[?].
It makes special mention of the fact that unlike other engineering problems when you fall behind schedule you can't just add people to the project and expect the extra hands to resolve the problem.
www.kids.net.au /encyclopedia-wiki/th/The_Mythical_Man-Month

  
 Gamasutra - Features - "The Secret's in the Schedule: Bending The Mythical Man-Month"
The Mythical Man-Month states that adding people to a project experiences a law of diminishing returns until a point where growing the team actually creates a net loss in progress.
The Mythical Man-Month is a seminal work on not just software engineering but the psychology of human interaction inside a team environment.
The schedule is becoming less structured and instead the team is being driven by daily and hourly updates derived from the test team along with oversight from the departmental leads and producer.
www.gamasutra.com /features/20040421/saladino_01.shtml

  
 Mythical Man-Month, The: Essays on Software Engineering, Anniversary Edition, 2/E
# re: Mythical Man-Month, The: Essays on Software Engineering, Anniversary Edition, 2/E
Mythical Man-Month, The: Essays on Software Engineering, Anniversary Edition, 2/E
I finished reading Mythical Man Month (aka MMM) recently and quite honestly I was amazed at how a book that was originally published in 1975 can be so on target with so man aspects of software development.
weblogs.asp.net /sibrahim/archive/2004/04/28/122628.aspx

  
 Gamasutra - Features - "The Secret's in the Schedule: Bending The Mythical Man-Month" Printer Friendly
These two different approaches together will allow a manager to, in effect, bend the mythical man-month as far as possible to get the most productivity from each member of the team.
There are essentially two ways to keep control of this growth: one is to reduce cross-person dependencies and thus reduce the communication requirements; the other is to increase communication bandwidth.
The process's central purpose is to increase communication flow which naturally becomes a larger bottleneck as a project's size increases.
www.gamasutra.com /features/20040423/saladino_pfv.htm

  
 The Mythical Man-Month: Essays on Software Engineering (20th Anniversary Edition) - Book Review - DeveloperDotStar.com
The essays in The Mythical Man-Month cover a variety of topics, from management-related topics such as estimating and process, to lower level design and construction topics.
If you aspire to become involved in software development projects at a higher level in a role such as technical lead, architect, or project manager, then understanding of the less technical subjects is essential.
The best essays in the collection, however, are those that deal with the higher level topics like people; process; scheduling and estimation; architecture and the conceptual integrity of systems; the nature of software development; and the state of the discipline and field.
www.developerdotstar.com /mag/bookreviews/read_manmonth.html

  
 Where Is Moore's Law for Software?, or, The Mythical Man-Month Strikes Back: Archive Entry From Brad DeLong's Webjournal
In Brooks' "Mythical Man Month", he notes a piece of programmer folk wisdom, which is that a programmer has roughly constant productivity measured in lines of code regardless of the language he works in.
Software has come a long way since The Mythical Man Month was first published, and in the anniversay edition of the book, Brooks notes many incremental improvements.
Recent editions of "The Mythical Man Month" have included it as its last chapter.
www.j-bradford-delong.net /movable_type/archives/001084.html

  
 java.net Forums: The Mythical Man Month
Since the first publication of The Mythical Man-Month in 1975, no software engineer's bookshelf has been complete without it.
Many software engineers and computer scientists have claimed to be "on their second or third copy" of the book.
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Participation.
forums.java.net /jive/forum.jspa?forumID=19

  
 The Mythical Man-Month: Essays on Software Engineering
As far back as 1975, when software engineering was a very young profession, Frederick Brooks keenly observed that the man-month concept is but a myth.
A program that can be crafted by one programmer in two months will probably take two programmers three months to complete.
I guess this kind of logic is probably right in some sort of projects, because otherwise, economists wouldn't have been so fond of it.
www.forum2.org /tal/books/mythman.html

  
 Compare Prices and Read Reviews on Mythical Man Month Essays on Software 2e at Epinions.com
Additional information on Mythical Man Month Essays on Software 2e or other products.
Compare Prices and Read Reviews on Mythical Man Month Essays on Software 2e at Epinions.com
This is an armchair thesis, never have I seen a team function in this manner, and I don't think it is the best approach to development.
www.epinions.com /book-review-6FB1-42B8F01-39359DEF-prod5

  
 GURTEEN Book: The Mythical Man-Month (1975) by Frederick P. Brooks Jr.
The Mythical Man-Month is one of the classics in the field of software program management.
The Mythical Man-Month by Frederick P. Brooks Jr.
GURTEEN Book: The Mythical Man-Month (1975) by Frederick P. Brooks Jr.
www.gurteen.com /gurteen/gurteen.nsf/0/E39A4CE2BBB9D54E802568310043047E

  
 The Mythical Man-Month by Freder
The Mythical-Man Month is undoubtedly his most famous work in which he compiled essays about his work on the IBM 360 Series.
I believe that the illusion of the non-applicability of "mythical man-month postulate" and Brooks' law is limited only to projects for which a fully functional prototype already exists and most or all architectural problems are solved...
They talk about the "Mythical Man Month") is that the what kills timelines software projects more than anything else is communication overhead.
www.softpanorama.org /Bookshelf/Classic/tmmm.shtml

  
 The Mythical Man-Month: Have we learned anything in 30 years?
Come on down and join the java.net bookclub discussion about Frederick P. Brooks' The Mythical Man-Month.
The Mythical Man-Month: Have we learned anything in 30 years?
Be the first to post a comment about this weblog entry.
www.artima.com /weblogs/viewpost.jsp?thread=49859

  
 Book Review: Mythical Man Month CaseySoftware.com
I know I'm not the first and I certainly won't be the last, but I've decided to review Mythical Man Month by Fred Brooks anyway.
Unless you are in the technology realm, you probably haven't heard of it.
blogs.caseysoftware.com /?q=node/20

  
 /* Rambling comments... */: Mythical Man Month
The mythical man month inspired me early on in my career.
It was a good read, and, just as when I read it just after the 20th anniversary edition came out, still very relevant to software development today.
Sometimes I still get that feeling, of "man I just did that!" Today was one of those days.
www.lenholgate.com /archives/000312.html

  
 FabTime Book Reviews: The Mythical Man-Month by Frederick Brooks, Jr.
The name-sake essay (The Mythical Man-Month) discusses the indivisibility of many programming tasks, and why this makes the addition of manpower to a software project a futile effort.
Published in 1975, The Mythical Man-Month is a classic text on software development.
Brooks’ essays cover a variety of the challenges inherent to large-system programming, but are useful reading for anyone involved in software development.
www.fabtime.com /man-month.shtml

  
 Ian Alexander's Reviews of Books on Requirements Engineering and Related Subjects - Brooks on Mythical Man-Month
It's rather like what the plain man said on reading Shakespeare: the book is full of quotations, so influential has Brooks been.
A graph shows time versus number of workers for a perfectly partitionable task: the months fall away in a smooth asymptotic curve as the men increase.
There really are awfully few books written a generation ago that can claim to be relevant to system development today (Checkland's Soft Systems Methodology among them), but this classic by Fred Brooks is still alive and kicking.
i.f.alexander.users.btopenworld.com /reviews/brooks.htm

  
 The Mythical Man-Month
This second is the most dangerous system a man ever designs.
These get stored away to be used "next time." Sooner or later the first system is finished, with firm confidence and a demonstrated mastery of that class of systems, is ready to build a second system.
www.cs.wisc.edu /~param/quotes/man-month.html

  
 Notes from Classy's Kitchen: June 2002 Archives
The Mythical Man Month Finally got round to buying and reading (some of) the classic software project management text The mythical man month.
If you want a look at what there is to be afraid of for Humanistic interfaces, take a look at The Dasher Project.
Man kan ikke slå analysen fra fordi det føles bedre, for så holder tingene op med at virke.
www.classy.dk /log/archive/2002_06.html

  
 The Mythical Man-Month
The man-month is a fallacious and dangerous myth, for it implies that men and months are interchangeable.
The book sprang from a conviction that the quality of the people on a project, and their organization and management, are much more important factors in success than are the tools they use or the technical approaches they take.
Brooks's Law: Adding manpower to a late software project makes it later.
home.earthlink.net /~huston2/books/mmm.html

  
 The Mythical Man-Month revisited: ZDNet Australia: News: Business
Even though The Mythical Man-Month essays are more than 25 years old, they are as relevant today as they were when first written.
Brooks’ major premise of the title essay, The Mythical Man-Month, focuses on the mistaken idea that lagging software project deadlines can be met by simply assigning more developers to the project.
This month we received the desktop machines that most of us mere mortals just dream about.
www.zdnet.com.au /news/business/0,39023166,20268075,00.htm

  
 Discussion: Mythical Man Month
I believe that the illusion of the non-applicability of "mythical man-month postulate" and Brooks' law is limited only to projects for which a fully functional prototype already exists and most or all architectural problems are solved ---------------- Open Source vs. Brook (i.e.
They talk about the "Mythical Man Month") is that the what kills timelines software projects more than anything else is communication overhead.
Actually the term "Brooks' Law" is usually formulated as "Adding manpower to a late software project makes it later".
www.michaelmoser.org /slashdot/brooks.htm

  
 nick gray dot net: The Mythical Man-Month - Wikipedia, the free encyclopedia
The Mythical Man-Month - a classic book on software project management written by Fred Brooks.
Regent Aerospace to construct $20 million factory in South Korea
nickgray.net /2005/01/mythical-man-month-wikipedia-free.html

  
 ASIST AM 04 - A Citation Context Analysis of Frederick P. Brooks' The Mythical Man-Month
The focus of our research is Frederic Brooks’ The Mythical Man-Month (MMM).
Since its publication in 1975, it has been recognized as an important contribution to the general area of Software Project Management and other, related topics in Software Engineering.
When the taxonomy is stabilized, we expect to report the frequency with which the different concept classes occur across the citing document set, their rise and fall in frequency across time, and the diffusion, over the 25 years, of the concepts for which MMM is cited into the subject areas outside of Software Engineering proper.
www.asis.org /Conferences/AM04/abstracts/207.html

  
 Usability First: Usability Glossary: mythical man-month
This perspective is called "mythical" because it doesn't apply in many organizational settings, and in particular in software development environments.
The basic idea is that if you want to produce twice as many sprockets, then you can hire twice as many people to get it done.
Thus, what takes 1 person 100 months to perform should take 100 people 1 month to perform.
www.usabilityfirst.com /glossary/term_719.txl

  
 Mythical Man-Month
If you create, maintain, manage, or are involved in part of the software engineering process, you must read The Mythical Man Month.
From the hard-nosed advice to the enjoyable anecdotes, you will enjoy this book.
While this paper caused a lot of rebuttal in the software engineering community, Brooks was right--there has been "No Silver Bullet."
www.robelle.com /library/smugbook/manmonth.html

  
 Gregarius » Signal vs. Noise » The Mythical Man-Month
The Mythical Man-Month: Essays on Software Engineering, a book on software project management written by Fred Brooks, was mentioned by a few commenters at the recent thread on Three people for version 1.
Gregarius » Signal vs. Noise » The Mythical Man-Month
Posted: August 25th, 2005, 10:25am EDT by Matt
carterparks.com /agg/Signal_vs._Noise/2005/08/25/The_Mythical_Man_Month

  
 The Mythical Man Month : E-consultancy.com
I have just finished re-reading 'The Mythical Man Month' by Frederick P.Brooks Jr.
The book is considered a classic in software engineering circles, but I couldn't recommend it highly enough to anyone involved in web project management (which, despite its creative elements, is also about software project management).
The book is considered a classic in software engineering circles, but I couldn't recommend it hig...
www.e-consultancy.com /forum/128-the-mythical-man-month.html

  
 Course Technology--InfoWeb: Mythical Man-Month
After you connect to the site, enter "Mythical Man-Month." Brooks received the Bower award and Prize in Science (sln.fi.edu/inquirer/brooks.html).
Frederick P. Brooks' book, The Mythical Man-Month (Addison-Wesley, 1995), is among the classics of information systems literature.
Dobb's Electronic Review of Computer Books You can find reviews of significant computer books--including the 1996 anniversary edition of The Mythical Man-Month--at this Web site.
www.cciw.com /content/manmonth.html

  
 Journal of jplindstrom (594)
The Mythical Man Month - notes 3
08:48 AM The Mythical Man Month - notes 3
The hard thing about building software is deciding what to say, not saying it.
use.perl.org /~jplindstrom/journal/12680

Try your search on: Qwika (all wikis)

Factbites
  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.