Mythical Man-Month, The: Essays on Software Engineering,... y más de 950.000 libros están disponibles para Amazon Kindle . Más información

Activar el pedido en 1-Clic.
Se requiere periodo de prueba de Amazon Premium. Regístrate al completar el pedido. Más información
Más opciones de compra
¿Tienes uno para vender? Vende el tuyo aquí
Lo sentimos, este producto no está disponible en
Imagen no disponible del

Empieza a leer Mythical Man-Month, The en tu Kindle en menos de un minuto.

¿No tienes un Kindle? Consigue un Kindle aquí o descarga una aplicación de lectura Kindle GRATUITA.

The Mythical Man Month: Essays on Software Engineering [Edición especial] [Tapa blanda]

Frederick P. Brooks
5.0 de un máximo de 5 estrellas  Ver todas las opiniones (1 opinión de cliente)
Precio recomendado: EUR 35,31
Precio: EUR 33,54 y este producto está disponible con envío GRATIS. Ver condiciones
Ahorras: EUR 1,77 (5%)
  Todos los precios incluyen IVA
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
En stock.
Vendido y enviado por Amazon. Se puede envolver para regalo.
¿Quieres recibir el pedido el miércoles 30 julio? Elige el envío 1 día al completar tu pedido. Ver detalles


Precio Amazon Nuevo desde Usado desde
Versión Kindle EUR 15,13  
Tapa blanda, Edición especial EUR 33,54  

Comprados juntos habitualmente

The Mythical Man Month: Essays on Software Engineering + Code Complete: A Practical Handbook of Software Costruction (Dv Professional) + Clean code: A Handbook of Agile Software Craftsmanship (Robert C. Martin)
Precio para los tres: EUR 108,33

Mostrar disponibilidad y detalles de envío

Comprar los productos seleccionados conjuntamente

Los clientes que compraron este producto también compraron

Descripción del producto

Reseña del editor

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."

Biografía del autor

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-Zurich.

Detalles del producto

  • Tapa blanda: 272 páginas
  • Editor: Prentice Hall; Edición: Nachdr. 20th Anniversary Edition. (1 de enero de 1995)
  • Idioma: Inglés
  • ISBN-10: 0201835959
  • ISBN-13: 978-0201835953
  • Valoración media de los clientes: 5.0 de un máximo de 5 estrellas  Ver todas las opiniones (1 opinión de cliente)
  • Clasificación en los más vendidos de Amazon: nº5.545 en Libros en idiomas extranjeros (Ver el Top 100 en Libros en idiomas extranjeros)
  • Ver el Índice completo

Opiniones de clientes

4 estrellas
3 estrellas
2 estrellas
1 estrellas
5.0 de un máximo de 5 estrellas
5.0 de un máximo de 5 estrellas
Las opiniones de cliente más útiles
5.0 de un máximo de 5 estrellas Problemas en Ingeniería del software 9 de septiembre de 2013
Por David
Formato:Tapa blanda|Compra verificada
Excelente libro en el que se plantea la problemática que se puede generalizar a la mayoría de proyectos software. Muy recomendable.
¿Esta opinión te ha parecido útil?
Opiniones de clientes más útiles en (beta) 4.5 de un máximo de 5 estrellas  210 opiniones
346 de 355 personas piensan que la opinión es útil
5.0 de un máximo de 5 estrellas I would give it a 100 stars if I could! 29 de mayo de 2004
Por A. Imran - Publicado en
Formato:Tapa blanda
If you have managed some software projects or have worked on some non-trivial software systems, undoubtedly you have faced many difficulties and challenges that you thought were unique to your circumstance. But after reading this book, you will realize that many of the things you experienced, and thought were unique problems, are NOT unique to you but are common systemic problems of developing non-trivial software systems. These problems appear repeatedly and even predictably, in project after project, in company after company, regardless of year, whether it's 1967 or 2007.
You will realize that long before maybe you were even born, other people working at places like IBM had already experienced those problems and quandries. And found working solutions to them which are as valid today as they were 30 years ago.
The suggestions in this book will help you think better and better manage yourself, and be more productive and less wasteful with your time and energy. In short, you will do more with less.
Some of Brooks insights and generalizations are:
The Mythical Man-Month:
Assigning more programmers to a project running behind schedule, may make it even more late.
The Second-System Effect:
The second system an engineer designs is the most bloated system she will EVER design.
Conceptual Integrity:
To retain conceptual integrity and thereby user-friendliness, a system must have a single architect (or a small system architecture team), completely separate from the implementation team.
The Manual:
The chief architect should produce detailed written specifications for the system in the form of the manual, which leaves no ambiguities about any part of the system and completely specifies the external spcifications of the system i.e. what the user sees.
Pilot Plant:
When designing a new kind of system, a team should factor in the fact that they will have to throw away the first system that is built since this first system will teach them how to build the system. The system will then be completely redesigned using the newly acquired insights during building of the first system. This second system will be smarter and should be the one delivered to the customer.
Formal Documents:
Every project manager must create a roadmap in the form of formal documents which specifies milestones precisely and things like who is going to do what and when and at what cost.
In order to avoid disaster, all the teams working on a project, such as the architecture and implementation teams, should stay in contact with each other in as many ways as possible and not guess or assume anything about the other. Ask whenever there's a doubt. NEVER assume anything.
Code Freeze and System Versioning:
No customer ever fully knows what she wants from the system she wants you to build. As the system begins to come to life, and the customer interacts with it, he understands more and more what he really wants from the system and consequently asks for changes. These changes should of course be accomodated but only upto a certain date, after which the code is frozen. All requests for more changes will have to wait until the NEXT version of the system. If you keep making changes to the system endlessly, it may NEVER get finished.
Specialized Tools:
Every team should have a designated tool maker who makes tools for the entire team, instead of all individuals developing and using their private tools that no one else understands.
No silver bullet:
There is no single strategy, technique or trick that will exponentially raise the productivity of programmers.
57 de 57 personas piensan que la opinión es útil
5.0 de un máximo de 5 estrellas A timeless classic "must read" 22 de febrero de 2001
Por B. Scott Andersen - Publicado en
Formato:Tapa blanda
There are few must reads in this industry. This is one. First published in 1975, this work is as applicable to software engineering today as it was then. Why? Because building things, including software, has always been as much about people as it has been about materials or technology--and people don't change much in only 25 years.

In the preface to the First Edition, Brooks states "This book is a belated answer to Tom Watson's probing question as to why programming is hard to manage." This short book (at just over 300 pages) does a masterful job answering that question.

It is here we first hear of Brooks's Law: "Adding manpower to a late software project makes it later." Brooks doesn't just drop that on the reader without explanation. Instead, he walks through the reasoning, discusses how communication in a group changes as the group changes or grows, and how additions to the group need time to climb the learning curve.

Those new to the industry or who are reading the book for the first time might be put off by the examples and technology discussed. Indeed, even in the newly released edition, the original text from 1975 is still present, essentially untouched. So, talk of OS/360 and 7090s, which permeates the text, is perhaps laughable to those not looking deeper. When talking about trade-offs, for example, Brooks offers "... OS/360 devotes 26 bytes of the permanently resident date-turnover routine to the proper handling of December 31 on leap years (when it is day 366). That might have been left to the operator." This is 26 bytes he's talking about!

Brooks provides a light, almost conversational tone to the prose. This isn't to say the observations and analysis were not very well researched. Comparing productivity number with those of Software Productivity Research (SPR), you'll find Brooks came up with the same measurements for productivity as Jones--only 20 years earlier!

Other wisdom is also buried in this work. Brooks declares "The question, therefore, is not whether to build a pilot system and throw it away. You will do that. The question is whether to plan in advance to build a throwaway, or to promise to deliver the throwaway to customers." The state of products I buy today tells me not enough people have taken Brooks's observations to heart!

The latest version of the text includes his work "No Silver Bullet." Brooks, who had brought us so much before, had one last "parting shot."

As I started this review I will also end it: this book is a classic. Read it.
138 de 156 personas piensan que la opinión es útil
5.0 de un máximo de 5 estrellas Must reading, but too seldom read 27 de abril de 2000
Por Bruce F. Webster - Publicado en
Formato:Tapa blanda|Compra verificada
In giving testimony before Congress a few years ago on IT issues, I said the following:
"Humanity has been developing information technology for half a century. That experience has taught us this unpleasant truth: virtually every information technology project above a certain size or complexity is significantly late and over budget or fails altogether; those that don't fail are often riddled with defects and difficult to enhance. Fred Brooks explored many of the root causes over twenty years ago in The Mythical Man-Month, a classic book that could be regarded as the Bible of information technology because it is universally known, often quoted, occasionally read, and rarely heeded."
I have been involved in software engineering for over 25 years, have written many articles and even a few books on the subject. Yet every time I think I've discovered some new insight, chances are I can find it tucked away somewhere in The Mythical Man-Month. And the tarpits and other dangers he lays out plague the IT industry today. I wonder when we will grasp and apply the fundamental insights that Brooks, Jerry Weinberg, and others laid out nearly three decades ago. ..bruce..
26 de 27 personas piensan que la opinión es útil
5.0 de un máximo de 5 estrellas Oldy but Goody 5 de marzo de 2001
Por Joanna Daneman - Publicado en
Formato:Tapa blanda
This book is a classic, but recently revised and corrected. The amazing thing is how relevant the book still is to software product development. If you are involved in software, this book is a must-read.
The most valuable part of the book, I believe, is the "plan to throw out" prototype chapter. While the goal is always to make a bigger, better, fast whatever, it is almost an axiom that you WILL build something that has to be discarded and reworked. This absolutely happens every time, I can tell you from first-hand experience. Therefore it is vital to plan to throw out so you can migrate your users to whatever will follow. If you dream that the first product is THE ONE, you risk abandoning them on a product that will inevitably evolve. Planning the throw-away also helps meet the schedule goals by setting reasonable milestones that can be met.
In my role as a product manager for a top-selling software product in its class, I found that the Mythical Man-Month was absolutely vital. However, some additional reading is recommended; Walker Royce's Software Project Management was published in 1998 and adds the dimension of software project evolution. This goes into more detail why you can't write all the specifications upfront, and even if you do, they are certain to change by the time the product is released.
21 de 22 personas piensan que la opinión es útil
5.0 de un máximo de 5 estrellas are your deadlines an exercise in futility? 22 de diciembre de 1999
Por Blake Jenkins - Publicado en
Formato:Tapa blanda
I find myself going back to this book regularly as management tries to double the size of a team in order to cut development time in half, or make supervisors out of great technical people. Normally when you read a technology book as old as this one, its distracting to see how much things have changed; in this case, its sobering to see how little things have changed. Brooks' project examples are artifacts of another era, but teams are still failing to deliver quality software on time for all the same reasons they were then. There's room for disagreement with some things in the Mythical Man-Month (most of which are addressed in the new chapters at the end), but it convinced me that making project deadlines doesn't have to be a roll of the dice, and gave me the insight to start looking at software development as a process instead of as an accident.
Ir a para ver las 210 opiniones existentes 4.5 de un máximo de 5 estrellas

Buscar productos similares por categoría