Identify the failure points in interactive web interfaces most likely to cause loss, and control them first.
Building Interactive User Interfaces with Modern Web Technologies
Build a working method for interactive web interfaces that stands up to scrutiny and survives daily pressure.
📍 Cairo🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Technical debt in interactive web interfaces is borrowed against future delivery capacity, at compound interest. Most outages involving the technology and systems delivery discipline are triggered by a change somebody considered routine. It concentrates on the parts of this part of technology and systems delivery that determine outcomes and treats the rest proportionately. Participants who influence interactive web interfaces 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 programme builds the judgement to know which parts of the practice within technology and systems delivery to standardise and which to leave flexible. Field experience suggests that the barrier to better interactive web interfaces is rarely technical. Buying a tool rarely fixes this part of technology and systems delivery; the underlying capability has to be built internally first. The course ends by identifying what the participant will stop doing to make the practice within technology and systems delivery sustainable.
Expected Learning Outcomes
Build the deployment pipeline for interactive web interfaces so releases are routine rather than events.
Establish escalation routes for interactive web interfaces that work outside normal hours.
Control technical debt in interactive web interfaces deliberately rather than by neglect.
Assign clear ownership for each element of interactive web interfaces across the functions involved.
Measure delivery and reliability of interactive web interfaces with indicators teams trust.
Define the availability, performance and recovery targets for interactive web interfaces.
Who Should Attend
Network and communications engineers supporting interactive web interfaces.
Solution architects designing interactive web interfaces.
Database administrators managing data within interactive web interfaces.
Information security specialists protecting interactive web interfaces.
Officers preparing reports on interactive web interfaces for boards or oversight committees.
Planning staff whose forecasts and budgets are affected by interactive web interfaces.
Course Modules
Interactive web interfaces: requirements, targets and service levels
2 sessions · 8 pointsSession 1The change to interactive web interfaces that caused the last outage
- Document the runbook for interactive web interfaces to the level a new engineer could use.
- Run a load test on interactive web interfaces at expected peak plus a margin.
- Inventory third-party dependencies inside interactive web interfaces and their update status.
- Identify where judgement in interactive web interfaces is legitimate and where it is not.
Session 2Sizing capacity for interactive web interfaces on measured growth
- Record what was learned when interactive web interfaces did not go as planned.
- Confirm every release of interactive web interfaces can be rolled back within a defined time.
- Set out the decisions in interactive web interfaces that require sign-off and by whom.
- Test the failover for interactive web interfaces rather than assuming it works.
Interactive web interfaces: incident response and severity
2 sessions · 8 pointsSession 1What has to be agreed before work on interactive web interfaces starts
- Identify the single points of failure in interactive web interfaces.
- Anticipate the objections interactive web interfaces will raise and prepare the answers.
- Apply change control to interactive web interfaces including emergency changes.
- Test the procedure for interactive web interfaces against a realistic scenario.
Session 2Moving interactive web interfaces from approval to execution
- Write down the assumptions underpinning the approach to interactive web interfaces.
- Draft the minimum viable technical standard for interactive web interfaces.
- Decide what will be stopped to create capacity for interactive web interfaces.
- Restore a backup of interactive web interfaces in a test environment and time it.
Interactive web interfaces: security, identity and least privilege
2 sessions · 8 pointsSession 1Proving the backup of interactive web interfaces by restoring it
- Confirm the support model and escalation path for interactive web interfaces.
- Close out actions on interactive web interfaces rather than leaving them open indefinitely.
- Configure alerting on interactive web interfaces that reflects what users experience.
- Assess the exit route from any cloud or vendor dependency in interactive web interfaces.
Session 2Documenting interactive web interfaces so someone else can operate it
- Define incident severity levels for interactive web interfaces and the response each triggers.
- Identify single points of dependency in interactive web interfaces and reduce them.
- Establish the boundary of interactive web interfaces and record what sits outside it.
- Map the handovers in interactive web interfaces between functions and secure them.
Interactive web interfaces: documentation, support and handover
2 sessions · 8 pointsSession 1Running an incident on interactive web interfaces calmly
- Measure current load on interactive web interfaces and project it forward twelve months.
- Confirm data retention and deletion rules applied within interactive web interfaces.
- Build the internal briefing that explains interactive web interfaces to those affected.
- Establish who is informed, consulted and accountable in interactive web interfaces.
Session 2Reviewing interactive web interfaces when nothing has gone wrong
- Confirm that those complying with interactive web interfaces understand why it exists.
- State the availability and recovery objectives for interactive web interfaces as numbers.
- Review access rights on interactive web interfaces and remove what is no longer needed.
- Prepare the response for the most likely failure in interactive web interfaces.
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.