This is a sample deck that introduces a small to medium size organization to a straight-forward IT Governance methodology. Tools and tips are available for this at no charge. Contact steve@gerick.org

1. IT INTERNAL REVIEW BOARD OVERVIEW
TECHNOLOGY SERVICES
DESIGNED BY STEVE GERICK
October 2007

2. IMPORTANT GOVERNANCE PRINCIPLES
IT principles – Clarifying the business role of IT
IT architecture – Defining integration and
standardization requirements
IT infrastructure – Determining shared and
enabling services
Business application needs – Specifying the
business need for purchased or internally
developed IT applications
IT investment and prioritization – Choosing which
initiatives to fund and how much to spend

3. IT ENGAGEMENT PROCESS

4. COMPANY PROJECT GOVERNANCE

5. IT PROJECT REQUEST PROCESS

6. IT INTERNAL REVIEW PROCESS

7. ITRB ROLES AND RESPONSIBILITIES
• Operations
• If service is not in the IT Service Catalog - determine if
SLA requirements are required. If so, work with
Governance and Applications Management to develop SLA
prior to review at the IT Internal Review Board meeting.
• If service is in the IT Service Catalog – be prepared to
discuss how service support procedures will occur.
• Ensure service is not in violation of existing security and/or
IT security policies.
• If application is new COTS application, ensure that IT
desktops are prepared to run the application including
testing and report results to the board.
All Assignments Defined Should Be Perform Prior to Convening the Board

8. ITRB Roles and Responsibilities
• Applications Management
• If non-COTS application is not in the IT Service Catalog, work
with Governance to develop requirements prior to review at
the IT Internal Review Board meeting.
• Determine if new non-COTS applications is consistent with the
existing IT application architecture/roadmap and report back
at board meeting.
• Ensure new non-COTS application is not in violation of
existing security and/or IT security policies.
• If application is new non-COTS application, be prepared to
run application testing and report results to the board. Also,
work with Governance to determine if IT desktops can run
application
All Assignments Defined Should Be Perform Prior to Convening the Board

9. ITRB ROLES AND RESPONSIBILITIES
• Governance
• If non-COTS application is not in the IT Service Catalog work with
Applications Management to develop requirements prior to review
at the IT Internal Review Board meeting.
• Ensure new COTS and non-COTS applications met overall San
Jose Airport strategic business objectives.
• If application is new COTS application work with Operations to
determine if IT desktops can run application.
• Determine if new technology/service and/or applications new
business process improvement(s) before implementation and
develop plan for implementing – report to board.
• Report to board on ROI/TCO or other justifications metrics relative
to the issue being discussed at the board.
All Assignments Defined Should Be Perform Prior to Convening the Board

10. NOTE #1 QUESTIONS TO BE ASKED FOR THIS PART OF THE REVIEW
• Does IT have resources to assign to this project?
• Does this project need formal project management?
• Will IT staff need training to enable them to support this?
• Does IT have the right people assigned to assist
management in making this decision?

11. NOTE #2 QUESTIONS TO BE ASKED FOR THIS PART OF THE REVIEW
• How does the solution fit with the existing architecture, and
how well aligned is it to the IT Guiding Principles?
• How will the solution be deployed?
• Does the solution depend on leverage from the existing
infrastructure? If so - what specifically?
• Are the technologies migration-ready to future technologies?
• Do the technologies conform with existing IT security
standards and industry standards – if applicable?

12. NOTE #3 QUESTIONS TO BE ASKED FOR THIS PART OF THE REVIEW
• What assets exists in the proposed deployment environment?
• What are the costs of the assets?
• How are the assets currently used?
• Why were the assets originally purchased?

13. NOTE #4 QUESTIONS TO BE ASKED FOR THIS PART OF THE REVIEW
• Doe IT have any historical information we can draw from to
help in the decision-making process?
• Is there pertinent background and/or mitigating
circumstances that should be considered?
• Are the goals of this initiative and/or business case
consistent with overall Company business objectives?