Business requirements should be what drives I/T. Unless an I/T solution is directly addressing a specific business challenge, it should not be undertaken. Also, ideal I/T solution specifications are generated independent of a specific technology.

The sooner technology folks come to understand this reality, the incidence failed/death march projects will diminish.


>>I would say there are more business implications than technical implications. And FWIW, the business implications are what normally do and should drive the decision...
>>
>
>normally do -- yes
>
>and should -- only from a bean counter's or manager's point of view ;)