|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
 Gutschein erhalten
Tauschen Sie jetzt Software Estimation: Demystifying the Black Art: The Black Art Demystified (Best Practices (Microsoft)) gegen einen Amazon-Gutschein in Höhe von EUR 2,80 ein - einlösbar für Tausende von Artikeln bei Amazon.de. Entdecken Sie mehr eintauschbare Bücher im Bücher Trade-In Shop. Bitte beachten Sie die Teilnahmebedingungen.
 Jetzt für Amazon Student anmelden und um 20% erhöhten Eintauschwert sichern. |
Wird oft zusammen gekauft
Produktinformation
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
Ist der Verkauf dieses Produkts für Sie nicht akzeptabel? |
Mehr über den Autor
Entdecken Sie Bücher, lesen Sie über Autoren und mehr
› Besuchen Sie die Seite von Steve McConnell auf Amazon
› Besuchen Sie die Seite von Steve McConnell auf Amazon
Produktbeschreibungen
Kurzbeschreibung
Often referred to as the black art because of its complexity and uncertainty, software estimation is not as difficult or puzzling as people think. In fact, generating accurate estimates is straightforward once you understand the art of creating them. In his highly anticipated book, acclaimed author Steve McConnell unravels the mystery to successful software estimation distilling academic information and real-world experience into a practical guide for working software professionals. Instead of arcane treatises and rigid modeling techniques, this guide highlights a proven set of procedures, understandable formulas, and heuristics that individuals and development teams can apply to their projects to help achieve estimation proficiency. Discover how to: Estimate schedule and cost or estimate the functionality that can be delivered within a given time frame Avoid common software estimation mistakes Learn estimation techniques for you, your team, and your organization Estimate specific project activities including development, management, and defect correction Apply estimation approaches to any type of project small or large, agile or traditional Navigate the shark-infested political waters that surround project estimates When many corporate software projects are failing, McConnell shows you what works for successful software estimation.
Synopsis
Often referred to as the black art because of its complexity and uncertainty, software estimation is not as difficult or puzzling as people think. In fact, generating accurate estimates is straightforward once you understand the art of creating them. In his highly anticipated book, acclaimed author Steve McConnell unravels the mystery to successful software estimation distilling academic information and real-world experience into a practical guide for working software professionals. Instead of arcane treatises and rigid modeling techniques, this guide highlights a proven set of procedures, understandable formulas, and heuristics that individuals and development teams can apply to their projects to help achieve estimation proficiency.Discover how to: Estimate schedule and cost or estimate the functionality that can be delivered within a given time frame Avoid common software estimation mistakes Learn estimation techniques for you, your team, and your organization Estimate specific project activities including development, management, and defect correction Apply estimation approaches to any type of project small or large, agile or traditional Navigate the shark-infested political waters that surround project estimates When many corporate software projects are failing, McConnell shows you what works for successful software estimation.
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
In diesem Buch
(Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Vorgeschlagene Tags zu ähnlichen Produkten(Was ist das?)Setzen Sie den ersten relevanten Tag hinzu (ein Schlüsselwort, das mit diesem Produkt in engem Zusammenhang steht).
|
Eine digitale Version dieses Buchs im Kindle-Shop verkaufen
Wenn Sie ein Verleger oder Autor sind und die digitalen Rechte an einem Buch haben, können Sie die digitale Version des Buchs in unserem Kindle-Shop verkaufen.
Weitere Informationen
Kundenrezensionen
Die hilfreichsten Kundenrezensionen
3 von 3 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
Carefully written books are not the rule in computing where the speed of developments often overtakes an author while he still broods over his topic. Much in IT is , for this reason, written in great haste. The present book is a rare exception to this rule. It is the outcome of many years of experience and repeated verification of the techniques presented.
Software estimation, i.e. the informed guess at how long some task or project will take and what kind of effort is required, is a necessary prerequisite for steering a project: Unless a project manager has some idea of the schedule ahead, he is not in a position to plan and staff a project, let alone provide the necessary budget. But how does one make reasonable assumptions about an uncertain future? The key, at least in software development, is estimation. Estimation is not a black art, insists the author of the present book, but there are techniques which help making informed and well reasoned assumptions about the future. These techniques are what the book is about. The book has three parts: It starts by examining the the critical estimation concepts. I have in particular enjoyed reading about where estimation errors usually come from. The core of the book is part two, which is devoted to estimation techniques. At their very foundation is 'count, compute, judge', not guess. The last part discusses the various estimation challenges, which include converting estimates into planning parameters, or political issues resulting from contentious estimates.
Where much praise is due some criticism is also in order. If there is one aspect of estimation which I think remains somewhat out of focus then it is the question of the sources of requirements. The book, in its larger part, assumes that requirements are given in a form which is accessible to estimation. In actual practice this is not usually the case. And even if requirements are available, estimation usually requires that these requirements should be brought into a formal form which allows one to submit them to 'counting, judging, computing'. There are few hints in this book regarding these two fundamental questions. The first might be delegated to books on requirements engineering, while the second, I think, should have been included, at least in the form of extended examples (the examples of the book are suitably simple for the purpose of the exposition, they remain sub-ideal as applicable templates).
The art of estimation is one of the tools that should be in any architects toolbox. Unfortunately, this tool is often forgotten in introductions to (pragmatic) software architecture. As I know no better book on the topic of estimation, I think this book is a must-have for all software architects. Or should I say: A must-read!
Software estimation, i.e. the informed guess at how long some task or project will take and what kind of effort is required, is a necessary prerequisite for steering a project: Unless a project manager has some idea of the schedule ahead, he is not in a position to plan and staff a project, let alone provide the necessary budget. But how does one make reasonable assumptions about an uncertain future? The key, at least in software development, is estimation. Estimation is not a black art, insists the author of the present book, but there are techniques which help making informed and well reasoned assumptions about the future. These techniques are what the book is about. The book has three parts: It starts by examining the the critical estimation concepts. I have in particular enjoyed reading about where estimation errors usually come from. The core of the book is part two, which is devoted to estimation techniques. At their very foundation is 'count, compute, judge', not guess. The last part discusses the various estimation challenges, which include converting estimates into planning parameters, or political issues resulting from contentious estimates.
Where much praise is due some criticism is also in order. If there is one aspect of estimation which I think remains somewhat out of focus then it is the question of the sources of requirements. The book, in its larger part, assumes that requirements are given in a form which is accessible to estimation. In actual practice this is not usually the case. And even if requirements are available, estimation usually requires that these requirements should be brought into a formal form which allows one to submit them to 'counting, judging, computing'. There are few hints in this book regarding these two fundamental questions. The first might be delegated to books on requirements engineering, while the second, I think, should have been included, at least in the form of extended examples (the examples of the book are suitably simple for the purpose of the exposition, they remain sub-ideal as applicable templates).
The art of estimation is one of the tools that should be in any architects toolbox. Unfortunately, this tool is often forgotten in introductions to (pragmatic) software architecture. As I know no better book on the topic of estimation, I think this book is a must-have for all software architects. Or should I say: A must-read!
4 von 5 Kunden fanden die folgende Rezension hilfreich
Super Buch, wenn man mehr über Aufwandsschätzung von Software Projekten wissen möchte.
28. September 2007
Format:Taschenbuch
Ich habe mich im Kontext eines Vortrages mit dem Thema Aufwandsschätzung von Software Projekten befasst und bin auf dieses Buch gestoßen, welches mir bei weitem am Besten zu diesem Thema gefallen hat. Steve McConnell weiß einfach worauf es ankommt und bringt dieses Wissen in einer Art und Weise rüber, die einfach klasse ist. Die Liste der 118 Tips in dem Kontext ist Gold wert und nach der Lektüre weiß man worauf man bei der Aufwandsschätzung achten muss und wie man diese durchführt. Ich kann das Buch nur empfehlen.
Format:Taschenbuch
I am not finish with reading, yet. But my first impression is very positive.
One of the first chapters describes how to read the book. If you follow this guide, you can get directly go to the applied estimation techniques. Thus, you can start using the book very fast without reading it from the beginning to the end. But of course, you should also read the theory if you can free some time.
Number one book on software estimation. Very Good.
One of the first chapters describes how to read the book. If you follow this guide, you can get directly go to the applied estimation techniques. Thus, you can start using the book very fast without reading it from the beginning to the end. But of course, you should also read the theory if you can free some time.
Number one book on software estimation. Very Good.
Möchten Sie weitere Rezensionen zu diesem Artikel anzeigen?
Waren diese Rezensionen hilfreich?
Wir wollen von Ihnen hören.
Die neuesten Kundenrezensionen
Was bedeutet Schätzen, was ist eine gute Schätzung und warum...
Zählen, Berechnen und erst als letzte Option Schätzen lautet die Empfehlung des Autors. Verschiedene Methoden und ihre Anwendbarkeit auf Projekte in Bezug auf... Lesen Sie weiter...
Vor 16 Monaten von _local veröffentlicht
Erste Wahl bei der Such nach Infos über Software Schätzung
Aus meiner Sicht braucht man als Software Projekt Manager drei Bücher: Software Estimation, Rapid Development und Software Project Survival Guide. Lesen Sie weiter...
Veröffentlicht am 11. März 2010 von ogni42
Kunden diskutieren
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
Lieblingslisten
|
|
Ähnliche Artikel finden
Anhand des Sachgebietes nach ähnlichen Produkten suchen:
Ihr Kommentar
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
|
