Neu:
42,17€42,17€
GRATIS Lieferung Donnerstag, 23. Januar für qualifizierte Erstbestellung
Oder schnellste Lieferung Dienstag, 21. Januar. Bestellung innerhalb 22 Min.
Auf Lager
Versand
Amazon
Verkäufer
Amazon
Rückgaben
Retournierbar innerhalb von 30 Tagen nach Erhalt
Zahlung
Sichere Transaktion
Mit „Gebraucht – Sehr gut“ sparen
27,91€27,91€
Lieferung für 4,30 € 25. Januar - 13. Februar
Versand durch: worldofbooksde Verkauft von: worldofbooksde
Lade die kostenlose Kindle-App herunter und lese deine Kindle-Bücher sofort auf deinem Smartphone, Tablet oder Computer – kein Kindle-Gerät erforderlich.
Mit Kindle für Web kannst du sofort in deinem Browser lesen.
Scanne den folgenden Code mit deiner Mobiltelefonkamera und lade die Kindle-App herunter.
Bild nicht verfügbar
Farbe:
-
-
-
- Herunterladen, um dieses Videos wiederzugeben Flash Player
Dem Autor folgen
OK
The Mythical Man-Month. Essays on Software Engineering Taschenbuch – 2. August 1995
Kaufoptionen und Plus-Produkte
Few books on software project management have been as influential and timeless as The Mythical Man-Month . With a blend of software engineering facts and thought-provoking opinions, Fred Brooks offers insight for anyone managing complex projects. These essays draw from his experience as project manager for the IBM System/360 computer family and then for OS/360, its massive software system. Now, 20 years after the initial publication of his book, Brooks has revisited his original ideas and added new thoughts and advice, both for readers already familiar with his work and for readers discovering it for the first time.
The added chapters contain (1) a crisp condensation of all the propositions asserted in the original book, including Brooks' central argument in The Mythical Man-Month: that large programming projects suffer management problems different from small ones due to the division of labor; that the conceptual integrity of the product is therefore critical; and that it is difficult but possible to achieve this unity; (2) Brooks' view of these propositions a generation later; (3) a reprint of his classic 1986 paper "No Silver Bullet"; and (4) today's thoughts on the 1986 assertion, "There will be no silver bullet within ten years."
- Seitenzahl der Print-Ausgabe336 Seiten
- SpracheEnglisch
- HerausgeberAddison-Wesley Longman
- Erscheinungstermin2. August 1995
- Abmessungen23.04 x 15.52 x 1.91 cm
- ISBN-109780201835953
- ISBN-13978-0201835953
Wird oft zusammen gekauft

Weitere Artikel entdecken
Produktbeschreibungen
Amazon.de
Der Klassiker zur Problematik des menschlichen Faktors im Software-Engineering. Software-Tools und Entwicklungsumgebungen mögen sich in den 21 Jahren seit dem ersten Erscheinen des Buches verändert haben, aber die seltsamen, nicht linear verlaufenden Größenvorteile in der Zusammenarbeit und in der Natur des Einzelnen oder der Natur von Gruppen haben sich in keinster Weise geändert. Wenn Sie selbst im Software-Engineering tätig sind oder abhängig sind von anderen in diesem Bereich Tätigen, dann sollten Sie sich so schnell wie möglich dieses Buch besorgen -- von Amazon.de, Ihrer Bibliothek oder von jemand anderem. Sie (und/oder Ihre Kollegen) werden es nicht bereuen. Das Buch ist äußerst zu empfehlen.
Kein Buch über Software-Projektmanagement war so bedeutend und so zeitlos wie The Mythical Man-Month. Heute, 20 Jahre nach dem ersten Erscheinen des Buches, rollt Frederick P. Brooks Jr. Seine ursprünglichen Ideen wieder auf, stellt neue Überlegungen an und entwickelt neue Ratschläge sowohl für Leser, die seine Bücher bereits kennen als auch für diejenigen, die zum ersten Mal ein Buch von ihm lesen.
Buchrückseite
Few books on software project management have been as influential and timeless asThe Mythical Man-Month. With a blend of software engineering facts and thought-provoking opinions, Fred Brooks offers insight for anyone managing complex projects. These essays draw from his experience as project manager for the IBM System/360 computer family and then for OS/360, its massive software system. Now, 20 years after the initial publication of his book, Brooks has revisited his original ideas and added new thoughts and advice, both for readers already familiar with his work and for readers discovering it for the first time.
The added chapters contain (1) a crisp condensation of all the propositions asserted in the original book, including Brooks' central argument in The Mythical Man-Month: that large programming projects suffer management problems different from small ones due to the division of labor; that the conceptual integrity of the product is therefore critical; and that it is difficult but possible to achieve this unity; (2) Brooks' view of these propositions a generation later; (3) a reprint of his classic 1986 paper "No Silver Bullet"; and (4) today's thoughts on the 1986 assertion, "There will be no silver bullet within ten years."
Über den Autor und weitere Mitwirkende
Frederick P. Brooks, Jr., was born in 1931 in Durham, NC. He received an A.B. summa cum laude in physics from Duke and a Ph.D. in computer science from Harvard, under Howard Aiken, the inventor of the early Harvard computers.
At Chapel Hill, Dr. Brooks founded the Department of Computer Science and chaired it from 1964 through 1984. He has served on the National Science Board and the Defense Science Board. His current teaching and research is in computer architecture, molecular graphics, and virtual environments.
He joined IBM, working in Poughkeepsie and Yorktown, NY, 1956-1965. He is best known as the "father of the IBM System/360", having served as project manager for its development and later as manager of the Operating System/360 software project during its design phase. For this work he, Bob Evans, and Erick Block were awarded and received a National Medal of Technology in 1985.
Dr. Brooks and Dura Sweeney in 1957 patented a Stretch interrupt system for the IBM Stretch computer that introduced most features of today's interrupt systems. He coined the term computer architecture . His System/360 team first achieved strict compatibility, upward and downward, in a computer family. His early concern for word processing led to his selection of the 8-bit byte and the lowercase alphabet for the System/360, engineering of many new 8-bit input/output devices, and providing a character-string datatype in PL/I.
In 1964 he founded the Computer Science Department at the University of North Carolina at Chapel Hill and chaired it for 20 years. Currently, he is Kenan Professor of Computer Science . His principal research is in real-time, three-dimensional, computer graphics-"virtual reality." His research has helped biochemists solve the structure of complex molecules and enabled architects to "walk through" buildings still being designed. He is pioneering the use of force display to supplement visual graphics.
Brooks distilled the successes and failures of the development of Operating System/360 in The Mythical Man-Month: Essays in Software Engineering , (1975). He further examined software engineering in his well-known 1986 paper, "No Silver Bullet." He is just completing a two-volume research monograph, Computer Architecture , with Professor Gerrit Blaauw. Now, 20 years after the initial publication of his book, Brooks has revisited his original ideas and added new thoughts and advice within The Mythical Man-Month, Anniversary Edition .
Brooks has served on the National Science Board and the Defense Science Board. He is a member of the National Academy of Engineering and the American Academy of Arts and Sciences. He has received the the IEEE John von Neumann Medal, the IEEE Computer Society's McDowell and Computer Pioneer Awards, the ACM Allen Newell and Distinguished Service Awards, the AFIPS Harry Goode Award, and an honorary Doctor of Technical Science from ETH-Zürich.
Produktinformation
- ASIN : 0201835959
- Herausgeber : Addison-Wesley Longman; Jubiläumsausg. Edition (2. August 1995)
- Sprache : Englisch
- Taschenbuch : 336 Seiten
- ISBN-10 : 9780201835953
- ISBN-13 : 978-0201835953
- Abmessungen : 23.04 x 15.52 x 1.91 cm
- Amazon Bestseller-Rang: Nr. 112.220 in Bücher (Siehe Top 100 in Bücher)
- Nr. 142 in Projektmanagement (Bücher)
- Nr. 185 in IT-Projektmanagement
- Nr. 206 in Softwareentwicklung (Bücher)
- Kundenrezensionen:
Informationen zum Autor

Entdecke weitere Bücher des Autors, sehe ähnliche Autoren, lese Buchempfehlungen und vieles mehr.
Kundenrezensionen
- 5 Sterne4 Sterne3 Sterne2 Sterne1 Stern5 Sterne66%21%9%2%1%66%
- 5 Sterne4 Sterne3 Sterne2 Sterne1 Stern4 Sterne66%21%9%2%1%21%
- 5 Sterne4 Sterne3 Sterne2 Sterne1 Stern3 Sterne66%21%9%2%1%9%
- 5 Sterne4 Sterne3 Sterne2 Sterne1 Stern2 Sterne66%21%9%2%1%2%
- 5 Sterne4 Sterne3 Sterne2 Sterne1 Stern1 Stern66%21%9%2%1%1%
Kundenbewertungen, einschließlich Produkt-Sternebewertungen, helfen Kunden, mehr über das Produkt zu erfahren und zu entscheiden, ob es das richtige Produkt für sie ist.
Um die Gesamtbewertung der Sterne und die prozentuale Aufschlüsselung nach Sternen zu berechnen, verwenden wir keinen einfachen Durchschnitt. Stattdessen berücksichtigt unser System beispielsweise, wie aktuell eine Bewertung ist und ob der Prüfer den Artikel bei Amazon gekauft hat. Es wurden auch Bewertungen analysiert, um die Vertrauenswürdigkeit zu überprüfen.
Erfahren Sie mehr darüber, wie Kundenbewertungen bei Amazon funktionieren.Spitzenrezensionen aus Deutschland
Derzeit tritt ein Problem beim Filtern der Rezensionen auf. Bitte versuche es später erneut.
- Bewertet in Deutschland am 1. Oktober 2019Mr. Brooks and his team needed 5000 man years from 1963 to 1966 to create OS/360. Peak head count was 1000 persons. Today we ask the question: was this massive amount of labor necessary? I think so. Today the art of operating systems is much advanced. But at Brooks time, he had to break new ground, fast and in good quality. He and his very large team did write history, like Prof. Corby (Corbató) did with Multics. Next to Brooks law I like his scheduling rule most: 1/3 planning, 1/6 coding, 1/4 component test and early system test and 1/4 system test, all components in hand. In my projects I used the surgeon team, Mill's Proposal. It worked again and again.
- Bewertet in Deutschland am 11. Februar 2017Trotz seines Alters, ist und bleibt dieses Buch ein Klassiker, der in vielen Bereichen immer noch aktuell ist. Es ist sehr Lesenswert und schafft es verschiedene Aspekte innerhalb des Projektmanagements gut zu beleuchten.
- Bewertet in Deutschland am 31. Juli 2015Es ist interessant zu sehen, dass das Buch immer noch zum Teil relevant ist - und wo nicht ist das an sich nicht unbedingt uninteressant, weil man es als ein historisches Dokument betrachten kann. Man muss aber manchmal aushalten - ab und zu habe ich einen Teil übersprungen, weil ich den Teil doch veraltet fand, nur später zu merken, dass eine kleine interessante Information versteckt war.
- Bewertet in Deutschland am 11. August 2014The classic message is somehow timeless: More developpers is not necessarily faster development! Every developer is aware of/knows this. It remains to be almost a day to day problem to many projects, though. The silver bullet solution is still to be found, even in 2014.
- Bewertet in Deutschland am 20. August 2012even if outdated by some technical facts, this book offers a timeless inside into the world of project management. forget all the others books - if you have read this one, you have read all. this is my management bible ;).
- Bewertet in Deutschland am 4. Mai 2022I haven't read the book yet, but the printing quality is pretty terrible. It looks like something I printed on my home printer. What's more, the book arrived a little dinged.
- Bewertet in Deutschland am 14. Mai 2015Wer Planung in der IT verstehen möchte kommt an diesem Klassiker nicht vorbei. Brooks Gesetz: Warum wird ein Software-Projekt nicht schneller fertig, obwohl ich mehr Mitarbeiter reinstecke?
- Bewertet in Deutschland am 20. März 1998In 1975, Frederick P. Brooks, Jr. wrote a ground breaking insightful book about computer science. He accurately captured someof its more esoteric aspects and relayed them in a colorful narrative. I especially liked his use of the illustrations and quotations as the opening of each chapter. Each was thoughtfully chosen and served to set the tone for the following text.
Also entertaining is Brooks' use of the analogy. In the section using the tar pit to describe the struggle faced during large system programming, one comes away saying, "Been there, seen that!" This technique draws you in and makes you want to read on.
Readers of this book will find themselves looking at computer science differently. No longer will it be just a science. The philosophical and artistic values will become clear. Brooks' holistic approach may very well sway some readers toward a more pensive view of computer science. At the very least, the reader should come away with a deeper appreciation for software engineering.
My only negative commentary would be with the added chapters. While the insight gained over twenty years is useful, it comes off as a little defensive. It's almost as if the passion which so beautifully captured the message in the 1975 version, was spent on defending twenty year old statements. I suspect that the author might argue that he was trying to be systemic and clear. In my opinion this came off as overkill. To borrow an old argument, maybe Dr. Brooks fell victim to the "Second-System Effect" of which he so vividly warns us.
Spitzenrezensionen aus anderen Ländern
-
Dmitry RochaBewertet in Kanada am 11. Dezember 20225,0 von 5 Sternen The book is in good conditions
The book is in good conditions. There are some minor issues in the cover, but nothing too serious.
It was worth paying half price (+shipping).
-
giammaBewertet in Italien am 27. Oktober 20245,0 von 5 Sternen Utile
Letto molti anni fa all'inizio della carriera, l'ho visto in offerta usato e ho voluto comprarlo per la mia libreria.
Racconta molte cose che dovrebbe essere ovvie a tutti, ma purtroppo ancora oggi si incontrano professionisti del settore a cui mancano decisamente le basi.
-
D. M. TolleyBewertet in Großbritannien am 20. September 20235,0 von 5 Sternen A masterwork
Although almost 50 years old now, Brooks has stood the test of time. Today it works both as a history of software engineering and as a classic of practical lessons in how software engineering should be managed. The lessons are largely timeless and written in a way which allow the reader to think broadly about their useful application. This is probably the kindle book I have highlighted most!
-
Paula Cristiane SilvaBewertet in Brasilien am 15. Oktober 20205,0 von 5 Sternen Um clássico assustadoramente atual
Um clássico que sempre assusta: como estamos errando e falando das mesmas coisas há tantos anos? Estamos aprendendo com as experiências passadas, ou apenas reinventando a roda e caindo nos mesmos erros a cada novo sistema? Leitura obrigatória para todos os profissionais de TI, principalmente desenvolvedores.
-
Cliente de AmazonBewertet in Mexiko am 22. Juli 20185,0 von 5 Sternen Excelente libro
En el se revela los errores que cometemos al desarrollar un proyecto, nunca esta de más este tipo de libros que te señalar errores que no percibes y sin embargo en algún momento caes en ellos sin darte cuenta, 100% recomendable.







