Ten Rules of Governance

1
Ten Rules of Governance

• Identify and Describe Each Initiative That
  Requires IT Budget Before a Decision Can Be
  Taken. This document should include scope,
  timings, required budget, and a costbenefit
  analysis for non-legal projects. Scope and
  estimates are end-to-end. End-to-end means
  including required budget and resources of every
  domain from the start of the project until
  delivery.
• Separate the Initiating Phase from the Delivering
  Phase. In the Initiating Phase, a Prestudy and an
  Architectural Study Is Done. Based on these
  studies, that include the long-term cost impact,
  initiatives are budgeted, prioritized, and
  decided.
• Identify a Responsible IT Manager for Each
  Project. This person reports to a steering group
  (where business and IT is represented) that is
  responsible for the follow up of realizing the
  scope within assigned budget and timing.
• Divide the IT Budget into Production, Strategic
  Projects (Investments), and Tactical Projects
  (Continuity).
• Investment Budgets (Strategic Projects) Must Be
  Decided at Executive Committee Level.
• Install a Forum That Decides on the Year Planning
  and Regular Corrections on It. Frequency is not
  so important but needs to be at least quarterly.
• For a Good Alignment Between Business and IT,
  Install the Role of Process Manager (Business)
  and Business Analyst (IT).
• Install Domain Forums Where Business and IT Are
  Represented That Prepare the Initiatives. At this
  forum the content of an initiative is discussed
  and members need to agree on scope, architecture,
  impact on the different domains, and required
  budget. In this way the initiative is ready for
  decision.
• Make Sure the ITCreate Costs Are Allocated to
  the Business Domains to Make Them Aware That
  These Costs Can Be Directly Impacted by Their
  Decisions. This requires the calculation of an IT
  man-week-price.
• 10. Make a Bottom-Up Year Planning with a 100
  Reconciliation Between Planned and Available
  Resources. On team level, names of persons
  required to work on specific projects are not yet
  required. These names are required in the project
  charter that is made at the start of the
  delivering phase and approved by the steering
  group.