- 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
2.5. Other roles
Previous | Next | Up | Contents
The project manager is involved in the project review. The project manager initiates the review, and ensures that the review has the input that it needs from the project team. After each stage of the review, the project manager addresses the risks and issues identified by the review.
The comparison and evaluation process is used as part of a broader system selection process, for example to support a request for proposal (RFP) or invitation to tender (ITT).
The evaluation owner is the lead role in this process. They initiate the comparison and evaluation process, and make sure that it meets the needs of the broader selection process.
The evaluation stakeholders contribute to the process by discussing and agreeing the criteria to be used for the evaluation.
The evaluation owner would usually be included as one of the evaluation stakeholders.
The compliance audit process is used to introduce a new requirement into system governance outside of the normal review cycles, and to measure compliance to the new requirement.
The compliance owner represents the new requirement. For example, if the new requirement is a regulatory obligation, the compliance owner would be the manager charged with ensuring that the organisation meets the new obligation.
The compliance stakeholders help elaborate the new requirement. The work alongside the system governance committee, but only during this process.
The compliance owner would usually be included as one of the compliance stakeholders. In some cases, there is no difficulty in elaborating the new requirements, and the compliance owner is the only compliance stakeholder.
Previous: 2.4. System governance committee | Next: Chapter 3. System governance tools and techniques | Up | Contents
