• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (3)

1 localhost commented Permalink

I think it will also help if both sides(business/IT) have periodic sessions(irrespective of a particular project/s) which enlightens about each others domains, new processes etc.

2 localhost commented Permalink

In my experience, the issue is most often dollars and rarely schedule. One problem is that if big projects take 2 years to develop/deploy, the corporate architecture and standards do not stay frozen that long. So a standards change in the middle of a project has an impact that was not planned for, and usually the projects are broke, overbudget and behind schedule at that point.So the typical mid-lifecycle scenario is a mandated change with no funding. Often there might be no issue if that CR had come forward with funding to support the impacts. But usually the "corporate view" is that it is a standard, the project must pay for it. I disagree with that view; I think it should be a corporate obligation to make baselined projects whole again if the corporate standards change midstream or else offer waivers.The other problem, which you note, is at the initial point where project scope is defined and the situation arises that the business unit doesn't see the value of the standard and would prefer to deploy new revenue generating functions instead, rather than paying for compliance. The classic case is a working but non-standard function ... what business project owner would sink money into fixing something they don't think is broken? At that point, I think the corporate standards setters should have authority to kick the project's butt; they need teeth to prevent deployment without conformance. The tradeoff is that the business units need to sit on the standards setting boards to help set the strategic direction, so they also have some ownership of those standards and the adoption requirements.

3 localhost commented Permalink

I have to quote from Russ' original email from me which he toned down for the comment below:

What your blog cites is certainly an issue (though one among many). I agree with what you say up to the end, where you have your "hold hands and sing kumbaya" conclusion ;-)
Thanks Russ!

Add a Comment Add a Comment