Information Technology and Communications

Establishing Information Technology Governance Committees and Defining Roles

Move technology governance committees from general awareness to a repeatable, reviewable practice.

  • 5training days
  • 4modules
  • 8sessions
  • 32topics
View packages and pricesCourse outline
Establishing Information Technology Governance Committees and Defining Roles
5days

About the programme

Course Overview

Systems supporting technology governance committees fail in ways that are obvious afterwards and invisible before. Availability targets for the practice within technology and systems delivery are commercial commitments, whatever the engineering team calls them. Participants gain a clear basis for measuring what this aspect of technology and systems delivery has actually achieved. The difficulty is not agreeing that technology governance committees matters — it is deciding what to stop doing to make room for it. Participants who influence the technology and systems delivery capability without directly controlling it will find the content directly usable. Each session closes with a decision the participant must justify about the technology and systems delivery discipline in their own setting. The professional literature on technology governance committees converges on a small set of controls that reliably work. It concentrates on the parts of this aspect of technology and systems delivery that determine outcomes and treats the rest proportionately. The final session converts the week's work on this strand of technology and systems delivery into commitments with owners and dates.

Expected Learning Outcomes

  • Assess the current state of technology governance committees against a structured set of criteria rather than impressions.

  • Plan capacity for technology governance committees against measured growth rather than optimism.

  • Test technology governance committees under realistic load before it meets real load.

  • Identify the failure points in technology governance committees most likely to cause loss, and control them first.

  • Measure delivery and reliability of technology governance committees with indicators teams trust.

  • Set acceptance criteria for technology governance committees before work begins rather than after.

  • Apply access control and least privilege throughout technology governance committees.

Who Should Attend

  • Analysts producing the data on which decisions about technology governance committees rest.

  • Software engineers and technical leads building technology governance committees.

  • Infrastructure and platform engineers operating technology governance committees.

  • Solution architects designing technology governance committees.

  • Anyone whose accountability for technology governance committees exceeds their current formal training in it.

  • Information security specialists protecting technology governance committees.

Course Modules

Open any module to see its sessions and topics.

01

Technology governance committees: requirements, targets and service levels

2 sessions · 8 points

Session 1Sizing capacity for technology governance committees on measured growth

  • Run a load test on technology governance committees at expected peak plus a margin.
  • Set the review interval for technology governance committees and who attends.
  • Confirm data retention and deletion rules applied within technology governance committees.
  • Review logging on technology governance committees for coverage and retention.

Session 2The cost of technology governance committees and how to present it

  • Establish the boundary of technology governance committees and record what sits outside it.
  • Confirm the support model and escalation path for technology governance committees.
  • Identify single points of dependency in technology governance committees and reduce them.
  • Identify the single points of failure in technology governance committees.
02

Technology governance committees: incident response and severity

2 sessions · 8 points

Session 1Making releases of technology governance committees routine instead of risky

  • Restore a backup of technology governance committees in a test environment and time it.
  • Apply change control to technology governance committees including emergency changes.
  • Test the failover for technology governance committees rather than assuming it works.
  • Assess the exit route from any cloud or vendor dependency in technology governance committees.

Session 2Escalation and decision rights in technology governance committees

  • Test the procedure for technology governance committees against a realistic scenario.
  • Remove steps in technology governance committees that add effort without adding assurance.
  • Record the rationale for each significant choice made about technology governance committees.
  • Confirm that reporting on technology governance committees reaches the people who can act.
03

Technology governance committees: security, identity and least privilege

2 sessions · 8 points

Session 1Monitoring technology governance committees from the user's point of view

  • Inventory third-party dependencies inside technology governance committees and their update status.
  • Name a single owner for each element of technology governance committees.
  • Review access rights on technology governance committees and remove what is no longer needed.
  • Distinguish symptoms from causes when technology governance committees underperforms.

Session 2Documenting technology governance committees so someone else can operate it

  • Reduce the variation in how technology governance committees is carried out between teams.
  • Set delivery and reliability indicators for technology governance committees the team trusts.
  • Rank the weaknesses in technology governance committees by consequence rather than by ease of fixing.
  • Define incident severity levels for technology governance committees and the response each triggers.
04

Technology governance committees: capacity, performance and load

2 sessions · 8 points

Session 1The paperwork for technology governance committees that is actually needed

  • Set out the decisions in technology governance committees that require sign-off and by whom.
  • Document the runbook for technology governance committees to the level a new engineer could use.
  • Measure current load on technology governance committees and project it forward twelve months.
  • Agree what will be standardised in technology governance committees and what will not.

Session 2Dependencies and supply chain risk in technology governance committees

  • Record the technical debt in technology governance committees and schedule repayment.
  • Compare the cost of technology governance committees with the cost of its absence.
  • Check that records of technology governance committees answer the questions likely to be asked.
  • Arrange the handover of technology governance committees so capability survives staff changes.

Choose the package that suits you

Silver Package

At least 3 people

USD1,250
  • Workshop or Program Participation
  • Airport Transfers
  • Customized Badge
  • Expert Mentorship (Private Sessions)
  • Supervision & Secretarial Services
  • Accredited Certificate of Participation
  • Complete Training Kit
  • Coffee Break
  • Closing Ceremony

Gold Package

At least 3 people

USD1,850
  • 5-night stay in a 5-star hotel
  • Workshop or Program Participation
  • Airport Transfers
  • Customized Badge
  • Expert Mentorship (Private Sessions)
  • Supervision & Secretarial Services
  • Accredited Certificate of Participation
  • Complete Training Kit
  • Coffee Break
  • Closing Ceremony

Complete your registration

We will contact you within one business day to confirm.

Share this course

🔗 Short link
View packages and prices

✆