Defining Roles for IT Governance (Part 3)

Home  >  Articles  > 







Defining Roles for IT Governance (Part 3)

by George Jucan PMP

May 30, 2006


Increasing pressure from stakeholders for efficiency forces most organizations to find new ways to ensure every dollar is judiciously spent, both in private and public sector. It is no surprise that companies realized that independent projects--each with its own objective, resources and methodology (stove-pipes)--are either overlapping or allowing gaps in the coverage of business needs, both being a waste of money: Either by duplicating work in the first place, or by costly plug-ins and/or rework after delivery.
 
Cross-projects coordination was one of the most obvious responses to the above issue. More or less formal, this overall view of most if not all projects executed allows aligning the pieces of the puzzle early in their lifecycle, when the adjustment costs are minor. The most common coordination form (and the least formal) simply consists of a charter and/or scope statement review by the PMO, or a presentation of upcoming projects in the regular meeting of all project managers.
 
While each project manager is generally aware of other project with potential impact, they have no clear responsibility to coordinate with each other.



Please login/register to read the entire article.





sponsored announcements and special offers
Position yourself for success with Florida Tech's MBA in Project Management, accredited by PMI® GAC. There's no GMAT or GRE required, and you'll also qualify for 1,500 experience hours that can be used toward earning a prestigious PMP® credential.
The Enterprise PPM and PMO Blue Print. Learn strategies and best practices for taking a top-down, enterprise-wide approach to PPM processes and system deployment. To learn more and register now, click here!



Necessity is the mother of taking chances.
- Mark Twain