×

Uh-oh, it looks like your Internet Explorer is out of date.

For a better shopping experience, please upgrade now.

Debugging the Development Process
     

Debugging the Development Process

5.0 1
by Steve Maguire
 

In Debugging the Development Process, Maguire describes the sometimes controversial but always effective practices that enabled his software teams at Microsoft to develop high-quality software - on schedule. With the refreshing candor reviewers admired in Writing Solid Code, Maguire talks about what did and what didn't work at Microsoft and tells you how to

Overview

In Debugging the Development Process, Maguire describes the sometimes controversial but always effective practices that enabled his software teams at Microsoft to develop high-quality software - on schedule. With the refreshing candor reviewers admired in Writing Solid Code, Maguire talks about what did and what didn't work at Microsoft and tells you how to energize software teams to work effectively - and to enjoy their work; why you might want to kick your star programmer off your team; how to avoid corporate snares and overblown corporate processes; which tiny changes produce major results; how to deliver on schedule and without overwork; how to pull twice the value out of everything you do; how to get your team going on a creative roll; and how to raise the average programmer level at your company.

Product Details

ISBN-13:
9781556156502
Publisher:
Microsoft Press
Publication date:
08/01/1994
Series:
Code Series
Pages:
183
Product dimensions:
7.41(w) x 9.25(h) x 0.69(d)

Customer Reviews

Average Review:

Post to your social network

     

Most Helpful Customer Reviews

See all customer reviews

Debugging the Development Process 5 out of 5 based on 0 ratings. 1 reviews.
Guest More than 1 year ago
This book is an absolute must-read for development leads and program managers. The approaches to managing and executing a development effort presented are clear and concise. Additionally, the information can be very easily translated to ANY project, whether its development-, infrastructure-, or non-IT-related. The book is very well-organized and is an easy read. One could finish it in an evening, but spending time to reflect on the content is a must. I found myself taking notes on each of his major recommendations, finding them so useful and plentiful that I wanted to make sure I can eventually implement every one of them. If you're a new program manager or development lead, this is an excellent way to get acquainted with the dynamics of your new role. I'd also suggest you have your test leads and senior programmers read it, too.