Rating: 
Summary: Must Read for Dev Managers
Review: This is probably a little too much HR for a developer, but for anyone from Team Leader to Development Manager, you'll get a lot from this book. I suggest programmers read Code Complete, another masterpiece from the same author.
Rating:
Summary: An absolute must
Review: This book is a must for Project managers and Software engineers.
it is the most comprehensive review of common practices and common mistakes I've seen so far. Read this book BEFORE YOU START your first project as a manager and it will save you more time and trouble that you could ever imagine.
Rating:
Summary: Excellent roadmap for success
Review: This really is an excellent book for learning the best practices of software development. A friend recommended it to me two years ago and I just got around to reading it. My projects over the last two years would have greatly benefitted from this book, and at least now I know the future projects will be much, much better. I also recommend "Code Complete" and "Software Project Survival Guide".
Rating:
Summary: Programmer to Project Manager
Review: This is the best book on Software development today and will remain for years to come. If you are in any way related to information technology, this book is a paradise for you..its a must buy...i would pay any amount to get this book...Mirror Mirror on the Wall, Which is the best book on Software development of all?? Ans: Rapid Development: taming wild software schedules by Steve is no doubt the best book of all...
Rating:
Summary: Excellent, the best book I've read so far
Review: As a technical manager in an internet start up I run a team of developers. This book provides an excellent overview on how to structure your team, run the development process, schedule, supervise and lead to a successful conclusion a technical project. I particularly liked the structure. It starts out describing how to approach a project and then touches on important things like motivation and teamwork. Every chapter has 2-3 cases which describe a typical development flaw or a good practice. This book should be a mandatory reading for any developer or a team leader. Highly recommended.
Rating:
Summary: Excellent Reference
Review: This book is very well written and offers clear, concise, in depth explanations of the fundamentals that can make or break a software project. The author lists references to other resources that are devoted to a particular topic at the end of each chapter. The "Best Practices" section is excellent. You won't be dissapointed.
Rating:
Summary: To The Critics
Review: 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.
Rating:
Summary: Great for Managers and Developers
Review: This is an excellent project-centric book for both managers and developers. If you are a manager, it tells you what to do and what not to do. Teaches you not to be bullied by technologically ignorant corporate officers, how developers think and how to make them happy. Most of all, it teaches you how to leverage your projects to get the most bang for your buck. Sites real-world examples as well as the hypothetical. I highly recommend this book for anyone working professionally in the IT/IS industry.
Rating:
Summary: Just buy it!
Review: A great book for Technical team leaders and their project managers. Lots of sound insight and advice. Chapters can be read in isolation - so you can leave this book by your computer and read a chapter as you want it. McConnell is a very easy read. The case studies are interesting but don't offer much insight by themselves. He really lets you see the advantages and disadvantages of various project lifecycles, different best practices and how and when to apply them.
Rating:
Summary: THE bible for software developers, managers, and consultants
Review: 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.
| 
