- Paperback: 225 pages
- Publisher: Microsoft Press,U.S. (1 Sep 1994)
- Language English
- ISBN-10: 1556156502
- ISBN-13: 978-1556156502
- Product Dimensions: 23.1 x 18.5 x 1.8 cm
- Average Customer Review: 4.3 out of 5 stars See all reviews (15 customer reviews)
-
Amazon Bestsellers Rank:
237,272 in Books (See Top 100 in Books)
- #4 in Books > Computers & Internet > Computer Science > Programming > Languages & Tools > Tools
- See Complete Table of Contents
| ||||||||||||
Did you know you can trade in your old books for an Amazon.co.uk Gift Card to spend on the things you want? Visit the Amazon.co.uk Trade-In Store for more details. |
Product details |
More About the Author
Product Description
Synopsis
The author explains how he organized and supervised effective software development teams at the Microsoft company to come up with timely and high-quality commercial applications, offering a candid look at the group dynamics of software development. Original. (Advanced).
Inside This Book
(Learn More)
First Sentence
Have you ever stopped to consider what makes one project lead or programmer more effective than another? Read the first page
Front Cover | Copyright | Table of Contents | Excerpt | Back Cover
Have you ever stopped to consider what makes one project lead or programmer more effective than another? Read the first page
Explore More
Concordance
Browse Sample PagesConcordance
Front Cover | Copyright | Table of Contents | Excerpt | Back Cover
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organise and find favourite items. |
Sell a Digital Version of This Book in the Kindle Store
If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store.
Learn more
Customer Reviews
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
4 of 4 people found the following review helpful:
5.0 out of 5 stars
An enjoyable "How I Won the War" story,
By A Customer
This review is from: Debugging the Development Process (Paperback)
The author's style is wonderful- much more personal than most texts dealing with management, while still managing to be more than a collection of 'cute' anecdotes. This book will provide the greatest benefit to professionals, such as myself, who have had a few years experience in software development processes and are looking for that 'next level' of guidance. In that respect, Steve Maguire's writing is effective because he presents knowledge to the reader as if from a mentor to an apprentice.I would, however, contrast it with another work which I believe to be equally important though radically different- "The Mythical Man Month". Where Maguire writes as a seasoned guru with an arm around your shoulder, Brooks writes like an evangelist and discusses software development on an almost religous plane. "The Mythical Man Month" also approaches the subject in a broader, more philosophical sense. In the end, I feel that I've gotten more out of each of these books having read the other. While contrasting in terms of eras (mainframe vs pc) and environments (short-sleeve button-down IBM vs hacky-sack Microsoft), it's interesting to note how many conclusions are shared between these works. Bottom-line: read this book, you'll love it :)
4 of 4 people found the following review helpful:
3.0 out of 5 stars
A great and terrible book.,
By A Customer
This review is from: Debugging the Development Process (Paperback)
There is enough good advice in any one chapter to improve your next software project (or your life.) Unfortunately, critical principles are explained through highly specific examples. If you are already an experienced project manager or mentor then the book will read like common (if rare) sense. If you are not an experienced project manager or mentor this book will not teach you how to become one. Try Steve McConnell's Rapid Development instead.A real danger of this book is that the examples can be taken to mean exactly the opposite of what the author intends. For example, it would be easy to read the author's objection to *needless* process work as an objection to process work of all kinds.
2 of 2 people found the following review helpful:
3.0 out of 5 stars
A great and terrible book.,
By A Customer
This review is from: Debugging the Development Process (Paperback)
There is more than enough good advice in any one chapter to make your project (or your life) dramatically better. The problem is that the book discusses important principles through highly specific examples. It is all too easy for people to misread specific examples and come to exactly the wrong conclusion. For example, Maquire is against needless process work (what developer isn't?) He's also working at the largest software organization in the world. In the smaller organizations I've worked with there is a crying need for more process work, not less. Reading Maquire it would be easy for someone to find "evidence" that they should spend less time on design work and planning! This isn't Maquire's point, but he's not there to straighten the reader out. If you are an experienced project manager and mentor you'll resonate with a lot of what Maquire says. If you aren't that experienced this book won't teach you how to be a great project manager. Get Steve McConnell's vastly superior "Rapid Development" instead.
Share your thoughts with other customers: Create your own review
Would you like to see more reviews about this item?
|
Most Recent Customer Reviews |
Listmania!
Look for similar items by category
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
