Computerworld
Quick Menu
Search



Ads by TechWords

See your link here


Subscribe to our e-mail newsletters
For more info on a specific newsletter, click the title. Details will be displayed in a new window.
Networking
Computerworld Daily News (First Look and Wrap-Up)
Computerworld Blogs Newsletter
The Weekly Top 10
More E-Mail Newsletters 
Computerworld 2007Subscribe to Computerworld
40 years of the most authoritative source of news and information for IT leaders.

Keep Lawyers in Loop

August 13, 2001 (Computerworld) A large majority of IT development projects end up as failures, in terms of missed deadlines, blown budgets and dissatisfied users. And while many of the IT projects carried out by external vendors do have the contractual equivalent of a prenuptial agreement that covers how the two sides would "divorce," neither party ever seems prepared for the messy legal aftermath of a failed project. When I tell project managers that litigation costs in large IT organizations will likely exceed the cost of coding, they're shocked. And well they should be, for while they have often devoted great care and attention to coding (along with all the other technical activities associated with systems development), they tend to ignore the legal issues until a lawsuit is staring them in the face. By that time, it's usually too late to prevent the
consequences of mistakes that occurred throughout the project.
Reasons for this include ignoring or excluding lawyers during the negotiating and contracting stages of an IT project; asking them to draft elaborate provisions for technical issues that they don't understand; or letting them create contracts whose terms and conditions turn out to be unworkable from the beginning and that both parties proceed to ignore without bothering to inform their legal advisers. While there are exceptions to this dismal assessment, the prevailing situation is that the conduct of the project takes place - often over a period of months or years - without any legal review, oversight or guidance. Then, when things blow up at the end, and the vendor and customer angrily blame each other for having caused the problem, it's often an entirely new set of attorneys who are brought in to serve as hired guns to help orchestrate a legal punishment on the other side.
Interestingly, the resulting lawsuits tend to focus on very esoteric, sophisticated technical issues, such as the question of whether the vendor succeeded in delivering a system whose "cyclomatic complexity" (the amount of decision logic in a single software module) exceeded industry norms, even though neither party had ever heard of this metric of software maintainability before the lawsuit was filed (see www.mccabe.com/products/qa_method. htm for more details, if you're curious). And while the lawyers, the jury and the judge are all grappling with the nuances of this technical buzzphrase, the real problem usually turns out to be far more basic: There was no contract at all; there were no tangible, objective acceptance criteria that described when the project could be considered finished; or the contract was emasculated and renegotiated during the course of the project, but without any written record of what was agreed to, and under what circumstances.
Ironically, the only time that most IT organizations decided to pay attention to their lawyers was during preparations for Y2k. As it turned out, there were very few Y2k problems that were serious enough to cause lawsuits. But I know from experience that many IT managers were pleasantly surprised by the pragmatic, common-sense advice they received from their lawyers: "Develop a process for doing your Y2k remediation work," the lawyers said. "Document the process, in case you need to explain it in a lawsuit. Make sure your project teams actually follow the process, and provide an audit trail to demonstrate that they did so."
Bottom line: If



XenServer FREE trial
XenServer FREE trial
Citrix XenServer is the simplest and most effective way to virtualize and provision servers. XenServer combines comprehensive server virtualization capabilities with unparalleled scalability, performance, economics, and ease-of-use. Based on the open source Xen hypervisor, XenServer delivers fast performance, easy management, and advanced features such as live migration.

Request free trial now

Over The Top
Who needs Mrs. Doubtfire? When it comes to spot-on "advice," we've got Aunt Donna.
White Papers
Accelerate your pursuit of perfection
For almost 80 years, Kodak has been helping banks, insurance companies, healthcare providers, government agencies and other businesses produce billions of document images. So Kodak is uniquely positioned to know and deliver–what customers want: easy-to-use scanners that output the best possible image quality.
Download this white paper now! 
Featured Column
Networking Know-HowNetworking Know-How
For tips and best practices on building anything in the network, see Sandra Gittlen's regular column.

Click here to read the latest column by Sandra Gittlen
White Papers
Read up on the latest ideas and technologies from companies that sell hardware, software and services.
A Guide to Understanding Messaging Archiving
Archiving Compliance with Sunbelt Exchange Archiver
The Impact of Messaging and Web Threats
View more whitepapers 
 

Troubleshooting Remote Site Networks - Best Practices
Management and remote site employees expect the same level of network service as the headquarters site. However, when IT staff are faced with limited resources to support remote site networks, often the applications, services and performance at those sites is not as robust as the headquarters site. See how to deliver a high level of network service at remote sites using the best practices outlined in this white paper.

Read whitepaper now
Super-size your LAN with fiber
Fiber optic technology frees the Local Area Network (LAN) from the confines of a single building, allowing a LAN to extend across a campus or a metropolitan area. Read how the selection of fiber optic components affects repeaterless transmission distance and how one school district used fiber to build a more reliable and more cost effective high-speed, district-wide network. Also, read how Metropolitan Area Network (MAN) ownership may require self-assessment of network performance.

Read whitepaper now
Determining the cause of poor application performance
Are users constantly complaining that your network is too slow? Or that they can���t connect or can't stay connected? Are network applications hanging and slowing productivity? Do you spend way too much time trying to isolate the source of the problem and to prove that often the issue isn't the network at all but the application? In this on demand webcast, learn best practices and common root causes of application problems using case studies and live network traffic.

Watch webcast now