Through CIO-CFO collaboration, the right mindset can be better shaped in IT transformation.

There should be very few IT projects but rather business projects with IT involvement. IT has only one mission, and that is to drive business success. Business therefore needs to share responsibility for IT investments and projects as well. And it is crucial to build strong CIO-CFO relationship for IT governance effectiveness and efficiency.
The right mindset: Should the CFO care about their IT projects and performance, the majority opinion is a resounding “YES”! Through CIO-CFO collaboration, the right mindset can be better shaped in IT transformation project; such as: ROI-focused, vigilant on scope, knowing the business objects and how this transformation project links to the overall business goals. The strong senior leadership can enforce IT governance principles and practices, to ensure ROI is really going to achieve; control project scope and exploit business objectives accordingly.
The logic steps: CIO and CFO should both require some very
specific information for each major IT project prior to initiation, and follow the following logic steps
in IT governance:
1) An approved business case that clearly
states the purpose and objectives, high level scope, proposed timeline, planned
return on investment or value proposition, and how the project aligns with the
organization or department strategic objectives.
2) Identify the executive sponsor who has accepted accountability for successful delivery.
3) Identify the project manager who is responsible for successful delivery.
4) A preliminary risk assessment identifying organizational, technological, and external risks at a minimum.
5) A detailed project schedule with clear milestones, named deliverables, and assigned resources that have the necessary availability to complete the work.
2) Identify the executive sponsor who has accepted accountability for successful delivery.
3) Identify the project manager who is responsible for successful delivery.
4) A preliminary risk assessment identifying organizational, technological, and external risks at a minimum.
5) A detailed project schedule with clear milestones, named deliverables, and assigned resources that have the necessary availability to complete the work.
6) A
review process needs to be in place on a regular basis to evaluate whether
based on any external or internal events, the view of the organization towards
the project has changed and items 1 through 5 need any adjustments (minor or
major)
7) It
is very beneficial to have an independent governance process in place, to
ensure the project team is neither too conservative nor too risky, as this
could cause significant delivery issues once the project starts.
The better communication: CFO is frustrated with IT for the very reason.
The main problem is that IT is unable to express how they create value (IT for
business), and often focus on wrong things (IT for IT). It often talks of new
platforms, outsourcing deals, process maturity, but very little how these
activities transform into business value. Though the important thing to understand
is that this is often a role IT is given by CFO or business. Secondly, cost
levels are monitored but not managed. There is a need to create full
transparency and business accountability in order to manage cost. This is
usually not done smoothly. IT is related
to general IT performance and effectiveness (value creation / cost levels).

CIO and CFO need to
work more collaboratively to enforce IT governance, and well establish document
and resource management, take the best practices and next practices, to ensure
the project investments have to be conceptualized and executed as business
projects not IT projects with clear-defined business case and risk management
strategy. IT governance is converging with business governance, and IT is
business.
0 comments:
Post a Comment