Javascript Menu by Deluxe-Menu.com

Adminpal

Software Project Survival Guide (Pro -- Best Practices)

Adminpal
Search Advanced SearchView Cart   Checkout   
 Location:  Home » Software » Microsoft » Software Project Survival Guide (Pro -- Best Practices)November 18, 2008  
Departments
Computers
Software
Electronics
Cell Phones
Cameras
Music
Games
GPS
TVs and HDTVs
Subcategories
Paperback
Mass Market
Trade
Software Project Survival Guide (Pro -- Best Practices)
Software Project Survival Guide (Pro -- Best Practices)

 enlarge 
Author: Steve Mcconnell
Publisher: Microsoft Press
Category: Book

List Price: $24.99
Buy Used: $0.40
You Save: $24.59 (98%)



New (50) Used (76) from $0.40

Avg. Customer Rating: 4.5 out of 5 stars 63 reviews
Sales Rank: 63366

Platform: No Operating System
Media: Paperback
Edition: 1
Number Of Items: 1
Pages: 304
Shipping Weight (lbs): 1.3
Dimensions (in): 9.1 x 7.3 x 0.9

MPN: 1-57231-621-7
ISBN: 1572316217
Dewey Decimal Number: 005.10684
UPC: 790145162175
EAN: 9781572316218
ASIN: 1572316217

Publication Date: November 14, 1997
Availability: Usually ships in 1-2 business days

Customer Reviews:
Showing reviews 6-10 of 63
 « PREV  
1 2 3 4 5 6 7
... 13   NEXT »

3 out of 5 stars I liked the book, but if you don't know 90% of this stuff already, you aren't in software.   May 12, 2007
 3 out of 8 found this review helpful

There's a caliber of people called "project managers" that haven't taken more than a semester's worth of computer programming and software engineering, that this book is the most valuable for. If you're becoming a project manager as a computer science graduate or basement-life coder, for the first time on a project, then this book is also for you. It's good to have this information written out somewhere to see that it's not just one guy being a weenie when he suggests having a process and a revision control system-there is a science to software engineering.

However, through some experience that most everyone gets as a 'grunt', this is 90% of what people already know as common sense in 2007. Get a version control system for everyone. Come-up with a realistic deadline. Build-and-test so your customer can see the results, correcting you as you go.

I liked the book, it read easy-enough, it just wasn't the sage advice about things I didn't know that I didn't know, that I was hoping it would be. It did deal with things like having 4 different "bosses/customers" and the need to basically contract-out who dictates what features-unfortunately that was less than 10% of the book.



5 out of 5 stars McConnell's high level approach to Project Management remains valuable even today. Be sure to read his more recent texts   May 1, 2006
 8 out of 10 found this review helpful

The Software Project Survival Guide by Steve McConnell remains applicable today as when first published in 1995. McConnell has a clear knack for combining research, experience, and theory. His writing style is clear, concise, and easy to understand.

McConnell approaches the topic of project management (design through to delivery) from a high abstract level; he outlines the best practices, provides comprehensive checklists, but leaves the fine details to other authors. McConnell States, "Whereas this book provides a big picture technical framework for a project, [Fergus] O'Connell's book focuses on the many specific activities a project manager must perform." (Part IV)

McConnell's writing style maintains a high sense of integrity and he always encourages personal research and development through his extensive use of external references.

Selected quotes:
"Software development is inherently an exercise in climbing steep learning curves - an exercise in problem solving - and the learning curves don't disappear" (Chapter 17)

"No individual is a success who hurts the team, and no individual is a failure who helps it." (Chapter 18)

This is an excellent book, a great reference; although a little too heavy to be comparable to the "first aid kit you carry in your backpack" (Chapter 20).

The "Cone of Uncertainty" (chapter 3) and the "Survival Needs" section (chapter 1) were quite interesting. In the "Survival Needs" section McConnell draws many parallels with the basic human needs and the basic needs for a successful project. Similarly intriguing is his Project Team's Bill of Rights (chapter 1).

Be sure to visit the book's website it provides the chapter checklists in digital form and many other useful resources.

There is no one-size-fits-all or simple solution - this book is not an exception. Continue reading other project management books and some of McConnell's more recent texts like Software Estimation Demystifying the Black Art.



5 out of 5 stars Software leads need this book   March 14, 2006
 6 out of 8 found this review helpful

Software Project Survival Guide is one of the best books I've ever read about leading a software project. The author is not trying to sell any specific process or methedology, instead the book is full of down-to-earth practical advice about software development. If you are a software lead, new or old timer, read this book. If you are a software manager, buy a copy of this book for every one of your leads.


4 out of 5 stars Common sense approach for all projects   October 5, 2005
 5 out of 5 found this review helpful

Most of us have been involved with software projects that we would just as soon forget--or at least run away from screaming. If you want to learn how software projects should be run, or how to run one correctly yourself, then Steve McConnell presents a straightforward, common-sense approach that can be applied to all types of projects. The companion web site provides a complete collection of templates to support all aspects of managing a software project.


5 out of 5 stars Open your managers eyes.   September 13, 2005
 9 out of 11 found this review helpful

I bought this book because I wanted to open my managers eyes.

You see, I work for a brand new software development company. I work under managers with no coding experience, so their methodology is "code now, fix later. Plan... well, don't plan". The lead developer and myself were about to go insane, and then we found this little gem.

This book is an eye-opener, especially for managers, project leads and others involved in the software development process (even developers). This book provides proven concepts backed with solid information. This book provides check-lists so you can see where your project is heading, also there are tons of graphs that will illustrate important concepts visually. I casually passed this book along to my managers and the next thing I know big changes were happening... for the better. We are now able to make plans before developing, and now the tension at my work has gone down quite a bit. We are now planning for changes instead of waiting for them.

If you are in my shoes and are in need of a primer to prove to your managers that your project is heading in the wrong direction then I would pick this book up right now. This book provides factual information about how the software development process should work (and how it can break if not planned correctly) Steve McConnell is an icon in the software industry, listen to him.


Copyright © 2006 Adminpal LLC