Slide 4 of 14
Notes:
IT people are happy to allow some things to be seen as “IT” problems because then they can work away with “interference” from users. That’s not a good idea in euro conversion.
Many euro projects are run by the chief accountant. That’s good in that it takes the focus away from IT, but runs the risk of focusing only on trading accounts and leaves pricing problems until they hit them.
Marketing and purchasing people need to be involved in the euro project too.
Users who got away with no involvement during the Y2K project may wish to pass the euro conversion over too; until the first data input or conversion error happens, and then they will want to be told why.
I’ll skip over end-user applications, that’s a whole other presentation.
The main issue here is that the users have to know when there is a problem; the scale of values in euro may not be sufficiently different, in Ireland and (when? 2004?) in the UK.
