Project updates anyone


Anonymous

Guest
IRIS
Tivoli --> Tidal
Mainframe --> Verizon
AS/400 shuffle
Data Center Consolidation
GFS
Storage SAN upgrade
Beerse Power
MOPS as a DR site
Migrations to MOPS
Exchange 2010
 




0 for 11 baby!

You are a "sick puppy" to rejoice over failure. Aren't you part of the team?

I would agree that the "cronyism" allowed incompetent individuals to be placed into positions, while very qualified people do not stand a chance. But to rejoice over the failures of projects really makes me sick.
At the end of the day me, you, and practically all who will be reading this post are on the same team.

Please grow up..
 


The term "team" would indicate that each individual has a prescribed role and is a required element in order for the team to be successful. These roles would be respected by other team members and relied upon. Now, if you know anything about the current management then you already know this is not a teamwork environment.

In fact it reminds me of 5 yr olds playing baseball. If, and I mean IF, someone actually hits the ball in the outfield. Now you have every player chasing the ball. Looks like chickens being fed. Why, you ask? Because 5 yr olds are not experienced at the roles of the positions in baseball nor do they understand how staying in their role actually helps the team. Kinda like IT leadership at J&J.

Now don't get me wrong, it is possible for a real good center fielder to move in a play second base. But with an arm like that in center field wouldn't the team be better off with him out there. Maybe some of those who moved into Operations should have stayed in Sourcing where they were being so successful. I guess it is time for a new Coach or General Manager. The failure belongs to those who allowed or put the players in the positions they are in. The players do have a responsibility to do their best in the position assigned and to learn about that position. I do not believe there is a shortage in commitment from the players in the field.

So please, come down off your soap box and clean your transparent lenses so you can see the game. Looks more like a hockey score though!

For those lovers of baseball, I apologize for using such a sacred sport in this analogy.
 


Part of the problem is these projects are announced with overall finish dates by the LT based on when they want them done. This is before anyone can sit down and define the project scope and when they can be delivered from a technical standpoint.

The way we get around this is to not announce the year. Velochitty was June -- we just implied it was the same year. Same as IRIS -- August. Oops, wrong year again.

The other way to describe finish dates is to give them by time periods. "How long before we are done?" "Three months." No one takes note of what the date is so when someone asks again in two weeks, you can give the same answer -- "three months........." Viola, you just robbed two weeks from Father Time.
 


So if none of the projects are done. Are they at least moving into the next phase? Don't they have some sort of "crack" PMO that is tracking the progress of these project and reporting them up to the LT. I'm certain the LT is interested in understanding which projects are not hitting their timelines. What is the point of putting together all the project charter's, plans, etc. if nobody give a hoot.

I could understand a couple projects being impaired by inept leadership, but all of them. Come on, where is the accountability we keep hearing about! I bet by the time the reports get to LC so many filter lenses cover it that she cannot see the truth on the paper. As a CIO you would think she can tell those are not roses they are giving her, more like dandelions.
 






hey who cares if a project gets done as long as the SDLC is followed and Clarity, Time sheets, plus score cards are updated, what else matters?

And make sure that you click on the box that you watched the Shackleton video. Worlds falling apart and that's the one thing MH sends an all-hands email for.
 









Write your reply...