Prepare a short, evidence-based briefing on technology landscape simplification for senior management.
Building Strategies to Simplify the Complex Corporate Technology Landscape
Practical training in technology landscape simplification, grounded in real cases and applied to your own operation.
📍 Cairo🗓️ 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 landscape simplification whether or not anyone says so. Availability targets for this aspect of technology and systems delivery are commercial commitments, whatever the engineering team calls them. The programme takes participants through this strand of technology and systems delivery end to end, from framing the problem to closing it out. The course leaves participants able to diagnose weaknesses in technology landscape simplification before they become incidents. A common pattern is strong design of this part of technology and systems delivery paired with weak follow-through. It is designed for mixed groups, so that this area of technology and systems delivery is examined from more than one functional angle. The teaching approach is deliberately practical: participants build a technical standard for technology landscape simplification as they go. Field experience suggests that the barrier to better the technology and systems delivery discipline is rarely technical. Participants leave with a first-ninety-days plan for this area of technology and systems delivery rather than a set of notes.
Expected Learning Outcomes
Test technology landscape simplification under realistic load before it meets real load.
Agree the first three actions on technology landscape simplification that will be taken on returning to work.
Assess and manage third-party and cloud dependencies in technology landscape simplification.
Manage change to technology landscape simplification so every release can be rolled back.
Draw practical lessons from failures in technology landscape simplification without assigning blame that suppresses reporting.
Build the deployment pipeline for technology landscape simplification so releases are routine rather than events.
Who Should Attend
Quality and test engineers verifying technology landscape simplification.
Infrastructure and platform engineers operating technology landscape simplification.
Database administrators managing data within technology landscape simplification.
Solution architects designing technology landscape simplification.
Members of committees that take decisions affecting technology landscape simplification.
Those responsible for briefing external stakeholders on technology landscape simplification.
Course Modules
Technology landscape simplification: capacity, performance and load
2 sessions · 8 pointsSession 1Dependencies and supply chain risk in technology landscape simplification
- Agree the indicators that will show whether technology landscape simplification is improving.
- Confirm that those complying with technology landscape simplification understand why it exists.
- Remove steps in technology landscape simplification that add effort without adding assurance.
- Prepare the summary of technology landscape simplification that senior management will read.
Session 2Where technology landscape simplification typically breaks, and why
- Assess the exit route from any cloud or vendor dependency in technology landscape simplification.
- Set delivery and reliability indicators for technology landscape simplification the team trusts.
- Estimate the resource technology landscape simplification requires to run as designed.
- Review logging on technology landscape simplification for coverage and retention.
Technology landscape simplification: change control and rollback
2 sessions · 8 pointsSession 1Running an incident on technology landscape simplification calmly
- Test the failover for technology landscape simplification rather than assuming it works.
- Agree the smallest change to technology landscape simplification that would be visibly useful.
- Confirm data retention and deletion rules applied within technology landscape simplification.
- Set out how exceptions to technology landscape simplification are requested and approved.
Session 2Setting availability and recovery targets for technology landscape simplification honestly
- Record the technical debt in technology landscape simplification and schedule repayment.
- Review access rights on technology landscape simplification and remove what is no longer needed.
- Name a single owner for each element of technology landscape simplification.
- Collect evidence on the present handling of technology landscape simplification before proposing changes.
Technology landscape simplification: architecture and designing for failure
2 sessions · 8 pointsSession 1Reviewing technology landscape simplification when nothing has gone wrong
- Configure alerting on technology landscape simplification that reflects what users experience.
- Confirm every release of technology landscape simplification can be rolled back within a defined time.
- Restore a backup of technology landscape simplification in a test environment and time it.
- Run a load test on technology landscape simplification at expected peak plus a margin.
Session 2The paperwork for technology landscape simplification that is actually needed
- Confirm the support model and escalation path for technology landscape simplification.
- Rank the weaknesses in technology landscape simplification by consequence rather than by ease of fixing.
- Confirm that reporting on technology landscape simplification reaches the people who can act.
- Measure current load on technology landscape simplification and project it forward twelve months.
Technology landscape simplification: incident response and severity
2 sessions · 8 pointsSession 1Monitoring technology landscape simplification from the user's point of view
- Plan the sequence in which improvements to technology landscape simplification will be introduced.
- Verify six months later that changes to technology landscape simplification have held.
- Apply change control to technology landscape simplification including emergency changes.
- Document the runbook for technology landscape simplification to the level a new engineer could use.
Session 2Documenting technology landscape simplification so someone else can operate it
- Confirm that contractual obligations around technology landscape simplification are understood.
- Agree what will be standardised in technology landscape simplification and what will not.
- Identify the single points of failure in technology landscape simplification.
- Map the handovers in technology landscape simplification between functions and secure them.
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.