Home :: Books :: Computers & Internet  

Arts & Photography
Audio CDs
Audiocassettes
Biographies & Memoirs
Business & Investing
Children's Books
Christianity
Comics & Graphic Novels
Computers & Internet

Cooking, Food & Wine
Entertainment
Gay & Lesbian
Health, Mind & Body
History
Home & Garden
Horror
Literature & Fiction
Mystery & Thrillers
Nonfiction
Outdoors & Nature
Parenting & Families
Professional & Technical
Reference
Religion & Spirituality
Romance
Science
Science Fiction & Fantasy
Sports
Teens
Travel
Women's Fiction
77 Sure-Fire Ways to Kill a Software Project: Destructive Tactics That Cause Budget Overruns, Late Deliveries, and Massive Personnel Turnover

77 Sure-Fire Ways to Kill a Software Project: Destructive Tactics That Cause Budget Overruns, Late Deliveries, and Massive Personnel Turnover

List Price: $9.95
Your Price: $9.95
Product Info Reviews

<< 1 >>

Rating: 5 stars
Summary: Great little book!
Review: As a project management trainer, I often work with IT folks who are struggling with too many projects and not enough time to complete them. Typically IT people don't take the time to reflect and document management practices that drive them crazy and kill their projects. Instead, they just leave the company! In this rare book, two veteran soft developers irreverently vent their frustrations and provide plenty of insight for anyone wanting to better manage software development teams. While they provide a bunch of items related to technical and programming management issues, the also share some management-related sure-fire ways to kill a software project. Some hightlights from their list of items include: #13 -- Begin design while requirements are fluid. #18 -- Make developers fight for every purchase. #28 -- Concentrate on cosmetics, not functionality at inspections. #33 -- Forgo prototyping. #41 -- Give everyone beepers [... so they can be reached even in the middle of the night about cosmetic problems.] #47 -- Schedule as many meetings as possible. #58 -- Jump on the process improvement bandwagon. #59 -- Create lots of TQM groups. #60 -- Hire a TQM expert from outside the company. #68 -- Require overtime work without compensation. #70 -- Hire temp programmers [and pay them for all hours, even overtime, at a rate higher than staff] #73 -- Give humiliating performance reviews. #74 -- Get rid of developers over 40 [years old]. #75 -- Refer to people as "units."

This book is clean, crisp, and fun to read... and might well generate some valuable discussions in your organization that could improve the effectiveness of your projects!...

Rating: 4 stars
Summary: Funny book, but a little narrow.
Review: The book is quite funny, but displays the author's bias for government work. As a development manager/implementor, I have seen some of these 77 sins, but others are rather esoteric and limited to the author's domain. Purchase it for a laugh, to educate the ignorant, or to know you are not alone.

Rating: 4 stars
Summary: Funny book, but a little narrow.
Review: The book is quite funny, but displays the author's bias for government work. As a development manager/implementor, I have seen some of these 77 sins, but others are rather esoteric and limited to the author's domain. Purchase it for a laugh, to educate the ignorant, or to know you are not alone.


<< 1 >>

© 2004, ReviewFocus or its affiliates