A Survival Guide to Computer Contracts: How to Select & Negotiate for Business Computer Systems

Rating:
Summary: An Excellent Primer on Computer Contracts
Review: A Survival Guide to Computer Contracts turned out to be just that for me! I'm an experienced attorney--but have little experience in this niche. The book was a great help. To the Author: Can't wait 'till the Second Edition! Hope you cover Internet deals!

Rating:
Summary: Great Book that was very informative.
Review: I sit on the board of a major company and after reading this book was able to talk to the people at my company with much knowledge about this subject. It makes a lot of sense, saves money and time, and most of all headaches. Kudos to the author.

Rating:
Summary: Great Book that was very informative.
Review: I sit on the board of a major company and after reading this book was able to talk to the people at my company with much knowledge about this subject. It makes a lot of sense, saves money and time, and most of all headaches. Kudos to the author.

Rating:
Summary: Nothing much new if you're in the IT business
Review: This book is written by a lawyer who has obviously had extensive experience in dealing with, and ratifying, IT contracts. However, it has a number of shortcomings which make the book somewhat inadequate unless you're a novice:

1) The text focuses primarily on License Agreements for software acquisitions (custom and packaged software). There is little here regarding third-party Systems Integrators (e.g. Big Five) and how to structure and negotiate a Systems Integration services contract - for instance, how do you structure contracts where a third party Systems Integrator is contracted to implement another party's software package on yet another vendor's hardware platform ? If things go wrong, how do you determine who is at fault, and who's liable to remedy the fault ?

2) There is extensive advice, including sample text, on the "legal" verbiage to be employed; however, not so much focus on how critical it is to determine whether the technical solution is sound, and strategies to go about assessing that - as I often say, you can draft an iron-clad contract to receive a three-wheeled car, but you still have only a three-wheel car, unless you ensure you've got the scope covered.