Linked by David Adams on Mon 4th Aug 2008 18:56 UTC
Permalink for comment 325654
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
More News »
Sponsored Links



Member since:
2005-11-09
11. If you are planning a project make sure your time line meets the deadline of your customers (other departments). I have seen more then one CIO violate this rule and have it cost them their job. Someone else gets to figure out how to make something work while the customer is screaming because their department has ground to a halt as they wait for a project that is behind.
11a. If things work now in the real world. Think twice, no three times before you cross bridges that are one way. Nothing like getting halfway through a project and discovering that the goal can't be achieved with your current path or time line. Then you get the joy of telling departments they have to redo work to get back to where they were.
In case you were wondering, at my place of employment both are taking place. The townspeople are at the IT doors with torches and pitchforks..... and they are not smiling. The CIO looks nervous and twitchy.