Document technology risk management to the level a new engineer could operate it.
Designing Corporate Technology Risk Management Strategies
Practical training in technology risk management, grounded in real cases and applied to your own operation.
📍 Tunis🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Security and delivery speed are traded against each other in technology risk management whether or not anyone says so. Most outages involving this area of technology and systems delivery are triggered by a change somebody considered routine. Each session closes with a decision the participant must justify about this aspect of technology and systems delivery in their own setting. Participants develop a defensible line of reasoning for the choices they make about technology risk management. Participants who influence the technology and systems delivery discipline without directly controlling it will find the content directly usable. The version of this strand of technology and systems delivery described in the manual and the version practised on the floor tend to diverge over time. Participants leave with a method for technology risk management, not a set of opinions about it. Where the technology and systems delivery discipline is measured, it improves; where it is only discussed, it drifts. It closes by agreeing the smallest change to the technology and systems delivery capability that would make a visible difference.
Expected Learning Outcomes
Build the deployment pipeline for technology risk management so releases are routine rather than events.
Secure the software supply chain and dependencies within technology risk management.
Test technology risk management under realistic load before it meets real load.
Set a realistic target state for technology risk management and a defensible route to it.
Adapt recognised practice on technology risk management to local constraints without hollowing it out.
Design a practical operating method for technology risk management that fits the organisation's size and maturity.
Who Should Attend
Internal auditors reviewing how technology risk management is designed and operated.
Project managers delivering changes to technology risk management.
Information security specialists protecting technology risk management.
IT managers and service owners responsible for technology risk management.
Managers with direct responsibility for technology risk management within the technical platform.
Database administrators managing data within technology risk management.
Course Modules
Technology risk management: backup, recovery and continuity
2 sessions · 8 pointsSession 1Retiring the legacy part of technology risk management
- Review logging on technology risk management for coverage and retention.
- Define incident severity levels for technology risk management and the response each triggers.
- Agree the smallest change to technology risk management that would be visibly useful.
- Establish what evidence demonstrates technology risk management is under control.
Session 2Monitoring technology risk management from the user's point of view
- Set delivery and reliability indicators for technology risk management the team trusts.
- Run a load test on technology risk management at expected peak plus a margin.
- Collect evidence on the present handling of technology risk management before proposing changes.
- Confirm every release of technology risk management can be rolled back within a defined time.
Technology risk management: build, pipeline and release discipline
2 sessions · 8 pointsSession 1Comparing technology risk management with recognised practice
- Record the technical debt in technology risk management and schedule repayment.
- Restore a backup of technology risk management in a test environment and time it.
- Configure alerting on technology risk management that reflects what users experience.
- Close out actions on technology risk management rather than leaving them open indefinitely.
Session 2The paperwork for technology risk management that is actually needed
- Confirm the support model and escalation path for technology risk management.
- Prepare the response for the most likely failure in technology risk management.
- Assign responsibility for keeping documentation of technology risk management current.
- Benchmark the organisation's technology risk management against comparable operations.
Technology risk management: incident response and severity
2 sessions · 8 pointsSession 1Designing technology risk management around how it will fail
- Inventory third-party dependencies inside technology risk management and their update status.
- Confirm that reporting on technology risk management reaches the people who can act.
- Confirm that contractual obligations around technology risk management are understood.
- Set the review interval for technology risk management and who attends.
Session 2Least privilege in technology risk management without blocking the work
- Test the failover for technology risk management rather than assuming it works.
- Review access rights on technology risk management and remove what is no longer needed.
- Name a single owner for each element of technology risk management.
- Assess the exit route from any cloud or vendor dependency in technology risk management.
Technology risk management: requirements, targets and service levels
2 sessions · 8 pointsSession 1Making releases of technology risk management routine instead of risky
- Apply change control to technology risk management including emergency changes.
- Document the runbook for technology risk management to the level a new engineer could use.
- Identify the single points of failure in technology risk management.
- Identify where judgement in technology risk management is legitimate and where it is not.
Session 2The hard cases in technology risk management and how to reason about them
- Check that technology risk management still works when volumes rise unexpectedly.
- Rank the weaknesses in technology risk management by consequence rather than by ease of fixing.
- Verify six months later that changes to technology risk management have held.
- Arrange the handover of technology risk management 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.