Assess the current state of recurring problem management against a structured set of criteria rather than impressions.
Building Strategies to Manage Recurring Technical Problems
A structured, applied course in recurring problem management — designed to be used the week you return.
📍 Tunis🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Availability targets for recurring problem management are commercial commitments, whatever the engineering team calls them. Most outages involving this aspect of technology and systems delivery are triggered by a change somebody considered routine. They gain the ability to sequence improvements to the practice within technology and systems delivery in an order their organisation can absorb. Cases are chosen to expose the trade-offs in recurring problem management rather than to illustrate ideal conditions. The material serves both public bodies and commercial organisations dealing with this strand of technology and systems delivery. This programme builds this area of technology and systems delivery from first principles, without padding and without omitting what matters. The professional literature on recurring problem management converges on a small set of controls that reliably work. The difficulty is not agreeing that the technology and systems delivery discipline matters — it is deciding what to stop doing to make room for it. The final module sets out how progress on the practice within technology and systems delivery will be evidenced six months later.
Expected Learning Outcomes
Build incident response for recurring problem management with defined severity and escalation.
Secure the software supply chain and dependencies within recurring problem management.
Build the deployment pipeline for recurring problem management so releases are routine rather than events.
Estimate what recurring problem management costs to run properly, and what is lost when it is not.
Design the architecture of recurring problem management around its failure modes, not only its happy path.
Test the organisation's response to recurring problem management under conditions that are less than ideal.
Who Should Attend
Business partners who must understand recurring problem management well enough to challenge it.
Quality and test engineers verifying recurring problem management.
Database administrators managing data within recurring problem management.
Project managers delivering changes to recurring problem management.
Vendor managers overseeing suppliers involved in recurring problem management.
Public sector officials applying recurring problem management within a regulated framework.
Course Modules
Recurring problem management: monitoring, alerting and observability
2 sessions · 8 pointsSession 1Monitoring recurring problem management from the user's point of view
- Set escalation thresholds for recurring problem management that work out of hours.
- Run a load test on recurring problem management at expected peak plus a margin.
- Prepare the response for the most likely failure in recurring problem management.
- Inventory third-party dependencies inside recurring problem management and their update status.
Session 2Moving recurring problem management from approval to execution
- Define acceptance criteria for recurring problem management in advance.
- Test the failover for recurring problem management rather than assuming it works.
- Define incident severity levels for recurring problem management and the response each triggers.
- Review logging on recurring problem management for coverage and retention.
Recurring problem management: documentation, support and handover
2 sessions · 8 pointsSession 1Setting availability and recovery targets for recurring problem management honestly
- Configure alerting on recurring problem management that reflects what users experience.
- Restore a backup of recurring problem management in a test environment and time it.
- Remove steps in recurring problem management that add effort without adding assurance.
- Confirm every release of recurring problem management can be rolled back within a defined time.
Session 2Who answers for recurring problem management, and to whom
- Reduce the variation in how recurring problem management is carried out between teams.
- Identify single points of dependency in recurring problem management and reduce them.
- Confirm data retention and deletion rules applied within recurring problem management.
- Test the procedure for recurring problem management against a realistic scenario.
Recurring problem management: change control and rollback
2 sessions · 8 pointsSession 1Making releases of recurring problem management routine instead of risky
- Measure current load on recurring problem management and project it forward twelve months.
- Set delivery and reliability indicators for recurring problem management the team trusts.
- Confirm that those complying with recurring problem management understand why it exists.
- Record the technical debt in recurring problem management and schedule repayment.
Session 2Dependencies and supply chain risk in recurring problem management
- Build the competence framework that supports recurring problem management.
- Identify the data already collected that bears on recurring problem management.
- Record the rationale for each significant choice made about recurring problem management.
- Check that recurring problem management still works when volumes rise unexpectedly.
Recurring problem management: incident response and severity
2 sessions · 8 pointsSession 1Testing recurring problem management before relying on it
- Review access rights on recurring problem management and remove what is no longer needed.
- Establish who is informed, consulted and accountable in recurring problem management.
- Distinguish symptoms from causes when recurring problem management underperforms.
- State the availability and recovery objectives for recurring problem management as numbers.
Session 2Documenting recurring problem management so someone else can operate it
- Establish what evidence demonstrates recurring problem management is under control.
- Verify six months later that changes to recurring problem management have held.
- Document the runbook for recurring problem management to the level a new engineer could use.
- Assess the exit route from any cloud or vendor dependency in recurring problem management.
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.