I just dont gettit.

[James Deuce]

NOTHING to do with the VICTIM IT Company? Ppppfffttt..I see some IT person speaking from their side only.

You'd wonder why most projects are blown out of budget with little/no result and end up failing.

Nasty outlines:



+1

Did you read Nasty's post? Did you read mine?

I currently work for an IT company. I haven't always. I've run successful projects, I've worked in successful projects. People often call technology projects "IT" projects when they are no such thing. The Y2K project (that most people call a failure) was in fact the most successful project ever run. Clear outcomes and minimal problems - for those who bothered to pay attention. Barclay's Bank lost 2bn pounds in credit card transactions overnight because their credit card arm didn't change to a 4 digit year date field. Yeah. Nothing happened with the Y2K "bug". It wasn't a bug. It was identified as a problem 12 years before the fix was required. Most people added fixing it to their normal business years before they needed to.

The most sure fire way to ensure the failure of an "IT" project is to let it commence without involving any IT people. I'm in a support role now. 30% of my work in the last 2 years has been making a "finished" project work, so don't tell me I'm arse covering or don't know what I'm talking about.

Failed IT projects get reported as such by business managers who refused to fund or staff a project appropriately due to cost projections and then need a place to hang their failure. IT projects fail at commencement, not failed completion.

Tradesmen OTOH seem to be accorded mystical status. They suck. They have no customer service skills, are abusive, and take the piss with their charging. If you ring 18 plumbers and no one returns the first call, I'd call that something that I don't get.

[FROSTY:Me]

Im using puter issues as examples but with such big fuckups at top level what chances do we stand

[Usarka]

My CFO is currently the Sponsor . .

If it's not a financial project then wrong sponsor! If it is a financial project then you have my symapthy.....

[Nasty]

If it's not a financial project then wrong sponsor! If it is a financial project then you have my symapthy.....

You are right ... its a financial project .. that is why the CFO ... thing is its a financial systems project .. even more fun! Why would the CFO be the sponsor if it was nothing to do with finance ..

[Nasty]

Did you read Nasty's post? Did you read mine?

I currently work for an IT company. I haven't always. I've run successful projects, I've worked in successful projects. People often call technology projects "IT" projects when they are no such thing. The Y2K project (that most people call a failure) was in fact the most successful project ever run. Clear outcomes and minimal problems - for those who bothered to pay attention. Barclay's Bank lost 2bn pounds in credit card transactions overnight because their credit card arm didn't change to a 4 digit year date field. Yeah. Nothing happened with the Y2K "bug". It wasn't a bug. It was identified as a problem 12 years before the fix was required. Most people added fixing it to their normal business years before they needed to.

The most sure fire way to ensure the failure of an "IT" project is to let it commence without involving any IT people. I'm in a support role now. 30% of my work in the last 2 years has been making a "finished" project work, so don't tell me I'm arse covering or don't know what I'm talking about.

Failed IT projects get reported as such by business managers who refused to fund or staff a project appropriately due to cost projections and then need a place to hang their failure. IT projects fail at commencement, not failed completion.

Tradesmen OTOH seem to be accorded mystical status. They suck. They have no customer service skills, are abusive, and take the piss with their charging. If you ring 18 plumbers and no one returns the first call, I'd call that something that I don't get.

I read your post .. and agreed ...

[rainman]

iam working on a site at taranaki

there are a 1000 of us working on site and we earn $3000 a week
out of that 1000 about 10 of us do any work

Got any vacancies?

[riffer]

James Deuce and Nasty talk a lot of sense. I work as an operations development manager for an IT company working primarily in the heritage sector (which involves both government and private clients), and have an opinion of this.

It seems to me that there's two big differences between my government and private clients.

1. Project sponsors in private have both the guts and the clout to make a decision regarding the project without interminable meetings.

2. They also have to answer for their actions for it too.

I shake my head at some of the clusterfucks masquerading as projects within the public sector. I don't know how you put up with the public sector Nasty. You're far too talented.

[mynameis]

Did you read Nasty's post? Did you read mine?

I currently work for an IT company. I haven't always. I've run successful projects, I've worked in successful projects. People often call technology projects "IT" projects when they are no such thing. The Y2K project (that most people call a failure) was in fact the most successful project ever run. Clear outcomes and minimal problems - for those who bothered to pay attention. Barclay's Bank lost 2bn pounds in credit card transactions overnight because their credit card arm didn't change to a 4 digit year date field. Yeah. Nothing happened with the Y2K "bug". It wasn't a bug. It was identified as a problem 12 years before the fix was required. Most people added fixing it to their normal business years before they needed to.

The most sure fire way to ensure the failure of an "IT" project is to let it commence without involving any IT people. I'm in a support role now. 30% of my work in the last 2 years has been making a "finished" project work, so don't tell me I'm arse covering or don't know what I'm talking about.

Failed IT projects get reported as such by business managers who refused to fund or staff a project appropriately due to cost projections and then need a place to hang their failure. IT projects fail at commencement, not failed completion.

Tradesmen OTOH seem to be accorded mystical status. They suck. They have no customer service skills, are abusive, and take the piss with their charging. If you ring 18 plumbers and no one returns the first call, I'd call that something that I don't get.

Certainly not "disagreeing" as such, however there is always two sides of a coin, which is what I am trying to highlight. As spoken right from the horses mouth below:

fuck ups
you want to see a fuck up
this is the biggest fuckup since dunkirk..
iam working on a site at taranaki

there are a 1000 of us working on site and we earn $3000 a week
out of that 1000 about 10 of us do any work
on top of that .. most of the stuff we are doing is rework
fixing other peoples fuckups
no wonder these think big projects cost so much
its a fucken JOKE

+1 Well put some projects really are a joke.

[riffer]

this might help to illustrate some of it...

[kevfromcoro]

Got any vacancies?

yes sure the best i done was 5600 in 6 days

pm me. its money for jam

[Mikkel]

That's humans for you I am afraid. The good old latin proverb still holds true.

[mynameis]

this might help to illustrate some of it...

More of a Management lesson init? Very true though.

[Timber020]

Plenty of failed projects due to IT people pushing products that
a) were never going to be suitable to existing systems or organisation
b) were never going to be affordable (but the IT guy gets nice kickbacks for all those addition features that will never be used)
c) were going to make the IT people the most money

Plenty of really ugly IT projects out there, often its the client who is lead down the merry path of failure and cost over run by the trusted hired "expert" who is happy to bleed the public sector for all its worth and then wash there hands of it once it gets messy.

At least thats what Im told by people in the industry. IT guys get paid to much to screw up and not be tied to there mistakes.