Dynamics of Software Development (Paperback)

by Jim McCarthy (Author) "Shipping great software on time, the subject of this book, is a simple enterprise-at least at the conceptual level..." (more)
Key Phrases: Slip Processed, Jeff Harbers, Product Management

Editorial Reviews

Product Description
Here is the candid collected wisdom of Jim McCarthy, a software industry veteran and the director of the Microsoft Visual C++ development group. In McCarthy's words, "More people have ascended bodily into heaven than have shipped great software on time"; but shipping great software on time can be done, he insists, and this book tells how. DYNAMICS OF SOFTWARE DEVELOPMENT is divided into five sections that chart the progress from initial design to successful product. Throughout, McCarthy expresses his sometimes-controversial judgments in witty, memorable maxims, one of which has become the title of the book. Destined to be a cult classic, DYNAMICS OF SOFTWARE DEVELOPMENT will get a lot of attention in the industry and cause a favorable stir in the press.

Product Details

• Paperback: 184 pages
• Publisher: Microsoft Press (August 1, 1995)
• Language: English
• ISBN-10: 1556158238
• ISBN-13: 978-1556158230
• Product Dimensions: 9.1 x 7.3 x 0.6 inches
• Shipping Weight: 5.6 ounces
• Average Customer Review: 4.3 out of 5 stars See all reviews (34 customer reviews)
• Amazon.com Sales Rank: #277,832 in Books (See Bestsellers in Books)

Customer Reviews

Most Helpful Customer Reviews

17 of 17 people found the following review helpful:

5.0 out of 5 stars Great for solving so-called high-tech labor shortage, January 15, 1999

By A Customer

You hear a lot today that talent is so scarce, esp. in the field of programming. Well, that's one of the biggest lies of our times. I've found Jim McCarthy's book extremely helpful in finding valuable characteristics programmers have. Programming is a lot more than just writing code and this book will help you see that. It'll encourage you to find out the other parts of software development and how people who may not know the latest buzzwords are nevertheless far more capable than the industry tends to give them credit.

It'll definitely cause you to question your processes of software development (do you have any where you work?), esp. if you believe that your way is the only way. Programming is much more about problem solving, so will you be versatile enough to welcome the many ways that many gifted individuals are able to design and create software, even when it's not what you originally had in mind?

I've found the Appendix extremely helpful. I love the part where Jim explains that the biggest mistake hiring managers make is their present obsession with buzzwords of the day, buzzwords which 2 to 4 years later become obsolete. Instead, what's really needed is to understand how a programmer uses technology to solve the problems at hand. The way programmers are evaluated during job interviews are in many places so inaccurate as this book points out, and you'll also get some ideas as to how to rectify this.

Probably the only people I have found who are not turned on by this book are those who say that software development and computers in general have no place for "touchy-feely" aspects like motivation and job satisfaction. But for those who want to find more of a human connection with the programming they do, I highly recommend it. That especially goes for managers in high-tech who usually get promoted because of their technical abilities alone. These same managers get no training in management, esp. in the handling of people skills. This book is indeed a great investment to begin learning some of these vital skills, esp. when so many say they got into high-tech professions like Information Technology because such occupations don't have to deal with hot human issues like egos and office politics. Guess again!

Lastly, my other favorite part within the book is the comparison of a well-run software organization with that of an awesome jazz band. Jazz lets individuals solo and improvise while the accompanying team provides an invigorating backdrop. And individuals each get a chance to solo, supported by team members' respect and admiration. I've experienced tremendous highs playing in both great jazz ensembles and software teams. Now you can too!

10 of 10 people found the following review helpful:

5.0 out of 5 stars Common Sense That Is Not So Common, September 3, 2003

By	P. Heath (Hurst, TX United States) - See all my reviews (TOP 500 REVIEWER)    (REAL NAME)

This book delivers great insight into what goes on in software development. Although presented in the context of work performed on Microsoft Visual C++ 1.0, the author does a good job of generalizing specific experience. McCarthy gives us an honest look into the ups and downs without sugar coating or promising silver bullets.

Presented in a format similar to Meyers' "Effective C++" books, the text flows very well and is a pleasure to read. When you read many of the pitfals presented, you may think "Duh!". However, these are things that I see happen regularly. Here are some of the highlights.

Rule #2 "Get Their Heads Into The Game". This sounds like a very simple rule. Everyone on the team needs to be contributing ideas toward creating intellectual property. However, most people know this is easier said than done. McCarthy goes on to explain the barriers to the flow of ideas.

Rule #4 "Don't Flip The Bozo Bit". This rule is necessary to keep #2 working. The author deals with the natural tendency that people have to become defensive when criticism is offered of their ideas. This can actually cause both the critic and the one being criticized to tune each other out. The author suggests that team members call each other on it when the Bozo Bit is being flipped.

Rule #25 "Don't Accept Dictation". This topic is addressed in many other texts, but that fact should tell us that we aren't getting it. McCarthy reminds us that it is foolish to accept dictation of scheudle, features, and resources. The "Holy Triangle" has to be balanced and tradeoffs are required when changing any one of these three. Managers are encouraged to be strong and take a stand when they find themselves in this situation. Eight years after this book was published, I still see this very thing happening. Until something changes, we will continue to see this issue addressed in software management texts.

Rule #31 "Beware Of A Guy In A Room". Software development is a collaborative effort. Don't let people isolate themselves. There is no opportunity for feedback or help when problems arise, and this can derail the project.

The appendix on "Hiring And Keeping Good People" is also very helpful. If you are like most managers, you didn't get to hire most of the people that work for you. Here you will find practical advice for letting your superstars reach their potential and getting something out of everyone.

8 of 8 people found the following review helpful:

5.0 out of 5 stars Astounding!, April 7, 2000

By	Charles Ferebee (Nashua, NH) - See all my reviews

Someone truly understands this crazy world of software development. I could not be more impressed with a book - and guess what, it is language _and_ system independent. Not only this, it is for developers, engineers, QA engineers, technical writers and managers alike.

This book provides such keen insight into the problems and complexities of full life cycle development and support, project management and system architectural initiatives that you would think McCarthy was sitting in on every design and architecture meeting you have ever attended -scary!

I have never been so impressed with a single technical book in my career, and it does not even require a computer - only a desire to get along with each other, raise our intellect a few notches, and develop solutions on time. Not only this, it is 5 years old, which in techy years, makes it timeless.

I applaud!