Hide this

Results from Google Books

Click on a thumbnail to go to Google Books.

Software Project Survival Guide (Pro -- Best Practices) by Steve McConnell
Loading...

Software Project Survival Guide (Pro -- Best Practices)

by Steve McConnell

MembersReviewsPopularityAverage ratingConversations
341None15,259 (3.99)None
Recently added byprivate library, suzannejb, scitlec, BaykaJIak, HeroicLife, winis, JimPratt, punkfairy
Loading...
won't like will probably not like will probably like will like will love

Sign up for LibraryThing to find out whether you'll like this book.

No reviews
no reviews | add a review
You must log in to edit Common Knowledge data.
For more help see the Common Knowledge help page.
Series (with order)
Canonical Title
Original publication date
People/Characters
Important places
Important events
Awards and honors
Epigraph
Dedication
First words
Quotations
Last words
Disambiguation notice
Publisher's editors
Blurbers
Book description

Amazon.com (ISBN 0735605971, Paperback)

This three-book set includes Steve Maguire's Debugging the Development Process, Jim McCarthy's Dynamics of Software Development, and Steve McConnell's Software Project Survival Guide. Together, these books convey the field knowledge of three experienced development-team leaders. Anyone planning to participate in a software project, particularly as a manager, should read these books.

Debugging the Development Process shows how Microsoft goes about creating, writing, testing, and improving products. Maguire always keeps one eye on the product's purpose--as well as the purpose of the company--as he offers valuable advice on how to design and build software products that are efficient in terms of time and money. The book is full of design philosophy, including entertaining passages on conflicts between marketing people and developers. (The LAYOFF parable, the highly ominous Excel macro that almost was, is amusing).

Dynamics of Software Development explores the crazy mix of creativity, intelligence, technical skill, and general humanity that makes up a software development team. Such groups require special handling in order for them to yield good products. McCarthy offers a bromide-rich explanation of techniques he's used (again, at Microsoft) to hire bright people, motivate them, stave off burnout, and still get the product out the door on time. His advice is sound and should prove invaluable--even if your development team consists of one person.

Because software development is inherently complex and developers often must attempt to satisfy shifting goals, even successful, well-managed software projects have a death-march aspect to them. Software Project Survival Guide explains what you can do to make building software enjoyable and rewarding, not just survivable. McConnell goes heavy on hints, tips, and checklists of things you can implement now to create a better development team. --David Wall

(retrieved from Amazon Fri, 24 Apr 2009 07:58:24 -0400)

The first test round has been closed. Visit the Open Shelves Classification group for details.

Popular covers

 

Help/FAQs | About | Privacy/Terms | Blog | Contact | LibraryThing.com | APIs | WikiThing | Common Knowledge | 45,591,607 books!