Information Technology and Communications

Building Systems to Manage Technical Change Requests Safely

A senior-level treatment of technical change request management, focused on what changes outcomes.

  • 5training days
  • 4modules
  • 8sessions
  • 32topics
View packages and pricesCourse outline
Building Systems to Manage Technical Change Requests Safely
5days

About the programme

Course Overview

Technical debt in technical change request management is borrowed against future delivery capacity, at compound interest. Security and delivery speed are traded against each other in request management whether or not anyone says so. Participants leave with a method for the technology and systems delivery discipline, not a set of opinions about it. Benchmarking exercises repeatedly place technical change request management among the areas with the widest performance spread. It is designed for mixed groups, so that this area of technology and systems delivery is examined from more than one functional angle. Each session closes with a decision the participant must justify about request management in their own setting. Participants gain a realistic view of what technical change request management costs and what it returns. A common pattern is strong design of request management paired with weak follow-through. It closes by agreeing the smallest change to the wider technology and systems delivery agenda that would make a visible difference.

Expected Learning Outcomes

  • Estimate what technical change request management costs to run properly, and what is lost when it is not.

  • Apply access control and least privilege throughout request management.

  • Build a concise technical standard for technical change request management that colleagues can follow without further explanation.

  • Prepare a short, evidence-based briefing on request management for senior management.

  • Assess and manage third-party and cloud dependencies in technical change request management.

  • Measure delivery and reliability of request management with indicators teams trust.

  • Build the deployment pipeline for technical change request management so releases are routine rather than events.

Who Should Attend

  • Network and communications engineers supporting technical change request management.

  • Infrastructure and platform engineers operating request management.

  • Project managers delivering changes to technical change request management.

  • Department heads accountable for the results of request management.

  • Solution architects designing technical change request management.

  • Members of committees that take decisions affecting request management.

Course Modules

Open any module to see its sessions and topics.

01

Technical change request management: capacity, performance and load

2 sessions · 8 points

Session 1Moving technical change request management from approval to execution

  • Confirm that contractual obligations around technical change request management are understood.
  • Set delivery and reliability indicators for request management the team trusts.
  • Check that records of technical change request management answer the questions likely to be asked.
  • Configure alerting on request management that reflects what users experience.

Session 2The change to request management that caused the last outage

  • Identify the single points of failure in technical change request management.
  • Test the failover for request management rather than assuming it works.
  • Remove steps in technical change request management that add effort without adding assurance.
  • Apply change control to request management including emergency changes.
02

Request management: change control and rollback

2 sessions · 8 points

Session 1Building the method for request management step by step

  • Review access rights on technical change request management and remove what is no longer needed.
  • Build the internal briefing that explains request management to those affected.
  • Run a load test on technical change request management at expected peak plus a margin.
  • Agree the indicators that will show whether request management is improving.

Session 2Documenting request management so someone else can operate it

  • Confirm the support model and escalation path for technical change request management.
  • Confirm data retention and deletion rules applied within request management.
  • Assess the exit route from any cloud or vendor dependency in technical change request management.
  • Reduce the variation in how request management is carried out between teams.
03

Request management: monitoring, alerting and observability

2 sessions · 8 points

Session 1The cost of request management and how to present it

  • Test the procedure for technical change request management against a realistic scenario.
  • Inventory third-party dependencies inside request management and their update status.
  • Confirm every release of technical change request management can be rolled back within a defined time.
  • Draft the minimum viable technical standard for request management.

Session 2Monitoring technical change request management from the user's point of view

  • Document the runbook for technical change request management to the level a new engineer could use.
  • Map the handovers in request management between functions and secure them.
  • Restore a backup of technical change request management in a test environment and time it.
  • Plan the sequence in which improvements to request management will be introduced.
04

Request management: architecture and designing for failure

2 sessions · 8 points

Session 1Making releases of request management routine instead of risky

  • Establish who is informed, consulted and accountable in technical change request management.
  • Decide what will be stopped to create capacity for request management.
  • Anticipate the objections technical change request management will raise and prepare the answers.
  • Benchmark the organisation's request management against comparable operations.

Session 2Designing request management around how it will fail

  • Compare the cost of technical change request management with the cost of its absence.
  • Identify the data already collected that bears on request management.
  • Record the technical debt in technical change request management and schedule repayment.
  • Measure current load on request management and project it forward twelve months.

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

✆