Rapid Development
und über 1 Million weitere Bücher verfügbar für Amazon Kindle .
Erfahren Sie mehr
| ||||||||||||||||||
 Gutschein erhalten
Tauschen Sie jetzt Rapid Development: Taming Wild Software Schedules gegen einen Amazon-Gutschein in Höhe von EUR 2,35 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.
|
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
Amazon.com
I can hear some of you exclaiming, "How can you possibly recommend a book about software scheduling published by Microsoft Press and written by a consultant to Microsoft?!" Well, put aside any preconceived biases. This is a tremendous book on effective scheduling software development, and it drinks deeply from the wisdom of all the classics in the field such as Brook's Mythical Man Month -- and is likely well-informed by McConnell's experiences, good and bad, in Redmond.
The nine page section entitled "Classic Mistakes Enumerated" is alone worth the price of admission and should be required reading for all developers, leads, and managers. Here are some types of the 36 classic mistakes that McConnell describes in detail:
- People Related Mistakes
- Heroics
- Adding people to a late project
- Politics placed over substance (etc.)
- Process Related Mistakes
- Abandonment of planning under pressure
- Planning to catch up later
- "Code-like-hell" programming (etc.)
- Technology Related Mistakes
- Silver-Bullet syndrome
- Overestimating savings from new tools or methods
- Switching tools in the middle of a project (etc.)
I suspect that if you've ever been involved in software development, you winced after reading each of these nine points. And you will learn a great deal from the remaining 640 pages about concrete solutions.
My only substantive gripe: cheesy Powerpoint graphics. Nonetheless, this book is Very Highly Recommended.
Kurzbeschreibung
Corporate and commercial software-development teams all want solutions for one important problem how to get their high-pressure development schedules under control. In RAPID DEVELOPMENT, author Steve McConnell addresses that concern head-on with overall strategies, specific best practices, and valuable tips that help shrink and control development schedules and keep projects moving. Inside, you ll find: A rapid-development strategy that can be applied to any project and the best practices to make that strategy work Candid discussions of great and not-so-great rapid-development practices estimation, prototyping, forced overtime, motivation, teamwork, rapid-development languages, risk management, and many others A list of classic mistakes to avoid for rapid-development projects, including creeping requirements, shortchanged quality, and silver-bullet syndrome Case studies that vividly illustrate what can go wrong, what can go right, and how to tell which direction your project is going RAPID DEVELOPMENT is the real-world guide to more efficient applications development.
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
In diesem Buch
(Mehr dazu)
Einleitungssatz
THE PRODUCT MANAGER TOLD ME he wanted to build a product right for a change. Lesen Sie die erste Seite
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
THE PRODUCT MANAGER TOLD ME he wanted to build a product right for a change. Lesen Sie die erste Seite
Mehr entdecken
Wortanzeiger
Ausgewählte Seiten ansehenWortanzeiger
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
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).
|
Kundenrezensionen
|
Sagen Sie Ihre Meinung zu diesem Artikel:
|
||||||||||||||||||||||
|
Die hilfreichsten Kundenrezensionen
6 von 7 Kunden fanden die folgende Rezension hilfreich:
3.0 von 5 Sternen
A complete Lexicon - but talkative and not precise,
Von Ein Kunde
Rezension bezieht sich auf: Rapid Development: Taming Wild Software Schedules (Taschenbuch)
Now Steve McConnell is known for books like his famous survival guide where he writes alot of prosa around psychology of teams and their managers, using colorful methaphors and an entertaining style. Rapid development comes with two parts, the first more resembling that, and a larger part with a lexicon where each word you might come to know (Like Evolutionary delivery, Micro Milestones etc.) is packed within a "Best Practise" chapter, and explained in detail. And I truly believe this is nothing which McConnell is good at. Most of the stuff is given without too much explanation ,and where he makes comparisons (say between different life cycle models), he always stays nebulous and then just brings one or two statements of what he calls "hard data" (like : "you're twice as fast [compared to what ??] using EVO", or "with Basic, you only need a fourth of the lines of code than in C++ [why ???]"). I can recommend the book for people who want a lexicon with 4 pages for every trendy method in software engineering, but its not usable to really learn methodologies, or to take decisions on applying them or not.
Helfen Sie anderen Kunden bei der Suche nach den hilfreichsten Rezensionen
8 von 10 Kunden fanden die folgende Rezension hilfreich:
5.0 von 5 Sternen
To The Critics,
Rezension bezieht sich auf: Rapid Development: Taming Wild Software Schedules (Taschenbuch)
Hi,Just wanted to laugh at the folks criticizing this book because it comes from someone who worked at Microsoft. The funny thing is that, in my 10 years as a software developer, 99% of the people who complain about Microsoft sofware being buggy are themselves working on a project suffering from the same problems or worse. Let those who are free of sin cast the first stone. And since software engineering involves trying to control something that is inherently chaotic and error prone as a rule, I don't believe many of us will be casting stones. (Unless you are working on a one man project at a University or something). Keep in mind that Microsoft produces more software then anybody else out there, and given the level of sophistication, do a pretty good job. There is a group of people who deeply resent having to run MS software on their PC's because they wanted other platforms to have more of a following. I am one of those hard to find people who understand the technical limitations of much of MS software but who respects, from a business point of view, the software machine that they've become. My recommendation to those of you without a deep seeded hatred of Microsoft (and with an ounce of open mindedness left) is this: go to a bookstore and just peruse Chapter 3 on classic mistakes. If this doesn't adequately describe the most common mistakes you've seen in your development career, then you don't need the book. Helfen Sie anderen Kunden bei der Suche nach den hilfreichsten Rezensionen
1 von 1 Kunden fanden die folgende Rezension hilfreich:
5.0 von 5 Sternen
Best practices for developers and managers,
Rezension bezieht sich auf: Rapid Development: Taming Wild Software Schedules (Taschenbuch)
I've been kicking around the industry for 25 years, as a developer and technical manager, and this book expresses many concepts that I have half-formed over that time but never really been able to express. McConnell also backs them up with relevant data.If you're a developer, read this for the sections on estimation, negotiation and overtime. Then you'll want to read the rest of it. If you're a technical manager, just buy and read the whole thing. It's all *very* relevant, because you're in the middle of the whole process. Buy the book because you'll want to keep it nearby afterwards to point your line managers and developers at the hard data when they try to get round you! If you're a line manager, read this for the sections on teamwork, how to motivate developers, and overtime. Then read the rest anyway; it's relevant to you, too. McConnell has an easy style, and the book is an entertaining read. It's also split into small sections; I read it over three weeks on the train to and from work. Helfen Sie anderen Kunden bei der Suche nach den hilfreichsten Rezensionen
Sagen Sie Ihre Meinung zu diesem Artikel: Eigene Rezension erstellen
|
Die neuesten Kundenrezensionen |
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?
