Distinguish the parts of technology business continuity that must be standardised from those that require judgement.
Designing Technology Business Continuity Planning Strategies
Develop the judgement and the documentation needed to run technology business continuity properly.
📍 Cairo🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Availability targets for technology business continuity are commercial commitments, whatever the engineering team calls them. Systems supporting this area of technology and systems delivery fail in ways that are obvious afterwards and invisible before. They acquire practical criteria for judging when this strand of technology and systems delivery is working and when it is only appearing to. The version of technology business continuity described in the manual and the version practised on the floor tend to diverge over time. It is appropriate for those preparing to take on wider responsibility for this part of technology and systems delivery. It treats the wider technology and systems delivery agenda as an operating discipline and equips participants to run it as one. Cases are chosen to expose the trade-offs in technology business continuity rather than to illustrate ideal conditions. The most reliable predictor of sound this part of technology and systems delivery is whether anyone reviews it when nothing has gone wrong. The course ends by identifying what the participant will stop doing to make the wider technology and systems delivery agenda sustainable.
Expected Learning Outcomes
Present the case for investment in technology business continuity in terms that a finance function will accept.
Build incident response for technology business continuity with defined severity and escalation.
Assess and manage third-party and cloud dependencies in technology business continuity.
Structure the service desk and support model for technology business continuity.
Diagnose whether a problem in technology business continuity is one of design, resourcing or discipline.
Design backup and recovery for technology business continuity and prove it by restoring.
Who Should Attend
Quality staff verifying that technology business continuity performs as designed.
Coordinators responsible for keeping records and documentation of technology business continuity current.
Project managers delivering changes to technology business continuity.
Network and communications engineers supporting technology business continuity.
Information security specialists protecting technology business continuity.
Database administrators managing data within technology business continuity.
Course Modules
Technology business continuity: capacity, performance and load
2 sessions · 8 pointsSession 1Moving technology business continuity from approval to execution
- Test the failover for technology business continuity rather than assuming it works.
- Record what was learned when technology business continuity did not go as planned.
- Close out actions on technology business continuity rather than leaving them open indefinitely.
- Map the handovers in technology business continuity between functions and secure them.
Session 2Setting availability and recovery targets for technology business continuity honestly
- Confirm every release of technology business continuity can be rolled back within a defined time.
- Agree the smallest change to technology business continuity that would be visibly useful.
- Draft the minimum viable technical standard for technology business continuity.
- Prepare the summary of technology business continuity that senior management will read.
Technology business continuity: change control and rollback
2 sessions · 8 pointsSession 1Least privilege in technology business continuity without blocking the work
- Apply change control to technology business continuity including emergency changes.
- State the availability and recovery objectives for technology business continuity as numbers.
- Remove steps in technology business continuity that add effort without adding assurance.
- Name a single owner for each element of technology business continuity.
Session 2Running an incident on technology business continuity calmly
- Agree what will be standardised in technology business continuity and what will not.
- Document the runbook for technology business continuity to the level a new engineer could use.
- Review access rights on technology business continuity and remove what is no longer needed.
- Define acceptance criteria for technology business continuity in advance.
Technology business continuity: architecture and designing for failure
2 sessions · 8 pointsSession 1The change to technology business continuity that caused the last outage
- Agree the indicators that will show whether technology business continuity is improving.
- Anticipate the objections technology business continuity will raise and prepare the answers.
- Build the internal briefing that explains technology business continuity to those affected.
- Review logging on technology business continuity for coverage and retention.
Session 2Monitoring technology business continuity from the user's point of view
- Identify the single points of failure in technology business continuity.
- Arrange the handover of technology business continuity so capability survives staff changes.
- Establish the boundary of technology business continuity and record what sits outside it.
- Configure alerting on technology business continuity that reflects what users experience.
Technology business continuity: security, identity and least privilege
2 sessions · 8 pointsSession 1Reading the current state of technology business continuity honestly
- Run a load test on technology business continuity at expected peak plus a margin.
- Set delivery and reliability indicators for technology business continuity the team trusts.
- Restore a backup of technology business continuity in a test environment and time it.
- Confirm the support model and escalation path for technology business continuity.
Session 2Getting other functions to support technology business continuity
- Record the technical debt in technology business continuity and schedule repayment.
- Build the competence framework that supports technology business continuity.
- Assess the exit route from any cloud or vendor dependency in technology business continuity.
- Confirm data retention and deletion rules applied within technology business continuity.
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.