Rating: 
Summary: You WILL be impressed with the quality & depth of this book!
Review: How many books in all of amazon.com have 30+ customer comments--ALL of them rating 5 stars? Enough said.
Rating:
Summary: A Must-Have Desk Reference for All Development Managers
Review: As more and more senior executives are demanding all three sides of the product pyramid (Low Cost, High Quality, and Speed to Market) development managers are under more pressure than ever before to tame software development schedules. McConnell takes a very realistic look at what kills schedules and ultimately projects. Any development manager would be hard pressed to not nod their head in agreement or snicker at some of the horror stories used as examples. The book's examination of Risk Management through fully understanding how projects go bad is a must read. I know that I've made chapters 1 through 4 must reads for my project managers.
Rating:
Summary: THE MYTHICAL MAN-MONTH
Review: 200
Rating:
Summary: Excellent !!
Review: One of the best books I have read on Software engineering. The best part is that it is eminently readable and doesnot feel like you are reading a technical tome. I wish I had this book many years back, when I started out on career. Should be on the desk of every Project Manager, Team lead and even an startup programmer.
Rating:
Summary: Excellent book !
Review: Great man, great book. Very much fun to read. No need to say more. Every single person developing software *MUST* read it.
Rating:
Summary: Open at any page and you'll say 'Ain't it the Truth'
Review: There are not many books that you can open at any page, at any time, and say 'Ain't it the Truth'. This is a pragmatic and practical bible about the problems, pitfalls and 'classic mistakes' of project management, coupled with recommendations and 'best practices' for every style of project. I have used this book as a University textbook, and every mature aged student with development experience made the same comments; basically 'Ain't it the Truth'. One said 'When I read the chapter on 'classic mistakes' I cringed; How many of those classic mistakes have I made?'. Why did I adopt this as a textbook? Because a project manager said 'Look at this book. We have 6 copies in our office, and everyone reads it'. What better recommendation for a text book for learning programmers and analysts.
Rating:
Summary: A page turner that can change your life!!!
Review: 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?
Rating:
Summary: Required reading for anyone in the computer industry
Review: I wish I had known about this book 3 years ago when I started my first software job. Full of important software engineering concepts, presented in a clear and humorous manner. I got (and read it) a month ago, and it made a major positive impact in getting the crises at work under control. It's full of references to research, books and papers that I now use as ammunition to push for better software engineering standards in my company.
Rating:
Summary: a must for every future software engg
Review: a must for every future software engineer
Rating:
Summary: Essential reading for programmers and their managers
Review: 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.
| 
