Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Follow the authors
OK
Debugging the Development Process : Practical Strategies for Staying Focused, Hitting Ship Dates, and Building Solid Teams Paperback – Bargain Price, July 31, 1994
- Print length183 pages
- LanguageEnglish
- PublisherMicrosoft Press
- Publication dateJuly 31, 1994
Editorial Reviews
From the Back Cover
Product details
- ASIN : B00005R08G
- Publisher : Microsoft Press (July 31, 1994)
- Language : English
- Paperback : 183 pages
- Item Weight : 1.2 pounds
- Customer Reviews:
About the authors

Discover more of the author’s books, see similar authors, read author blogs and more

Discover more of the author’s books, see similar authors, read author blogs and more
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on Amazon-
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
Great ideas on how to lead software development teams. Lots of practical advice from someone who has been leading teams at Microsoft for years.
I find the ideas useful, refreshing, and focused on making the best of your software developer resources. So much of what we end up doing in todays corporate world takes away valuable time and creates an less than idea environment for productive work.
If you're buried in the development process at you're company this is a _must_ read to inspire you to take a look at you're teams, how to motivate them, and keep them focused on developing and improving the product.
The book mainly explains the obvious (although too often ignored) practices that helps your development project: stay focused, avoid distractions, avoid interruptions, avoid wasting time, avoid unnecessary meetings (meetings are interruptions and far too often a waste of time), fix bugs early. The book has some stories to explain the above practices. But, the book has no hard facts to help you fight for the above practices in case you have a "pointy haired" boss.
In my opinion "Rapid Development" by Steve McConnel is a far better book. "Rapid development" has all the hard facts that "Debugging the development process" lacks. "Rapid development" also describes more practices and has a broader view of the development project that "Debugging the development process".
Maguire gives some simple, practicle advice for improving the development environment that a manager is responsible for. For example, he recommends starting each day by asking, "What can I do today that will help keep the project on track for the next few months?"
I also found the section on feedback loops to be interesting. The suggestion that you have a person stop feature work to fix a bug that they created as soon as it is found is a way to emphasize quality and make it in the best interest of developers to produce high quality code.
The chapter on attitudes is also very good. Much of the time, there isn't a lot knowledge wise that separtes good and bad developers. The difference comes in attitude. Attitudes such as, "We can't do that!", "The users won't care!", "Bugs are going to happen!" need to be rooted out.
This book gives good insight as to what you as a manager can do and help your developers do in order to have smoother projects that are high quality and on time.
Chapter 1 talks about "laying the groundwork" -- priorities work, establish goals, coding priorites. How true this is ... how often have we started development when we are unsure of what the management wants to achieve out of it.
Some of the other strategies include having 40 hour week(hmm ... reminds me of Extreme Programming) and about the danger of having working 12 hours per day. He also spoke about ensuring personal growth in dividuals, and how it directly helps the company.
This book is written in simple english, straight to the point. To everyone doing software development, this is a must-read!!!
Anyone who needs to manage programmers, or is dependent on programmers should read this book. It is also a good read for anyone looking to help improve the overall productivity of "information workers." Simple things like how and why you schedule your meetings make a big impact.
Top reviews from other countries
It's probably way out of date in terms of technology these days. But if you can read past that, read into it the general ideas and approaches, there is a wealthy of experience.