Rating: 
Summary: This book pulls you right in!
Review: The prologue suggests you read chapter 1 and 2 at a bare minimum. However, you'll find yourself in chapter 6 before you know it! The case studies, though contrived, are entertaining and hauntingly familiar.Even though the latter half of the book is supposed to be used as reference, the entire book reads like a good novel. You'll be able to use techniques from this book almost immediately, and you'll improve your ability to effectively create project schedules you can live with.
Rating:
Summary: A very good starter
Review: This book is a great starting point for anyone involved in software development management. If You need deeper knowledge of any of the issues, You should consider buying one of the many books in the bibliography (maybe one of the author).
Rating:
Summary: A great reference source for project management
Review: Having read many books on such subjects, I found this one very good. Though a bit wordy at times, I found that I could immediately apply some of the principles that were outlined. Since then, I've also used it as a reference guide during a very aggressive software development schedule. This is one of the few books that I've found that does a good job of covering the leadership, motivation, and political aspects of software development. This is crucial, as none of us are immune from such issues.
Rating:
Summary: This book restored my hope for effective project management
Review: This is the best book on software project management I have ever read. It tells, in detail, how to manage software development and implementation projects in ways that actually lead to on-time, under-budget delivery--what a concept!
Rating:
Summary: RAPID DEVELOPMENT: The project manager's Bible
Review: 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.
Rating:
Summary: I HAVE RECOMMENDED THIS BOOK TO EVERYONE IN MY ORGANIZATION.
Review: MCCONNELL WENT BEYOND THE CONCEPTUAL AND PROVIDED HARD DATA TO SUPPORT MOST OF HIS ASSERTIONS. GOOD CASE STUDIES ALSO GIVE PRACTICAL EXAMPLES OF THE TOPICS. BEYOND BEING INTENSELY INFORMATIVE, THE BOOK PROVIDES A NUMBER OF GOOD REFERENCES FOR FURTHER RESEARCH. IT'S QUITE LONG, BUT WORTH THE READ. I WOULD RECOMMEND THIS BOOK TO ANYONE INVOLVED IN THE SOFTWARE ENGINEERING PROCESS, MOST ESPECIALLY THOSE INVOLVED IN TECHNICAL MANAGEMENT.
Rating:
Summary: worth every cent!
Review: Amazing book! Go buy it at once ... You will find yourself reading the book from cover to cover and more importantly, will use it as a reference manual,to dip into from time to time, to solve specific problems.thanx a million Steve!
Rating:
Summary: Currently, the best software management book available.
Review: I've bought 5 copies of this book. One copy for myself and four for other managers. The other four raved about this book. I've seen better than a dozen technology management books and this is the most outstanding one so far.
Rating:
Summary: Excellent, if a bit long
Review: I wish someone had given me McConnell's first
book, "Code Complete", when I first started
programming for a living. Similarly, I wish
I'd been given "Rapid Development" when I first
started to manage software projects, and other
programmers. His survey of software project
management issues and techniques is thorough,
readable, well-organized, and 100% relevant to
small software development teams (which is where
most of us work). For the full text of my review,
see the March '97 issue of "Doctor Dobbs", or
the Electronic Review of Computer Books at:
http://www.ercb.com/ddj/1997/ddj.9703.html
Rating:
Summary: Have your entire development staff read it.
Review: Steve McConnell has a very clear and concise writing style. He has a no nonsense approach to project management. Rapid Development is a must read for all developers and development management. Have your team take two hours a week and review it together. We did
| 
