Blogs

How to Avoid Doomed IT Projects

02.04.14

Successful IT projects are rarely noticed, only the disasters which can generally be avoided by having detailed contracts that spell out exactly what will happen, and who will do what. Involving a lawyer with IT experience at the earliest point of IT planning (before the RFP is issued) can make sure that all things that can go wrong are spelled out in the contract, so when those things actually go wrong, the parties have already decided what will happen.

If you observe enough IT projects it becomes easier to identify critical signs that an IT project may be doomed. Infoworld’s 2013 report entitled “11 signs your IT project is doomed” is a pretty good outline of what to watch out for:

Red flag No. 1: The project has launched without senior buy-in

Red flag No. 2: No detailed project plan exists

Red flag No. 3: Meetings have been scheduled without concern for team member availability

Red flag No. 4: Users have had little (to no) early involvement

Red flag No. 5: The project targets the minimum specs

Red flag No. 6: Testing is an afterthought

Red flag No. 7: No recovery plan is in place in the event of failure

Red flag No. 8: Expert recommendations have been rebuffed without testing outcomes

Red flag No. 9: The go-live date is a weekend or holiday

Red flag No. 10: Expectations have not been set

Red flag No. 11: Skimp on training

When lawsuits and trials occur because of failed IT projects, no one is ever happy with the outcome. Of course the cost of a failed IT project is always more than a successful IT project.

The publications contained in this site do not constitute legal advice. Legal advice can only be given with knowledge of the client's specific facts. By putting these publications on our website we do not intend to create a lawyer-client relationship with the user. Materials may not reflect the most current legal developments, verdicts or settlements. This information should in no way be taken as an indication of future results.

Search Tips:

You may use the wildcard symbol (*) as a root expander.  A search for "anti*" will find not only "anti", but also "anti-trust", "antique", etc.

Entering two terms together in a search field will behave as though an "OR" is being used.  For example, entering "Antique Motorcars" as a Client Name search will find results with either word in the Client Name.

Operators

AND and OR may be used in a search.  Note: they must be capitalized, e.g., "Project AND Finance." 

The + and - sign operators may be used.  The + sign indicates that the term immediately following is required, while the - sign indicates to omit results that contain that term. E.g., "+real -estate" says results must have "real" but not "estate".

To perform an exact phrase search, surround your search phrase with quotation marks.  For example, "Project Finance".

Searches are not case sensitive.

back to top