Our Choices

“There are three constants in life... change, choice and principles.”

~ Stephen R. Covey

What counts for a successful IT project

Today i was reading this article when I came across a very thought provoking comment from Hemant Kogekar. On the subject of great universal lies, he says, I quote,

17. Project success is being on time, on quality and on budget
“As we all know, a project is successful only when the business gets the promised benefits.”

UNQUOTE

Those of us who have spent time in IT and Projects would know of the number of times success criteria has been defined as above, on time, on quality, on budget.

And yet, business never even blinked when a new release was operationalised in IT. More often it has been shouting when projects ever slightly tweak the user interface / service delivery to adopt the new release - discounting the opportunity / benefits that has been envisaged in the project. 

Isn't it time we all started to define the measurement of a project by business outcome? How will you measure success of a project?

Its 4C: No more no less - company, channel, customer and competitor

In my opinion, we need to address all the four C in conjunction and not one over the other.
Today I read this interesting and "almost" convincing article in Fortune. It made my resolve stronger in the view that we need to look at the overall company strategy from all the four perspectives.
Over emphasis on any one may lead you towards a direction that is too skewed. It takes away the balance. So whether Customer Is King or Competitor is the true measure of Customer Shift is not the only question to be evaluated.
What is the Route to Market strategy with the channel?
And the last but the most important, what is the core values and strategy that the company wants to drive.
I would like to hear from my learned friends on this aspect.