business case

Greenfield and migration strategies have specific advantages and disadvantages. To be able to make a decision you have ask yourself questions like:

• What are we going to do with our current legacy infrastructure?
• What are we going to do with are current legacy technology?
• And what are going to do with our current employees?

We all know examples of projects that did not meet their planned result. There can be many different reasons for such a failure. Common causes of project breakdowns are:

• The effects of other current projects were not properly taken into account.
• The requirements of other departments were not sufficiently met.
• The delivered specifications were not checked against specific testability.
• The delivered specifications were not bundled into over time deliverable sets by adequate project phasing.

It is time to execute an assessment if one or more of the following points check:

• The project planning has changed once more, and you ask yourself why did I ever started it:
  • Again the requirements were to optimistic, wrong or lacking;
  • You seemed to have passed the point of no return (again).
  • Important issues have become second place, and unimportant issues have become crucial for success
  • Nobody seems to know anymore where it was all about in the first place.
  • Time is running out.

Did you ever realized how many projects fail, and how this occurs?

Forrester reports on poor requirements (2006) a survey of the Standish Group's 1994 Chaos Report. Standish found, querying over 352 companies reporting on over 8,000 software projects, that the top three project impairment factors were:

• Lack of user input (12.8% of respondents);
• Incomplete requirements and specifications (12.3%);
• Changing requirements and specifications (11.8).