|
|
Software Project Survival Guide (Pro -- Best Practices)
|
List Price:
$24.99
Global Home Business Price:
$16.49
Your Savings: $ 8.50 ( 34% )
Subject To Change Without Notice
Availability: Usually ships in 24 hours
Manufacturer: Microsoft Press
|
Average Customer Rating:  
|
|
Binding: Paperback
Dewey Decimal Number: 005.10684
EAN: 9781572316218
ISBN: 1572316217
Label: Microsoft Press
Manufacturer: Microsoft Press
Number Of Items: 1
Number Of Pages: 304
Platform: No Operating System
Publication Date: 1997-11-14
Publisher: Microsoft Press
Studio: Microsoft Press
|
|
|
|
|
|
Editorial Reviews:
|
The author of the classics "Code Complete" and "Rapid Development" throws a lifeline to the industry's huge and indispensable population of rookie managers and technical leads. This book is a roadmap to how an effective software project works--understandable even for those with limited project experience.
|
|
|
Spotlight customer reviews:
|
Customer Rating: 
Summary: I've read this book a long time ago, but the remembering is good
Comment: I've read this book several years ago, in 1998, I think. It was my first glimpse on software project planning. At the time, I was a bit confusing, the book has a lot of examples of very big projects. But the best practices it provides are useful until today.
Don't know if it's a good book nowadays, but it's definitely a book I won't forget.
Customer Rating:
Summary: A must for project leaders
Comment: The book presents an analysis about the project management in a very practical way.
In it, Steve demystifies that in a project the "well" and "fast" are in opposite sides. By contrast, him tells us that for do it fast and cheap, it is essential to do it well.
A project leader should have it in his desk.
Customer Rating:
Summary: well-researched
Comment: I'm a one-man database development shop at a nonprofit with a shoestring budget. Without the benefit of senior level programmers, I've had to learn most of my software engineering lessons the hard way- by experience.
I picked up this book seven years into the job, which in retrospect was about seven years too late. In some respects, this book repeats lessons that that have already become obvious through experience (e.g., software testing needs to be performed separately from development). But, this lends credibility to my judgment, and provides new insights substantiated by software engineering research studies. Non-technical management and funders are responsive to the hard figures I often find myself citing from this book. For example:
1) Programmers are 2.5 times more productive in a quiet office vs. a cubicle- so, I need to be allowed to work from home
2) The most efficient programmers are 10 times more productive than the least efficient programmers- really, you would think this would be obvious, but when work needs to be contracted, the low bidder is not necessarily the best choice over the long haul
Currently faced with my most substantial and challenging programming project yet, I'm essentially using this book as a cookbook to process. Upfront I was a bit overwhelmed with the scope of the project. Having finished the book, I have a well-defined process in place, am confident this will get done, and feel I am much more articulate describing the stages of software development to management and contracted vendors. Some presumably industry-standard strategies are proving invaluable- implementing a Top Ten Risk list to ensure that major barriers are addressed upfront rather than deferred, creating specific milestones, etc.
This book (or an equivalent) should absolutely be mandatory for anyone about to take on their first major software project. It is most useful because it reads like a cookbook- guiding you through all the phases of software development, one after the other.
Customer Rating:
Summary: The presented methodology is good but...
Comment: will the book be convincing enough for you to adopt it?
I have not found this book very fun to read because of its very structured and academic format. I have not learned much from it as much of its content is general wisdom that anyone with many years of experience in the industry has probably seen around before. Something positive I can say about the book is that I totally adhere to the methodology explained in the book. In my software development career, I have experienced myself the benefits of applying similar software development management methodology and I have also seen the negative consequences of not following it.
Customer Rating:
Summary: Purpose: Project management templates
Comment: The biggest part of managing a large project with deliverables is knowing the timing and details of your deliverables to make sure that all pieces are in place and planned for...time and resource wise. This book is a huge help in providing those pieces. Whether you use all the pieces or not it gives you the details you need to think through before you incorporate a deliverable and help you weigh how much detail and effort needs to be a part of it.
|
|
|
|
|
|
|
|
