There has been many news about cases of failed
and unsuccessful IT-projects in public administration and state administration
in past few years. The most known probably is the catastrophic start of the new
e-ticket system of the national railways, which caused a massive chaos on
railway stations, queues on the ticket counters and many internet customers
being unable to buy their tickets. There are others like that as well and also
those, which are still under work, after five or even ten years. Good example
is the national information software project, which includes a development of a
national archive on patient information and an electronic doctor's
prescription. The first one has been under development at least over 10 years
and the first version of the e-prescription didn't work in practice.
The reason for failing IT-projects cannot solely
be found from the side of the software company, since the coder who actually
constructs the whole software possibly has little relation to the field the
software is targeted for. An IT company usually tries to meet the needs of the
customer, but that isn't an easy task, if the customer self doesn't actually
know what she is after. The more complicated the functionalities and the user
profiles are, the more difficult is meeting the needs of the customer. Some software’s
are probably easier to build to work, such as accounting software’s (in Finnish
= kirjanpito-ohjelma) or customer register software’s
since the general function are all the same and not depending on the special
needs of the special situations. But for example an e-ticket system can be a
very complicated thing to tailor for all kinds of situations where the vast
variety of users, such as customers or ticket counter workers can be in.