The 18 Month Rule: Avoiding the Endless Project

Celent will help qualify your requirements and introduce you to the vendor
Spotted a missing vendor? Use this form to alert a vendor to the Celent service
Create a vendor selection project & run comparison reports
Register to access this feature
Click to express your interest in this report
Indication of coverage against your requirements
Vendor requires PRO subscription to activate this feature
Requires research subscription, contact Celent for more info
9 November 2006

Abstract

New York, NY, USA November 9, 2006

Insurance carriers have invested heavily in project management, but large projects continue to fail. A new approach is required.

In a new report, , Celent provides a guide to address the pitfalls of large IT projects.

The report examines the history of large projects in insurance, including why they have failed so often in the past. Also considered are how insurers define success and failure of a project, often believing a project has succeeded when it has not.

Celent suggests an approach that includes breaking down large projects into a program預 group of related, dependent, and often parallel projects. None of those projects should be greater in length than 18 months.

"To most carriers, any project that gets finished and meets the original specifications is a success," said Chad Hersh, a senior analyst in Celent's Insurance practice and author of the report. "Insurers need to focus not only on completing projects on time and on budget, but on shortening projects so that the resulting systems aren't outdated from the day they go live."

The report also provides recommendations on how to set up a program management office and how to break large projects up into programs.

The 20-page report contains two figures and one table. A table of contents is available online.

Insight details

Content Type
Reports
Report Type
Case studies, Technology trends, Vendor landscape
Location
Asia-Pacific, EMEA, LATAM, North America