how to suCCeed at projeCt governanCe
Your IT and business teams work on large projects, which include
the development of sales applications, nancial applications, human
resource applications, and order entry applications for internal users.
ey also develop applications for customers, such as customer ser-
vice applications, as well as logistic applications for your channel part-
ners. ese teams also work on smaller projects such as application
enhancement releases, help desk issue, and incident resolution. Even
the activities associated with an outsourced or purchased application is
a project. ere are always data center projects to improve eciency or
install new equipment. e point here is that most work activities are
indeed part of a project and need to be managed through a governance
model to ensure successful outcome.
IT organizations manage many projects. Whether big or small,
these projects always have risks and project managers (PMs) always
want to minimize risk. Project plans are perfect the moment they
are developed. Once the project clock starts, subsequent events
inuence project schedules and costs. Resources with the required
skills might not be available resulting in errors or increased work
eort. Incorrect or expanded scope requirements extend project
schedules. Improper testing results in rework. Each of these risk
areas aects the ability of the IT organization to optimize project
throughput—the number of projects executed during the scal year.
When schedules extend beyond planned dates, or costs exceed bud-
get, fewer projects complete in a scal year, and potential business
benets of projects not able to be implemented are deferred to a
future point in time.
If you think about projects only in terms of cost, schedule, and
resources, then you need to change your focus. You need to realize
that projects provide business benets in terms of customer value,
improved revenue, reduced cost, and shareholder wealth. Once you do
this, your perspective on the importance of project success will change
benecially. Now, let us get back to some basic issues that aect suc-
cessful project delivery.
A Gartner survey in 2012 cited that large IT projects “are more
likely to fail than small projects…due to functionality issues and sub-
stantial delays.” Projects with budgets greater than $350,000 exceeded
budgets 25% of the time. e failure rate of projects greater than
one million dollars was almost 50% higher than projects with budgets