- Home
- Products
- Services
- Support
- Getting Started
- Documentation
- System Governance Handbook
- Table of contents
- Chapter 1. Introduction
- 1.1. An overview of system governance
- 1.2. About this book
- 1.3. Uses of system governance
- 1.4. Principles of system governance
- Chapter 2. System governance roles and responsibilities
- 2.1. IT decision makers
- 2.2. System governance sponsor
- 2.3. System governance manager
- 2.4. System governance committee
- 2.5. Other roles
- Chapter 3. System governance tools and techniques
- 3.1. Metrici Advisor
- 3.2. Assessment
- 3.3. Validation
- 3.4. Analysis
- 3.5. Criterion maintenance
- Chapter 4. System governance processes
- 4.1. Process overview
- 4.2. Business case
- 4.3. Initiation
- 4.4. Roll out (waterfall)
- 4.5. Roll out (iterative)
- 4.6. Annual review
- 4.7. Interim review
- 4.8. Project review
- 4.9. System review
- 4.10. Comparison and evaluation
- 4.11. Compliance audit
- 4.12. Proof of concept
- Appendix A. System governance reports
- A.1. Terms of reference
- A.2. System portfolio review report
- A.3. Iterative review report
- A.4. System governance review report
- A.5. Interim review report
- A.6. Evaluation review report
- A.7. Compliance audit report
- Appendix B. Example reports
- B.1. Example terms of reference
- B.2. Example system portfolio review report
- Appendix C. System governance meetings
- C.1. Committee briefing
- C.2. Criteria development workshop
- C.3. Iterative review meeting
- C.4. System governance review workshop
- C.5. Interim review meeting
- C.6. Evaluation criteria development workshop
- Appendix D. System governance training
- D.1. System governance overview
- D.2. System governance with Metrici Advisor
- D.3. System governance alignment
- D.4. Comparison and evaluation
- Appendix E. Cross reference
- Index
- System governance: the missing link in IT governance
- System Governance Handbook
- Contact Support
- FAQs
- Customers
- Contact Us
- Sign On
4.1. Process overview
Previous | Next | Up | Contents
This chapter describes startup processes to establish system governance with an organisation, and ongoing processes to use and improve system governance every year.
This overview section provides a brief introduction to all the processes. It describes the ongoing processes first.

The diagram above shows the processes involved in using and improving system governance.
The centre of the diagram shows the annual review and interim review cycle.
The annual review is the main vehicle for delivering value to the organisation. It covers all the IT systems in the organisation, and delivers proposals to help IT meet objectives. These proposals can be to cut cost, to improve quality, to meet targets, to improve compliance, and so forth. The proposals will reflect priorities set during the establishment of system governance.
The annual review also includes a review of the system governance process itself. This allows the priorities and focus of system governance to evolve in step with broader IT objectives.
The interim review provides an opportunity to monitor the progress of system governance between the annual reviews, and to address any important issues that arise.
The main review cycle is augmented by four other processes.
- The project review is used to assess IT projects, to make sure that new systems meet objectives.
- Existing systems are reassessed at least once per annual review cycle using the system review.
- Where a comparison of options is required, for example to compare competing products, the comparison and evaluation process ensures that the competing options are evaluated against the system governance objectives.
- If new compliance requirements arise during the course of the year, and can not be met within the main review cycle, an additional compliance audit measures the level of compliance to the new requirements.
Although they benefit from an established system governance regime, the project review and comparison and evaluation processes can be used before system governance is established.

The diagram above shows the processes involved in implementing system governance. Business case establishes the case for system governance. Initiation gets the organisation ready for the roll out of system governance.
The roll out can take one of two forms.
- It can follow a relatively formal “waterfall” approach in which the criteria and list of systems are defined before any assessments take place. See Section 4.4, Roll out (waterfall).
- Alternatively, a less formal “iterative” approach can be used, in which the criteria and the list of systems are built up through a number of iterations. See Section 4.5, Roll out (iterative).
The choice between waterfall and iterative is based on a number of factors, which are explored during the initiation process. See Plan roll out.
The processes described above are appropriate for organisations who want to formally evaluate, implement and use system governance. The system governance tools and techniques can also be used less formally.
Organisations that wish to investigate system governance before starting a formal project may want to consider running a proof of concept.
If an organisation starts using system governance informally, the other processes will be useful when the time comes to implement system governance as a more formal activity within the organisation. There is no need to throw away criteria and assessments that have been carried out informally, as these can be carried over into more formal processes when required.
The sections below describe each of the processes in more detail, and break each process down into a series of steps.
The processes refer to roles and techniques that are defined in the previous two chapters of this document. The responsibility for each step is given.
In many cases, organisations will wish to extend the processes and roles to meet their own requirements, and to fit in with existing processes and roles. Where this is the case, the processes should provide a good starting point.
Previous: Chapter 4. System governance processes | Next: 4.2. Business case | Up | Contents
