IT should not be hard; all we are doing is pushing a bunch of ‘1’s and ‘0’s around a business and providing a bit of magic to make this information have some form of meaning to business users.
I want to upgrade one of my customers from Oracle 9.2 to 10gR2. There are a couple of features in the latest version of the database that would really help my customer in terms of better use of their hardware resource. But the upgrade is stalled because their version of a third-part BI tool is not certified to run queries against Oracle 10g. And the upgrade of the reporting tool is stalled because it requires the latest SUN JVM for the web clients, and that is stalled because they have not verified if SUN JVMs will run in their exclusively Citrix Metaframe environment. Still if I raise our request to upgrade now, it may get done in a few years time.
Posted by: Peter Scott | January 6, 2006
IT should not be hard
Posted in BI and DW, Technology
>> IT should not be hard
Who told you that?
Seriously, the problems are rarely in the ones and zeroes. That’s the easy bit. The grief is usually in the realm of project management (loosely defined). I’ve just returned from a meeting in which I’ve discovered there will be more /levels/ of management directing my project and its interactions with other projects than there will be actual technical people delivering the system.
Mmmmm, I can smell the productivity already.
Cheers, APC
By: APC on January 6, 2006
at 4:03 pm
IT is only hard because we (royal we here) make it so.
Upgrading your DB from one version to another is complicated by your appls (regardless of whether it’s home grown or third party) because we don’t practise good programming techniques and/or good design.
apc said…
The grief is usually in the realm of project management (loosely defined). I’ve just returned from a meeting in which I’ve discovered there will be more /levels/ of management directing my project and its interactions with other projects than there will be actual technical people delivering the system.
That might be a case of an over-zealous project manager who want to do everything by the book. Depending on the nature and size of the project, you could ended with quite a fair amount of different subgroups (e.g. QA, Change Mgmt, Communications, Tech, Business, etc).
By: Peter K on January 6, 2006
at 7:58 pm
[...] http://pjsrandom.wordpress.com/2006/01/06/it-should-not-be-hard/ [...]
By: Upside of MOSS « MOSS 2010 on June 22, 2007
at 11:04 am