Kundenrezensionen


55 Rezensionen
5 Sterne:
 (48)
4 Sterne:
 (5)
3 Sterne:
 (1)
2 Sterne:    (0)
1 Sterne:
 (1)
 
 
 
 
 
Durchschnittliche Kundenbewertung
Sagen Sie Ihre Meinung zu diesem Artikel
Eigene Rezension erstellen
 
 

Die hilfreichste positive Rezension
Die hilfreichste kritische Rezension


2 von 2 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Best practices for developers and managers
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...
Veröffentlicht am 25. Mai 2000 von Peter Crowther

versus
7 von 9 Kunden fanden die folgende Rezension hilfreich
3.0 von 5 Sternen A complete Lexicon - but talkative and not precise
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...
Am 21. November 1999 veröffentlicht


‹ Zurück | 1 26 | Weiter ›
Hilfreichste Bewertungen zuerst | Neueste Bewertungen zuerst

2 von 2 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Best practices for developers and managers, 25. Mai 2000
Rezension bezieht sich auf: Rapid Development (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 
War diese Rezension für Sie hilfreich? Ja Nein


9 von 11 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen To The Critics, 19. Juli 2000
Rezension bezieht sich auf: Rapid Development (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 
War diese Rezension für Sie hilfreich? Ja Nein


1 von 1 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen RAPID DEVELOPMENT: The project manager's Bible, 31. Dezember 1997
Von Ein Kunde
Rezension bezieht sich auf: Rapid Development (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.
Helfen Sie anderen Kunden bei der Suche nach den hilfreichsten Rezensionen 
War diese Rezension für Sie hilfreich? Ja Nein


1 von 1 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Clients should also be forced to read this..., 26. März 2000
Rezension bezieht sich auf: Rapid Development (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.
Helfen Sie anderen Kunden bei der Suche nach den hilfreichsten Rezensionen 
War diese Rezension für Sie hilfreich? Ja Nein


1 von 1 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen A page turner that can change your life!!!, 10. November 1998
Rezension bezieht sich auf: Rapid Development (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?
Helfen Sie anderen Kunden bei der Suche nach den hilfreichsten Rezensionen 
War diese Rezension für Sie hilfreich? Ja Nein


7 von 9 Kunden fanden die folgende Rezension hilfreich
3.0 von 5 Sternen A complete Lexicon - but talkative and not precise, 21. November 1999
Von Ein Kunde
Rezension bezieht sich auf: Rapid Development (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 
War diese Rezension für Sie hilfreich? Ja Nein


5.0 von 5 Sternen Pflichtlektüre in Sachen Softwareprojekte, 7. März 2014
Verifizierter Kauf(Was ist das?)
Rezension bezieht sich auf: Rapid Development (Taschenbuch)
Von McConnell kannte ich ja schon Code Complete, das ich unter den vielen Ratgebern für professionelle Programmierung am gelungendsten fand -- gut strukturiert, knapp und sachlich geschrieben, undogmatisch... einfach prima. Jetzt schmöker ich seit einigen Tagen in diesem Buch, und obwohl es schon knapp 20 Jahre auf dem Buckel hat, ist es mit Abstand wiederum das Beste seiner Klasse -- hier als praxisorientierte Einführung in und Ratgeber für professionelle Softwareentwicklung.

Man sollte ich von dem Titel nicht irreführen lassen: Hier geht es mitnichten nur um schnelle Softwareentwicklung. Ich bin mit dem Autor einer Meinung -- nämlich, dass diese nur möglich ist, wenn man zuvor die allgemeinen Grundlagen effizienter Softwareentwicklung beherrscht. Und diese beschreibt McConnell im ersten und im zweiten Abschnitt einfach hervorragend: umfassend, fundiert und einleuchtend. Mir gefällt sehr, dass er die jeweiligen Praktiken nie als Wunderwaffe preist, sondern immer sehr genau auf die spezifischen Voraussetzungen, Begrenzungen und Risiken eingeht, in den meisten Fällen auch durch Zahlen und Ergebnisse seriöser Untersuchungen belegt. Dadurch gewinnt man ein gutes Verständnis dafür, ob und wann man die jeweilige Methode überhaupt anwenden kann, und welchen Preis man dafür möglicherweise zahlen muss.

Der dritte Teil besteht aus einem kurzen Lexikon der wichtigsten "Best Practices" für schnelle Softwareentwicklung. Jeder Begriff wird definiert, und auch hier werden wieder Voraussetzungen und Risiken sowie Tipps zur Umsetzung angegeben. Zwar wiederholt sich auf den 650 Seiten manches, andererseits ist dies bei der Nichtlinearität des Themas eh nicht zu vermeiden (und Wiederholung ist eh gut fürs Einprägen!). Sehr gelungen die beiden großen Tabellen zu Beginn des dritten Teils. Die erste eine kategorisiert alle im Buch erwähnten Praktiken (in "Fundamental", "Best Philosophy", "Best Practice" und "Not a Best Practice") und verweist auf die jeweiligen Kapitel. Die zweite stellt eine Übersicht über die wichtigsten Auswirkungen aller der im Buch erwähnten Best Practices zusammen und ist ein unschätzbarer Startpunkt, um zu Beginn eines Projektes potenziell geeignete Praktiken zu identifizieren -- je nachdem, ob man präzise Terminierung oder flexible Anforderungen wünscht, kompetente Entwickler hat usw.

Ebenfalls absolut beispielhaft ist die Strukturierung und Verlinkung der Inhalte. Wo immer es geht, verweist McConnell auf Querbezüge zum Thema und natürlich weiterführende Literatur. Das verstärkt nur die Tauglichkeit des Buches als Nachschlagewerk zum täglichen Gebrauch, der einem schnell einen Überblick und jeweils interessante weiterführende Punkte verschafft.

Manch einer wird kritisieren, dass das Buch doch absolut veraltet sein dürfte, da fehlen Scrum, XP oder Entwurfsmuster ganz, und das ist tatsächlich ein Manko. Aber was die Grundlagen der Softwareentwicklung angeht, ist dieses Buch genauso aktuell wie eh und je. Und es versetzt einen in die Lage, neuere Praktiken zu analysieren und hinsichtlich ihrer Anwendbarkeit auf spezifische Projekte einzuschätzen.

FAZIT: Jeder, der einen professionellen Ansatz zur Softwareentwicklung verfolgt, wird von diesem Buch profitieren. Für technische Leiter und Manager von Softwareprojekten ist dieses Buch meines Erachtens ein absolutes Muss, und da übertreibe ich nicht. Für mich jedenfalls waren die lächerlichen 2 Euronen, die ich für dieses Buch gebraucht hier berappt habe, die profitabelste Investition aller Zeiten. Meine Empfehlung lautet somit einfach: Kaufen, studieren, ins firmeneigene Bücherregal und zumindest die ersten beiden Teile allen Beteiligten als Pflichtlektüre verschreiben.

PS. Nein, ich erhalte genauso kein Geld oder sonstige Vergünstigungen von Herrn McConnell oder Microsoft Press für diese Rezension wie wohl die anderen 48 von 54 Rezensenten hier, die das Buch mit 5 Sternen wärmstens empfehlen :)
Helfen Sie anderen Kunden bei der Suche nach den hilfreichsten Rezensionen 
War diese Rezension für Sie hilfreich? Ja Nein


5.0 von 5 Sternen Rapid Team Development with ColdFusion, 9. März 2000
Rezension bezieht sich auf: Rapid Development (Taschenbuch)
I read Michael Dinowitz's review of Steve McConnell's Code Complete in last week's issue of Fusion Authority, and wanted to tell you about another great book by him called "Rapid Development". This one is good for team ColdFusion projects on a short deadline (and what ColdFusion project is not rapid development!). The sub-title "Taming Wild Software Schedules" sums it up.
The book covers both technical ideas (such as estimation, risk management and mini milestones) and the psychology of both programmers and teams. The latter may be particularly useful on the high burnout 12-hour-a-day work cycle of many ColdFusion programming teams I have seen. Keeping everyone motivated and working together as a team is often more important than technical programming tricks on a large project.
Project Management Cookbook
The second half of the book, "Best Practices," is a cookbook of 36 techniques for project leaders designed to stop overruns and control those out-of-control, large ColdFusion projects. I have been developing for over 20 years, and nearly all of McConnell's tips ring true. The book is not about ColdFusion per see; it concerns any Rapid Development language.
I liked the fact that he rated each of these cookbook methods by the following criteria:
Potential reduction from nominal schedule Improvement in progress visibility Effect on schedule risk Chance of first time success Chance of long-term success
Here are some 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.)
If you are like me and have been involved in a few "projects from hell" then I am sure you recognise some (or all) of the above!
There are also fun sidebars from the trenches of real development teams, both successes and disasters. Twenty real-life case studies round it out.
This is a long book (650 pp) but I have found myself dipping into it for new insights in my daily work as a ColdFusion project manager.
Review by: Michael Smith, TeraTech
Helfen Sie anderen Kunden bei der Suche nach den hilfreichsten Rezensionen 
War diese Rezension für Sie hilfreich? Ja Nein


5.0 von 5 Sternen THE bible for software developers, managers, and consultants, 26. Juni 2000
Von 
Shawn Kresal (San Francisco, CA) - Alle meine Rezensionen ansehen
(REAL NAME)   
Rezension bezieht sich auf: Rapid Development (Taschenbuch)
Have you found yourself on a project that was running weeks or months late when the timeline itself was only a few months? The schedule was aggressive but reasonable, so where did things go awry? With software becoming more and more complex and growing pressure to release as quickly as possible it becomes critical for timelines to be maintained and adhered to. Rapid Development establishes a set of 27 Best Practices to help tame run-away software development schedules.
Is our project better suited for evolutionary or throwaway prototyping? What are the risks involved with each practice and how can we increase our chances of first-time success with this practice? McConnell's approach is credible and smart. He provides anecdotal and academic evidence of these practices with real-world examples and documented case studies, many of which come right from the halls of NASA, IBM, and Microsoft. How did the Windows management team motivate their developers to put in 18-hour days only to have them request that washers and dryers be installed so they wouldn't need to go home and do laundry? This and many other stories work as valuable lessons for every member of a software development team.
Although the book is aimed at project management and team leads, it is a must-read for anyone looking to establish a better grip on their effort/cost estimates, reduce development risk, or learn how to make a more accurate schedule.
A must-have, indispensible book for software developers, managers, and consultants. If you think you might benefit from this book, then just buy it. The chapter on morale alone is worth the cover price.
Helfen Sie anderen Kunden bei der Suche nach den hilfreichsten Rezensionen 
War diese Rezension für Sie hilfreich? Ja Nein


5.0 von 5 Sternen Essential reading for programmers and their managers, 27. Juli 1998
Rezension bezieht sich auf: Rapid Development (Taschenbuch)
As a developer, you have been on that project.  The one that seems that it will never end. Requirements change daily, testing seems to discover new bugs faster than you can fix them, release dates come and go and noone seems to know when the project will be completed. If you're like me, maybe you thought that was just the way software projects were.
And then I read this book. Chapter 3 contains a case study of classic mistakes.  It sounded like every project I had ever worked on. Steve McConnell shows you how to avoid those mistakes, and how to leverage best practices in planning and development to achieve maximum predictability and control over your software schedule.  This should be required reading for all software project managers, technical leads and top management.  
While it's a long book, it lends itself to easy browsing. You can almost dip in at random and find some useful tip on how to improve your chances of bringing your project in on time and unde! r budget. But you'll want to read it straight through at least once. The last section of the book is devoted to individual Best Practices.  Each practice is explained along with its risks and benefits. Not all practices will be applicable to all projects, and the book guides you through when each is appropriate along with what practices it compliments.
Helfen Sie anderen Kunden bei der Suche nach den hilfreichsten Rezensionen 
War diese Rezension für Sie hilfreich? Ja Nein


‹ Zurück | 1 26 | Weiter ›
Hilfreichste Bewertungen zuerst | Neueste Bewertungen zuerst

Dieses Produkt

Rapid Development
Rapid Development von Steve McConnell (Taschenbuch - 2. Juli 1996)
EUR 24,95
Auf Lager.
In den Einkaufswagen Auf meinen Wunschzettel
Nur in den Rezensionen zu diesem Produkt suchen