From the front of the Oracle Siebel CRM classroom

Last month I promised I would write about a project where everything went wrong and still managed to be considered a success. The customer was a major bank that had gone through 5 mergers in 6 years. They were looking for a way to consolidate their business and bring together data segmented across many different banking applications. On this project the implementation team did too many customizations, wrote too much code, came in over budget, and delivered the project late. Despite all of these problems our customer had the solution they needed and saw the project as a success.

In this month’s article instead of talking about past projects, I discuss a pet project that I have been working on. For quite a while I have been advocating an approach that I believe will reduce the time and cost associated with the requirements gathering and design stages of an implementation project.