A fundamental software engineering project management guide based on the practical requirements of 'Taming Wild Software Schedules'. Emphasizes possible, realistic and 'best practice' approaches for managers, technical leads and self-managed teams.

Statistical Techniques Statistical Mechanics. Avs All Products Cracker.

The author emphasizes efficient development concepts with an examination of rapid development strategies and a study of classi A fundamental software engineering project management guide based on the practical requirements of 'Taming Wild Software Schedules'. Emphasizes possible, realistic and 'best practice' approaches for managers, technical leads and self-managed teams. The author emphasizes efficient development concepts with an examination of rapid development strategies and a study of classic mistakes, within the context of software-development fundamentals and risk management. Dissects the core issues of rapid development, lifecycle planning, estimation and scheduling. Contains very good and practical discussions of customer-oriented development, motivation and teamwork.

Explains such fundamental requirements as team structure, feature-set control (the dreaded feature creep in every project), availability and use of productivity tools and project recovery options. Relevant case studies are analyzed and discussed within the context of specific software development problems. Over 200 pages in this publication are devoted to a summary of best practices, everything from the daily build and smoke test, through prototyping, model selection, measurement, reuse, and the top-10 risks list. This publication is definitely recommended and will become a classic in the field, just as the author's prior publication, 'Code Complete' already is.

How can I add any value to the multitude of reviews that obviously say 'You must buy this'? When I was working 80 hours a week - this was the only book I read cover-to-cover. When I lent my book to one of my staff and he left the firm, I bought another copy off the shelf within 24 hours (I couldn't wait for Amazon's delivery time). This was after having read the book twice.

This is the only book I have bought 3 copies: one for work, one for home, and one to share. It's the only book which caused me How can I add any value to the multitude of reviews that obviously say 'You must buy this'? When I was working 80 hours a week - this was the only book I read cover-to-cover. When I lent my book to one of my staff and he left the firm, I bought another copy off the shelf within 24 hours (I couldn't wait for Amazon's delivery time). This was after having read the book twice. This is the only book I have bought 3 copies: one for work, one for home, and one to share. It's the only book which caused me to specifically make a trip to the bookstore to get a signature and hear a writer speak.

This is the 2nd of McConnell's books I've read. Code Complete was great. I couldn't believe anything could be better but this book is it. It repeated a few facts and figures but it's worthwhile to have it reorganized and re-presented for a different view. This book has led me to be a confirmed McConnell reader. His other books are good, but this is his best. Unfortunately, my expectation is so high now that his subsequent books are not impressing me as much.

Because of this book, I will attend my second course from his company - even if it means flying into Seattle's rain. One book and he's hooked me for literally a thousand dollars - that's an effective writer! I think this book is really showing it's age. McConnell's advice feels genuine, but the data is based on experiences from the early 90s. A lot has happened in the software world between then and now so there are many things that don't fit with some of the best practices that modern development embraces. Unless you're staying on top of how companies do development today, it's hard to filter out what is outdated advice versus what is still relevant.

Therefore, in spite of the book having some good I think this book is really showing it's age. McConnell's advice feels genuine, but the data is based on experiences from the early 90s. A lot has happened in the software world between then and now so there are many things that don't fit with some of the best practices that modern development embraces. Unless you're staying on top of how companies do development today, it's hard to filter out what is outdated advice versus what is still relevant. Therefore, in spite of the book having some good information, I can't recommend it strongly because uninformed readers might be lead astray by practices that have proven themselves to be fads (I'm looking at you, JAD) or are just mediocre advice.