Rapid Development (Developer Best Practices) und über 1,5 Millionen weitere Bücher verfügbar für Amazon Kindle. Erfahren Sie mehr
EUR 21,44
  • Alle Preisangaben inkl. MwSt.
Nur noch 1 auf Lager (mehr ist unterwegs).
Verkauf und Versand durch Amazon.
Geschenkverpackung verfügbar.
Menge:1
Rapid Development ist in Ihrem Einkaufwagen hinzugefügt worden
Ihren Artikel jetzt
eintauschen und
EUR 0,60 Gutschein erhalten.
Möchten Sie verkaufen?
Zur Rückseite klappen Zur Vorderseite klappen
Anhören Wird wiedergegeben... Angehalten   Sie hören eine Probe der Audible-Audioausgabe.
Weitere Informationen
Dieses Bild anzeigen

Rapid Development (Englisch) Taschenbuch – 2. Juli 1996


Alle 4 Formate und Ausgaben anzeigen Andere Formate und Ausgaben ausblenden
Amazon-Preis Neu ab Gebraucht ab
Kindle Edition
"Bitte wiederholen"
Taschenbuch
"Bitte wiederholen"
EUR 21,44
EUR 18,83 EUR 2,47
20 neu ab EUR 18,83 26 gebraucht ab EUR 2,47

Hinweise und Aktionen

  • Studienbücher: Ob neu oder gebraucht, alle wichtigen Bücher für Ihr Studium finden Sie im großen Studium Special. Natürlich portofrei.


Wird oft zusammen gekauft

Rapid Development + Software Project Survival Guide (Developer Best Practices)
Preis für beide: EUR 39,70

Die ausgewählten Artikel zusammen kaufen

Kunden, die diesen Artikel gekauft haben, kauften auch

Jeder kann Kindle Bücher lesen — selbst ohne ein Kindle-Gerät — mit der KOSTENFREIEN Kindle App für Smartphones, Tablets und Computer.


Produktinformation

  • Taschenbuch: 680 Seiten
  • Verlag: Microsoft Press Books (2. Juli 1996)
  • Sprache: Englisch
  • ISBN-10: 1556159005
  • ISBN-13: 978-1556159008
  • Größe und/oder Gewicht: 18,5 x 4,1 x 22,6 cm
  • Durchschnittliche Kundenbewertung: 4.8 von 5 Sternen  Alle Rezensionen anzeigen (55 Kundenrezensionen)
  • Amazon Bestseller-Rang: Nr. 39.065 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
  • Komplettes Inhaltsverzeichnis ansehen

Mehr über den Autor

Entdecken Sie Bücher, lesen Sie über Autoren und mehr

Produktbeschreibungen

Amazon.de

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.

Synopsis

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
Mehr entdecken
Wortanzeiger
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Hier reinlesen und suchen:

Kundenrezensionen

4.8 von 5 Sternen

Die hilfreichsten Kundenrezensionen

2 von 2 Kunden fanden die folgende Rezension hilfreich Von Peter Crowther am 25. Mai 2000
Format: 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.
Kommentar War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback. Wenn diese Rezension unangemessen ist, informieren Sie uns bitte darüber.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen
9 von 11 Kunden fanden die folgende Rezension hilfreich Von Mike Schaefer am 19. Juli 2000
Format: 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.
Kommentar War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback. Wenn diese Rezension unangemessen ist, informieren Sie uns bitte darüber.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen
1 von 1 Kunden fanden die folgende Rezension hilfreich Von Ein Kunde am 31. Dezember 1997
Format: Taschenbuch
I work for an Internet software development company, and I have made this book required reading for every project manager and technical lead in our company. McConnell's combination of conceptual knowledge, supported by hard facts, is a rare thing in software development "how-tos."
The best-practices section at the back of the book is an invaluable reference. His "bad" case studies depressed me sometimes -- mainly because they were too close to my own projects -- but the "good" ones have become the scripts for my presentations to clients. He has a way of capturing the essence of the atmosphere in a development shop, so the case studies feel as if they took place in your own office.
I would highly recommend this book to anyone whose job is managing the development process, whether that be in a technical lead or a project management position. Maybe if more people read this book and follow its guidelines, we could all stop working weekends.
Kommentar War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback. Wenn diese Rezension unangemessen ist, informieren Sie uns bitte darüber.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen
1 von 1 Kunden fanden die folgende Rezension hilfreich Von Tagishsimon am 26. März 2000
Format: Taschenbuch
I concur with the view that this book should be required reading for anyone involved in software development - from the lowliest member of the team to the project management.
However, in addition, (assuming you write bespoke software) I'd suggest you try to get your clients to read it, to give them an insight about the software development process. And, if you can, get it for senior management involved in commissioning software.
I am in no doubt that there can be no-one involved in software development who would not profit by reading it; as such it is well worth its price.
I'm not at all impressed by the reviewer who gave it only a single star for the reason that it came out of Seattle: that just seems to be a dumb thing to do.
Kommentar War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback. Wenn diese Rezension unangemessen ist, informieren Sie uns bitte darüber.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen
1 von 1 Kunden fanden die folgende Rezension hilfreich Von Mumbo Gumbo am 10. November 1998
Format: Taschenbuch
I usually get hooked on one author and read all of his books. It was Jarasic Park for Michael Crichton, Rainmaker for John Grisham, and Rapid Development for Steve McConnell. Steve McConnell has great approach of using examples and statistics in making his methodologies real and his message hit home. Having been stuck with managing several disasterous software project, I found myself laughing with most of McConnell's examples. I actually used methods presented in this book to create a plan to sucessfully save one project from pending litigation. One question: since McConnell was once a Microsoft consultant, is it only a coincidence that the evil manager in most of his examples is named Bill?
Kommentar War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback. Wenn diese Rezension unangemessen ist, informieren Sie uns bitte darüber.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen
7 von 9 Kunden fanden die folgende Rezension hilfreich Von Ein Kunde am 21. November 1999
Format: 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.
Kommentar War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback. Wenn diese Rezension unangemessen ist, informieren Sie uns bitte darüber.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen

Die neuesten Kundenrezensionen