- 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.12. Proof of concept
Previous | Next | Up | Contents
The process is used when organisations are first considering system governance, and want to explore the subject more fully before proceeding to a business case.
The proof of concept is run before system governance is formally established and before system governance roles are filled.
The steps in this process are suggestions for some of the main activities that an organisation may wish to consider. The organisation is of course free to run a proof of concept however they wish.
If an organisation runs a proof of concept and then moves to a more formal adoption of system governance, there is no need to throw away assessments that have been carried out. These can be carried over into more formal processes, and can take the place of the initial assessments produced during the initiation.
-
Research system governance
Research published material on system governance. Review Section 1.3, Uses of system governance and Section 1.4, Principles of system governance.
Consider attending system governance overview training. See Section D.1, System governance overview.
-
Explore toolset
Investigate the Metrici Advisor toolset. Carry out some informal assessments and run analysis reports.
-
Consider value
Consider how in your organisation system governance could add value, and what the greatest priorities on it would be. Look at the business case process for ideas on how to consider value.
-
Pilot use
Pick a subset of systems (ten systems is ideal) and perform an assessment of these using the standard Metrici criteria. (Do not bother validating the assessments or tailoring the criteria.)
Run the standard analysis reports and see whether the measures and issues are useful and insightful.
See:
Section 3.2, Assessment Section 3.4, Analysis Consider whether a similar approach, with tailored criteria applied across all your systems, could provide value to your organisation.
Previous: 4.11. Compliance audit | Next: Appendix A. System governance reports | Up | Contents
